What to Say in Your Performance Review Meeting

Your manager sends the calendar invite. "Performance Review Discussion, 30 minutes." Your stomach drops. Not because you did bad work, but because you have no idea what you are supposed to say in that meeting.

Most engineers treat the performance review conversation like a doctor's appointment. You sit, you listen to the diagnosis, you nod, and you leave. That is a mistake. The review meeting is one of the few moments where you can directly shape how your work is understood, ask the questions that actually matter for your career, and set up the next six months in your favor.

Here is what to say in every scenario you might walk into.

Before you open your mouth: the two-minute prep

You should already have your self-review done by this point. If you do not, the software engineer self-review guide can help you catch up fast. What you need in the meeting itself is simpler:

• Your top three wins for the period. Not your whole self-review. Three specific things you are proud of, stated in one sentence each. Have these ready to bring up if your manager does not mention them.
• One question about promotion. Not "am I getting promoted?" but something specific: "What would need to be true for me to be considered for the next level in the next cycle?"
• One question about gaps. Something like: "What is the one area where you think I could grow the most right now?"

That is it. You are not preparing a presentation. You are preparing to have a real conversation instead of passively absorbing a rating.

Scenario 1: You got a good rating

This is where most engineers relax and coast through the meeting. Do not waste this opportunity.

A good rating means your manager already believes in your work. That makes this the easiest moment to have the promotion conversation. Your manager is not defensive, and they are already thinking about your strengths.

What to say

"Thank you for the feedback. I am glad to hear the work on [specific project] landed well. I wanted to ask: based on where I am right now, what would you say is the gap between my current level and the next one?"

This question does three things. It shows you are thinking beyond the current cycle. It gives your manager a chance to name something concrete. And it creates a record that you initiated the promotion conversation, which matters for the next cycle.

What not to say

Do not say "So am I getting promoted?" That forces a yes or no answer and puts your manager in an awkward spot if the answer is not yet.

Do not spend the whole meeting accepting compliments. A good rating is momentum. Use it to get specific intelligence about what promotion looks like from here.

Follow up with this

"That is helpful. Can we set a check-in for [specific date, 2-3 months out] to see if I am making progress in that area?"

You just created an accountability touchpoint. Your manager will remember this conversation when the next cycle starts, and you will have a built-in prompt to discuss your trajectory again.

Scenario 2: You got a mediocre rating

This is the most common outcome, and also the one engineers handle worst. A "meets expectations" or equivalent rating feels like a punch in the gut when you thought you did good work. The instinct is to either shut down or start arguing.

Both reactions hurt you. Here is what to do instead.

Absorb before you respond

Take a breath. Let your manager finish explaining the rating. Do not interrupt with "but I also did X." Your manager has already decided, and debating the rating in the room will not change it. What you can change is what happens next.

What to say

"I appreciate you sharing that. I want to make sure I understand the gap. Can you give me a specific example of what 'exceeds' would have looked like this cycle for someone at my level?"

This question shifts the conversation from judgment to actionable information. Your manager now has to give you a concrete picture of what they wanted to see, which is the single most useful thing you can get from this meeting.

If their answer is vague ("just more impact"), push gently:

"Can you point to a specific project or situation where you think I could have done that differently?"

Most mediocre ratings happen because of a visibility gap, not a performance gap. Your manager may not have known about half the things you did. This meeting is your chance to surface work that was missed.

What to say if they missed something

"That makes sense. I also want to flag something I may not have communicated well enough: [specific project or win]. I led [brief description] and the result was [outcome]. I realize I could have done a better job making that visible."

You are not arguing. You are adding information. Your manager may not change the rating, but they will remember this data point when the next calibration meeting comes.

What not to say

Do not say "That is not fair." Even if it is true. The word "fair" puts your manager on the defensive and makes the conversation adversarial. Frame everything as a learning conversation, even if internally you are frustrated.

Do not say "I guess I need to just work harder." That signals you do not understand the actual gap. The gap is almost never effort. It is visibility, scope, or communication.

Scenario 3: You got a bad rating (or a surprise)

If your review catches you off guard with a low rating, a PIP warning, or feedback you have never heard before, you are in damage-control mode. The goal of this meeting is not to fix anything. It is to gather information and buy yourself time to think clearly.

What to say immediately

"This is not what I expected, and I want to take some time to process it before I respond fully. Can you walk me through the specific examples that drove this rating?"

This is the most important sentence in this article. It does three things: it signals emotional maturity (your manager will notice), it prevents you from saying something you will regret, and it forces your manager to provide concrete evidence rather than vague impressions.

Write everything down

Ask your manager if you can take notes during the meeting. If they say no (rare), write down everything you can remember immediately after. You need a written record of what was said, especially if this is headed toward a PIP conversation.

What to ask before you leave

"I want to understand exactly what success looks like from here. Can we schedule a follow-up in the next week to go over a plan together?"

This buys you time. You do not need to agree or disagree with the rating in this meeting. You need to leave with the information you need to decide your next move.

What not to say

Do not agree that the rating is justified if you do not believe it is. Nodding along to end the discomfort creates a record that you accepted the assessment.

Do not threaten to leave. Even if you are thinking it, saying it out loud gives your manager information they can use and removes your negotiating power.

The three questions that matter more than your rating

Regardless of what rating you receive, these three questions will give you more career value than anything else you say in the meeting.

1. "What would I need to demonstrate to be considered for the next level?"

Forces your manager to name specific, measurable criteria. Write down their answer word for word. This becomes your roadmap.

2. "Is there anything I did this cycle that you did not know about?"

Surfaces the visibility gap. If your manager says "no, I think I had a good picture," you have a different problem than if they say "actually, I did not realize you led that migration."

3. "Who else's feedback influenced this rating?"

This tells you who else in the organization is shaping your trajectory. If your skip-level or a peer gave input you did not expect, you now know where to focus your relationship-building.

After the meeting: the 24-hour window

What you do in the 24 hours after your review meeting matters almost as much as the meeting itself.

Send a follow-up email within a day. Summarize what was discussed: the rating, the key feedback, and the next steps you agreed on. This creates a paper trail and shows you took the conversation seriously. Keep it factual, not emotional.

Here is a template:

"Hi [Manager], thanks for the conversation today. To make sure I captured everything correctly: my rating was [X], the main feedback was around [Y], and the areas to focus on going forward are [Z]. I am planning to [specific action]. Let me know if I missed anything."

Process your emotions separately. Talk to a friend, a partner, your therapist. Do not vent on Slack. Do not post on Blind while you are still angry. Give yourself 48 hours before making any career decisions based on what you heard.

Start documenting immediately. Whatever gaps your manager identified, start building evidence against them starting today. The next review cycle has already begun, and your manager will remember whether you took the feedback seriously. If you need a system for preparing before the next conversation, the guide on how to prepare for your performance review conversation covers the full lead-up.

---

CareerClimb's AI coach helps you prepare for exactly these conversations. Walk into your review meeting with the right questions, the right wins, and a plan for what to say no matter what rating you receive.