What does asking a hiring manager what success looks like in the first 90 days get a candidate?
answer
- Think about who writes your first review
- The job description is not the standard
- Ask for the first quarter, concretely
- Specific and testable beats ramping up
- Ninety days, defined in the manager's words
basics
~20 sAsking a hiring manager to define success at 90 days converts an advertised job description into the standard you will actually be judged against, and it reveals whether the manager has shaped the role at all.
solid answer
~40 sThe job description is marketing; the hiring manager is the person who will write my first review, so I ask them directly what a successful first 90 days looks like. A strong answer is specific and testable — on a mobile app team, something like owning the release train and shipping two releases with no rollback. A weak answer, such as 'ramp up and get to know the code', tells me the role has not been shaped yet, which is a real risk I would want to surface before I go further. I also listen for what the answer depends on: if my first quarter hinges on a team the manager does not control, that is worth knowing while I can still ask about it.
go deeper
Have this question ready and ask it of the hiring manager specifically, not of whoever happens to be last. Listen for whether the answer names something that ships, and write down the wording you hear rather than your summary of it.
Be ready to push one polite turn past a vague answer, usually by asking what a disappointing first quarter would look like. Notice the checkpoint cadence inside the answer — how often you meet, when anything gets written down — because that is the real management signal.
Ask what is explicitly outside your first 90 days as well as what is inside it. Test whether the expectation depends on teams the manager does not control, and decide in the moment whether the stated quarter is achievable given what you have heard elsewhere in the loop.
Own the judgment about whether a stated 90-day expectation is a genuine mandate or an aspiration with no funding behind it. Where the two conflict, name the gap to the manager in the conversation rather than discovering it after you start.
## What the question is actually doing `What does success look like in the first 90 days?` is the highest-yield question a candidate can put to a hiring manager, and it is high-yield for a structural reason: the hiring manager is the one person in the loop who owns the role, the work, and your future performance review. A job description is usually assembled from a template plus a wish list from several people. The manager's own answer is the specification. Asking for it moves the conversation from advertising to requirements. It is also a two-way instrument. You learn the standard you will be measured against, and you learn whether the manager has thought about the seat carefully enough to state one. ## What a strong answer contains Four ingredients tell you the answer is real rather than improvised: 1. **A named deliverable** — a thing that exists or ships, not a state of mind. 2. **A way to tell** — how the manager will know it happened. 3. **A dependency** — what you need from other people to do it. 4. **A checkpoint** — when the two of you will look at it. A concrete version, from a hiring manager on a mobile app team: *"In your first 90 days I want you owning the release train for the app. Two releases out the door with no rollback, and the manual regression pass trimmed so it stops gating the release date. We do a one-to-one every week, I write a short check-in note at week 6, and we look at the whole quarter at week 13."* That answer is testable. You can picture failing it, which is the surest sign it is a real expectation rather than a slogan. It also hands you a cadence — weekly one-to-ones, a written note at week 6, a review of the quarter at week 13 — which is far more informative than any adjective the manager could use to describe themselves. ## What a weak answer contains, and how to read it The weak answer is some version of *"ramp up, get to know the codebase, meet everybody."* That is not automatically disqualifying, but it has three common causes and they are worth separating: - **The role is not shaped.** Headcount was approved before the work was defined. You may end up defining your own job, which some people want and many find exhausting. - **The manager is new to managing, or new to this team.** They may be perfectly good and simply have no model yet for the first quarter. - **The seat is a backfill nobody has re-scoped.** The previous person's work drifted, and the manager is describing the old shape of the job. You can usually tell which by asking one more turn rather than accepting the first answer. The most reliable follow-up is the inverted one: rather than asking again what a good quarter looks like, ask what a disappointing first quarter would have looked like. Failure is easier to describe concretely than success, and managers who cannot produce a specific success story often produce a very specific disaster story — which is the same information. ## How to ask it so you get the specific version - **Ask early in your question window.** The answer reframes everything else you might ask, and if the window gets cut short you want this one banked. - **Anchor it to their scope, not the company's.** "Success in this role, on your team" keeps the manager out of corporate-strategy register. - **Do not accept the first pass if it is abstract.** One polite follow-up is normal and reads as engagement, not interrogation. - **Write down their words while they are still their words.** Paraphrase drifts within a day, and the exact phrasing is what you will want to compare against what other people on the loop say. ## The mistake this question exists to prevent The most common way candidates waste their time with a hiring manager is spending the whole window on the product — the roadmap, the feature set, what is shipping next — and never asking how they will be managed or measured. Product questions feel safe and interested, and they are answerable by almost anyone in the loop. Only the hiring manager can tell you what your first quarter is for. If you leave a manager conversation knowing the roadmap and not knowing the standard, you spent a scarce, non-repeatable window on the wrong person. ## What changes with seniority A first-job candidate should ask the question and listen. A more experienced candidate should also ask what is explicitly *not* theirs in the first 90 days — the boundary is where new senior hires most often collide with an existing team member who thought that work was still theirs.
- What if the hiring manager's answer is just 'ramp up and get to know the codebase'?Treat it as information, not a dead end, and take one more turn. Ask what a disappointing first quarter would have looked like instead — failure is easier to describe concretely than success, and the specific answer usually falls out. If both passes stay abstract, the honest reading is that the role has not been shaped yet, and that is something to weigh rather than something to argue with in the room.
- Is there anything you would ask a hiring manager about the first 90 days beyond what success is?Yes — what is explicitly not mine in that window. New hires, especially experienced ones, collide with someone who still considers that work theirs. Asking the manager to name the boundary surfaces it while it is cheap. It is also worth asking what the first 90 days depend on: if the deliverable needs another team's cooperation, that dependency is the actual risk in the expectation.
- Should you ask this of everyone on the panel, or only the hiring manager?Ask the hiring manager, because they own the answer that counts. It is fair to ask others what they think a new person on the team should accomplish early, but treat that as a consistency check rather than a second authority. If the manager and the team describe visibly different first quarters, that gap is worth raising with the manager directly.
saying these in an interview costs you the question
- Spending the whole manager window on the product roadmap only
- Accepting a vague 90-day answer without a single follow-up
- Asking what the company expects rather than what this manager expects
- Treating the job description as the standard you will be judged on
- Recording a loose paraphrase instead of the manager's actual words