Software engineering career paths branch into at least five distinct routes once you pass the senior grade: specialist, architect, staff-plus individual contributor, engineering manager and founder. Each one rewards a different mix of skills, and the day-to-day work differs far more than the job titles suggest. Most engineers I speak to pick between them based on the label and the pay band. That's a poor basis, because the working week is what you'll live with.
So this is what each week looks like, in rough order.
The specialist: deep in one corner
A specialist might be a performance engineer, a security engineer, a database or data-platform engineer, or a machine learning engineer. The week is mostly hands-on. Monday could be profiling a slow service with a tracing tool such as OpenTelemetry-backed dashboards, Tuesday reading a query plan, Wednesday arguing in a pull request about a schema change.
The reason this route pays well is scarcity. A team can usually find three competent generalists faster than it can find one person who truly understands, say, Postgres internals or Kubernetes networking. In the UK, senior specialists in demand areas commonly sit in the £80,000 to £110,000 range outside London, and above that in the capital, though those are my observations of the market, not survey data.
The pressure is narrower. You're the person called when production is on fire in your area, which means on-call rotations and the occasional bad weekend.
Beyond Tick Boxes: Diversity Recruitment Strategies That Actually Transform UK Workplaces
Master the Virtual Hot Seat: 7 Video Interview Techniques Recruiters Don't Tell You
AI Governance Careers Surge in 2026: Why This Role Will Define the Next Decade
The architect: decisions on paper
Architects spend far less time in the editor than people assume. A typical week is writing and reviewing design documents, sitting in architecture review meetings, and sketching systems in tools like Miro or Lucidchart. Many teams use Architecture Decision Records (ADRs), short documents that capture what was chosen and why, so the reasoning survives after the author leaves.
The work looks like this. A new request lands, perhaps a product team wanting real-time notifications. The architect maps what already exists, writes up two or three options with trade-offs, takes them to a review, and then answers questions for months while teams build it. The skill that matters most is writing. Not code. Clear prose that a tired engineer can follow at four on a Friday.
It's a route with a risk I've watched play out: architects who stop coding lose credibility with the people they're advising. The good ones keep a hand in, even if only reviewing pull requests.
Staff-plus: the individual contributor with a wide remit
Staff, principal and distinguished engineer titles sit on a parallel ladder to management at most scaling companies. The role is unusual because nobody reports to you, yet you're expected to move whole teams. Your week is split between hard technical problems that cross team boundaries, mentoring, and what some engineers call glue work: unblocking others, writing the RFC that settles a long argument, chasing alignment between three squads.
Staff engineer versus engineering manager is the comparison candidates ask about most. The honest difference is what you spend your influence on. A staff engineer earns influence through technical judgement and spends it on direction. A manager earns it through trust and spends it on people: one-to-ones, hiring loops, performance reviews, compensation conversations, team health.
Pay is broadly comparable at the same level, often £100,000 to £140,000 base in the UK at scaling companies, more in London and at big employers. Don't assume management pays more. It frequently doesn't.
The engineering manager: you're now building the team
The manager's week is calendar-heavy. Weekly one-to-ones, sprint planning in Jira or Linear, stakeholder syncs with product, interview panels, and a surprising amount of time spent on hiring and headcount planning. Code becomes occasional or disappears.
What do you actually produce? Outcomes through other people. That's a different craft, and plenty of excellent engineers find they dislike it. I've seen good ones go into management because it was the only visible route to promotion, then quietly return to individual contributor work a year later. There's no shame in that, and the better companies make the swing back easy.
If you want to test it first, ask to run a project, lead a hiring panel or mentor a graduate before committing.
The founder route
Founding is the outlier. The work is less engineering than selling, hiring, fundraising and fixing whatever broke overnight. Technical founders in early teams still write code, but the share shrinks quickly. Pay is the least predictable of the five: often low salary, equity that may be worth nothing.
The skills that carry over are product sense and tolerance for ambiguity. What doesn't carry over is the comfort of a clear ticket.
How to choose
Pick by the work you'd do when nobody's watching. If you'd rather debug than attend a meeting, specialist or staff. If you like diagrams and written arguments, architect. If you get energy from other people's progress, management. If you can't stop yourself starting things, founder.
The routes in are mostly internal. Ask your manager for a scoped design doc, an on-call lead role, or a cross-team project. Look at how a prospective employer structures its ladder: browse engineering vacancies on OHUB and check whether roles list staff and principal grades alongside management ones, because that tells you whether the individual contributor track is real. For pay context, the ONS earnings data gives wider UK trends, and OHUB's insights cover how engineering salaries are moving.
And if you're unsure, ask the people two grades above you what their Tuesday looks like. It's the quickest research you'll do.
