Roles by discipline
Backend roles with an architecture question attached
Every backend engineer inherits a decision. Somebody chose the queue, drew the service boundary, picked the database, and then left the company. The thing that decides whether this job is interesting is not what they chose. It is whether you would be allowed to change it, how long that would take, and who you would have to convince. A stack list answers none of that.
What we ask before we post one
The questions the ad never answers.
- Who makes the architecture call, and can an engineer reverse one?
- What is the current deploy frequency, measured rather than estimated?
- How much of recent work was new, and how much was keeping the lights on?
- Is there a written technical strategy, and when did it last change?
- How does someone reach staff level here, and who did it most recently?
- Which part of the system does nobody want to touch?
What we will not post
We do not post a senior title where the work is closing tickets someone else has already designed.
For hiring teams
Hiring for this discipline?
We work through the role and hiring criteria with your team as part of embedded recruitment. Talk to Jonathan about what you need to hire.