Staff Software Engineer
Staff Software Engineer
Posted 2 days ago
SENIORITY
Lead
About the role
- A lot of Staff roles give you influence by taking you further away from the code. This one doesn’t.
- They want engineers who can make architectural decisions, own difficult problems end-to-end and still build. You’ll work close to the product and business, with enough autonomy that the expectation is to define solutions rather than simply execute against somebody else’s design.
- For the right engineer, that means startup-level ownership without joining at the point where product-market fit and funding are still open questions.
- What you’ll be working on:
- Building core systems and products as the company scales
- Owning architecture and implementation end-to-end
- Solving scalability, reliability and system design problems
- Working directly with product and commercial stakeholders
- Setting technical standards as the engineering organisation grows
- Senior or Staff-level software engineering experience
- Strong production engineering and system design fundamentals
- Evidence of owning complex software from idea through production
- Comfort operating in high-autonomy, fast-moving teams
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
