picked.
Log inPost a role
picked.ai/hire/staff-engineer/interview-questions
30 staff engineer
interview questions that actually work.
Pulled from the Neuroworx item bank: nine years of calibration against twelve-month performance outcomes on 14,083 staff 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 project you killed that you had originally argued for.
judgementintegrity
Listen for
A specific project. The moment they called it. The way they wrote the kill memo.
Ignore
"We pivot a lot." Vague.
catches · Engineers who only kill other people's projects.
02
Walk me through an architecture review you led. What changed because of you?
architecturespecificity
Listen for
A specific review. The change. The follow-up. They name who they had to convince and who they did not.
Ignore
"My reviews are very thorough."
catches · Engineers who run reviews as a rubber stamp.
03
Describe a one-page doc you wrote that changed a team's direction.
influencecraft
Listen for
A specific doc, the team, the direction change. They name what they cut from the doc to make it land.
Ignore
A 20-page strategy doc.
catches · Engineers who write to impress instead of to land.
04
Tell me about an engineer you mentored who is now more senior than you would expect.
mentorhumility
Listen for
A specific engineer. A specific gap they helped close. The way the engineer surpassed them.
Ignore
"Everyone I mentor grows." A platitude.
catches · Engineers who measure their mentees by how grateful they remain.
05
When did you last decide not to rewrite something that you found ugly?
pragmatism
Listen for
A specific system. A specific reason to leave it. A small intervention they made instead.
Ignore
"I rarely want to rewrite." Often a lie.
catches · Engineers whose instinct is to rebuild before they read.
06
How do you choose what to work on when nobody is assigning you a project?
agency
Listen for
A real frame. They name the conversations they have. The cost of choosing wrong. The way they say no to other work.
Ignore
"I work on the highest-impact thing." Vague.
catches · Engineers who default to the loudest request in the room.
07
Describe a cross-team conversation you initiated that saved your org months of work.
influencespecificity
Listen for
A specific conversation. The two teams. The work it spared. The thing they had to give up to get the agreement.
Ignore
"I do a lot of cross-team work." Vague.
catches · Engineers who do not have a single named example.
08
Tell me about a time you were wrong about an architectural call.
humility
Listen for
A specific call, the consequence, the way they told the team, the change they made after.
Ignore
"I am usually right." A red flag.
catches · Engineers who externalise their architecture failures.
09
How do you keep up with relevant technology without chasing every trend?
curiosityoperating
Listen for
A named, short list of sources. A cadence. A filter that protects their attention.
Ignore
"I read everything." Untrue.
catches · Engineers who confuse Hacker News for a curriculum.
10
One thing you want from the next role you would not have applied for if not.
stage fit
Listen for
A specific something. A particular CTO relationship. A specific scope. A product domain.
Ignore
"Hard problems." Vague.
catches · Engineers who are not 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
Read this 5-page architecture proposal from a team you do not work on. Write the review, including three questions and one push-back.
architecture reviewIC3+
Listen for
Questions that engage with the trade-offs. A push-back with a real alternative. They name what they would not change.
Ignore
Stylistic edits.
catches · Engineers who cannot critique without rewriting.
02
Design the cutover for migrating a 12-team monorepo to two repos. Sketch the first month and the rollback.
systems designIC4+
Listen for
A migration plan with a real rollback. The first month is conservative. They name the cost they will accept.
Ignore
A big-bang migration.
catches · Engineers who plan migrations without a rollback.
03
You parachute into a stuck six-month project. Tell me the first three conversations you would have and what you would change in week one.
project surgeryIC3+
Listen for
Specific conversations (the manager, the original author, the stakeholder). A small week-one move, not a relaunch.
Ignore
A relaunch in week one.
catches · Engineers who default to taking over the project.
04
Write the one-page memo that would convince a peer team to abandon their planned rewrite.
influenceIC3+
Listen for
A memo that is honest about the upside of the rewrite. A real reason to wait. A path the peer team can live with.
Ignore
A memo that wins by intimidation.
catches · Engineers who only know how to push.
05
Take this real production incident and write the post-incident review for the company, not the team.
commsIC3+
Listen for
A review that names the cause without scapegoating. Names the company-level change. Reads as honest at any level of the org.
Ignore
A team-internal post-mortem rebadged.
catches · Engineers who cannot tell the same story to two audiences.
06
Estimate the engineering cost of the proposal you reviewed in question 1, in engineer-months. Show your working in three sentences.
estimationIC3+
Listen for
Reasonable orders of magnitude. They name the assumptions. They notice when the number is implausible.
Ignore
A precise number with no reasoning.
catches · Engineers who underestimate by an order of magnitude as a habit.
07
Write the brief for the engineer you would assign to lead the proposal in question 1. What are you looking for?
talentIC4+
Listen for
A specific profile, with strengths and the gap they would need support on. A named candidate would be a bonus.
Ignore
A generic seniority spec.
catches · Engineers who cannot describe the people side of a project.
08
In 200 words: why might the architecture in question 1 be the wrong call even if your review was correct?
humilityIC4+
Listen for
Genuine engagement with an alternative. A real "I might have over-rated X".
Ignore
A defence of the original critique.
catches · Engineers without perspective on their own reviews.
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 do you most want to grow as a staff engineer this year?
growthmanager fit
Listen for
A specific gap. A plan. A peer they would learn from.
Ignore
"I want to be a principal." Title-laddering.
catches · Engineers without a learning agenda.
02
Tell me about a time you disagreed with a CTO or VP eng. What happened?
authoritymanager fit
Listen for
A real disagreement, the way they raised it, the outcome. They did not always win.
Ignore
"I always defer to the CTO." A worrying answer.
catches · Engineers who do not push upward.
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 wrestle with.
Ignore
"I take feedback well." Tells us nothing.
catches · Defended self-narrative.
04
Walk me through a project you wish you had backed away from sooner.
judgementoperating
Listen for
A specific project. The moment they should have called it. The reason they did not.
Ignore
A late-save story with no failure.
catches · Sunk-cost thinkers.
05
What is a strong opinion about architecture you have changed in the last year?
intellectual humility
Listen for
A specific opinion, what changed it, the new practice they adopted.
Ignore
"My mind is always open."
catches · Closed-loop thinkers.
06
Pick two staff engineers you admire. What do they do differently from you?
taste
Listen for
Concrete habits. The ones they adopted. The ones they consciously did not.
Ignore
Pure praise.
catches · Engineers without taste for other engineers.
07
Tell me the last technical thing you read outside your stack that changed how you think.
curiosity
Listen for
A specific source, what they took from it, the way it shows up in their work.
Ignore
A book they mean to finish.
catches · Engineers who do not read outside their stack.
08
When are you most useful to an org in trouble?
operating model
Listen for
A self-aware answer. A specific pattern they bring (the one who writes the doc, the one who sits between two teams).
Ignore
"I show up whenever they need me."
catches · Engineers without self-instrumentation.
09
Where would you rather be in three years, principal IC or back into management?
careerretention
Listen for
A direction and a reason. Honesty about the uncertainty.
Ignore
"Wherever the company needs me."
catches · Drifting engineers.
10
If you join, what would your first month look like?
agencyonboarding
Listen for
A specific plan. Often: read the last three architecture reviews, sit with two teams, write one short doc.
Ignore
"Whatever you suggest."
catches · Engineers without an onboarding instinct.
11
What would make you leave us within six months?
dealbreaker
Listen for
A specific irritant. A reporting line that defangs the role. A pattern of decisions made without the engineers in the room.
Ignore
"As long as the work is good."
catches · Hidden dealbreakers, surfaced post-offer.
12
What would you want to ask our most cynical senior IC?
probingcuriosity
Listen for
A real question. "Which decision did we make this year that you would reverse?"
Ignore
A softball.
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.
Staff engineer interview questions · Picked.ai