Why asking for a raise in IT is a project, not an emotion
Asking for a raise rarely works as an improvised conversation in the hallway. Successful salary negotiations follow a project structure: preparation, evidence, a scheduled conversation, a clear ask, and a written follow-up. Managers think in terms of budget and role value, not personal circumstances — and that is entirely normal.
What actually drives a salary review decision
Most salary decisions rest on three factors: an expanded scope of responsibility, scarcity of your role on the market, and outcomes the business can see. If at least two are missing, the conversation turns into a personal favour — and those get declined. Your preparation should translate results into measurable arguments and your role into a market-readable position.
Step 1. Collect evidence of your value before the talk
The strongest argument in a salary conversation is not tenure — it is impact. Start with facts: what you shipped, which metrics improved, what would have happened to the project without you. This is not bragging; it is the language your manager uses with finance.
What exactly to write down
- Scope growth: tasks you took on beyond your original role in recent months.
- Measurable impact: what became faster, cheaper, more reliable, or more profitable.
- Complexity: new technologies, integrations, or verticals you learned to serve the team.
- Resource savings: automation, process improvements, bugs prevented in production.
- Mentorship and beyond-project value: onboarding, documentation, code review.
Check our salary benchmarks by role to understand which market references to anchor your request to.
Step 2. Define a realistic market range
A request without market context sounds like a personal wish. Before the meeting, research what similar roles pay in your segment: responsibility level, stack, work format, location. On WEB-HH, for example, there are around 1,897 active vacancies in the digital space, 47% of which offer remote work — a useful reference point for how competitive your role is.
How to build a range and a single number
A professional approach is to name a range and justify a specific number inside it. The floor is the level below which you are not ready to continue under current conditions; the ceiling is a realistic market reference for the role one step above yours. The number you call out should honestly reflect your scope, not the maximum you hope to squeeze out.
Step 3. Prepare a conversation script
A salary conversation is a short business meeting, not an emotional monologue. Prepare a talking track with four blocks: context, facts, the ask, and next steps. This is the same skill as interview preparation — except instead of an external offer, you are defending your position inside the company.
Four blocks and timing
- Context — thank them for the meeting, name the topic, keep the tone calm.
- Facts — a short list of results and expanded responsibility.
- The ask — a specific number or range justified by market data.
- Next steps — what you will own next and when to revisit.
Aim for 20-30 minutes. Anything longer than 40 minutes loses focus and turns into a discussion of daily tasks.
Step 4. How to actually ask, and what to say
One of the biggest mistakes is framing the conversation as a request. Replace the ask with a proposal: "I would like to discuss a salary review given that I have taken on X, Y, and Z." This framing shifts the discussion from "give me" to "let us agree on a fair level."
Phrases that work
- "Over the past months I closed direction, which was not in my original scope — I suggest reviewing my salary accordingly."
- "Based on market data, this responsibility level pays above my current level — I would like to sync on numbers."
- "I want to keep growing the project, so let us fix the next review in N months if tasks X and Y stay with me."
What not to say
Ultimatums and comparisons with colleagues erode trust. "I have a mortgage," "another employee earns more," "I was supposed to get a raise long ago" are weak arguments. They shift the conversation from role value to personal circumstances — not the ground on which salary decisions are made.
Step 5. How to handle a refusal
A refusal is not a permanent no — it is a point to restart from. The professional response is to clarify concrete conditions: what results, timeline, and metrics are needed for the question to return to the table. If the manager says "no budget," ask to fix the conditions under which budget will appear.
Common responses and what to do
| What the manager says | A reasonable reply |
|---|---|
| "No budget right now" | Clarify the timeline and schedule the review for a specific period |
| "Let us wait until next quarter" | Agree on criteria: which tasks must be closed to return with a number |
| "The market is tough" | Anchor on market data for your role, not on the broader economy |
| "You already earn well" | Compare your scope to the market, not to your salary history |
| "Let us discuss next time" | Fix a date and an agenda so the conversation does not dissolve |
If "no" is repeated several times without clear criteria, that is a strong signal that your ceiling is lower than you want. Then the logical next step is to test the external market. Browse affiliate and media buying vacancies to compare your current position with what is offered outside.
Step 6. What to ask for if money is off the table
Sometimes a company genuinely cannot review the salary but is open to improving conditions in other ways. This is not a win, but it is a step toward one. Properly structured non-salary perks often convert into a raise one or two quarters later.
Alternatives that actually work
- A formal role upgrade with expanded responsibility (this changes your market value on paper).
- Flexible or fully remote schedule — a real saving in time and money.
- Budget for courses, conferences, and certifications.
- Extra vacation days or paid days off.
- A fixed review date in writing.
It also helps to study general negotiation principles that apply both to internal talks and external offers — our career guides cover these scenarios separately.
How salary talks differ across IT roles
In IT, the raise conversation looks very different by role: developers defend results through task quality and complexity, media buyers through funnels and traffic profitability, managers through team metrics and process. Grade expectations differ too, so compare yourself with a similar role, not abstract "IT in general."
Grades and role comparison
| Level | What proves your value | How to frame the request |
|---|---|---|
| Junior | Growth speed, tasks closed with mentorship | Ask for a review inside the grade, not above it |
| Middle | Independently owned tasks and their impact | Compare to roles that require autonomy |
| Senior | Architectural decisions, mentorship, roadmap influence | Justify the level through scope and effect |
| Lead / Head | Team, processes, strategic metrics | Discuss base pay together with bonuses and structure |
Levels mean different things at different companies. If you position as middle but deliver senior tasks, that is your strongest argument — not your tenure.
Common mistakes in a raise conversation
Most failed salary talks fail not because of budget, but because of approach. The good news: these mistakes are easy to avoid once you know how your request sounds from the other side of the table.
Checklist before the meeting
- Send the meeting agenda in advance — it respects your manager's time.
- Do not tie the request to personal expenses — only to role value.
- Do not compare yourself with colleagues out loud — compare with the market.
- Never threaten to leave unless you are actually ready to leave.
- Put the outcome in writing — date, conditions, next steps.
If after several attempts you see no real path inside the company, explore remote jobs — many teams now pay market rates regardless of your city. And if you are the one hiring, check the salary benchmarks on the market and review employer pricing plans before setting your offer.
Frequently asked questions
When is the best time to ask for a raise?
The best time is right after a confirmed result: a shipped project, an expanded role, or a completed cycle with measurable impact. Avoid tying the conversation to the end of probation or personal circumstances. Prepare facts and market references one to two weeks before the meeting.
Should I name a specific number first?
Yes — a specific number disciplines the conversation and shows you prepared. But it must be backed by a market range and a clear scope of responsibility. Naming a too-high number without justification weakens your position; naming a too-low number locks you in for a long time.
What if the manager says there is no budget?
Ask under which conditions the budget will appear and when you can revisit it. Request that the criteria and date be written down. If the refusal repeats without clear terms, evaluate the external market — it is a signal of a ceiling inside the company.
Can I use an offer from another company?
You can, but only if the offer is real and you are genuinely ready to accept it. Bluffing almost always gets exposed and damages trust. Using an offer as an argument is legitimate when you honestly say you have received one and want to discuss staying.
How do I ask for a raise on a remote team?
Remote work strips away the "presence" argument, so rely only on measurable results and market data. The format stays the same: schedule a call, prepare a script, name a number. Being remote can even help — the outcome is easier to fix in writing after the call.
What if the raise has been denied for a long time?
Assess whether your market value and scope are growing. If not, time is being lost. Start exploring the external market, refresh your resume, and take a few interviews: this is often how you discover your real market range, and the next internal conversation becomes concrete instead of emotional.