If You Got a Meets Expectations Rating - Your Promotion Path Isn't Closed, Just Delayed

May 6, 2026Career9 min read

A Meets Rating Isn't a Door Closing

The year-end performance review just wrapped up and your manager said "meets." Maybe "meets expectations," maybe a "B" rating in the local system - whatever the label, the meaning is the same: middle of the pack. Not exceeding, not below.

The first reaction is usually identical for most engineers: "So no promotion, I've fallen out of favor, time to look elsewhere." All three are most likely wrong. The meets rating accounts for the majority of ratings handed out in Türkiye's software sector - statistically, it's the average review outcome. The problem isn't the rating itself; it's what you do after it.

This post is meant to give you a concrete action plan beyond the "this is unfair" feeling. How to prepare for a performance review is a separate post; here we're talking about the 6 weeks after the review ends.

What a Meets Rating Actually Means

A meets rating is as much about what it isn't as what it is. In most companies the distribution is roughly calibrated like this:

Exceeds: 15-25% (capped by calibration)
Meets: 55-70% (the large majority)
Below: 5-15%

If you got a meets, you're statistically in the same bucket as more than half of your team. That's not bad news; nor is it a promotion blocker on its own. On its own, it slows the promotion timeline but doesn't close it.

There are two types of meets ratings, and distinguishing them is critical:

Healthy meets: You hit your goals, scope grew, the team wants to keep working with you - but there was no "wow" moment. Here the promotion timeline might shift by 6 months at most.

Signal-carrying meets: Half your goals slipped, one or two projects ran late, your manager's feedback has many "but on this point" sentences. This kind of meets can be a polite version of "below" and should be taken seriously.

The two are managed differently; turning the first into unnecessary panic is as harmful as reading the second as "everything is fine."

Follow-Up With Your Manager - Within 2 Weeks

During the review meeting your first reaction was likely shock or disappointment; that's natural. The real work doesn't end there - within two weeks request a separate 30-minute follow-up with your manager. The opener can be:

"I've sat with our review conversation from last week. I'd like to dig into a couple of points more deeply, to get clarity on the next period."

In that meeting you should ask three questions:

1. "What specifically separated meets from exceeds?"

Don't settle for general phrases ("be more proactive," "more visibility"). Ask for concrete examples. "Which project, which moment?" If your manager can't give an example, the rating was largely subjective; that's valuable information in itself.

2. "Which projects of mine did you discuss in calibration?"

In calibration, your manager speaks for you. Find out which wins came up, which gaps were debated. Often it turns out managers don't remember your brag list - which tells you what you need to do.

3. "Concretely, what would I need for an exceeds rating?"

Ask this politely but precisely. If the answer is vague ("show leadership," "increase impact"), it's on you to make it specific. What does "leadership" mean on this team? Mentoring a junior, writing an RFC, leading a cross-team project? If your manager doesn't offer the concrete equivalent, propose options yourself and get their buy-in.

Note: This conversation shouldn't be defensive. If you slip into "this is unfair" sentences, your manager goes into defense mode and you'll get no useful information. The tone should be "I want to understand, I want to do better."

Pushback on the Criteria - When It Makes Sense, When It Doesn't

If you feel "this is unfair" after the meets rating, criteria pushback is one option. But it's not always sensible; tell the two cases apart.

Pushback makes sense:

Your goals shifted mid-year for reasons outside your scope (project canceled, team changed, manager changed) and the review used the old goals
You hit the concrete metrics but the rating was lowered for a subjective reason ("communication")
In calibration, your manager didn't represent your wins (e.g., your 6-month major project wasn't mentioned)

Pushback doesn't make sense:

You feel "I deserve more" but have no concrete evidence
Your performance was genuinely middle-of-the-pack and others stood out
You joined the team recently and only worked the last 3 months of the cycle

If you have a sensible pushback, the next step isn't your manager - it's your manager's manager. Request a 1:1, open with "I have an additional thought on this cycle's review, can I share it?" Present the data (concrete goals, concrete outputs), don't expect a rating change - just open the conversation about "how do we prevent this for the next cycle."

Pushback rarely changes the rating itself. But it ensures next period's goals are better defined and leads to your manager speaking more strongly on your behalf in the next calibration.

Redefine Next Period's Goals

The most critical action after a meets rating is rebuilding your goals for the next 6 months. If your goals for this period were set at the start of the year, they were likely written in the same format and with the same vagueness; this time write them differently.

A good goal carries these three properties:

Tied to output, not action. "Improve backend tests" is action; "Raise backend test coverage from 40% to 75% and ship the period with zero regressions" is output. A meets rating is often the result of action-bound goals - your manager may be saying "you did it but didn't measure the impact."

Visible and measurable. Not just you - your manager and your team should know what the goal is. Goals should be revisited every 3 months in your 1:1s. An invisible goal, even when hit, doesn't get told in calibration.

Tied to the exceeds rating. If you hit this goal, can your manager build the exceeds case for you in calibration? If the answer is no, it's the wrong goal. After a meets rating, the goal list should be more aggressive, not more defensive.

Send the goals to your manager in writing. "These are the three goals I'm thinking about for this period - make sense?" Get written feedback. This paper trail both protects you (the year-end review knows what's measured) and gives your manager a story to tell in calibration.

Visibility Strategy - Quiet Work Isn't Enough

The most common manager feedback after a meets rating is this: "Visibility wasn't there." That is, the issue isn't the quality of your work but that others didn't know you were doing it.

Visibility builds in three layers:

Horizontal visibility - will other engineers want to work with you? Are your code reviews high-signal, are your RFCs being read, do you respond to questions in the channel?

Vertical visibility - does your manager's manager know your name? Demo days, all-hands presentations, written reports feed this layer. Your manager representing you isn't enough; sometimes you need to show up in your own voice.

Cross visibility - do other teams (PM, design, data) know you as a reference? Leading a cross-team project or sharing knowledge with another team builds this layer.

A meets rating often comes from gaps in vertical or cross visibility. Horizontal is usually fine (your team knows you), but the manager's manager doesn't. This is a solvable problem; it just requires intentional action.

Practical tip: Build a "demo schedule" at the start of the new period. Every 6 weeks, create an opportunity to present your work to a wider audience - join an existing all-hands, use your team's demo day, write a blog post, share an RFC. At year-end you can say "this period I did 4 demos, three of them to a cross-team audience."

Meets Rating and the Raise

An important distinction: the meets rating affects the promotion decision but doesn't automatically dictate the raise decision. These two are often conflated in Türkiye's software sector.

In most companies the raise structure works like this:

The main portion of the annual raise is inflation and market correction (around CPI)
A performance band sits on top (3-5% for meets, 8-15% for exceeds, 0-2% for below)

If you got a meets, the likely raise scenario is: market correction + a small performance bonus. That's a raise close to inflation. The annual raise negotiation playbook covers it in detail: if you've decided to stay, 8-12 points of real growth on top of CPI is a negotiable target.

You can still negotiate the raise even with a meets rating. Ask your manager: "Suppose I hit my goals for this period and you build the exceeds case. Which band would the raise reference?" This question both clarifies the goal context and creates an internal accountability for your manager to make you a fair offer.

Stay or Leave - The 6-Month Test

The first thing that comes to mind after a meets rating is "should I look elsewhere?" Instead of answering immediately, set a 6-month test.

The test:

Did you have the follow-up conversation above with your manager? Yes/No
Did you clarify this period's goals in writing? Yes/No
Did you set up a visibility strategy? Yes/No
Mid-period, did your manager give concrete feedback? Positive/Vague
Before the year-end review, did your manager verbally confirm the promotion timeline? Yes/No

If at least 4 out of 5 answers are positive, stay and continue. The meets rating was a snapshot from the start of the year; it can change by year-end.

If fewer than 4 are positive, or after 6 months of effort with your manager you still aren't getting direction, start looking for outside offers. The salary impact of changing jobs is a separate post; but "I tried bargaining to stay and got nothing" after a meets rating is the strongest case for rotation.

The difference between rotating immediately and trying for 6 more months is small in the long run of your career; but the outside offer you'll get after 6 more months will be stronger because you'll be leaving as an engineer who hit goals and built visibility post-review.

Three Actions for This Week

If the meets rating landed in the last 2 weeks, do these three things this week:

Schedule a 30-minute follow-up with your manager - have the three questions ready
Build or update your brag document - put what you did last period into a written file (brag document method covered in the performance review post)
Draft this period's goals - tied to output not action, measurable, three goals tied to the exceeds rating

These three steps give the highest return after a meets rating. The next review starts this week - not by next week, but by the steps you take this week.