Year-End Appraisal Guide: 10 Strategies to Get the Rating and Raise You Actually Deserve

Every year, sometime between October and January, something happens in Indian IT offices that produces more anxiety, more resentment, and more career-altering outcomes than almost any other event in the professional calendar. The year-end appraisal cycle.

I've been through fifteen of these as an engineer. I've watched colleagues with objectively better performance get lower ratings than people who were better at the politics of the process. I've seen engineers destroy six months of goodwill with a single poorly written self-evaluation. I've watched the same bell curve produce a 4-rating for someone who did genuinely exceptional work — not because the manager was unfair, but because nobody fought for them in the calibration room.

And I've learned, gradually and sometimes painfully, that the year-end appraisal process rewards not just the people who do the best work — but the people who do good work AND know how to document it, communicate it, and advocate for it at the right moments. This guide is everything I know about that second part.

The Honest Reality of How Indian IT Appraisals Actually Work

Most appraisal guides are written as if the process is a straightforward evaluation of your performance against your goals. In the best-run companies, it is. In most Indian IT companies — including many good ones — it's significantly more complicated. Understanding the actual mechanics helps you navigate them.

The Bell Curve — What It Is and Why It Matters

Most large IT organisations in India — service companies and many product companies — use a forced distribution or bell curve for ratings. This means that regardless of how well the team performed, a predetermined percentage of employees must receive each rating level. A typical distribution might be: 10–15% receive the top rating, 70–75% receive the middle rating, and 10–15% receive the bottom rating.

What this means practically: you are not being evaluated in isolation. You are being ranked against your peers. An engineer who performed at a 4 out of 5 level in absolute terms may receive a 3 rating if there are five other engineers who performed comparably and only two top slots are available for the team.

The Gap Between Rating and Raise

A second reality most guides don't address: in many Indian IT companies, the connection between your performance rating and your actual raise is weaker than you think. Salary increments are often determined by a combination of your rating, your current position in the salary band, market benchmarks, and the company's overall budget — in that order. An engineer at the top of their salary band may receive a smaller percentage increase than an engineer at the bottom, even with a higher rating.

This means your year-end appraisal strategy should have two separate goals: getting the best possible rating (which affects future promotions, visibility, and how you're perceived) and negotiating the best possible increment (which is a separate conversation with its own dynamics). Don't conflate them.

10 Year-End Appraisal Strategies That Actually Change Your Outcome

1 Build Your Evidence File All Year — Not in the Last Two Weeks

This is the most important of all year-end appraisal strategies, and the one that requires the least effort when done continuously but the most effort when left until November.

Every week — five minutes on a Friday — add one bullet point to a running document: what you did, what the outcome was, what the number was if there is one. Over twelve months you'll have 50 bullet points. Your appraisal self-evaluation writes itself. Without this document, you'll spend three evenings in December trying to remember what you did in March — and you'll forget the three things your manager most needs to know about.

2 Rewrite Your Self-Evaluation in Impact Language — Not Activity Language

The single most consistent weakness in engineer self-evaluations is describing what you did rather than what it produced. Activity language tells your manager you were busy. Impact language tells them you mattered.

Notice the formula: what you did + the specific number + the lasting impact. Every bullet in your self-evaluation should follow this structure. If you can't attach a number directly, attach a scope (12 services, 6 team members, 3 months) or a qualitative outcome (became the team standard, used by other engineers, referenced in the post-mortem).

3 Have a Mid-Year Conversation — Before the Appraisal Season Starts

One of the highest-leverage year-end appraisal strategies costs you 30 minutes in July: a direct conversation with your manager about where you stand at mid-year and what you need to do in the second half to achieve the rating you're targeting.

This conversation does two things simultaneously: it signals ambition and self-awareness, and it gives your manager an opportunity to redirect you if you've been focusing on the wrong things. An engineer who has this conversation in July and adjusts accordingly almost always has a better outcome than one who is surprised by their rating in January.

4 Make Your Manager's Job Easy — Give Them What They Need for the Calibration Room

Your manager goes into the calibration meeting armed with information you've given them. Most engineers give their manager a vague impression of good performance. The engineers who get the best ratings give their manager a specific, quantified, narrative-ready case.

In the two weeks before your self-evaluation deadline, send your manager a brief note — separate from the official form — that summarises the three most significant things you contributed this year, with numbers. Not a long document. Three bullet points with evidence. Frame it as "I wanted to make sure you had this context ahead of the appraisal season."

This is not brown-nosing. It's giving your manager the ammunition they need to advocate for you when they're in a room with eight other managers, all of whom also have engineers they want to rate highly.

5 Address Failures Honestly — But With a Systemic Frame

Many engineers either ignore their failures in their self-evaluation (which makes the document look incomplete and self-serving) or over-admit to them in a way that becomes the thing their manager remembers. The right approach is honest acknowledgement with a forward-looking, systemic frame.

That entry acknowledges the failure specifically, takes clear ownership, and shows you turned it into a process improvement. That's the kind of entry that actually builds trust with your manager — more than a document that reads like nothing went wrong all year.

6 Calibrate Your Aspirations Against the Organisational Reality

Before you write your self-evaluation, understand the landscape. How many people are at your level on your team? How many top-ratings slots typically exist for your team's size? What has the historical distribution looked like? What's your manager's track record on fighting for their engineers in calibration?

I'm not suggesting you accept an unfair outcome without pushing back. I'm suggesting that walking into appraisal season with accurate expectations — rather than hopes — makes you a more effective advocate for yourself. If you know there are three engineers at your level and typically two get the top rating, you know you're competing for one slot and you can focus your energy accordingly.

7 Use the Promotion Conversation Separately From the Rating Conversation

If you're targeting a promotion — not just a good rating — have that conversation explicitly with your manager, at least two months before the appraisal cycle. Promotions in most Indian IT companies are a separate decision from ratings, often with separate approval chains and separate budget cycles. Assuming a strong rating automatically leads to promotion is one of the most common and most expensive assumptions engineers make.

This conversation in September or October gives you time to fill any gaps your manager identifies. The same conversation in December is too late.

8 Request and Incorporate 360 Feedback Proactively

Most companies collect 360 feedback as part of the appraisal process. Many engineers treat this as a formality — asking three friendly colleagues to write something positive. The engineers who use it effectively ask colleagues who have directly experienced the impact of their work to give specific, substantiated feedback.

Before the formal 360 cycle opens, reach out to: the product manager you collaborated most closely with, the junior engineer you mentored, and the stakeholder who benefited most from something you built or fixed. Ask them directly: "Would you be willing to provide specific feedback about [specific project or contribution] in the 360 review? I'd particularly appreciate it if you could reference [the specific outcome]." Specific, outcome-focused 360 feedback is significantly more useful in a calibration discussion than generic "great team player" responses.

9 Negotiate the Increment Separately From the Rating Discussion

When your manager presents your rating and your increment, resist the impulse to discuss them simultaneously. The rating conversation and the increment negotiation are separate conversations — conflating them weakens both.

Accept the rating (or push back on it specifically if it's wrong — more on that below). Then say: "I'd like to schedule a separate conversation about the increment, once I've had a chance to review the market data for my role and experience level."

That separate conversation follows the same structure as any salary negotiation — market data, specific contributions, target number, silence. The full strategy is in our complete salary negotiation guide.

10 Push Back on an Unfair Rating — Specifically and Professionally

This is the strategy most engineers are afraid to use, and the one that most often changes outcomes when used correctly. If your rating doesn't reflect your actual performance, you are entitled to ask your manager to explain the reasoning and to present your counter-evidence.

The key is specificity. "I think I deserved a higher rating" is an opinion. "I led the Kubernetes migration, reduced P1 MTTR by 60%, and mentored two junior engineers — here's the specific evidence for each — and I'd like to understand what the delta is between this and the expectations for the rating above" is a professional conversation.

Most managers will have this conversation. Some will change the rating. Some won't — but they'll respect that you took it seriously and advocated for yourself, which affects how they perceive you going forward.

The Complete Self-Evaluation Template for SRE and DevOps Engineers

Here's a structured template you can adapt for your year-end appraisal self-evaluation. Fill in the brackets with your specific examples. Every field should have a number, a scope, or a named outcome — not vague language.

What to Do When the System Isn't Fair

I want to end with something honest, because I think appraisal guides that don't address this are doing you a disservice.

Sometimes the year-end appraisal process is genuinely unfair. A manager who doesn't advocate for you. A calibration process that consistently undervalues infrastructure work relative to product features. A company culture where visibility and politics matter more than technical contribution. A team structure where the engineers closest to leadership get disproportionate credit for collective work.

When this is the situation, the right response is not to fight harder at appraisal time. It's to recognise the structural problem and make a plan to address it — either by changing your positioning within the organisation, building a direct relationship with your manager's manager, or acknowledging that this organisation's appraisal system will never adequately value what you do and planning to find one that does.

The strategies in this guide work in a system that has normal human imperfections — politics, bias, incomplete information. They don't fix a system that is structurally broken. Knowing the difference is its own form of self-awareness, and it's what protects you from spending years fighting for recognition that was never going to come.

Related Guides

After a strong appraisal — negotiating the increment: Our complete salary negotiation guide covers the full increment negotiation strategy — market data framing, the silence tactic, and what to say when they tell you the budget is fixed.

If the appraisal outcome signals it's time to move: Our guide on when timing is everything in a career move covers the 12 signals — including consistently undervalued appraisals — that tell you when a job change is the right response.

Building visibility all year: Our guide on personal branding for DevOps and SRE engineers covers how to make your work visible to the people who make decisions about your career — the internal visibility strategies that feed directly into your appraisal outcomes.

If you're targeting a promotion next cycle: Our interview strategies for experienced professionals covers how to navigate the leadership conversations and strategic thinking demonstrations that senior-level promotions require.