Which of our stated values resonates most with you, and why?
answer
- pick one value, not the list
- restate it in your own words
- prove it with a decision you made
- name where the value gets hard
- ask how it shows up here
basics
~20 sChecks whether you read the values and can connect one to something you actually did. Pick a single value, restate it in your own words, prove it with a decision you made, and name where living it costs something.
how to answer
4 beats- the one value, and what you take it to meanName a single value and immediately restate it in your own words. The paraphrase is the part that shows you thought about it; quoting the published line back proves only that you can read.
- the decision that proves you already work this wayGive one specific choice you made where that value was the reason. A decision with a visible consequence beats a general claim about how you approach work.
- the honest tensionSay where the value is inconvenient or costs something, and what you do when it collides with a deadline. This is the beat that separates a considered answer from flattery.
- the check: how it shows up hereFinish with one question about how the value operates day to day — what happens when it conflicts with a date, or what it changed most recently. You get real information, and it signals you are evaluating the fit too.
your answer
4 story prompts- Read the published values and pick the single one you can prove with a decision.
- Write one decision where that value cost you speed, comfort or a visible win.
- Restate the value in your own words in one sentence, without its published phrasing.
- Name the value on the list you would struggle with, and your compensating habit.
draft and rehearse your own answer in a learn session
go deeper
This is a values-alignment and preparation probe. The interviewer wants to know whether you engaged with what the team publicly says it believes, and whether you can translate one of those statements into behaviour you have already chosen. A strong answer proves that values language maps onto your actual decisions, including the ones that cost you something.
The one I keep coming back to is the line about preferring a small reversible change to a big correct-looking one, because I have seen the cost of the alternative in my own work. I was handed a dashboard migration for our deploy pipeline — thirty-one dashboards to move onto a new metrics backend. The obvious plan was to script all of them in one pass. Instead I did the six that on-call actually opens during an incident and asked the on-call rotation to use them for a week. Two of those panels turned out to have been reading a stale series for months, which meant the broken-deploy graph everyone trusted was quietly wrong. If I had scripted all thirty-one in one go, I would have copied that mistake thirty-one times and found it much later. Where I find it hard: small and reversible looks slow from the outside. That week I had six dashboards done and someone else on the team had a branch that touched all of them, and mine looked like the lesser output until the stale series turned up. So the thing I would want to know is how this team decides when small stops being worth it, because I do not think it is always the right default.
The value is paraphrased rather than quoted, and it is proved by one decision inside the speaker's own task with a consequence attached. Admitting the value made them look slower is what makes the answer credible rather than performative. Without the stale-series discovery it would be an opinion about batch sizes.
The one about surfacing bad news early, which I read as: say it when you believe it, not when you can prove it. I was three weeks into consolidating our control-plane rollout across five regions, with a date that had already been shared outside the group. It became clear that only two regions would be ready. I raised it in the week-three review rather than letting the date arrive — I brought the numbers for the two regions we could finish, a failed-deploy rate of 2.7% against a 5.1% baseline, and a proposal to move the remaining three into a second phase with their own date. It was not a comfortable meeting. One director pushed back hard, and the cut cost my team the visible win of a single launch. But the second phase landed with no surprises, and the next time I flagged something early nobody asked me whether I was sure. The tension I feel with this one is that early and certain pull against each other. I have raised things at forty percent confidence and been wrong, which spends credibility. My rule now is to say the confidence out loud alongside the news. How does this team handle that — is an early warning welcome here, or is the expectation that you bring it once it is settled?
The value is demonstrated where it was expensive: an uncomfortable meeting and a lost launch narrative, with the scope cut owned rather than assigned. Naming a case where acting on the value went wrong, plus the rule that came out of it, is the reflection this rung is judged on. Dropping the cost would flatten it into a slogan.
Prove the value with a choice inside your own task — what you did when the quick path and the stated value pulled apart. Nobody expects org-level examples from you; they expect that the value describes something you have actually done once.
Show the value operating between people: a review you gave, a decision you documented, a scope you argued down. Add one sentence on where the value is inconvenient, since a value with no cost is a slogan.
Demonstrate the value where it was expensive — a cut you defended in front of stakeholders, a risk you surfaced before it was certain. At this level the interesting part is the trade you accepted, not the sentiment.
Talk about making a value operable across teams: the mechanism, ritual or default that let people act on it without you in the room, and how you noticed when the stated value and the actual incentives had drifted apart.
saying these in an interview costs you the question
- Reciting the published wording back with no behaviour behind it
- Praising every value on the list equally to stay safe
- Picking a value that contradicts how you described your own work earlier
- Treating it as a memory test rather than a question about conduct
- Flattering the company while saying nothing about your own choices
- Which of our values would you find hardest to live up to?Answer it honestly rather than reframing another strength. Choose a value that genuinely pulls against your instincts, say why in one line, and describe the compensating habit you have built — a checklist, a peer you ask, a rule you follow when you notice the pull. Refusing to pick one is the weakest available answer.
- Where have you seen a value like that break down in practice?Describe the mechanism of the breakdown, not villains: the value said one thing and the deadline, metric or promotion process rewarded another. Say what you did within your scope, and what you would want a team to change so the value survives pressure. Keep former employers out of the dock.
- How would you tell whether a team actually lives that value?Point at observable artefacts rather than atmosphere: what happens in a review when someone disagrees, whether cut scope is written down, how bad news travels, what the last postmortem changed. Naming two or three concrete tells shows you evaluate culture by evidence, and it earns you a genuinely useful answer.