I Left $38K on the Table at My First Tech Job — Here's the Salary Negotiation Script I Use Now

In 2019, I accepted a junior developer offer for $72,000 without negotiating. Not because I was happy with the number — I knew the range went up to $110K for that role. I just panicked. The recruiter said "we'd like to offer you..." and my brain short-circuited into gratitude mode. I said yes before she finished the sentence.

Over the next 18 months, I found out two things. First, a colleague who started the same week, with similar experience, was making $94K. Second, he'd negotiated for exactly 12 minutes during his offer call.

Twelve minutes. That's what $22,000 per year cost. Or rather, that's what my silence cost me.

Since then, I've been obsessed with salary negotiation. I've coached over 200 tech workers through their offer conversations — backend devs, product managers, DevOps engineers, data scientists. Most of them were in the same place I was: qualified, anxious, and one conversation away from a much better outcome.

Here's everything I've learned, including the exact scripts that work.

Why Developers Are Particularly Bad at This

Let's get this out of the way: if you feel weird about negotiating, you're not weak or ungrateful. You're experiencing something nearly universal in technical fields.

Engineers are trained to solve problems with correct answers. Negotiation doesn't have a correct answer — it has a range of acceptable outcomes, and the conversation feels ambiguous and political. Those aren't adjectives most developers enjoy.

A 2024 survey by Levels.fyi found that 58% of software engineers accepted their most recent offer without any negotiation attempt. Among those who did negotiate, 84% received an improved offer. Read that again: 84% who asked, got more.

The fear is that you'll look greedy or they'll rescind the offer. In reality? I've been on both sides of hundreds of offer conversations. I have never — not once — seen a company pull an offer because a candidate negotiated professionally. It simply doesn't happen at reputable companies. If it does happen to you, consider it a bullet dodged.

The Pre-Negotiation Work (This Is Where Most People Fail)

Negotiation doesn't start when you get the offer. It starts weeks before, and the prep work is honestly more important than anything you say on the call.

Step 1: Know Your Number Before They Ask

Before you apply anywhere, spend an hour researching. Not a vague "I think developers make around $120K" — actual, specific data for your role, your experience level, and your location (or remote market rate).

Here's where to look:

Levels.fyi — Best for verified total compensation data at tech companies. Filter by role, level, and company. This is your primary source.
Glassdoor salary data — Useful for mid-market and non-tech companies. Take with a grain of salt; self-reported data skews lower.
Blind — Anonymous professional network. Compensation threads are blunt and very specific. Great for recent data points.
Job postings with salary ranges — Colorado, Washington, New York, and California require salary ranges in postings. Even if you're not in those states, use those postings for the same roles to calibrate.

Compile at least 5-6 data points for your specific role. You want to build a range: a floor (lowest you'd accept), a target (what you'd be happy with), and an anchor (what you'll initially propose, typically 10-15% above your target).

For example, if you're a mid-level React developer looking for remote roles in 2026:

Floor: $130K (below this, you walk)
Target: $150K (this makes you happy)
Anchor: $165K (this is what you say out loud)

Step 2: Never Give Your Number First

At some point during the interview process — often during the first recruiter screen — someone will ask: "What are your salary expectations?"

This is a trap. Not a malicious one, but a structural one. Whoever names a number first sets the anchor, and anchoring bias is one of the most powerful forces in negotiation. If you say $130K and they were prepared to offer $160K, you just capped yourself.

Here's the script I give every client:

"I'm flexible on compensation and more focused on finding the right role and team fit. I'd love to learn more about the position first and understand the full compensation package before discussing specific numbers. Do you have a range budgeted for this role?"

About 70% of the time, the recruiter will share their range. Now you have information; they don't. That's a good position to be in.

If they push back and insist you name a number, use this:

"Based on my research for this type of role, experience level, and market, I'd be looking at something in the $[anchor] range for total compensation. But I'm open to discussing what makes sense based on the full picture — equity, benefits, growth, all of it."

Notice you're anchoring high and leaving room. You're also framing it as total compensation, not base salary, which gives you more levers later.

Step 3: Create Competing Options

The single most powerful tool in salary negotiation is an alternative. If Company A knows you're also talking to Company B and C, everything changes. They move faster, offer more, and negotiate more flexibly.

You don't need a competing offer in hand — you just need to be truthfully in process elsewhere. Apply to multiple companies simultaneously. Even if you strongly prefer one, having active conversations at others gives you genuine leverage.

I coached a DevOps engineer last year who had an offer from a Series B startup for $145K. She'd been casually interviewing at two other places but hadn't pushed those forward. I told her to accelerate both — schedule final rounds, tell them she had a timeline. Within two weeks, she had a second offer at $155K. She went back to the first company, shared (truthfully) that she had a competing offer, and they bumped to $162K plus an extra week of PTO.

$17K and a week of vacation. Because she didn't stop interviewing after the first yes.

The Offer Call: What to Say (Word for Word)

You've done the research. You know your numbers. The recruiter calls with an offer. Here's the playbook.

Rule #1: Never Accept on the Spot

No matter how excited you are, no matter how good the number sounds, do not accept during the call. Even if it's above your target. You need time to evaluate and respond strategically.

The script:

"Thank you so much — I'm really excited about this opportunity and the team. I'd love to take a day or two to review the full package and come back with any questions. Could you send over the details in writing?"

No recruiter will object to this. It's professional, expected, and buys you time.

Rule #2: Negotiate Over Email When Possible

Email is better than phone for negotiation. Here's why:

You can draft, edit, and perfect your words
There's no pressure to respond in real-time
Everything is documented
You avoid saying something impulsive (like I did with my $72K acceptance)

After receiving the written offer, here's a template that has worked for my clients consistently:

Subject: Re: Offer — [Role Name]

Hi [Recruiter Name],

Thank you again for the offer — I'm genuinely enthusiastic about joining [Company] and working with the [specific team/product]. After reviewing the package and doing some market research, I'd like to discuss the compensation.

Based on my [X years] of experience with [specific relevant skills], and considering current market rates for [role] at [similar-stage companies], I was hoping we could explore a base salary closer to $[your anchor number]. I've seen comparable roles in the $[range bottom]-$[range top] range, and given [specific value you bring — e.g., "my direct experience scaling payment systems, which is a core focus for this role"], I believe that range reflects the value I'd contribute.

I'm also open to discussing other elements of the package — equity, signing bonus, professional development budget, or PTO — if there's more flexibility there.

Looking forward to finding something that works for both of us.

Best,
[Your name]

Notice: it leads with enthusiasm (you want the job), grounds the ask in data (not feelings), highlights specific value you bring (not generic claims), and opens the door to non-salary compensation. Every element is deliberate.

Rule #3: Negotiate Beyond Base Salary

Base salary is just one piece. Especially at remote companies, there are often 5-8 other levers:

Equity / Stock Options — At startups, this can be the most valuable part of the package. Ask about vesting schedule, strike price, and total shares outstanding.
Signing Bonus — Companies sometimes can't budge on salary bands but have discretionary budget for signing bonuses. Ask for $5-15K.
Remote Work Stipend — $1,000-5,000/year for home office, coworking space, internet.
PTO — An extra week of vacation is worth thousands in quality of life and can be easier to approve than salary.
Professional Development — Conference budget, course reimbursement. $2-5K/year is common and rarely denied.
Title — This costs the company nothing but affects your future earning power. "Senior" vs. "Mid-level" on your resume compounds over your career.
Start Date — Negotiating a later start date gives you a break between jobs.
Review Timeline — Ask for a 6-month review with a potential salary adjustment instead of the standard annual review.

One of my clients couldn't get a startup to budge past $140K (their budget ceiling). She negotiated 0.15% additional equity, a $10K signing bonus, $4K remote stipend, and a 6-month salary review. The total package value increased by roughly $35K without touching the base number.

The Hardest Part: What to Say When They Push Back

Sometimes they'll say no. Or more commonly, they'll say "we can't go that high." This is where most people fold. Don't.

A pushback isn't a no — it's the start of the real conversation. Here are the most common pushback lines and how to respond:

"That's outside our budget for this role."

"I understand budget constraints — I appreciate you being transparent. What is the maximum the budget allows? And are there other parts of the compensation package where there might be more flexibility?"

"We pay everyone at this level the same."

"I respect pay equity, and that's actually something I value in a company. Given that framework, could we discuss the level itself? Based on my experience with [specific skills], would it make sense to bring me in at the next level up?"

"The offer is already competitive."

"I agree it's a strong offer, and I'm excited about the role. Based on my research, the current market range for this position is [X-Y], and I'm hoping to be closer to [your number] given [specific reason]. What can we do to close that gap?"

The key in every response: stay warm, stay collaborative, stay specific. You're solving a problem together, not fighting.

Remote-Specific Negotiation: The New Rules

Remote positions add some unique wrinkles to salary negotiation that didn't exist five years ago.

Geographic Pay Adjustments

Some companies (GitLab, Stripe, others) adjust compensation based on where you live. If you're in Boise and the role is benchmarked to San Francisco, you might see a 15-25% reduction.

How to push back: focus on output, not location. "I understand the geographic framework, but I'd note that my output, availability, and the value I deliver are identical regardless of where I sit. Companies like Basecamp and Buffer have moved to location-independent pay for this reason. Is there flexibility in how the framework is applied?"

You won't always win this one, but it's worth trying. More companies are moving toward location-independent pay as the talent market demands it.

The "Total Compensation" Argument

Remote workers save the company money — no desk, no office space, no snacks, no parking. McKinsey estimates the average cost of a physical office seat at $12,000-18,000 per year. You can gently make this case:

"Since this is a fully remote role, the company saves significantly on office overhead. I'd love for some of that savings to be reflected in the compensation package."

Time Zone Premium

If a US company wants you to work their hours and you're in a compatible time zone with strong English skills, that's valuable. If they're asking you to work odd hours to overlap with their team, that's a lifestyle sacrifice worth compensating.

Real Numbers: What Negotiation Actually Looks Like

Let me share three real cases from the past year (details slightly changed for privacy).

Case 1: Senior Full-Stack Developer
Initial offer: $155K base, standard equity
After negotiation: $170K base, $12K signing bonus, extra week PTO
Time spent negotiating: Two emails over 4 days
Increase: $27K+ in year-one value

Case 2: Mid-Level Data Engineer
Initial offer: $128K base
After negotiation: $138K base, $5K remote stipend, 6-month review
Time spent negotiating: One phone call, 15 minutes
Increase: $15K in year-one value

Case 3: Junior Backend Developer (First Job After Bootcamp)
Initial offer: $85K base
After negotiation: $92K base, $3K signing bonus, title bump to "Software Engineer" (from "Associate")
Time spent negotiating: One email
Increase: $10K in year-one value + better title for future negotiations

Even the junior developer negotiated successfully. "I don't have enough experience to negotiate" is a myth. Everyone negotiates. The junior who gets $92K today will negotiate from a higher base for their entire career.

The Compound Effect (Why This Matters More Than You Think)

Here's the math that should motivate you.

Let's say you negotiate $15K more at your next job. Conservative number — most of my clients get more. Assuming 3% annual raises and a job change every 3-4 years where you negotiate similarly:

Over 10 years: ~$180K in additional earnings
Over 20 years: ~$450K in additional earnings
Over a 30-year career: ~$850K in additional earnings

And that's conservative. If you invest the difference? With average market returns, that $15K/year negotiation advantage compounds to well over $1 million in additional wealth over a career.

One awkward conversation. One million dollars. The ROI on learning to negotiate is the highest return on time investment you'll ever find.

Stop Leaving Money on the Table

I lost $38K at my first job because I didn't know any of this. I learned it the expensive way. You don't have to.

The playbook is simple: research your market rate, never name your number first, don't accept on the spot, counter with data and enthusiasm, negotiate beyond base salary, and don't fold at the first pushback.

If you're actively looking for your next remote tech role, start browsing current openings on HireVane — and when that offer comes through, come back to this article. Bookmark it. Screenshot the scripts. Practice them out loud in the shower. Whatever it takes.

Because the difference between people who earn what they're worth and people who don't isn't talent or experience. It's whether they asked.

So ask.

— Written from 11+ years operating wardigi.com and observing how the global tech hiring market has shifted toward distributed teams.