Senior Software Engineer, Liverpool: £53,000 to £65,000

This is a role for someone who has already shipped serious production software and now wants their judgement, not just their code, to shape a product. Here is the whole picture.

What will you actually do as a senior software engineer here?

You will lead one workstream inside a cross-functional squad. That means owning a slice of the Happydance platform end to end: the technical direction, the architectural decisions, the delivery rhythm, and the quality bar for everything that ships from it. Day to day that looks like:

• Designing and building services and features across TypeScript, React, Node.js and .NET on Azure, then owning them in production.
• Making the calls on architecture and trade-offs for your workstream, and writing them down so others can follow your reasoning.
• Mentoring mid-level and graduate engineers through code review, pairing and honest conversations about their growth. This is a core expectation, not a side quest.
• Representing engineering in squad planning, pushing back on product scope when the technical cost is being underestimated, and saying so clearly.
• Raising the bar on the things enterprise clients hold us to: performance, security, multi-tenancy discipline and accessibility to WCAG 2.2 AA.

From day one we will expect you to form views and voice them. By the end of month one you should be steering your workstream's technical decisions. By month three the squad should be measurably better because you are in it.

What will you work on?

Real product, real scale. The Happydance platform powers careers sites for clients including National Grid, Canva, Uber, General Motors and Pinterest. Depending on your workstream you might lead the build of conversational navigation, AI content generation pipelines on LLM APIs, smart SEO automation, bias detection against 80 criteria, analytics dashboards or internal mobility sites. The platform delivers results clients can measure, including a 25% average increase in annual traffic and up to 25% conversion improvements, and senior engineers are directly accountable for keeping that true as the product grows. The full tech stack has its own page.

What are the honest hard parts of this senior role?

Every job here publishes its hard parts, and the senior ones are specific.

You carry ambiguity without a net. On plenty of decisions, you are the most senior technical voice in the room. There is no architect upstairs to escalate to. Some people find that energising. Others find it quietly exhausting, and it is worth knowing which you are.

Enterprise clients are exacting. When General Motors or National Grid finds a defect, the conversation is direct and the fix is urgent. "Nearly right" does not survive contact with our client base.

Multi-tenancy complicates everything. Your code runs across hundreds of client configurations you did not design for. Changes that look safe locally can behave differently at tenant twelve. Seniors are expected to think in that dimension by default.

The ground shifts. We are building AI features on a landscape that changes quarterly. Work you architected six months ago may need rethinking. If you need your decisions to stay settled to feel good about them, this will chafe.

Mentoring costs real time. Roughly a day a week of your capacity goes to other people's growth. Your personal output will look smaller than a pure individual contributor's, and we consider that the job working as designed.

Who is this senior job not for?

• Engineers who want to architect from a distance without shipping code. Seniors here commit to main every week.
• People who measure seniority by having the final word. The squad model means designers and product managers will challenge you, and being right quietly matters more than winning loudly.
• Anyone who finds mentoring a distraction from the real work. Here it is the real work.
• Specialists who want to sit in one narrow layer permanently. Workstream leadership means going where the problem is, across the stack.

What does progression look like beyond senior?

Liverpool market data puts principal engineers at around £67,400 and staff engineers near £78,500, and our career progression page maps how the path works here, including the honest bit about how many principal seats a company our size can sustain. Nobody will dangle a title to keep you.

How do you apply for this senior software engineer job in Liverpool?

Apply through this page with a CV and a short note about a technical decision you made that mattered, what you weighed, and what you would do differently. No cover letter theatre. The process is a conversation about your experience, a practical exercise drawn from our actual codebase problems, and a session with the squad you would lead within. Every stage is described on the interview process page, and we reply to every applicant, including the noes.

Frequently asked questions

If you are still reading, that is a signal

Seniors who thrive here are the ones who read the hard parts and felt interested rather than warned off. Compare this role against the other open engineering jobs if you are unsure of level, or check the progression map to see where it leads. Then apply when you are ready, not before.