Salary Negotiation for Your First Software Engineering Job

TL;DR

Negotiating your first offer almost never costs you the job. Employers expect it.
Research salary ranges before your first interview, not after you receive the offer.
When asked about expectations early, deflect with a range or ask them to share their band.
You can negotiate without a competing offer. A clear, professional counter is enough.
Base salary isn't the only lever: sign-on bonus, start date, and remote days are all fair game.

Getting your first software engineering offer feels like the finish line. After months of applications, rejections, and technical screens, someone finally said yes. The instinct is to accept immediately before they change their mind.

That instinct is understandable. It's also the most common reason new grads leave thousands of dollars on the table.

Salary negotiation for your first software engineering job feels different from negotiating anything else because the power dynamic seems so lopsided. They have the job. You need the job. What leverage do you actually have?

More than you think. And using it professionally doesn't threaten the offer.

Why You Should Almost Always Negotiate

The fear is that pushing back will make you seem difficult, ungrateful, or risky. Hiring managers hear this concern all the time, and most of them will tell you directly: a candidate who makes a professional counter is not a red flag. It signals that you understand your value and can advocate for yourself. Both of those are things employers actually want in engineers.

The negotiation window closes the moment you accept. You can't revisit base salary six months in because you realized you undersold yourself. The number you agree to also sets the floor for future raises and any performance-based increases that are calculated as a percentage of your current salary.

There is a version of negotiating that does damage: demanding a number 40% above the offer, rejecting a reasonable counter, or making ultimatums before you have full context. That's not what we're describing here. A calm, specific, professional counter-offer doesn't torpedo anything.

The realistic downside in most cases is that the employer says no and you accept the original offer. That happens. The realistic upside is $3,000-15,000 more in your first year's salary and a better starting point for everything that follows.

Research the Numbers Before You Interview

By the time you have an offer in hand, you're negotiating at a disadvantage if you haven't done your research. You need to know the market before the first interview, not after.

The best sources for entry-level software engineering salary data in 2026:

Levels.fyi is the most useful tool for total compensation data, especially at mid-size and large companies. You can filter by role (SWE, SWE New Grad), company, and location. Pay attention to total comp, not just base salary, because the mix of base, bonus, and equity varies significantly.

Glassdoor is less precise but covers smaller companies that don't appear on Levels.fyi. Filter by title and metro area.

LinkedIn Salary (under the "Jobs" tab) is inconsistently populated but sometimes surfaces ranges for specific companies.

Your network. This is underused. People who are one or two years ahead of you in a similar role will often tell you what they're making or at least give you a calibrated sense of ranges. Building those relationships on LinkedIn before you're in an active search pays off exactly here. You're not asking anyone to compromise their employer. You're asking peers what the market looks like.

For entry-level software engineers in 2026, ranges vary significantly by geography and company type:

Big Tech (FAANG and similar): Total compensation typically $170,000-$220,000+ for new grads, with a significant portion in equity
Funded startups (Series B and above): Base salary $110,000-$150,000, equity varies substantially
Mid-size tech companies: $90,000-$130,000 base
Non-tech industries (fintech, healthcare IT, enterprise SaaS): $80,000-$120,000 base
Smaller companies and startups (Seed/Series A): $75,000-$110,000 base, with equity that may or may not be meaningful

These are estimates. The actual range for a specific role at a specific company can differ. Use Levels.fyi and Glassdoor to narrow down to the company and location you're targeting, not just the category.

What to Say When They Ask About Salary Expectations

This comes up in two places: the initial recruiter screen and the offer itself.

On the recruiter screen, the question is often framed as "What are your salary expectations?" or "What range are you targeting?" Your goal is to avoid anchoring yourself too low before you have full context about the role, the company stage, or the full comp package.

There are two approaches that work:

Deflect with a question: "I'm still learning about the full scope of the role. Could you share the range budgeted for this position?" This works more often than people expect. Many recruiters will give you the range, which is genuinely useful.

Give a range based on your research: "Based on what I've seen for similar roles in [metro], I'm targeting something in the range of $[X] to $[Y]. Does that align with what you have budgeted?" Name a range where your real target is in the lower third. If they come back with an offer at the bottom of your stated range, you have room to negotiate up. If they come back well above it, you haven't left anything on the table.

The one thing to avoid: giving a single specific number unprompted when you don't know their range. If you say $95,000 and their budget was $115,000, you've just settled for $95,000.

How to Respond When You Receive an Offer

You don't have to respond immediately. In fact, you shouldn't.

When you receive a verbal offer, the right move is: "Thank you so much. I'm genuinely excited about this. I'd like a day or two to review the full package before I respond. Can you send me the written details?"

This is not a red flag. It's standard. Any recruiter who tells you they need an answer on the spot is applying pressure that isn't real. Written offers with a reasonable review period are the norm.

Review the full package before you counter. Base salary is one component. Also consider:

Annual bonus structure and targets
Equity (if any): number of shares, vesting schedule, strike price
Benefits: health insurance quality matters more than people realize
Start date flexibility
Remote days
Sign-on bonus

Now, write your counter.

The Counter-Offer Script

You're calling or emailing. Phone calls are slightly better because they allow for a real conversation, but email is fine and creates a record. Here's a template that works:

"Thank you again for the offer. I'm very excited about the role and the team. After reviewing the package, I'd like to discuss the base salary. Based on my research and the scope of the position, I was hoping we could get closer to $[target number]. Is there flexibility there?"

That's it. Short. Professional. Specific. Notice what's not in it: no apology, no extended justification, no threats. You're not saying you won't accept without it. You're asking a direct question.

Your target number should be $5,000-15,000 above the offer, depending on the gap between what you were offered and market rate. Going $30,000 above on your first counter isn't strategic; it's likely to cause friction. Going $3,000 above leaves too little room for them to meet you somewhere.

How to Negotiate Without a Competing Offer

This is where new grads get stuck. Every negotiation script you've read online seems to assume you have a competing offer to use as leverage. What if you don't?

You still have options.

Market research is legitimate leverage. "Based on what I've found for similar roles in this market, I was hoping we could get closer to $X" is a real reason, not a bluff. Recruiters know the market. If your target number is in range, the research gives them something to bring back to their hiring manager.

The second point of leverage is genuine interest plus momentum. If you're actively interviewing at other companies, mentioning that is honest and relevant, even without a specific competing offer. "I have a few other processes in progress, but I'm genuinely most excited about this role. I wanted to see if we could close the gap before I get too far into those conversations" gives them a reason to move.

You don't need to manufacture leverage. Ask professionally, state a specific number, and wait. Many initial offers have room built in for exactly this conversation. Having multiple active processes going simultaneously matters here: timing your applications so you're getting to offers around the same time is worth thinking about deliberately.

What's Negotiable Beyond Base Salary

If the base salary is truly fixed, there may still be room elsewhere.

Sign-on bonus. Often easier to get than a base salary increase because it's a one-time cost, not a recurring one. Asking for $5,000-10,000 in a sign-on bonus when they can't move base is a reasonable ask at many companies.

Remote days. If the role is on-site and you'd prefer some flexibility, now is the moment to ask. It's significantly harder to negotiate after you've accepted. Be specific about what you want: "I'd love to discuss whether there's flexibility for one or two remote days per week."

Start date. You may want more time to wrap up current obligations or take a break. Or you might want to start sooner to get moving. Either way, start date is usually flexible and worth discussing if the default timing doesn't work for you.

Professional development budget. Conferences, online courses, certifications. Some companies have standard policies. Others are open to committing to an annual budget in writing.

Title. Less common at the entry level, but if you're being offered a "Software Engineer I" role and your research suggests your responsibilities align with "Software Engineer II," it's worth asking.

Pick one or two items from this list. Negotiating everything at once signals that you're difficult. Negotiating one or two things specifically shows that you've thought about what actually matters to you.

When to Stop Pushing

There's a version of negotiation where you keep countering after a reasonable discussion has resolved. That version does real damage.

Once you've made a counter and they've responded, you have two choices: accept or decline. If they meet you partway, take it seriously. A $5,000 move in your direction on base, plus a sign-on bonus, might actually represent the limit of what they can do. Countering again after a genuine effort from their side creates friction without benefit.

If the final package still doesn't work for you, that's a legitimate reason to decline. Turn it down professionally and honestly. You may cross paths with those people again.

The general guideline: one counter, maybe two if the first one gets a partial response and there's clearly room. After that, you've done what you can. Accept and move on with full commitment, or decline and keep your search going.

After You Sign

Once you've negotiated what you can and accepted an offer, let the negotiation go. Don't arrive on day one still mentally re-litigating whether you could have gotten another $5,000. The number matters, but it's not the whole picture.

The first few months on the job will show you a lot about whether you're in the right place. Compensation bands widen as you grow. The engineers who earn the most over a five-year window aren't necessarily the ones who negotiated hardest on their first offer. They're the ones who built skills and relationships quickly and moved into roles with more scope.

What to expect in your first 90 days as a software engineer covers what comes right after signing: the onboarding process, how to ramp up quickly, and what good looks like in the first three months.

The negotiation conversation takes about five minutes. The research before it takes maybe a few hours. The difference in outcome can be thousands of dollars and a better foundation for every compensation conversation after this one.

New grads aren't in the same position as experienced engineers, and the leverage is genuinely different. But the bar for making a professional counter-offer isn't "do I have a competing offer?" It's "did I do my research and can I make a specific, polite ask?" If the answer is yes, make the ask.

If you're at the stage where you're getting offers and navigating this process, here's how Globally Scoped works for candidates who want structured support through the full job search.

For the full picture on offers and compensation: what software engineers actually make in 2026 covers entry-level ranges by company type. How to research salary before your interview covers where to find reliable data. Equity and RSUs explained for new grads covers the non-base-salary part of your offer. Startup offer vs. big company offer covers how to compare two very different structures. Total compensation: what to actually look at covers the full picture beyond base. And how to know if a job offer is fair covers calibration when you're not sure if your number is reasonable.