Software Engineer interview questions in the UK
Last updated August 2026 · Written by the HappyHire team
Short answer
Software Engineer interviews in the UK typically run through 5 stages, from a recruiter screen to a final interview, and are structured around STAR — Situation, Task, Action, Result. Expect questions such as "Walk me through a system you designed end to end." and "Tell me about a production incident you caused or resolved." The assessment stage is where the role is really decided: a live coding round of 45–60 minutes on data structures and algorithms, or a take-home exercise of a few hours, followed by a system design round for anyone above entry level. Talking continuously while you code is scored — silent correctness frequently loses to narrated near-correctness. The single most common reason qualified candidates are rejected is narrower than most people expect: describing what the team shipped instead of what you personally built. Interviewers cannot level a candidate they cannot locate in their own story.
The questions software engineers actually get asked
These six come up in almost every software engineer process, in the UK and elsewhere. What differs by country is not the question but the delivery — covered further down. The right-hand column is the part most preparation guides leave out: what the interviewer is scoring while you answer.
| Question | What the interviewer is scoring |
|---|---|
| Walk me through a system you designed end to end. | Whether you can hold a whole system in your head — data model, failure modes, what you traded away and why. Candidates who only describe the happy path get levelled down. |
| Tell me about a production incident you caused or resolved. | Ownership without defensiveness. The strongest version names the mistake plainly, describes the fix, and ends with the guardrail you added so it could not recur. |
| How do you decide when a piece of code needs a test? | Judgement rather than dogma. 'Everything gets tested' and 'we move too fast for tests' are both weak; the interviewer wants your actual risk calculus. |
| Describe a time you disagreed with a technical decision. | Whether you can dissent and then commit. The ending matters more than the argument — what happened after the decision went against you. |
| How would you scale this feature to a hundred times the traffic? | That you ask about the bottleneck before answering. Jumping straight to caching or sharding without establishing what breaks first is the single most common miss. |
| What have you learned recently, and how? | Genuine curiosity and a real mechanism. Naming a specific thing you built badly, then rebuilt, beats naming a course you watched. |
The mistake that costs software engineers the most offers: Describing what the team shipped instead of what you personally built. Interviewers cannot level a candidate they cannot locate in their own story.
How a British interview process is structured
Competency-based, and more formal than the US but less so than much of Europe. Expect to be asked for specific past examples rather than hypotheticals, and expect the interviewer to be visibly working through a scoring grid.
A typical software engineer process in the UK runs through these stages:
- Online application or CV screen
- Recruiter phone screen, 20–30 minutes, covering motivation, salary expectation and right to work
- Competency interview against the job's listed criteria, often with a scoring panel
- Technical exercise, presentation or case study for most professional roles
- Final interview with the hiring manager or a director
The assessment stage for this role specifically: A live coding round of 45–60 minutes on data structures and algorithms, or a take-home exercise of a few hours, followed by a system design round for anyone above entry level. Talking continuously while you code is scored — silent correctness frequently loses to narrated near-correctness.
How to structure your answers in the UK
STAR — Situation, Task, Action, Result. UK panels score against pre-written criteria, so an answer that never reaches a concrete Result loses marks even if the story is good. Say 'I' rather than 'we': British interviewers are listening for your specific contribution, and collective phrasing reads as hiding.
The delivery norms below are where internationally experienced candidates lose interviews they were qualified for — not on the content of the answer, but on how it lands in the UK.
- Understatement is the default register. 'I led the project and it went well' lands better than 'I was instrumental in a transformative success' — the second reads as inflated, and British interviewers discount inflated claims rather than challenging them.
- That said, understatement is not self-erasure. The most common failure for candidates from consensus-first cultures is describing team achievements without ever saying what they personally did.
- Small talk opens the interview and is not scored, but skipping it entirely reads as cold.
- Questions at the end are expected and are informally scored. Having none suggests you are not evaluating them back.
Work authorisation, and when it comes up
Every UK application form asks two questions: do you have the right to work in the UK, and will you now or in future require sponsorship. Answer both honestly and early. Many employers hold a sponsor licence but do not advertise it; the Home Office publishes the full register of licensed sponsors, and checking a company against it before applying saves weeks.
| Route | What it means for you |
|---|---|
| Skilled Worker visa | The main employer-sponsored route. Requires a job offer from an employer holding a sponsor licence, at or above the going rate for the occupation code. |
| Graduate Route | For those who completed an eligible UK degree — unsponsored work rights for a fixed period after graduation. Employers like it because it costs them nothing. |
| Global Talent visa | For endorsed leaders and potential leaders in academia, research, arts and digital technology. No job offer required. |
| High Potential Individual visa | For recent graduates of qualifying overseas universities. Unsponsored, fixed term. |
Rules and thresholds change regularly, so check the current position at gov.uk/browse/visas-immigration/work-visas rather than relying on any guide, including this one.
Getting to the interview in the first place
In the UK the document is always called a CV. Sending something labelled 'Resume' immediately reads as a copy-paste from a US application, and in academia the word CV additionally implies a longer publications-led document — context tells you which is meant. Two pages. One page is acceptable early-career; three is read as an inability to prioritise.
Applicant tracking systems screen on vocabulary before a human reads anything. For software engineer roles in the UK, mirror the wording of the advert and make sure these terms appear naturally in your experience section where they are true of you:
- software engineer · backend · frontend · full stack · Python · Java · JavaScript · TypeScript · React · Node.js · SQL · REST API · microservices · AWS · Docker · Kubernetes · CI/CD · unit testing · Git · Agile
Beyond the CV, the evidence that moves a software engineer application forward is specific: A GitHub profile with at least one repository that has a real README, or a deployed project with a URL. For engineers whose best work sits behind an employer's firewall, a written architecture summary works as a substitute.
One detail that quietly costs applications: use British spelling — organise, analyse, programme, centre, specialised.
The salary conversation
Salary is quoted as an annual gross figure in pounds. Adverts increasingly show a band, but a recruiter will still ask your expectation on the first call. Give a researched range rather than a single number, and never quote your current overseas salary as an anchor — cost bases differ too much for it to help you.
References are taken after an offer, not before, and are usually confirmation of dates and role rather than a character judgement. Notice periods are long by international standards — one month is typical, three months for senior roles — and employers plan around them.
Frequently asked questions
How many interview rounds should a software engineer expect in the UK?
5 stages is typical: online application or cv screen; then recruiter phone screen, 20–30 minutes, covering motivation, salary expectation and right to work; then competency interview against the job's listed criteria, often with a scoring panel; then technical exercise, presentation or case study for most professional roles; then final interview with the hiring manager or a director. A live coding round of 45–60 minutes on data structures and algorithms, or a take-home exercise of a few hours, followed by a system design round for anyone above entry level. Talking continuously while you code is scored — silent correctness frequently loses to narrated near-correctness.
What is the biggest difference between interviewing in the UK and interviewing elsewhere?
Understatement is the default register. 'I led the project and it went well' lands better than 'I was instrumental in a transformative success' — the second reads as inflated, and British interviewers discount inflated claims rather than challenging them. STAR — Situation, Task, Action, Result. UK panels score against pre-written criteria, so an answer that never reaches a concrete Result loses marks even if the story is good. Say 'I' rather than 'we': British interviewers are listening for your specific contribution, and collective phrasing reads as hiding.
Will employers in the UK sponsor a software engineer?
Every UK application form asks two questions: do you have the right to work in the UK, and will you now or in future require sponsorship. Answer both honestly and early. Many employers hold a sponsor licence but do not advertise it; the Home Office publishes the full register of licensed sponsors, and checking a company against it before applying saves weeks. The routes worth knowing by name are Skilled Worker visa, Graduate Route, Global Talent visa, High Potential Individual visa. Check the current requirements at gov.uk/browse/visas-immigration/work-visas.
What should I ask at the end of a software engineer interview in the UK?
Ask something only this employer can answer — how the team decides priorities, what happened to the last person in the role, what would make the first six months a success. Questions you could have asked any company signal that you are running a process rather than pursuing this job. Having no questions at all is informally scored against you.
How do I talk about salary as a software engineer in the UK?
Salary is quoted as an annual gross figure in pounds. Adverts increasingly show a band, but a recruiter will still ask your expectation on the first call. Give a researched range rather than a single number, and never quote your current overseas salary as an anchor — cost bases differ too much for it to help you.