> For the complete documentation index, see [llms.txt](https://openup.gitbook.io/handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://openup.gitbook.io/handbook/how-we-work/tool-development/coding-roles.md). # Coding Roles ## Lead developer * Lead developer role * Recruitment - * Contracting/outsourcing intermediate and senior developers * Oversight * Long-term sustainability of the tech ## **Front-end developer** * Technical design of front-end implementation (particularly React components) including interfaces, code structure and data structures. * Unblocks and helps other developers as needed * Implements features when there are resource constraints ## **Back-end developer** * Ensuring data is sufficiently understood, structured appropriately, and made available on the site as agreed in sprint planning * Ensures that a platform is built that supports user needs from a software development perspective * It is sustainable - suitably qualified software developers can develop the site further without unnecessary challenges and technical debt * Translate user stories into back-end requirements, tasks, work packets for back-end developers to implement --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://openup.gitbook.io/handbook/how-we-work/tool-development/coding-roles.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.