What is the software engineer career path at Happydance?

Most careers pages describe progression in fog: "opportunities to grow", ladders with no numbers, promotions that happen by mysterious consensus. That fog always benefits the employer, never the candidate. So here is the actual ladder, the actual money, and the actual mechanism, including the parts that are slower or harder than you might hope.

What are the levels and what does each one mean?

Five levels, each defined by the scope you reliably carry, not by years served:

• Junior engineer, around £25,600. You ship well-defined tickets with support, you are learning the codebase and the craft, and your main job is trajectory. Most joiners at this level come through the graduate route, including career changers from bootcamps.
• Engineer, around £41,900. You own features end to end within your squad, your pull requests need guidance rather than rescue, and you review others' code usefully.
• Senior engineer, around £53,000. You own problems, not just features. You lead work across a sprint or two, you make sound technical decisions without escalating, and squadmates get better because you are there.
• Principal engineer, around £67,400. Your scope crosses squads. You shape architecture, you are the person hard problems route to, and your written proposals move the platform.
• Staff engineer, around £78,500. You influence the technical direction of the whole company. Few people hold this level, and that is honest scarcity, not gatekeeping: the scope has to exist before the title can.

These figures track Indeed's Liverpool benchmarks, and yes, Liverpool salaries average about 13% below the national figure. We would rather state that than hide it, because the other half of the equation is that an average house here costs £221k against £351k nationally. The full argument, with the London comparison worked through, is on the salary page.

How does promotion actually work?

Promotion here recognises scope you are already carrying rather than promising scope you might grow into. Twice a year, you and your lead review your work against the written expectations for the next level, using real evidence: the features you led, the reviews you gave, the proposals you wrote, the incidents you handled. When the evidence says you have been operating at the next level for a sustained stretch, usually two consecutive quarters, the case goes forward.

The case is reviewed by a small panel of senior engineers plus your lead, not decided by one person's mood, and the outcome comes with written reasons either way. A yes means the title and the pay move together, immediately, not at some future review. A no means specific, actionable gaps, in writing, and a lead whose job includes helping you close them.

What this system deliberately is not: a queue. Time served earns you nothing by itself, and there is no annual promotion round where a fixed number of slots get shared out. Both of those cut two ways, and we will say so plainly in the next section.

How long does each step really take?

Honest ranges, from what has actually happened rather than what a slide would promise:

• Junior to engineer: one to two years. Career changers sometimes take the longer end while they close fundamentals gaps, and Marcus's story is a truthful account of doing exactly that.
• Engineer to senior: two to three years. This is the step where most growth happens and where impatience bites hardest. The gap is rarely coding skill; it is judgement, and judgement takes reps.
• Senior to principal: no fixed timescale, typically three years or more. This step depends on cross-squad scope existing and on you being the person who fills it. In a company our size, that opportunity is real but not annual.
• Principal to staff: rare and unscheduled. The honest version is that staff-level scope opens up when the company's growth creates it, not when an individual is ready for it.

If your plan is a title bump every eighteen months regardless of scope, a large consultancy will serve that plan better than we will, and it is kinder to say so here than to let you discover it at your second review.

What does progression look like beyond titles?

Between promotions, pay is reviewed annually against the Liverpool market so the ladder does not drift beneath you. Growth in scope shows up continuously rather than in leaps: leading your first cross-squad piece of work, running an incident review, mentoring the new junior, owning the technical relationship with an enterprise client's team, presenting a proposal that changes how the squads work.

There is also a deliberate choice here that suits some people and not others: this is a builder's ladder, not a manager's escape hatch. Moving up does not mean leaving the code. Engineers who want to manage people can and do have that conversation, and it is treated as a different path, not a promotion, because turning your best engineers into reluctant managers is how companies quietly break both jobs.

Who does this path suit, and who will it frustrate?

It suits engineers who want their growth measured in real scope, who like evidence more than politics, and who would rather be paid fairly in a city where £53,000 buys a genuinely good life than chase London titles and hand the difference to a landlord. It will frustrate people who want rapid title inflation, who need a ten-rung ladder with a step every year, or who measure progress only against London gross salaries without doing the cost of living maths.

That is not a judgement either way. It is a filter, offered in good faith, because the whole philosophy of this company is that the truth up front saves everyone the expensive version later.

Frequently asked questions about progression

Do I have to wait for a review cycle to be promoted?

Cases are assessed twice a year, but the evidence gathers continuously, and pay moves the moment a promotion is confirmed. What does not happen is spot promotions on the strength of a single good month.

Can I join at senior or principal level directly?

Yes. We hire into the level your demonstrated scope supports, assessed through the interview process, not the title your last employer printed.

What happens if my promotion case is declined?

You get the reasons in writing, specific gaps rather than vague vibes, and a plan with your lead to close them. Several current seniors had a declined case first, and the system is designed so that stings briefly and helps permanently.

Is there a salary band cap at each level?

Each level has a band around the benchmarks above, refreshed annually against Liverpool market data. Bands overlap at the edges, so strong performance late in a level is rewarded without needing the title to move first.

---

If you would rather climb a ladder with the rungs labelled and the numbers printed on, the open engineering roles tell you which rung you would start on. And for what the money genuinely buys in this city, the salary and cost of living page does the sums.