Developer
30 questions
architecture, debugging, delivery, and collaboration
Interview Question of the Day
Practice daily. One question, a worked answer, the STAR structure behind it, and the mistakes that sink it.
Write your answer first
The worked answer and the STAR breakdown stay hidden until you have had a go. Reading a model answer before attempting one is how you end up recognising it in the room instead of recalling it.
Kept in this browser only. Never uploaded.
Write your own answer above to unlock the worked answer. It is worth two minutes — the gap between what you meant and what you actually said is the thing this page is for.
Quote the feedback close to how it was actually said. Softening it into something flattering defeats the question.
Then show the specific behaviour change and how you know it worked.
The STAR breakdown unlocks with the worked answer, once you have written your own.
Situation: My lead told me my code reviews were slowing the team down.
Task: Take it seriously without over-correcting into rubber-stamping.
Action: I split comments into blocking and non-blocking, and stopped raising style points the linter could catch.
Result: Review turnaround dropped from two days to under one, with no rise in defects.
Choosing feedback that is secretly a compliment.
Describing your reaction rather than your change.
Suggesting the feedback was unfair.
Say it in the giver's words, not your rewrite.
Name the concrete behaviour you changed.
Give a way you measured the improvement.
Similar questions
How do you respond to criticism?
What would your last manager say you should improve?
Tell me about a time you changed how you work.
Tell me about a time you had to balance speed, quality, and scope.
Describe a time you worked on an ambiguous problem.
Tell me about yourself.
What is your biggest weakness?
Why do you want this role?
Why are you leaving your current job?
Tell me about a difficult stakeholder you had to work with.
Tell me about a time you missed a deadline.
Tell me about a time you disagreed with your manager.
Tell me about a project that failed.
Tell me about a time you gave someone difficult feedback.
How do you prioritise when everything is urgent?
Tell me about a time you had to learn something quickly.
Tell me about a process you improved.
Tell me about a decision you made using data.
Tell me about a time you influenced without authority.
How do you handle scope creep?
Tell me about delivering bad news to a stakeholder.
What is your proudest professional achievement?
Where do you see yourself in five years?
Can you explain the gap in your resume?
Tell me about a time you worked under significant pressure.
Tell me about a time another team blocked your work.
Tell me about someone you mentored.
Tell me about something repetitive you automated.
How do you handle competing instructions from two managers?
Tell me about a time you shipped something you were not happy with.
How do you get up to speed in an unfamiliar business domain?
What questions do you have for us?
Practice more
240 questions across 8 role tracks, the same bank ReachRole uses for AI practice.
Designer
30 questions
user research, interaction decisions, craft, and stakeholder alignment
Marketing Expert
30 questions
campaign strategy, channels, positioning, and measurement
Project Manager
30 questions
planning, risks, dependencies, teams, and delivery cadence
Product Manager
30 questions
discovery, prioritization, metrics, roadmap, and tradeoffs
Management Consultant
30 questions
structured thinking, analysis, recommendations, and executive communication
Sales Expert
30 questions
pipeline discipline, discovery, objection handling, and closing
Data / AI Expert
30 questions
modeling, data quality, experimentation, deployment, and business impact
Want AI feedback on your own answer?
Practise with the AI interviewer and get specific feedback instead of a model answer to memorise.
The full guide to interview question of the day
How to use everything above on a real application.
Why this question matters
This question tests judgment under pressure. Hiring teams want to know whether you can make tradeoffs without becoming defensive, whether you can explain risk in language stakeholders understand, and whether you can protect quality while still respecting urgency.
A strong answer names the competing constraints and shows how you created options. A weak answer treats the situation as a simple conflict where one side was right and the other was wrong. Real work is usually messier, so the best answers show maturity, communication, and practical decision-making.
How to build your own answer
Pick an example where the pressure was real but manageable. Write one sentence for the situation, one for the task, three for the actions you took, and one for the result. If the result did not have a clean metric, use a concrete operational outcome: fewer defects, faster sign-off, a clearer launch plan, or a stakeholder decision.
Avoid making yourself the only competent person in the story. Interviewers notice when an answer depends on everyone else being unreasonable. Show that you listened, clarified goals, and made the decision easier for the group.
- Use a real constraint.
- Describe your communication.
- Explain the tradeoff.
- Close with the result and lesson.
How ReachRole can help you practice
ReachRole turns practice into a repeatable workflow. Save your target role, generate role-specific questions, draft STAR answers, and compare your answer against common mistakes. The point is not to sound scripted. The point is to enter the interview with examples ready enough that you can listen, adapt, and answer calmly.
How to practice without sounding scripted
Good interview preparation does not mean memorizing paragraphs. It means preparing the raw material: the situation, the constraint, the decision you made, the result, and the lesson. Write those points in short notes, then practice saying the answer aloud in different ways. This keeps the answer natural while protecting you from rambling when the interview pressure rises.
For behavioral questions, prepare a small story bank. You need examples for conflict, ambiguity, leadership, failure, learning, stakeholder management, and measurable impact. One strong project can often answer several question types if you frame it correctly. The goal is to recognize the question behind the question and choose the example that shows the best judgment.
How to improve your answer after each practice round
Record what felt unclear. Did you spend too long setting context? Did you forget the result? Did you describe the team's work but not your own contribution? Each practice round should produce one edit. Tighten the opening, replace vague verbs, add the decision criteria, or clarify the business impact. Small improvements compound quickly when you practice daily.
ReachRole can help you keep this process organized by saving role-specific questions and turning rough answers into clearer STAR drafts. Use AI feedback to find gaps, but keep your examples personal. Interviewers are not evaluating whether you can produce a perfect script; they are evaluating whether your experience, judgment, and communication match the role.
FAQ
Questions job seekers ask before using this resource
How long should my interview answer be?
Most behavioral answers should take one to two minutes. Use STAR to stay focused and leave room for follow-up questions.
Should I memorize the sample answer?
No. Use it as structure. Your answer should use your own project, constraints, and outcome.
What if I do not have a workplace example?
Use a project, internship, volunteer role, or academic team example. The interviewer is listening for judgment and communication.
Improve your next application
Start