← All answers
New grads[ The answer engine ]

What salary should I ask for as a junior in 2026?

Matthew LaCrosse

Founder, iRocket Careers

August 5, 2026 · 5 min read
Ask for $72,000–$91,000 base for a junior software role in the US. Total comp at large tech companies runs $100,000–$140,000 with equity. Location and company tier matter more than your script.

The number you should ask for depends on what you are measuring. Base salary? Total compensation? A remote role at a startup or an in-office role at a public tech company? The range is wide — and most new grads anchor on the wrong number, then negotiate from confusion.

Here is the short version: for a junior software engineering role in the United States in 2026, the median base salary sits around $72,000, with most offers landing between $54,000 and $91,000 depending on city, company size, and specialization. At large tech companies, total compensation — base plus equity and bonus — often pushes the figure to $100,000–$140,000 for entry-level engineers.

What the data says

Payscale reports a median base salary of $72,245 for junior software engineers in 2026, with the 10th percentile at $54,000 and the 90th at $91,000. Entry-level engineers with less than one year of experience average closer to $68,000 in total compensation, while those with one to four years move toward the $72,000 midpoint.

The Bureau of Labor Statistics puts the national median for all software developers at $133,080 — but that figure includes mid-level and senior engineers, so it is not a useful anchor for a first offer. Levels.fyi, which tracks total compensation at large tech employers, reports a median of roughly $140,000 for entry-level engineers at companies that grant equity, with a range from $100,000 to $189,500.

$72K
median base salary for junior software engineers in 2026

Payscale

$54K–$91K
base salary range (10th to 90th percentile)

Payscale

$100K–$140K
typical total comp at large tech companies (base + equity + bonus)

Levels.fyi

What moves the number

Three factors separate a $60,000 offer from a $120,000 one. Understand them before you name a number.

  1. Location. San Francisco, Seattle, and New York pay 25–40% above the national median. Austin, Denver, and Chicago cluster closer to the middle. Remote roles vary: some companies pay national rates regardless of location; others adjust for cost of living. Ask which policy they use before you negotiate.
  2. Company tier. Startups often offer lower base but higher equity. Public tech companies (FAANG and equivalents) pay the highest total comp. Mid-market firms cluster around the median. Know which tier you are talking to before you anchor.
  3. Specialization. AI/ML and security roles command premiums of 15–30% above general software engineering. Frontend and QA roles often sit at the lower end of the range. Data engineering and DevOps cluster in the middle.

How to answer the question

When a recruiter asks "What are your salary expectations?" do not blurt a number. Counter with a range tied to data:

"Based on my research, the market range for this role in this city is $72,000–$91,000 base. Given my experience with [specific project], I am targeting the upper half of that range. I am open to discussing total compensation, including equity and benefits."

This does three things: it shows you have done homework, it anchors high but not absurdly, and it opens the door to negotiating beyond base. The recruiter knows you are serious — and that you know the market.

[DO THIS WEEK]

Look up the salary range for your target role in your target city on Payscale, Glassdoor, and Levels.fyi. Write down the 25th, 50th, and 75th percentiles. Pick a target number and practice saying it out loud. Negotiation is a skill, and skills are built through repetition.

FAQ

Should I give a number first?
No — if you can avoid it. The first number anchors the negotiation. If the recruiter insists, give a range based on data, not a single figure. The range should be tight: $72,000–$82,000, not $60,000–$100,000. A wide range signals uncertainty.
What if the offer is below my range?
Ask about total compensation — equity, bonus, benefits. If the total is still below your floor, counter with data: 'Based on my research, the market rate for this role in this city is $X. Can we discuss moving closer to that?' If they cannot, decide if the opportunity is worth the gap. Sometimes it is. Often it is not.
Does remote work change the number?
Yes — but unpredictably. Some companies pay national rates regardless of location. Others adjust for cost of living, which can reduce your offer by 10–20% if you are outside a major tech hub. Ask explicitly: 'How does your compensation policy work for remote employees?' Do not assume.
[SOURCES]

Sources & references

  1. Payscale: junior software engineer salary data Payscale
  2. Levels.fyi: entry-level compensation at tech companies Levels.fyi
  3. Bureau of Labor Statistics: software developer median wage BLS

Verified before publish. We only cite sources we've read.

[THE SIGNAL]

Proof > noise, weekly.

One essay a week on getting hired on proof — not keywords. No spam.

Know the number before the call.

Real roles with salary on every listing — no guessing, no negotiation blind. US-only, nothing older than 7 days.