As a non-exhaustive list of desirable traits, the ideal candidate:
had demonstrable full-stack technical skills in frontend as well as web3 backend and infrastructure, ideally via open-source code, or strong referrals if failing that.
has a good conceptual understanding of the architecture of EVM nodes, as well as the architecture of L2 rollups (in particular optimistic rollups), and understands EVM transaction lifecycles, including issues around transaction inclusion, nonce management, gas estimation, etc.
knows the best practices around building, hosting & securing traditional cloud/server software.
is able to read & write Javascript, Typescript, as well as at least one low-level language (Go & Rust preferred). Must be willing to pick up new languages if we decide to use them.
is well-read and knowledgeable in new blockchain infra-side technology like account abstraction, gas sponsorship, MPC wallets, …
likes reviewing code and strive for continuous improvement of our codebase and engineering practices. This will be one of the biggest parts of the job on the technical side, so make sure you're up for it.
Leadership Skills
The ideal candidate:
has experience leading technical teams as a tech lead or engineering manager, preferably in web3.
is able to manage the complexity (and the scheduling issues) of a team distributed around the world.
has good emotional intelligence, is able to understand the concerns and aspirations of engineers, and help resolve problems and conflicts when they arise.
is able to help engineers thrive by soliciting, understanding and relaying their feedback, as well as providing them with feedback of their own and mentoring when appropriate.
has great organizational and writing skills, is able to keep track of the work of the engineers and how these fit in with our roadmap. We endeavour to create a culture of clarity where things are systematically written down and presented in such a way that both engineers and leadership can easily understand what we are doing and why.
can direct collegial discussions between the engineers regarding our design documents and timelines.
understands the value of a good design document and making sure we build the right thing instead of just starting to write code. You will be responsible to direct conversations around these documents, and to make sure we adhere to them or amend them whenever necessary.