How to Ask for a Raise in a Tech Job (With a Meeting Script)
When to ask, what evidence to gather and exactly what to say in the meeting, with a word-for-word script for asking your manager for a raise in a tech job.
To ask for a raise in tech, time it 1 to 3 months before your company's review or budget cycle, gather evidence of your impact and market pay, then request a dedicated meeting. Name a specific number, tie it to results and market data, ask what it would take if the answer is no and follow up in writing.
Photo: Unsplash
On this page
You have shipped more, picked up a bigger scope and maybe watched new hires join at salaries close to yours. Yet your pay has barely moved. Asking for a raise feels awkward, so many people wait for the company to notice. Often it doesn’t.
The good news: in tech, compensation conversations are normal, and managers generally expect strong performers to raise them. What separates a successful request from an awkward one is preparation. This guide covers when to ask, how to build your evidence, and a word-for-word script for the meeting, plus what to do if the answer is “not now.”
Why timing matters more than you think
Most tech companies set raises during an annual or twice-yearly compensation cycle. Budgets are usually decided before managers ever sit down for review conversations. If you ask during the review meeting itself, the money may already be allocated.
Better times to ask:
- 1 to 3 months before your company’s review or budget cycle. Your manager can still advocate for you while numbers are being set. Ask your manager or HR when the cycle runs; many companies publish it internally.
- Right after a clear win. A successful launch, a fixed incident or a large customer win makes your impact visible.
- When your role has grown. If you now lead a team, own a system or do the work of the next level, your pay should match.
- When you have credible market data showing you are paid below range.
Times to avoid: in the middle of layoffs, right after a missed deadline you owned or in a hallway chat. Book a dedicated 30-minute meeting instead.
Raise vs promotion: know which one you are asking for
In tech, pay is usually tied to levels with salary bands. That changes the ask:
| Situation | What to ask for | What it usually requires |
|---|---|---|
| Doing your current level’s work well, paid low in the band | Merit raise or market adjustment | Evidence of strong performance and market data |
| Doing next-level work consistently | Promotion with a pay increase | Evidence across your company’s level criteria |
| Paid at the top of your band | Promotion, or equity refresh | Next-level scope, or a retention case |
| Holding a competing offer | Retention adjustment | A real offer you would consider accepting |
If you are near the top of your band, a raise may be capped and a promotion is the real path. Our guide on how to get promoted to senior engineer explains how to build that case. Also remember total compensation: an equity refresh can be easier to approve than base salary. See our guide to stock options vs RSUs.
Gather your evidence
Walk into the meeting with 2 kinds of evidence: what you have delivered and what the market pays.
Your impact
Make a one-page “brag document” covering the past 6 to 12 months:
- Projects shipped and their results (revenue, cost savings, performance, reliability, user adoption).
- Scope growth: systems you now own, people you mentor, cross-team work.
- Problems solved: incidents resolved, technical debt reduced, processes improved.
- Recognition: feedback from peers, customers or leadership.
Use numbers wherever you can (“cut build time from 20 minutes to 8”), but only numbers you can defend. Where you can’t share numbers, describe outcomes clearly.
The market
Market data turns “I’d like more” into “this is what the role pays.” Good sources include:
- Public pay ranges in job postings. Several states now require pay ranges in job ads. For example, New York’s pay transparency law took effect on September 17, 2023, and Washington’s Equal Pay and Opportunities Act requires a wage scale or salary range in postings by covered employers. Postings for similar roles at similar companies are strong evidence.
- Government wage data. The Bureau of Labor Statistics publishes median wages by occupation; for example, it reports a median annual wage of $135,980 for software developers in May 2025. Its OEWS data and CareerOneStop let you compare by state and metro area.
- Crowdsourced salary sites and conversations with peers and recruiters. Treat them as directional, not exact.
Under the National Labor Relations Act, most private-sector, non-supervisory employees have the right to discuss pay with coworkers, according to the NLRB. Those conversations can be a useful reality check. This is not legal advice; supervisors and some other groups are not covered.
Key takeaway: Ask before budgets are set, bring a specific number backed by your results and market data, and make it easy for your manager to advocate for you upward. A raise request is a business case, not a favor.
Decide on your number
Pick a specific figure or tight range, not “more.” To set it:
- Find the market range for your role, level and location.
- Note where you sit today.
- Choose a number that reflects your performance, typically toward the middle or upper part of the range if your evidence is strong.
- Decide your walk-away point privately: what would make you start looking elsewhere?
Asking for a percentage can work, but a dollar figure tied to market data is clearer. If base pay is constrained, prepare alternatives: an equity refresh, a bonus, a title change, a training budget or a committed promotion timeline.
The meeting script
Request the meeting in advance with a clear subject: “Could we set up 30 minutes to talk about my compensation and growth?” No surprises; your manager may want to check budget first.
Opening
“Thanks for making time. I want to talk about my compensation. Over the past year my role has grown a lot, and I’d like to make sure my pay reflects that.”
Your evidence
“Here are the highlights. I led the migration of our payments service, which reduced incidents and cut infrastructure costs. I’ve also taken on mentoring 2 newer engineers and now own on-call for the platform team. I’ve put the details in a short document I can share.”
The market
“I also looked at the market. Comparable roles in our area are posting ranges of roughly X to Y, and my current salary is below the middle of that range.”
The ask
“Based on that, I’m asking for an increase to $X. I’m committed to this team and want to keep growing here.”
Then stop talking and let your manager respond. Silence is fine.
If the answer is yes or maybe
“Great, thank you. What are the next steps, and when should I expect to hear back?”
If the answer is no or not now
“I understand. Can you help me understand what’s driving that? What would I need to show, and by when, for this to happen at the next cycle? Could we write those goals down and check in on them in 3 months?”
Afterward, send a short email summarizing what you discussed and any agreed next steps and dates.
Mistakes that weaken your case
- Using personal reasons (rent, a new car) as the main argument. Keep it about value and market.
- Bluffing about another offer. Only mention a competing offer if it is real and you would take it.
- Comparing yourself to a named coworker. Use market ranges instead.
- Ultimatums in the first conversation. They damage trust and often backfire.
- Accepting vague promises. “We’ll look at it later” should become specific goals with dates.
- Waiting until you are burned out or resentful. Our guide on avoiding burnout in tech covers raising concerns earlier.
Where to start: a 4-week plan
- Week 1: Find out when your company’s comp cycle runs. Start your brag document.
- Week 2: Research market ranges using job postings, BLS data and conversations with peers or recruiters.
- Week 3: Choose your number and alternatives. Practice the script out loud twice.
- Week 4: Book the meeting, have the conversation and send a written follow-up.
If the conversation makes it clear that growth is not possible where you are, it may be time to test the market. Refresh your LinkedIn profile for tech jobs, and when offers come in, use our guides to evaluating a job offer and negotiating a tech salary.
Conclusion
Asking for a raise in tech is a normal, expected conversation when you prepare for it. Time it ahead of the budget cycle, back it with clear evidence of impact and market pay, name a specific number and turn any “no” into concrete goals and dates. Even when the answer is not immediate, a well-prepared ask puts you on your manager’s radar for the next cycle.
Sources
- U.S. Bureau of Labor Statistics: Software Developers, Occupational Outlook Handbook — median annual wage and links to state and area pay data
- NLRB: Your Right to Discuss Wages — employee rights to discuss pay under the NLRA
- New York State Department of Labor: Pay Transparency Law — pay range requirements in job postings, effective September 17, 2023
- Washington State L&I: Equal Pay and Opportunities Act — salary range disclosure in job postings
Frequently asked questions
How much of a raise should I ask for in tech?
Ask for a specific number based on market data for your role, level and location, not a random percentage. If you are below the market middle and performing strongly, asking to move to the middle or upper part of the range is reasonable. Larger jumps usually come with promotions or level changes rather than merit raises within the same level.
When is the best time to ask for a raise?
The best time is usually 1 to 3 months before your company's annual or semiannual compensation cycle, when budgets are still being set. Asking right after a visible win or a clear increase in responsibility also helps. Avoid asking during layoffs or inside the formal review meeting, when raise budgets have often already been allocated.
Should I ask for a raise by email or in person?
Request the meeting by email, then have the actual conversation live, in person or on video. A live discussion lets you explain your case, answer questions and read your manager's reaction. After the meeting, send a short email summarizing what was discussed, your requested number and any agreed next steps and dates.
What do I say if my manager says no to a raise?
Stay calm and ask what is driving the decision and what you would need to show, and by when, to get a raise at the next cycle. Ask to write those goals down and schedule a check-in in about 3 months. If the answer is consistently no despite strong performance, it may be a signal to explore outside offers.
Is it OK to use a competing job offer to get a raise?
It can work, but only if the offer is real and you would genuinely accept it. Some companies match offers for people they want to keep; others will not counter at all. Present it calmly as information, not a threat. Never invent an offer, because it can damage trust and leave you in a difficult position if called.
Can I ask for a raise after 6 months?
You can, especially if your responsibilities have grown significantly or you discovered you were hired well below market. However, many companies only adjust pay during set review cycles, so the result may be a plan for the next cycle rather than an immediate raise. Use the conversation to agree on clear goals and timing.
Can my employer stop me from discussing my salary with coworkers?
Generally not, for most private-sector employees. The NLRB says the National Labor Relations Act protects covered employees' right to discuss wages with coworkers, and employer rules banning those discussions are unlawful. Supervisors and some other groups are not covered by the Act, and state laws may add protections. This is not legal advice.
Was this guide useful
No reviews yet. Share your experience and help other readers.
Write a review
Manishdai
Manishdai writes about the technology that is reshaping every industry — from AI agents and cloud platforms to healthtech, fintech and the IT companies building it all across the United States.
manishdai.com