What do you need from a manager to do your best work?
answer
- two or three concrete asks, not traits
- cadence and format, not vibes
- one example of it working
- say what you handle yourself
- ask how this manager actually works
basics
~20 sProbes how you will be managed and whether you can state your needs without sounding high-maintenance. Give two or three concrete asks — feedback cadence, decision clarity, escalation — each with a short example, then say what you handle yourself.
how to answer
4 beats- the two or three asks, stated up frontLead with concrete mechanisms — a cadence, a written decision, an escalation path — rather than adjectives like supportive. Two or three is the right number; a longer list starts to sound like conditions of employment.
- one short example of it workingGive a single instance where a manager did one of these and it visibly changed the outcome. Keep it to a few sentences; the example exists to make the ask concrete, not to become a story of its own.
- what you take care of yourselfName what you do not need managed — daily task assignment, chasing your own blockers, your own prioritisation within a sprint. This is the beat that stops the answer reading as high maintenance.
- the check backClose by asking how they normally work with their reports, or when they like to be pulled in. It converts the answer into a fit conversation and tells you whether your asks are realistic here.
your answer
4 story prompts- Write the two or three things a manager did that made your strongest quarter possible.
- For each, name the format: a cadence, a written decision, or an escalation path.
- Name one thing you explicitly do not need a manager to do for you.
- Take a past support gap and restate it as a need rather than a complaint.
draft and rehearse your own answer in a learn session
go deeper
This is a fit and manageability probe, usually asked by the person who would manage you. It tests whether you can describe your own support needs concretely, whether those needs are ones this team can actually meet, and whether you take ownership of everything outside them. A strong answer shows self-knowledge and low-drama working preferences rather than dependence or grievance.
Three things, and they are all small. A predictable one-on-one — twenty-five minutes a week is plenty, as long as it does not get cancelled two weeks running. Feedback close to the work rather than saved up; if something I wrote was hard to review, I would rather hear it in the review than in a summary months later. And a clear definition of done before I start, because that is where I have wasted the most time. The one that mattered most: I was assigned a cluster-upgrade runbook covering twenty-three services and I was quietly drowning in it. My manager asked what I had actually finished, then cut my slice to the four services responsible for most of the broken deploys. Those four went from nineteen failed deploys a week to five within the month, and the rest went back on the roadmap properly. I would not have proposed that cut myself at the time — I would have kept grinding — so having a manager who asks the awkward question early is worth a lot to me. What I do not need is someone assigning me work each morning. I will come with an attempt and a specific question. What I would want to know is how you like people to flag it when something is going badly.
The asks are mechanisms with a cadence attached rather than personality traits, and the example shows the speaker benefiting from help while still owning the work. The line about not needing daily assignment is what keeps it from sounding dependent. Vague asks for a supportive manager would downlevel it.
Two things, mainly. Clarity about which decisions are mine. On a secrets-rotation rollout I asked my manager for one sentence in writing: I could sequence it however I liked, provided no environment went more than six weeks without a rotation. That single boundary let me take the first pass down to staging plus one production shard instead of all eleven, which is what kept the rollout from stalling. Failed deploys held at 1.9% through the reduced version and we widened it two shards at a time afterwards. The second is honest information about constraints I cannot see from my seat — whether a date is real or aspirational, whether a partner team is about to reorganise. I will make different design calls depending on the answer, and I would rather get an uncomfortable answer than a comfortable silence. What I do not need is help prioritising inside my own scope, or a review of every technical decision. If something is at risk I will surface it early with options rather than arriving with a problem. What I would ask you is when you want to be pulled into something that is going sideways — some managers want it at the first signal, some want it once I have two options ready, and I can work either way once I know.
The asks are about decision rights and information rather than reassurance, and the proof is a written boundary the speaker requested and then used to cut scope. Offering two workable escalation styles instead of one preference shows the flexibility expected at this rung. Without the rollout detail it would read as generic autonomy talk.
Ask for what unblocks a first year: a regular one-on-one, feedback close to the work, a clear definition of done, and someone to sanity-check a plan before you spend three days on it. Say plainly that you will come with an attempt, not just a question.
Your needs move toward context and decision rights: knowing which calls are yours to make, having two competing priorities ranked when they land together, and getting feedback on how you work with people rather than only on your code.
Talk about what running a scope requires: air cover when you cut something, honest information about constraints you cannot see from your seat, and a manager who lets you carry the production consequences instead of reviewing each decision.
Frame it as a two-way working relationship: access to the forums where direction is set, a manager who will argue with your strategy early rather than politely later, and an explicit agreement about how your work is judged over quarters.
saying these in an interview costs you the question
- Saying you need nothing and can figure everything out alone
- Describing a manager only by traits such as supportive or hands-off
- Turning the answer into grievances about a previous manager
- Asking for constant direction with no sign of independent work
- Needs so specific that no real manager could plausibly meet them
- How would you want me to tell you your work was slipping?Answer with a mechanism, not a mood. Ask for it early, specific and about the work — the concrete gap and what good looks like — rather than saved for a review cycle. Then say what you will do with it: restate what you heard, agree a check-in date, and report back. That last part is what separates this from a demand for gentleness.
- What is the hardest feedback a manager has given you?Pick real feedback that stung and that you acted on, ideally about how you work with people. State it in their words rather than a softened paraphrase, say what you changed concretely, and give a small sign it took. Avoid humblebrag feedback like caring too much, which reads as a dodge.
- What did you not get from your last manager?This is the badmouthing trap. Answer as a structural gap, not a character verdict — priorities were rarely ranked, feedback arrived quarterly — say what you asked for, what improved, and what you learned to request earlier. One sentence of gap, two of what you did about it, and move on.