Asked “What would your manager say about you?”, answer with what your manager has already said. Start from your last performance review or another piece of written feedback. Pick two strengths and use your manager’s own words for them. Attach one short incident to each, so the interviewer has something to ask about. Then name the development area from the same review. Say what you changed and what has happened since. The whole answer takes about ninety seconds. Three adjectives like “hardworking, reliable, team player” fail for a plain reason. Anyone can say them. Nothing in them can be checked. The question tests how well you know other people’s view of you. So the answer has to sound like a real person’s view, including the part you’d rather skip. This post builds one Android engineer’s answer from her last review.
The question tests whether you know how others see you
Tasha Eurich is an organizational psychologist. In a January 2018 HBR article, she splits self-awareness into two kinds. Internal self-awareness is how clearly you see your own values, reactions and strengths. External self-awareness is knowing how other people see you on those same points. Her team found virtually no relationship between the two. So you can reflect a lot and still misread how your colleagues see you.
The same article says most people believe they are self-aware. Eurich’s team estimated that only 10 to 15 percent of the people they studied met their criteria. That number is an estimate from one research program. The team was still preparing the results for a journal when the article ran.
The manager question asks for external self-awareness directly. The interviewer can’t phone your manager in the middle of the round. What they can judge is whether your description seems to come from someone else. Quoted phrases, dated feedback and a criticism you didn’t pick are the signs that it does. A list of flattering adjectives suggests it doesn’t.
An Android engineer whose review praised her debugging and flagged late warnings
Ines is an Android engineer on a mobile banking app. Her last annual review came eight months ago. She remembers three lines from it. Her lead called her “the person we give the bugs nobody else can reproduce.” He noted that her code reviews catch state bugs before QA does. The development area was blunt. It read, “We often hear about a slipping task on the day it slips.”
Her first instinct in interviews was different. She would say “detail-oriented, persistent and a team player.” Each word was true. But none of them could be checked. None came from her lead either.
The ninety-second answer Ines built from that review
Ines, her bank and her review are made up for this post. Keep the order of the answer. Fill it with lines from your own feedback.
My lead would probably start with debugging. In my last review, he called me the person the team gives the bugs nobody else can reproduce. The clearest case was a login freeze. About one in two hundred users saw the app hang after coming back from the background. It took me four days to find. The token refresh and the fingerprint prompt were racing each other. I built a test that reproduced it every time, then fixed it.
He’d also bring up code review. The review credited me with catching state bugs before QA does. Last quarter I blocked a change that would have shown a stale balance after a transfer. QA’s test plan didn’t cover that path.
The criticism in the same review was that I flag risk too late. He was right. On one release, I knew for a week that my task was at risk. I stayed quiet until the day it slipped. Now I post a short risk note in the team channel every Monday. It lists anything of mine that might slip and the reason. In the two releases since, he heard about every slip at least five days early. I still underestimate testing time. That’s what I’m working on next.
Answer what would your manager say about you in your manager’s words
Look at where Ines’s first two claims come from. Each one repeats a line from a written review. “The person we give the bugs nobody else can reproduce” sounds like a manager wrote it. It’s specific and a little informal. It also describes how the team works. “Detail-oriented” is a word candidates pick for themselves.
Many engineers have this kind of text somewhere. GitLab’s public handbook page on 360 feedback shows one version. A manager collects input from three to five peers and stakeholders. Then they share the themes in the review discussion. The page carries no date. Your company’s version might be a review form, a promotion packet or peer feedback in an HR tool. Reread it before the interview. Pick the two lines that come up more than once. They’re stronger than the two most flattering lines.
Every trait needs one incident the interviewer can open
A quoted line is still only a claim. The incident behind it makes it believable. Ines gives one per trait. The login freeze has a rate, a duration, a cause and a fix. The code review example has a specific bug that QA would have missed. Each one invites a follow-up. If the interviewer asks how she found the race, she can talk for ten minutes. A trait with no incident gives them nothing to ask. They move on with nothing written down.
Keep the incidents short inside this answer. One or two sentences each is enough. The question asks how your manager sees you. A full STAR story for each trait would take five minutes. If the interviewer wants one, they’ll ask.
Name the criticism before the interviewer asks for it
The usual follow-up is a version of “What would they say you need to work on?” Ines answers it inside her first reply. A candidate who offers a real criticism shows they heard it. A candidate who waits to be asked often reaches for a disguised strength instead. Our post on the greatest weakness question covers why that backfires.
Eurich’s article points the same way. The people her team interviewed improved their external self-awareness by asking “loving critics” for feedback. She means people who want the best for you and will still tell you the truth. A manager’s development note is often that kind of feedback. Quoting it shows you took it in.
The criticism also needs a change and a result. Ines names the Monday risk note. She gives the result in her lead’s terms, since he now hears about slips five days early. Then she adds what is still unfinished. That last line stops the answer from sounding like a solved problem. GitLab’s handbook asks managers to pick one or two development areas. Progress on them then gets reviewed in quarterly one-on-ones. An interviewer used to that cycle may expect a development area to still be open. Maybe you think the criticism was only partly fair. Our post on critical feedback that was only partly right shows how to say so.
Say only what your manager would repeat on a reference call
Some employers do check. Topgrading is a hiring method sold to companies. Its 2014 blog post describes telling candidates from the start that they’ll arrange calls with former managers. Topgrading calls this the Threat of Reference Check. The post claims candidates tell the whole truth once they know the calls are coming. That claim comes from the firm selling the method. The post gives no data for it.
Imagining that call is useful even when nobody makes it. Picture your manager listening to your answer. Would they recognize every line? Would they object to any of it? Ines’s answer passes, because each line came from her lead’s own review. Our post on reference checks after the final interview covers who gets called and what they’re asked.
No written review? Ask a former lead one “what” question this week
Some engineers have never had a written review. Startups and contractors often go without them. Some managers only give feedback out loud. You can still answer from evidence. Look through pull request comments, retro notes and messages where someone thanked you for specific work. Those show how people saw your work at the time.
If that isn’t enough, ask a former lead or a senior peer before the interview. Eurich recommends “what” questions over “why” questions. One of her interviewees used a “what” question to make sense of negative feedback. So ask, “What would you tell a new manager about working with me?” Then ask what you should do more of and less of. Check any surprising answer with a second person, as Eurich’s interviewees did. In the interview, say where the words came from. Give the person’s role and the month you asked. Try “My last tech lead, when I asked her in October.” It shows the view is recent. It also shows it came from someone else.
1 thought on ““What Would Your Manager Say About You?” Start With Your Last Review”