> 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/solidity-engineer.md).

# Senior Solidity Engineer

### **General Information**

* **Salary range:** Competitive, negotiable
* **Position:** Full-time
* **Location:** Remote
* **Time-zone preference:** Any

### Your Responsibilities

* Architect, implement, and test smart contracts in **Solidity** across EVM-compatible chains.
* Scope, design, and deliver complex systems end-to-end, from idea to deployment.
* Collaborate with cross functional partners on all aspects of product development.
* Conduct code reviews and enforce best practices for security, efficiency, and maintainability.
* Continuously evaluate and improve gas optimization, security design patterns, and upgradeability.
* Proactively identify areas for improvement and innovation within PancakeSwap’s protocol architecture.

### Skills & Qualifications

* **5+ years** of software engineering experience, with **2+ years** focused on Solidity smart contracts.
* Deep understanding of **Solidity design patterns**, gas optimization, and contract upgradeability.
* Hands-on experience with **Hardhat** and **Foundry** (understands the trade-offs and tooling ecosystems).
* Strong understanding of **EVM internals**, **DeFi protocols**, and **on-chain architecture**.
* Excellent analytical, debugging, and problem-solving skills.
* Comfortable working autonomously in a fast-paced, globally distributed team.

### How to apply:

Email <hiring@pancakeswap.com> 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/solidity-engineer.md?ask=<question>&goal=<user_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.
