What is the software engineer role at Happydance really like?

That last sentence is not a throwaway. Happydance was founded by Bryan Adams, who wrote a book called Sell The Truth. The whole method is simple: tell candidates the truth, including the hard parts, so the right people lean in and the wrong people save themselves six months. This entire site is us practising what the book preaches, on ourselves. So here is the role, told straight.

What would you actually be building?

You would be building the product that powers careers sites for enterprise and mid-market companies: conversational navigation, AI content generation, smart SEO automation, structured data for AI discoverability, bias detection across 80 criteria, analytics dashboards, internal mobility sites and easy-apply overlays. The platform serves clients including General Motors, MGM Resorts, Box, Pinterest, Xero, Criteo and Ingram Micro, and the numbers it produces are the reason they stay: a 25% average increase in annual traffic, up to 50% more pageviews, over 75% more sessions year on year, and up to 25% improvement in conversion rates.

In plain terms, when a nurse in Ohio or a data scientist in Sydney finds a job that changes their life, there is a decent chance your code sat between them and it. Careers software sounds unglamorous until you remember what a job actually is to a person.

What does the work feel like day to day?

Most days are a mix of deep work and collaboration, in a hybrid rhythm of 2 to 3 days together per week and the rest wherever you focus best. You will work in a small cross-functional squad, in two-week sprints, with a code review culture that takes pull requests seriously and quarterly hack days where the roadmap gets out of the way.

We have written the honest version of a full week, meetings and all, at a week in the life of a software engineer here. It includes the boring bits, because your actual week will include them too.

What is the tech stack?

The core stack is TypeScript, React, Node.js and .NET services, running on Azure, provisioned with Terraform, shipped through GitHub Actions. The AI features are built on LLM APIs with structured data pipelines underneath, which is currently the most interesting and the most volatile part of the codebase.

There is technical debt. Every real platform has it, and we would rather show you where ours lives than let you find it in week three. The full picture, including why each choice was made and what you would learn, is in the Happydance tech stack, explained honestly.

Who is this role right for, and who should not apply?

This role suits engineers roughly mid to senior level who want hard problems, care about craft, and want a full life outside work in a city that makes that affordable. It does not suit people who want a huge-company career ladder with a thousand rungs, or who want to coast, or who find shifting ground stressful rather than energising.

Here is the filter, plainly:

• Lean in if you like small squads with real ownership, you find accessibility and enterprise standards a worthy constraint rather than a nuisance, and the AI era feels like the most interesting time to be building.
• Think twice if you need a big-brand name on your CV more than interesting work, you want pure greenfield with zero legacy, or you would resent enterprise clients having exacting opinions about what you ship. They do, and they are paying customers, so their opinions win more often than your elegant abstraction does.

The hard parts are real: multi-tenant complexity at scale, WCAG 2.2 AA accessibility as a hard requirement not an afterthought, and a product moving fast in the AI era, which means the ground shifts under you sometimes. Some people find that thrilling. Some find it exhausting. Only you know which you are.

How do people work together here?

Decisions get made close to the work, in squads, with engineers in the room when scope and architecture are set. Sprints are two weeks, reviews are honest, and hack days each quarter exist so good ideas do not have to queue behind the roadmap forever.

It is not friction-free. Things frustrate people here sometimes, and we have listed them rather than hidden them in how we work, because a culture page that contains no irritations is describing a company that does not exist.

What does it pay, and where can the role go?

Liverpool software engineer salaries average £43,497, which is about 13% below the national average, and we will not pretend otherwise. The honest version of the maths is that housing here averages £221k against £351k across England and Wales, roughly 37% cheaper, so the net position for most engineers is comfortably ahead of London or Manchester equivalents.

The ladder runs from junior around £25,600, through entry level around £41,900, senior around £53,000, principal around £67,400, up to staff around £78,500. How promotion actually works, including realistic timescales, is laid out in career progression from junior to staff, and the full money argument lives on the salary page.

What is the interview process?

The process is deliberately short and transparent: you will know every stage, what we assess at each one, and how long it takes before you commit an hour to us. We have published the whole thing, including the common reasons candidates do not get through and the accessibility adjustments we offer, at the Happydance interview process.

Where can you hear it from actual engineers?

The best evidence is people, so we have gathered stories from engineers across the team: a senior engineer raising a young family in Crosby, a couple who swapped London rent for a semi near Sefton Park, a frontend engineer living the Baltic Triangle life, an international relocator from Spain, and a former teacher who came in through a bootcamp. Start with the engineer stories hub and pick whichever life looks most like yours.

Frequently asked questions about the role

Is Happydance a startup or an established company?

Established but young. Happydance launched in 2022 with deep roots in employer branding, and serves enterprise clients including National Grid, General Motors and Canva. You get startup pace with real revenue and real customers, which cuts both ways: momentum, but also standards.

Do I need AI experience to apply?

No. You need strong engineering fundamentals in some part of our stack and genuine curiosity. The AI features are built on LLM APIs, and most of the team learned that layer on the job. What we cannot teach is caring about the craft.

Is the role fully remote?

No, and we say so upfront. We work hybrid, together 2 to 3 days per week, because the collaboration genuinely benefits from it. If you need fully remote, we are the wrong company, and we would rather you know now.

Can I speak to an engineer before applying?

Yes. Ask at any stage of the process and we will set up an informal call with someone doing the job, no recruiters listening in.

---

If the honest version of this role still sounds like your kind of problem, have a look at the software engineer roles we are hiring for now. And if you want to know what your evenings and weekends would look like before you decide, the people stories are the place to start.