picked.
Log inPost a role
picked.ai/hire/software-engineer/interview-questions
30 software engineer
interview questions that actually work.
Pulled from the Neuroworx item bank: nine years of calibration against twelve-month performance outcomes on 14,083 software engineers. Sorted by stage (screen, assessment, on-site) and level (IC1 to IC5). Each question comes with what to listen for, what to ignore, and the failure mode it is designed to catch.
30
questions
4
stages
5
levels
14k
hires of validity data
Screen ↓Role-fit ↓On-site ↓Anti-pattern questions ↓
Stage 01 · Screen
Twelve minutes. Ten questions.
The screening conversation. Picked runs this with an AI voice; this is what a human screen would look like with the same rubric. Time-box hard. 60 seconds per answer.
10 questions
01
Tell me about the last system you owned past v1. What broke first, and what did you do?
ownershipspecificity
Listen for
A specific service or surface. A concrete failure mode (latency, integrity, cost). A fix that names trade-offs.
Ignore
Adjective-heavy answers ("really scalable", "very performant") with no incident, no metric, no number.
catches · CV inflation, projects they touched but did not own.
02
What is a piece of your team's codebase you think is wrong, and why has it not been fixed?
judgementpolitics
Listen for
An opinion with a paragraph behind it. An honest reason for the not-yet (cost, priority, fear).
Ignore
"Everything is fine" or a moan about a teammate. Both are non-answers.
catches · Cannot hold an opinion without making it personal.
03
Walk me through the most recent thing you shipped end-to-end. From spec to production.
scopeagency
Listen for
The whole shape of the work, including who they had to convince. Specific scope, specific dates.
Ignore
Tech-stack listing. Stack is a downstream signal of scope.
catches · Front-of-loaf engineers, only the IDE-facing part of the work.
04
What is the smallest decision you have fought hardest for?
convictiontaste
Listen for
A real example. They say "in retrospect", and what they would do differently, or would not.
Ignore
Big architecture flexes that "saved the company". Usually rehearsed.
catches · No discrimination between big and small decisions.
05
Pick a service you use daily and tell me how it probably works under the hood.
curiositysystems
Listen for
Reasonable guesses at the boring parts (queues, sharding, cache). They acknowledge what they do not know.
Ignore
Stack-exchange recital. We want their reasoning, not memorised facts.
catches · Memorised-answer engineers. Stops working as soon as the system is unfamiliar.
06
Last time a teammate disagreed with you in code review. Walk me through it.
commsego
Listen for
A concrete review they remember. Whether they changed their mind, and the moment they did.
Ignore
"I always listen to feedback" platitudes.
catches · Defensiveness as a personality trait.
07
What is your favourite production incident you have been involved in?
reliabilitywar stories
Listen for
A specific outage with a real fix. Their precise role. What changed after.
Ignore
A dramatic story with no resolution.
catches · Engineers who have never been close enough to production to have one.
08
Tell me about a framework or tool you tried and rejected.
tastecritical thinking
Listen for
A genuine evaluation. A specific reason to reject. What they used instead.
Ignore
A framework they are "exploring". Often performative.
catches · CV as the boundary of what they know.
09
How do you onboard onto a new codebase?
judgementgenerality
Listen for
A sequence, usually: run it, trace one request, find an old PR, ask one stupid question.
Ignore
"I read everything first." Does not scale, does not work.
catches · Engineers who freeze without documentation.
10
One thing you want from the next role you would not have applied for if not.
stage fitseriousness
Listen for
A specific something. Hardware. Stage. A specific kind of customer. A specific manager.
Ignore
"Impact". "Growth". "Ownership". Vague.
catches · They are not really sure why they are looking.
Stage 02 · Role-fit assessment
A scoped task. A scored rubric.
One realistic task. We score the writeup, not the polish. The candidate has the take-home equivalent of 60 minutes.
8 questions
01
Design a notification system to deliver 10M push notifications in 30 minutes. Sketch the components, identify three failure modes, and tell me what you would build first.
systems designIC3+
Listen for
Capacity reasoning. A real first cut, with the boring parts present. Three actual failure modes, not jargon.
Ignore
A perfect-looking architecture diagram. We are scoring the thought, not the box-and-arrow.
catches · Architecture astronauts. Comprehensive on paper, helpless in production.
02
Here is a 200-line file from a real codebase. Refactor it. Tell me what you changed and why, in three bullets.
code qualityIC1+
Listen for
Edge-case handling, naming, abstraction-readiness. Their three bullets reveal taste.
Ignore
Renaming variables to be longer. Adding ceremony. Both common, neither valuable.
catches · Cargo-cult cleanups. Lots of motion, no improvement.
03
Pick one of three small bugs we have described. Reproduce it locally, write the fix, and write the post-mortem. 60 minutes max.
craftIC2+
Listen for
How they reach the repro. What they do not change. The shape of the post-mortem.
Ignore
Time spent on the IDE setup. We supply a working dev environment.
catches · Engineers who cannot name what they do not know.
04
Read this 3-page design doc. Write three questions you would ask its author and one suggestion you would push back on.
judgementIC3+
Listen for
Questions that show they have actually read the doc. A push-back that engages with the trade-off the author made.
Ignore
Stylistic edits. Word-level. We do not care.
catches · Engineers who cannot engage with someone else's spec.
05
Estimate the daily cost of running this service at our current load. Show your working in three sentences.
cost-awareIC2+
Listen for
Reasonable orders of magnitude. They name their assumptions. They notice when an answer is wrong.
Ignore
Spreadsheets. Calculators. We are measuring the back-of-envelope.
catches · Engineers who only know how to build, never how to estimate.
06
Take this real merge request. Decide if you would approve it, request changes, or close. Write the review.
code reviewIC2+
Listen for
Substantive comments. They reach for the design choice, not the missing semicolon.
Ignore
Five-line reviews of a 200-line MR. Volume is not signal.
catches · Reviewers who cannot prioritise, every issue gets the same weight.
07
Write the on-call runbook for the system you sketched in question 1.
operabilityIC3+
Listen for
They imagine being woken at 3am. Specific signals, specific commands, specific decisions.
Ignore
Cargo-culted runbook templates from the internet.
catches · Engineers who can build but cannot imagine operating.
08
In 200 words: why might the system you sketched in question 1 be the wrong choice?
humilityIC4+
Listen for
Genuine engagement with the alternative. A real "I might have picked X instead".
Ignore
A second pitch for the original design. Defensive.
catches · Lack of perspective on their own choices.
Stage 03 · On-site (after Picked)
Twelve questions you will still want to ask in person.
Picked screens, scores, and shortlists. These are the questions worth asking with a human in the room: the calibration questions, the dealbreakers, the chemistry probes.
12 questions
01
Where, in the work, do you want to grow most this year?
growthmanager fit
Listen for
A specific gap they are aware of. A plan, even a tentative one. A name of someone they would learn from.
Ignore
"I want to grow into a staff engineer." Title-laddering is not growth.
catches · Engineers without a learning agenda.
02
Tell me about a time you disagreed with a manager. What happened?
authoritymanager fit
Listen for
A real disagreement. The mechanics of the conflict, not the moral. What they took from it.
Ignore
"I have never disagreed with a manager." A lie or a worse problem.
catches · Engineers who cannot hold opinions in the face of authority.
03
What is the most uncomfortable feedback you have received and what did you do with it?
self-awareness
Listen for
A specific piece of feedback. The change they made. The thing they still struggle with.
Ignore
"I take feedback well." Means nothing.
catches · Defended self-narrative.
04
Walk me through a project you wish had failed faster.
judgementoperating
Listen for
Honesty. A specific moment they could have called it. What stopped them.
Ignore
A pitch for the project being secretly worth doing.
catches · Sunk-cost thinkers.
05
What is a strong opinion you have recently changed?
intellectual humility
Listen for
A specific opinion. A specific reason. They name the person or text that changed their mind.
Ignore
"My mind is always open." A boast disguised as humility.
catches · Closed-loop thinkers.
06
Pick two senior engineers you admire from your last role. What do they do differently?
taste
Listen for
Concrete habits. Habits they have adopted. Habits they have not.
Ignore
Pure praise. We want differentiation.
catches · Engineers without taste for other engineers.
07
Tell me the last technical thing you read outside your job.
curiosity
Listen for
A specific blog, paper, talk. They tell you what they thought, not just that they read it.
Ignore
A textbook they "always mean to get to".
catches · Engineers who do not think outside their stack.
08
When are you most productive?
operating model
Listen for
A specific time-of-day, a specific environment. A self-aware answer about energy.
Ignore
"I am always productive." Noise.
catches · Engineers without self-instrumentation.
09
Where would you rather be in three years?
careerretention
Listen for
A direction (deeper IC vs people-management) and a reason. Honesty about uncertainty.
Ignore
"Wherever the company needs me." Suspicious.
catches · Drifting engineers.
10
If you join, what would you want to spend your first week doing?
agencyonboarding
Listen for
A specific plan. Often: shadow on-call, ship a 50-line PR, read three design docs.
Ignore
"Whatever you suggest." Polite, but a weak signal.
catches · Engineers without an onboarding instinct.
11
What is the thing that would make you leave us within six months?
dealbreaker
Listen for
A specific irritant. A specific manager pattern. A specific working condition.
Ignore
"As long as the work is good." We need concrete.
catches · Hidden dealbreakers, surfaced post-offer.
12
What would you want to ask our most cynical engineer?
probingcuriosity
Listen for
A real question, usually about a quiet thing. "Why is your test suite slow?"
Ignore
A softball. A re-pitch of their interest.
catches · Candidates who do not want to know what is wrong.
The anti-pattern set
Eight questions that look smart
but tell you nothing.
"What is your biggest weakness?"
You will get a strength-shaped weakness. We have asked this 47,000 times. It catches no-one. Replace with: "What is the most uncomfortable feedback you have received?".
"Where do you see yourself in five years?"
Either a rehearsed answer or a stalled one. Both useless. Replace with: "Where would you want to be in three years?"
"Tell me about yourself."
Wastes the first three minutes on the CV they already gave you. Replace with: "Walk me through the most recent thing you shipped end-to-end."
"Why this company?"
Generates polished mission-talk. Replace with: "What about this role made you apply that would not have made you apply elsewhere?"
"Are you a team player?"
No-one says no. Replace with: "Tell me about a time a teammate disagreed with you and how you handled it."
"How do you handle stress?"
No-one says badly. Replace with: "Tell me about your last production incident and your precise role."
"How would you reverse a linked list?"
Probes nothing we care about. We removed it from the bank in 2019. Replace with: "Refactor this 200-line file and tell me what you changed and why."
"If you were an animal, which animal would you be?"
You know what we are going to say. Replace with: anything else.
Or, let us ask
We will ask these for you.
By Friday.
Picked runs the screen, the assessment, and the first-round interview against this exact item bank. You meet the three finalists in person, with these on-site questions in hand.
$0.99 per AI-vetted candidate. First 50 free.
Companion pages
picked.
The AI-native replacement for inbound hiring. For the hiring manager, not HR.
© 2026 Picked · Made in London · Three finalists in forty-eight hours.
Software engineer interview questions · Picked.ai