How do you ask a hiring manager how they measure performance without it sounding like an audit?
answer
- Adjectives about style tell you nothing
- Ask what the manager does, not is
- Cadence, written record, advancement, bad news
- One-to-ones measured in weeks
- Name the last person who advanced
basics
~20 sAsk for mechanics rather than adjectives: the cadence of your one-to-ones, what gets written down and when, how the last person on the team made a promotion case, and how you would first hear that something was off track.
solid answer
~40 sAsking a manager to describe their management style produces an adjective — 'hands-off', 'supportive' — that no candidate has ever been able to verify. So I ask about mechanics instead. How often do we meet one to one, and what happens in those meetings? What gets written down about my work, and when? How did the last person on this team who got promoted make the case, and what did you do to help? And if I am off track in month two, how do I hear about it, and how fast? Those are all comfortable questions for a manager who has done the job, and they are uncomfortable only for one who has not. The answers also give me something concrete to compare against how the team describes the same manager.
go deeper
Come with at least one question about how you would be managed, not only about what the team builds. Asking how often you would meet one to one and what happens in those meetings is enough at this stage.
Be ready to convert style questions into mechanics: frequency, what gets written down, how the last advancement case was made, how bad news reaches you. Know why the adjective version of the question is unverifiable.
Read the four answers as a set and spot the manager with good intentions and no system. Cross-check what the manager claims against what the team describes, and decide what that gap means for how you would be evaluated.
Own the judgment about whether you can operate under this manager's actual practice rather than their stated one, and be explicit with yourself about which weaknesses you could absorb and which would compound at your scope.
## The problem with asking about management style `What is your management style?` is the most-asked and least-useful question candidates put to hiring managers. It asks someone to describe themselves, in a setting where they are selling, with no downside to answering well. The output is a small set of adjectives — hands-off, supportive, high-trust, direct — that every manager believes about themselves and that no candidate can check. The fix is to stop asking what the manager *is* and start asking what the manager *does*. Behaviour has mechanics: a frequency, an artifact, a trigger, a first move. Those are answerable, and a manager either has answers or visibly does not. ## The four mechanics questions **Cadence.** How often do we meet one to one, and what actually happens in those meetings? A manager with a working practice answers instantly: weekly, half an hour, my agenda for the first half and yours for the second. An answer of *"whenever you need me"* is worth one more turn — it can mean genuine availability, and it can mean nothing is scheduled and busy weeks eat the meeting. **Written record.** What gets written down about my work, and when? Many companies run some sort of formal review cycle once or twice a year, but the specifics vary enormously between companies, so it is the manager's own habits that matter to you day to day. A manager who writes a short check-in note at, say, week 6 and again at week 13 of a new hire's first quarter is telling you your performance will be assessed against something recorded rather than remembered. **Advancement.** How did the last person on this team who advanced make the case, and what did you do to help? This is the highest-yield of the four and the least often asked. It is concrete, it is about the manager's actions rather than their intentions, and the failure state is loud: a manager who cannot name a single recent example is describing a team where advancement has not happened under them. **Bad news.** If I am off track two months in, how do I hear about it, and how quickly? What you are testing is whether corrective feedback is a conversation in the next one-to-one or a surprise in a review. Note that where things go after that varies a lot between companies — many have some form of documented improvement process, and the specifics differ — so keep the question on the manager's own first move rather than on formal procedure. ## Why this does not read as an audit Candidates worry these questions sound like interrogation. In practice they read as the opposite, for three reasons. First, they are questions about *the manager's job*, which competent managers enjoy answering — you are asking a professional to describe their craft. Second, they are framed from inside the role: "how do I hear about it" presupposes you working there, which is a warmer stance than "how do you handle underperformance." Third, they are specific, and specificity reads as preparation rather than suspicion. Tone does the rest. Ask two or three of them across the conversation rather than firing all four in sequence, and react to the answers — a follow-up on something the manager actually said is what separates a conversation from a checklist. ## The failure this replaces The common failure is spending the entire hiring-manager window on the product: what is on the roadmap, what the app does next, how the feature set is decided. Those questions feel engaged and they are safe, but almost anyone in the loop can answer them, and none of the answers tell you what your working life would be like. The hiring manager is the only person who can describe how you will be managed and measured, and you get one window with them. Spending it on the roadmap and none of it on the mechanics is the single most common way that window is wasted. ## Reading the answers Treat the four answers as a set rather than individually. A manager with a weekly one-to-one, a written note in a new hire's first quarter, a named recent advancement case, and a clear first move on bad news has a practice. A manager who is warm on all four but concrete on none has good intentions and no system, which is a specific kind of risk: you will be evaluated on impressions formed in rooms you are not in. Cross-check where you can. If the manager describes weekly one-to-ones and people on the team describe meetings that get cancelled, believe the pattern rather than the intention.
- Which single question would you keep if you only had time for one?How the last person on this team who advanced made the case, and what the manager did to help. It is concrete, it is about actions rather than self-description, and its failure state is unmistakable: a manager who cannot name one recent example is describing a team where it has not happened under them. It also implicitly answers how performance is judged.
- The manager says one-to-ones happen 'whenever you need me.' How do you read that?As ambiguous rather than bad, and worth one more turn. It can mean real availability, and it can mean nothing is scheduled and the busy weeks quietly eat the meeting. Asking when the last one happened, or how often they met with the newest person on the team, converts the intention into a fact you can weigh.
- Is it fair to ask a hiring manager what happens when someone is not meeting expectations?Fair, but better framed from inside the role: how would I first hear that I was off track, and how fast? That keeps the question on the manager's own first move rather than on formal procedure, which varies a great deal between companies. What you want to learn is whether corrective feedback arrives in the next one-to-one or as a surprise later.
saying these in an interview costs you the question
- Asking the manager to describe their own management style
- Spending the whole manager window on product and roadmap
- Accepting warm intentions with no cadence or artifact behind them
- Firing all the mechanics questions in a row like a checklist
- Never cross-checking the manager's account against the team's