Entry-Level SWE Salary Negotiation Checklist | HireFlow.net

11 min read

You cleared the loops. The recruiter sent base pay, maybe equity, maybe a start date. Your hands are hovering over Accept because you're afraid they'll pull it. I've seen that panic in Greenhouse threads all spring. It's normal. It's also expensive if you don't run a checklist first.

This salary negotiation checklist for US entry-level software engineers turns gut feelings into a short worksheet: written offer, market band, resume proof, one counter email. You don't need a competing offer to ask once, politely, with numbers you can defend.

Negotiation doesn't start on the phone. It starts with the file that got you here. If your internship bullets are buried in a two-column PDF, the recruiter already anchored low. Check your resume for free against the posting you cleared before you counter. A stronger parse score supports a stronger ask.

Below you'll get the data fields to log, when to negotiate, copy-paste email scripts, and edge cases new grads hit (intern conversion, remote bands, scam offers). No hype. Just the sequence I want every entry-level SWE to run before they click Accept.

What does a data-driven salary negotiation checklist for entry-level SWEs cover?

Data-driven here means you write down facts before you argue. Role title, level code on the letter, city band, base, bonus, equity with vest schedule, benefits tier. You compare that row against your minimum and your proof points from internships and projects. Feelings stay off the spreadsheet.

A salary negotiation checklist is the ordered pass you run after the written offer lands, not a speech you give on the first recruiter call. For US entry-level software engineers, the list covers whether to counter, what number to ask for, which email script to send, and how to confirm the final package on paper.

This is not about squeezing a five-person startup that truly has one flat band. It is about not accepting a corporate opener when your file shows production work, a return-intern track record, or a written competing offer at the same level. Know which case you are in.

Your resume and offer letter should tell the same story. If the letter says SDE I but your bullets read like coursework only, the hiring manager will push back on a senior-band counter. Alignment is part of getting hired faster at the right pay, not a side quest.

Recruiter filter: I forward candidates who state one clear number, cite one real project, and sound excited about the team. Rambling emotional appeals get labeled difficult before onboarding starts.

This is not the same as bluffing competing offers or naming a fantasy top-of-band figure with no proof. Read how to negotiate salary without competing offers when you only have one written package on the table.

Step-by-step: data-driven salary negotiation checklist for entry-level software engineers

Step 1: Freeze until the offer is in writing

Verbal numbers on a phone screen are not an offer. Wait for email with base, bonus, equity if any, level, and start date. Read RSU vesting and cliff language. Note whether bonus is guaranteed or performance-based.

Reply within twenty-four hours with thanks and a request for forty-eight to seventy-two hours to review. That pause is standard. Recruiters prefer it over a rushed yes that turns into regret in month two.

Step 2: Build your offer comparison sheet

Open a simple table. Columns: company, req ID, offer date, role level, city, base, signing bonus, equity grant, vest years, cliff months, start date, recruiter name. One row per offer. Entry-level hiring season moves fast. You will forget which version you accepted.

Match role title, city, and company size before you compare dollars. Backend new grad in Austin is not the same band as new grad in San Francisco at a public company. Use the level from the letter when you research.

Write three numbers in the next column: market midpoint for that row, your target counter, and walk-away minimum. If the opener sits below midpoint with no competing offer, counter toward midpoint, not a fantasy ceiling.

Step 3: Align resume proof to the band you want

Recruiters cross-check the counter against internship and project lines. Weak resume text kills your negotiating room even when your interview went well.

Take a composite new grad who interned on a payments API.
Before: "Worked on backend services."
After: "Built REST endpoints in Go handling 2M daily transactions; reduced p99 latency 18% after query tuning."

That second line is what you reference when you ask for a higher base. Open source work, hackathon wins, and return-intern offers count when they are specific and dated on the resume.

Second composite for a bootcamp career switcher:
Before: "Full-stack portfolio projects."
After: "Deployed React and Node app on AWS with CI via GitHub Actions; cut deploy time from 45 minutes to 12."

Fix the resume before you send the counter. Letters cannot invent proof the hiring manager will verify on week one.

Step 4: Decide what to negotiate first

Base salary is the headline. Signing bonus often flexes when base is fixed. Equity may move at growth-stage companies. Start date, relocation, and learning stipends are valid when cash is tight.

Pick one primary ask. Stack multiple asks only when you have a written competing offer at a similar level. Read total compensation vs base salary before you compare two packages with different equity stories.

Step 5: Send the counter email (copy-paste frame)

Replace every bracket. Keep it under one screen.

              {`Subject: Re: [Company] offer – [Your Name]

Hi [Recruiter Name],

Thank you for the offer for [Role] at [Company]. I'm excited about the team and the work on [specific product or team].

Based on my [internship / project] experience with [skill from posting] and current market data for [city] entry-level [stack] roles, I was hoping we could discuss a base salary of [target number]. I'm flexible on start date and happy to discuss the full package.

Could we schedule a brief call this week?

Best,
[Your Name]`}
            

One number. One proof point. One openness signal. No life story. Recruiters forward short counters to comp teams same day when the tone stays professional.

Step 6: Handle the follow-up call

Let them talk first. Repeat their constraint without arguing. "I understand base is tight for this level. Is there room on signing bonus or an earlier equity review?"

Silence for three seconds is fine. You are aligning numbers with someone who runs this playbook every week. Firm and polite beats dramatic.

Step 7: Confirm every term in writing

Do not start onboarding paperwork until the revised offer letter matches what you agreed. Bonus amounts, equity grant size, and start date must match the call.

Save PDFs as Company_offer_2026-03-24.pdf. Attach the same resume version you used when you cite project proof in the counter email.

Copy-paste scripts for common entry-level scenarios

Signing bonus when base is fixed: "If base is set for the new-grad band, could we explore a signing bonus to bridge the gap to [target total first-year comp]? I'm ready to sign once we align."

Competing written offer: "I have another offer at [level] with base [number]. [Company] is my preference. Can we close the gap on base or signing bonus?" Share only real letters. Recruiters verify.

Intern conversion: "During my internship I shipped [feature] which [metric]. I'd like to discuss aligning the full-time offer with market new-hire bands for [role] in [city]."

Draft a short note with the cover letter generator when you need to explain timeline or return-offer interest. Keep metrics identical to the resume.

Edge case: remote vs hybrid location bands

Some employers pay geography bands even for remote hires. If you live in a lower-cost city but the job posts against SF or NYC bands, confirm which geography sets pay before you counter.

Hybrid roles with mandatory office days may include commute costs you should factor into your minimum. Ask about parking, transit stipends, or relocation if you must move cities for the role.

Edge case: offer feels like a scam

Instant offer with no technical loop, pressure to pay for equipment, or crypto-only payment is not negotiation territory. It is fraud screening. Legitimate employers use branded email, named recruiters, and written offers on company letterhead or secure portals.

Walk away before you share bank details. No checklist fixes a fake employer.

Edge case: internship return offer below market

Return offers often anchor to intern pay memory. Counter with market new-hire data for the same level, not last summer's stipend. Reference production work from the internship with metrics in both resume and counter email.

Before: Accept default conversion at 85k.
After: Counter cites two shipped features and external band near 92k for the same level. Recruiter moves to 89k base plus 5k signing bonus. Polite data beats silence.

When not to negotiate

Skip the counter if the package already sits at or above your researched target, if you already accepted in writing, or if the employer stated a truly flat band for all new grads and confirmed no bonus flexibility. One ask is enough. Repeated pushes after a clear no can cost the offer.

Your next click: open the offer PDF, fill the comparison row, and schedule the counter email for tomorrow morning so you send it with a clear head.

Common mistakes entry-level software engineers make when negotiating

Accepting in the first email. Recruiters rarely pull offers because you asked once politely. They expect a counter when the opener sits below band.

Negotiating before the written offer. Early salary questions are screening, not final numbers. Answer with range flexibility until the package is formal.

Countering without a number. "Can you do better?" forces the recruiter to guess. State a specific target backed by your sheet.

Ignoring total compensation. Base alone misleads when bonus, equity, and benefits differ. Run the full row on your spreadsheet.

Resume that does not match the level you claim. Junior bullets plus a senior-band counter triggers hiring manager pushback. Fix the file first.

Skipping written confirmation. Verbal "we'll fix it in payroll" stories fail. Get the revised letter.

Negotiating via text or Slack. Use email for counters so recruiters can forward your number to comp teams with a paper trail.

Align your resume with the offer before you counter

Run HireFlow's free ATS resume checker with the posting you cleared. Fix parsing errors and add posting keywords to internship bullets. Recruiters anchor offers to what the file proves.

Use the cover letter generator when you need a short note explaining return-offer interest or competing timeline. Keep titles and metrics identical to the resume.

Upload a single-column PDF. Paste test in Notepad. If dates scramble, fix layout before you attach the same file to a counter email. A clean parse supports a clean counter.

Run the salary negotiation checklist for US entry-level software engineers before Accept

You do not need drama to boost an offer. You need a written letter, a comparison row, resume proof that matches the level, and one polite counter with a real number.

• Log every offer field in a spreadsheet before you reply.
• Anchor your counter with specific internship and project bullets.
• Confirm every negotiated term on the revised offer letter.

Open your offer PDF, run the free resume check on the file that won the role, and send one data-backed counter today if the number sits below your researched range. That is how entry-level software engineers get hired faster at pay that matches the work they already proved.