Take-home challenges for our engineering leadership roles. Your recruiter told you which one is yours. Open that folder and read its readme.
| Role | Folder | Time budget |
|---|---|---|
| CTO / VP of Engineering | cto-vp-engineering/ |
~4 hours |
| Engineering Manager / Senior Manager | engineering-manager/ |
~4 hours |
| Backend Lead | backend-lead/ |
~4 hours |
Do only your own folder. The others are visible because this repo is public, not because we want more from you.
Please do not open a pull request against this repository. A pull request would publish your work where every other candidate can read it, and we do not review submissions here. Send yours through your application instead, as described under Submission.
To get a copy you can work in, use the green Use this template button, or clone this repository and push to one of your own. Prefer either over forking: a fork can be publicly linked back to this repo, and so to your solution.
Each challenge is scoped to about four hours. We would rather read an unfinished submission with clear reasoning than a polished one that ate your weekend. Where a challenge sets a page or word limit, we stop reading at the limit. Editing is part of the exercise.
Allowed. Disclose at the end of your submission what you used them for.
You own every line and every decision you submit. Your first interview digs into your reasoning, and "the AI wrote that" is a failing answer. We filter on ownership, not abstinence.
Every challenge deliberately leaves gaps. Invent reasonable context and state the assumption inline rather than waiting on us. How you frame a missing constraint is part of what we read.
You can either provide a link to an online repository, attach the solution in your application, or whichever method you prefer. We're cool as long as we can view your solution without any pain.
It is important that you minimally attempt every part of your challenge, even if you do not arrive at a complete answer.