> For the complete documentation index, see [llms.txt](https://docs.pancakeswap.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pancakeswap.finance/welcome-to-pancakeswap/about-us/team/become-a-chef/frontend-engineer-contract.md). # Frontend Engineer (Contract) ### General Information * Salary range: Competitive, negotiable * **Duration: 1 - 2 quarters** * Position: Full-time / Part-time * Location: Remote * Time-zone preference: Any ### Your Responsibilities * Design and build an iOS / Android application for PancakeSwap in accordance to our requirements. * Envision and develop features to help grow the application. * Enthusiastically collaborate with a small team to plan projects at the task level. * Collaborate with cross-functional partners on all aspects of product development. ### Skills & Qualifications * 3-5 years of experience in building decentralised applications * Solid experience in Typescript and React JS. * Ability to write structured and clean code. * Experience with Javascript testing tools. * Experience with modern front-end build pipelines and tools. * Experience with defining and delivering scalable frontend architectures. * Some experience with GraphQL. * Experience working with Web3 and a decentralized application frontend. * Ability to work independently and innovate. ### Good to have * Understanding of Solidity and AMMs * Understanding of PancakeSwap products ### How to apply: Email with your resume! --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.pancakeswap.finance/welcome-to-pancakeswap/about-us/team/become-a-chef/frontend-engineer-contract.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.