How to Ask for a Raise in Tech: What to Prove Before Having the Conversation

Asking for a raise can feel uncomfortable, especially in the tech industry, where career growth is often connected to projects, results, technical skills, and the ability to bring value to the team. However, this conversation should not be based only on “I think I deserve more.” It should be supported by clear evidence of what you have achieved, how you have grown, and why your contribution has a real impact on the company.

In tech, salary is usually connected to more than years of experience. It also depends on the quality of your work, your autonomy, your ability to solve problems, your technical knowledge, your communication with the team, and the way you contribute to a project’s success.

That is why preparation is the most important step before asking for a raise.

Do not start with salary, start with value

Before talking about money, ask yourself: what value am I currently bringing to the team?

A raise should be supported by concrete results. It is not only about saying that you work hard or have more responsibilities. It is about showing how your work has helped the team, the project, or the client.

For example, you can show value if you have:

• Improved the performance of an application.
• Reduced bugs or production issues.
• Optimized internal processes.
• Automated repetitive tasks.
• Improved code quality.
• Supported other developers on the team.
• Delivered important features on time.
• Participated in relevant technical decisions.
• Learned a new technology and applied it to a project.
• Contributed solutions that improved the client or user experience.

The more specific you are, the stronger your case will be.

Show impact with data

In tech, data can help you tell your professional story more clearly. You do not need perfect metrics, but you should have clear examples of how your work created improvement.

Instead of saying: “I improved the system.”
You can say: “I optimized a query that reduced response time from 4 seconds to 1 second.”
 

Instead of saying: “I have worked a lot on the project.”
You can say: “I contributed to the delivery of 6 key features in the last 3 months, including authentication, external API integration, and improvements to the reporting module.”

Some data you can prepare includes:

• Features delivered.
• Critical bugs solved.
• Time reduced in processes.
• Performance improvements.
• Time saved for the team.
• Reduction in incidents.
• Participation in strategic projects.
• Positive feedback from clients, leaders, or teammates.
• New responsibilities assumed.
• Technologies learned and applied.

Data makes the conversation more objective and less emotional.
 

Show technical growth

In the tech industry, continuous learning is part of the job. Before asking for a raise, you should also be able to show how you have grown technically.

This may include new skills, tools, languages, frameworks, certifications, or best practices that you did not handle before and now apply in your daily work.

For example:

• You learned a new framework.
• You improved your cloud knowledge.
• You started working with CI/CD pipelines.
• You deepened your database knowledge.
• You improved your testing practices.
• You learned about security.
• You participated in code reviews.
• You improved your documentation skills.
• You took more responsibility in architecture or technical decisions.

It is not enough to say, “I have learned a lot.” Ideally, explain how that learning turned into better results for the team or project.
 

Talk about autonomy

A key sign of growth in tech is autonomy. If you previously needed a lot of guidance and now can solve tasks more independently, that is also part of your value.

You can show autonomy when you:

• Take ownership of complete tasks.
• Propose solutions before asking for help.
• Identify technical risks.
• Follow up on your deliverables.
• Communicate blockers on time.
• Help define better ways of working.
• Work with less supervision.
• Understand the business context, not only the code.

Companies value people who do more than execute tasks. They value professionals who understand problems, propose solutions, and help the team move forward.

Prepare examples of collaboration

In tech, work does not happen in isolation. Even if you have strong technical skills, it is also important to show that you know how to collaborate.

Before asking for a raise, think about moments when you contributed to the team beyond your individual tasks.

For example:

• You helped a teammate solve a problem.
• You explained a technical solution to the team.
• You actively participated in code reviews.
• You improved project documentation.
• You shared learnings or best practices.
• You supported the onboarding of new team members.
• You communicated effectively with QA, PMs, designers, or clients.
• You helped prevent errors before they reached production.

A strong tech profile does not only write code. It also communicates, collaborates, and contributes to the team’s growth.

Choose the right moment

Timing matters. A raise conversation may be stronger after an important delivery, a positive performance review, a clear project improvement, or a period where you have taken on new responsibilities.

Avoid starting the conversation during high-pressure moments, critical deliveries, major internal changes, or difficult company situations.

Good moments may include:

• After completing an important project.
• During a performance review.
• After taking on new responsibilities.
• After receiving positive feedback.
• Once you have shown consistent results over time.
• Before annual budget planning, if you know that cycle.

Asking for a raise is not only about being right. It is also about knowing when and how to present your case.

How to structure the conversation

A good conversation should be clear, professional, and direct. You do not need to sound aggressive or too hesitant. The best approach is to speak from facts.

You can structure it this way:

• Thank your manager for the time.
• Explain that you want to discuss your growth and compensation.
• Summarize your current responsibilities.
• Present your main achievements.
• Share specific data or examples.
• Explain how you have grown technically.
• Mention the range or adjustment you are looking for.
   

Ask about the next steps.

An example could be: “I would like to talk about my growth within the team and review my current compensation. Over the last few months, I have taken on new responsibilities, contributed to key deliveries, and helped improve project processes. I prepared some specific examples of my impact, and I would like to evaluate whether there is an opportunity to adjust my salary based on my current responsibilities and growth.”

What to avoid when asking for a raise

Just as it is important to know what to say, it is also important to know what to avoid.

Avoid:

• Comparing yourself directly to coworkers.
• Basing the conversation only on personal needs.
• Arriving without concrete examples.
• Threatening to resign.
• Using a complaining tone.
• Asking for a raise without knowing your impact.
• Improvising the conversation.
• Talking only about years of experience without results.
• Mentioning external offers aggressively.
• Treating a negative answer as final.

The conversation should focus on your value, growth, and contribution.

Use your performance review as a starting point

A good opportunity to talk about a raise may come after your performance review. This space is already designed to discuss your growth, results, responsibilities, and areas where you can continue improving.

If you received feedback in your previous review about specific areas, such as improving communication, strengthening a technical skill, becoming more autonomous, or participating more in project decisions, you can use those points as part of your preparation.

The key is to show that you listened to the feedback and worked on improving. For example:

• If you were asked to improve communication, you can show how you started reporting progress more clearly.
• If you needed more autonomy, you can explain tasks or projects you now manage with less supervision.
• If you had to strengthen a technology, you can mention how you learned it and applied it to the project.
• If you were encouraged to improve documentation, you can show concrete examples of documentation that helped the team.
   

This shows professional maturity, learning ability, and commitment to your growth. You are not only asking for a raise; you are showing that you took action, evolved, and brought more value since your last review.
 

You can also ask directly what expectations you need to meet to move to the next salary or career level. That way, if the raise does not happen immediately, you can leave the conversation with a clear plan, specific goals, and a date to review the topic again.
 

What to do if the answer is no

Getting a “no” does not mean the conversation failed. It can be an opportunity to understand what you need to prove to earn that raise in the future.

You can ask:

• What goals should I meet to be considered for a raise?
• What skills do I need to strengthen?
• What expectations does the company have for my level?
• Can we review this again in three or six months?
• Can we define a growth plan?
• Are there other benefits or responsibilities we can discuss?
   

The important thing is to leave the meeting with clarity. If there is no immediate raise, try to get a concrete plan with goals, dates, and expectations.

Keep growing with Rootstack

Asking for a raise in tech does not start on the day of the conversation. It starts much earlier, with the way you work, learn, collaborate, and document your impact.

At Rootstack, we share content, tips, and resources for developers who want to keep growing in their careers. Follow us on social media to stay updated with new blogs, events, webinars, professional recommendations, and opportunities for tech talent.
 

Explore our open positions

If you are looking for a new professional challenge, you can also explore our open positions. At Rootstack, we connect tech talent with challenging projects, collaborative teams, and growth opportunities.

Review our available roles and apply to the position that best matches your experience, skills, and interests.
Your next professional step can start with a well-prepared conversation.