skip to content

If I called your last manager, how would they describe you?

level: middleimportance: should knowfreq 41%

answer

  1. answer in their voice, not yours
  2. two or three words, not five
  3. one example behind the main word
  4. the edge they would also name
  5. keep it checkable

basics

~20 s

Tests whether your self-image matches how someone who watched you daily would describe you. Answer in their voice with two or three words they genuinely used, prove one with an example, and include the edge they would also mention.

how to answer

5 beats
  1. the two or three words they would actually use
    Open in their voice, close to phrasing you have really heard in a review or a one-to-one. Two or three words is the right density; five adjectives sounds like a self-description wearing a costume.
  2. one example behind the main word
    Pick the strongest word and prove it with a compact situation and an outcome. Thirty to forty seconds. Without this the whole answer is unverifiable praise, and interviewers discount it accordingly.
  3. the edge they would also name
    Give the criticism they raised, in their framing rather than a softened version of it. Volunteering this before you are asked is what makes the flattering half believable.
  4. where that edge stands now
    One or two sentences on what you changed and how it shows. Keep it concrete and avoid claiming the issue is finished; describing the current state honestly is stronger than reporting a cure.
  5. the invitation to check
    Close with one line saying you would be comfortable if they asked the same question in a reference conversation. Say it plainly and move on, and only say it if it is true.

your answer

4 story prompts
pick a story
  • Pull the exact adjectives from your last review or a one-to-one you still remember clearly.
  • Ask a current teammate what they would say if a recruiter called, and write their words down.
  • Pick the criticism your manager gave you more than once, and decide where it stands today.
  • This can reuse your greatest-strength story, retold in your manager's voice rather than your own.

draft and rehearse your own answer in a learn session

go deeper

This checks calibration: whether your self-assessment survives contact with someone who watched you work daily. It also probes coachability, because an honest manager description almost always contains a critique. Strong answers quote real language, ground the main word in a specific example, and include the edge rather than sanding it off.

at middle level

She would lead with dependable across teams, and then something like pushes for written agreements earlier than some people are ready for. Both are close to her actual wording in my last review. The dependable part comes from the release train. When I joined that mobile team we shipped roughly every five weeks, mostly because each release picked up a half-finished integration from somewhere else and then sat in testing. I took over the release checklist and set one rule: an integration either has a working end-to-end path by the cut or it ships behind a flag, no exceptions. I was the person saying no when saying no was awkward. We got to a release every eleven days, and crash-free sessions moved from ninety-eight point two percent to ninety-nine point four. The second half is fair too. I ask for a written contract at a point where other people still want room to explore, and one of the designers told me directly that I was asking her to decide things she was not ready to decide. That landed. Now I ask when a decision is likely rather than asking for the decision, which gets me the same planning information without the pressure. I would be comfortable if you asked her the same question in a reference conversation.

why this lands

Quoting close to the manager's real phrasing, then pairing the strength with an edge that had a named cost, is what makes this checkable rather than flattering. The cadence and crash-free numbers carry the proof; strip them and it collapses into an adjective list.

at senior level

He would start with owns the seams nobody owns, and then say I am slower to hand work back than he would like. The first comes from a four-month push on cold start. We were a seven-person client team inside a startup where the platform group, two SDK vendors and the growth team all shipped code into our app, and every one of them added a little work to the moment before first paint. Nobody owned the total. I took it, measured on the low-end device tier where most of our new installs actually were, published the numbers weekly whether they had moved or not, and negotiated a per-team budget in milliseconds instead of asking people to be careful. Median cold start on that tier came down from five point two seconds to two point seven, and the budget outlived me on that team, which I care about more than the number. The second thing is fair. I ran the weekly review myself far longer than I needed to because I liked being close to the data, and two engineers who should have been leading pieces of it were reporting into me instead. He raised it in a one-to-one, I handed the review over the month after and stayed on as a reader. He would tell you both halves and I would be fine with that.

why this lands

Senior signal comes from taking ownership of a problem no team owned, a mechanism that outlived the speaker, and a leadership weakness named with its cost to two engineers who were being held back. Without the line about the budget surviving, this reads as a strong individual contributor story instead of a senior one.

for a junior

Draw on a real review, a one-to-one comment or an internship wrap-up. If the relationship was short, say whose words you are quoting and keep the claim modest rather than inflating a single compliment.

for a middle

Expect the words to be about how you work with others: reliability on a feature, quality of your review, how you handle a dependency. Include one thing they pushed you on and say where it stands now.

for a senior

The description should include the scope you were trusted with and judgement calls you made without them in the room. The edge they would name should be a genuine leadership trade-off, not a tidy one.

for a principal

The believable answer quotes how peers and executives describe your effect on the organisation: direction set, standards adopted, people grown. Name the friction that comes with pushing at that scale, because there always is some.

saying these in an interview costs you the question

  • Reciting flattering adjectives with no example behind any of them
  • Describing yourself instead of what your manager would actually say
  • Claiming your manager had no criticism of you at all
  • Using the question to relitigate a bad relationship with that manager
  • Saying something a reference conversation would plainly contradict

  • And what would they say you need to work on?
    If you already included the edge, extend it rather than repeat it: give the second thing they raised, or the context in which the first one still appears. If you did not include one, give it now without flinching. Answering that there was nothing is the single fastest way to lose credibility on this question.
  • Would your peers describe you the same way?
    Usually the honest answer is mostly, with one difference, and that difference is the interesting part. Managers tend to see delivery and judgement while peers see day-to-day collaboration. Name the word a peer would add or subtract and why, which shows you have a picture of yourself from more than one angle.
  • Would you be comfortable if I asked them that in a reference check?
    You should be able to say yes calmly, which is the real reason to keep this answer close to things that were actually said. If the relationship ended badly, say so briefly and neutrally, offer a different reference who saw the same work, and do not editorialise about the manager. Composure here matters more than the details.

context

resolving links…