The Software Engineering career path

A ladder that forks, a level that everyone stalls at, and pay that is unusually legible.

By Surojit Chakraverti — ex-Citi and Rothschild M&A, now a hedge fund CIO

Software engineering has the most transparent levelling in any of these careers. Firms publish their ladders, the expectations at each rung are written down, and pay bands are close to public. Knowing where you stand is not the hard part.

What the ladders share is a fork. At around the senior level the path splits into management and a technical track, and the two are genuinely different jobs rather than one being a demotion.

The ladder

What changes at each level, rather than what the title is.

01
Junior or L3
Years 0 to 2
Delivering well-specified work reliably. Somebody else decides what to build and roughly how, and the measure is whether your part lands without needing rescue.
02
Mid-level or L4
Years 2 to 5
Owning a feature end to end, including the parts nobody specified. The step is ambiguity: you are expected to notice what was left out rather than to ask.
03
Senior or L5
Years 5 to 9
The level most careers settle at, and most firms are explicit that it is a fine place to stop. You own a system, you are trusted with the design, and you make other engineers more effective.
04
Staff, or engineering manager
Year 9 onward
The fork. Staff engineers take on problems that span teams and are measured on leverage rather than output. Managers take on people, and stop writing much code. Moving between the two later is common and not held against you.

The hours

Forty to fifty in a normal week at most firms, which is the lowest in this set by a wide margin. On-call rotations and launches are the exceptions, and both are usually bounded.

The variance is between employers rather than between levels. An early-stage startup and a large platform pay differently and ask for different weeks, and the difference is visible before you join.

What it pays, by level

Base and bonus at every rung, aggregated from published surveys rather than from anecdote.

Software Engineering compensation, level by level

Where people go next

A different company at a higher level
The most reliable pay increase in the industry, and the reason internal promotion cycles feel slow by comparison.
Quant development
Trading firms pay well above platform rates for systems engineers, and hire from exactly this pool.
Founding or early-stage
Equity in place of cash, and a job that is much broader than the title suggests.
Management
Not an exit so much as a branch, and one that is easier to take at a company that already knows you.

Open software engineering roles now

Every tracked programme, updated daily.

Common questions

What is the difference between staff engineer and engineering manager?

Both are senior and neither outranks the other at most firms. A staff engineer is measured on technical leverage across teams, a manager on the output and growth of the people they lead. The mistake is treating management as the only way up.

Do you need a computer science degree?

No, and the industry is unusually open about it. What the interview tests is data structures, systems design and whether you can write working code under observation, and none of that is gated on the degree.

Is it worth joining finance as an engineer?

Trading firms and banks pay above most technology companies for equivalent seats, and the work is narrower. It suits people who like latency and correctness more than product breadth.

Deciding is one thing. Getting in is another.

This page is the map. The prep track is the route: what the interviews test, what firms look for, and the questions you will actually be asked.

Software Engineering interview prep Book a diagnostic

Guides for this path

Software Engineering Interviews at Trading Firms and Banks