Negotiate Tech Salary: Don't Leave Money on the Table
You just nailed the system design, your code compiles, and the hiring manager loves you. They're going to make an offer. This is where most engineers, especially junior and mid-level folks, completely screw up their tech salary. They get excited, maybe a little intimidated, and they forget this is a business transaction. You have a product—your skills—and they want to buy it. Your goal isn't just to get an offer; it's to negotiate your best possible offer. I've been on both sides of this table more times than I can count, and believe me, there's a method to it.
Your Best Weapon: Information
The biggest mistake? Not knowing your worth. You need data, not gut feelings. Glassdoor, Levels.fyi, and Payscale are your starting points. But don't stop there. Talk to people. Find friends, former colleagues, or even LinkedIn connections in similar roles at similar companies. Ask them, "Hey, what's a realistic comp range for a Staff Engineer at a Series C startup in Seattle?" You'll be surprised how many folks are willing to share, especially if you frame it as research for your own career planning. This isn't about gossiping; it's about building a robust understanding of market rates. If you walk in knowing that companies A, B, and C pay $200k-$250k for your role, you're not going to accept $170k from company D without a fight.
The First Rule: Never Give a Number First
This is non-negotiable. Seriously, engrave it on your brain. When they ask for your salary expectations, your immediate response is always: "I'm looking for a compensation package that's competitive with the market rate for this role and my experience. What's the compensation band you've budgeted for this position?" Or, "I'm more interested in learning about the full scope of the role and the company's compensation philosophy before discussing specific numbers." They might push. They might say, "We need a range to see if we're aligned." Hold your ground. Reiterate that you prefer to understand the full picture first. If they absolutely force you, give a wide range, with the bottom end still above what you'd ideally want, and state it's dependent on the full benefits package. For example, "Based on my research, I'd expect a total compensation package in the $200k-$250k range, depending on the benefits, equity structure, and bonus opportunities." This shows you've done your homework without boxing yourself in.
Understand Total Compensation, Not Just Base
A lot of engineers fixate on the base salary. That's a huge mistake. Tech compensation is a three-legged stool: base salary, equity (stock options or RSUs), and bonus. Sometimes there's a sign-on bonus too. A company might offer a lower base but significantly higher equity that vests over four years, making the total compensation (TC) much more attractive. Always calculate the total compensation. For RSUs, divide the total grant value by the vesting period (usually 4 years) to get an annual figure. For options, it's trickier, but you still need to factor in potential upside. Ask about the vesting schedule, cliffs, and refreshers. Are RSUs evergreen? Do they typically grant more stock after the initial grant vests? These details matter for your long-term earnings.
The Counter-Offer: Your Power Play
Once you have an offer in hand, celebrate for five minutes, then get to work. Don't accept on the spot. Always, always say, "Thank you so much for the exciting offer. I need some time to review the details carefully. When would be a good time to connect early next week to discuss it further?" This buys you time.
Now, you formulate your counter. This isn't about being greedy; it's about getting fair market value.
- Identify your target: Based on your research, what's the highest you think you can realistically get? Add 10-15% to that for your opening counter.
- Anchor high: Your counter should be above their initial offer, obviously, but also above what you secretly hope to get.
- Justify your ask: Don't just throw out a number. "Based on my experience leading X project at Y company, and my research into similar roles with comparable scope, I believe a base salary of $Z, plus an RSU grant of $W over four years, would be more aligned with market value and my contributions." Highlight specific skills or experiences they seemed particularly interested in during interviews. Did you build a critical piece of infrastructure they're struggling with? Mention that.
- Consider all components: Maybe they can't budge much on base. Can they increase the sign-on bonus? Boost the RSU grant? Offer a relocation package? Better PTO? Get creative. Sometimes, asking for an extra week of vacation is worth more to your sanity than an extra $5k in base.
I once had a company offer me $180k base, $100k RSUs over four years, and no sign-on. My target was $220k base, $150k RSUs. I countered with $230k base, $200k RSUs, and a $20k sign-on, citing my specific expertise in their legacy system and my track record of delivering complex projects ahead of schedule. They came back with $215k base, $175k RSUs, and a $15k sign-on. That's a significant jump from their initial offer, all because I asked.
The Multiple Offers Strategy (If You Have Them)
This is the ultimate negotiating tool. If you have multiple offers, you have leverage. Don't be afraid to use it respectfully. "I'm very excited about Company A, but I've also received an offer from Company B that includes a higher equity component. Would there be any flexibility on the RSU grant to bring it closer to that?" Don't play games or lie; recruiters talk. But you absolutely can, and should, use competing offers to drive up your compensation. Give them deadlines if you have one. "Company B needs a decision by Friday. I'd love to make a decision on Company A before then if possible." This creates urgency.
However, a word of caution: if you play this game, be prepared to accept an offer if they meet your terms. Don't string companies along just to see how high you can go, especially if you have no intention of joining. That burns bridges, and the tech world is smaller than you think.
The "I'm Not Sure" Scenario
What if you don't have other offers? That's fine. Most people don't. Your leverage then comes from your market research and your value proposition. You're still asking for a competitive package based on your skills and the role's responsibilities, not just what you feel like you deserve. Focus on the value you bring and the specific problems you can solve for them. "My experience with large-scale distributed systems directly addresses the scaling challenges you mentioned during our architectural discussion, and I believe my compensation should reflect that impact."
When to Walk Away
Sometimes, despite your best efforts, a company just won't meet your expectations. They might have rigid bands, or they might simply undervalue your skills. This is where you need to know your walk-away point. What's the absolute minimum total compensation you'd accept? If they can't meet that, you politely decline. "While I appreciate the offer, I've decided to pursue other opportunities that are a better fit for my compensation expectations at this time." It's tough, but sometimes walking away from a lowball offer is the strongest negotiation tactic of all. It also frees you up to find a company that will pay you what you're worth. I've walked from offers that didn't feel right, and every time, I landed something better soon after. Your time and skills are valuable. Don't settle.
Ready to Ace Your Next Interview?
Practice with AI-powered mock interviews tailored to your target role and company. Start Practicing for Free | Explore Interview Prep