NHS software developer interview questions and examples
Practise NHS software developer interviews with original questions and fictional answers on requirements, testing, review and technical communication.
Applies to: England, Wales
Prepare a decision account rather than a list of tools
A useful software developer interview answer explains the problem, your own contribution and the evidence behind a decision. Familiar technology names can locate the example, but they do not explain why your approach suited the task. Start with the current person specification and the actual invitation. These original practice questions are not a released employer question bank or a prediction of your assessment.
The historical NHSBSA example required an IT degree and development experience; the Public Health Wales example allowed a degree-or-experience alternative while keeping separate technical and experience essentials. Use the actual current specification to judge your preparation.
Choose several genuine examples rather than forcing every question into one project. A clarified requirement, a useful review and a check that exposed a mistaken assumption may demonstrate different decisions. Keep the scope of each event intact. Do not claim that a practice exercise, a team achievement and an independently delivered live feature are interchangeable kinds of experience.
Question: what interests you about this developer role?
Connect your interest with the advertised contribution. Explain one aspect of development you enjoy and a real piece of preparation that supports it. Then identify what attracts you to this particular setting and level of responsibility. A general enthusiasm for technology leaves the panel to infer which part of the job you understand.
If you are moving between sectors, explain the connection without changing the history of the example. You can describe a relevant decision from another environment while recognising knowledge you still need to develop. Keep an award in progress separate from one achieved, and avoid suggesting that motivation removes an essential requirement.
Question: tell us about clarifying a requirement
In a fictional community-exhibition catalogue exercise, I was responsible for a small entry screen. The brief mentioned arrival dates and display dates, but my first version showed a single field labelled “Date”. I noticed that the example entries could not make its meaning clear. I wrote down the two interpretations and asked a practice partner what they understood from the screen. Their answer showed that my assumption was not shared. I revised the fictional brief to distinguish the two dates and left the remaining display question visible. The result was a clearer requirement for the exercise. I did not claim that I had resolved the needs of a real NHS service.
- All people, data, software and outcomes in this answer are invented.
- The answer identifies an assumption, a purposeful check and a bounded result.
- Replace this story with your own genuine evidence; it is not a script for submission.
For your own answer, identify what made the ambiguity matter. Explain the question you asked and what changed afterwards. If another person made the final decision, say so. A clear account of bringing an issue to the right decision owner can be more informative than claiming that you independently settled every requirement.
Prepare a follow-up about your first approach. You might explain why the assumption seemed reasonable, how you recognised its limit and what you would investigate earlier next time. Reflection works best when it remains connected to the actual event rather than becoming a generic promise to communicate better.
Question: how did you use a test result?
In an invented personal project for a fictional hobby club, I wrote a small feature to filter a list of activity names. One of my checks expected the list to retain its original order, although I had also specified alphabetical display. I first thought the implementation was wrong. I compared the written expectation with the purpose of the check and realised that I had combined two different assumptions. I corrected the test description and discussed the intended ordering with my practice partner before claiming that the exercise was complete. The result was a clearer test purpose and an identified decision about ordering. The exercise did not establish production readiness or prove that every behaviour had been checked.
- The club, feature, checks, partner and result are fictional.
- The candidate examines their own expectation instead of treating a failed check as automatic proof of a particular fault.
- This is recruitment rehearsal, not a testing procedure for a real system.
Question: describe receiving feedback on your work
Select an actual review where you can explain the original choice and the feedback clearly. What did the reviewer need to understand? Which part did you reconsider, and why? Show how you reached the revised position rather than reducing the event to accepting every suggestion or defending every line.
Give a result you actually observed. The reviewer may have understood the reason more clearly or agreed that a specific concern had been addressed. Those are useful outcomes without an invented claim that future defects disappeared. Preserve the reviewer’s contribution and any unresolved question. Follow confidentiality requirements when describing the work.
| Possible follow-up | Useful preparation | Avoid |
|---|---|---|
| Why was that check relevant? | Explain the behaviour or assumption it examined. | Listing a tool without its purpose. |
| What was your contribution? | Identify the code, analysis, explanation or revision you personally made. | Adopting the entire team delivery. |
| What remained uncertain? | Name the actual limit or unanswered requirement. | Calling a small check complete assurance. |
| How did you explain the change? | Describe the audience and the explanation they needed. | Assuming more technical vocabulary always improves clarity. |
Question: explain a technical choice to a different audience
Choose a real occasion when someone needed an explanation in order to make a decision or use your work. State what they needed to know and why. Describe how you selected the relevant detail and checked understanding. Avoid presenting the listener as incapable simply because their responsibility was different from yours.
Practise explaining the same event at two levels of detail. Begin with the purpose and consequence, then add the technical reasoning if requested. Keep both versions accurate. Simplifying an explanation should not hide an important limitation or imply that an unresolved decision has already been approved.
Prepare for the assessment in your invitation
A behavioural example and a practical task may assess different aspects of your preparation. Read the actual instructions, including permitted resources, submission conditions and any stated technology. Do not assume that an interview will contain a coding exercise merely because the role involves development. Equally, do not treat these worked answers as preparation for every possible technical assessment.
Rehearse follow-up questions with a partner who asks what you personally decided and what evidence supports the result. If those points remain unclear, revise the explanation before adding more detail. Keep the answer consistent with your application and with the real extent of your responsibility. Accurate, specific evidence is more useful than a polished story that cannot withstand a natural follow-up.
No. They are original practice prompts and fictional illustrations. The employer determines the actual questions and assessment.
Follow the question and invitation. Explain relevant technical reasoning, but do not disclose private code or supply unrequested confidential material.
Yes, where it is relevant and truthful. Explain the decision, what you learned and the actual outcome without inventing later success.
Use them to examine structure and boundaries. Your assessment evidence must describe your own experience and follow the employer’s rules.
Related free guides
Primary sources and context
Checked 21 October 2026.
Checked 21 October 2026.