Software Developer Salary

Bureau of Labor Statistics title: Software Developers

The median software developer salary in the United States is $135,980 per year ($65.38/hour). Salaries range from $82,460 at the entry level to $214,670+ for the top 10% of earners. There are 1,687,890 software developer jobs nationwide. Employment is projected to grow 15.8% through 2034.

Last updated: June 2026 Β· Source: U.S. Bureau of Labor Statistics

Also known asSoftware EngineerSWEProgrammerSDEApplication DeveloperBackend EngineerFull-Stack DeveloperiOS DeveloperAndroid DeveloperMobile DeveloperSREPlatform Engineer
Median Salary
$135,980
per year
Hourly Rate
$65.38
per hour
Employment
1,687,890
jobs in the U.S.

Salary Distribution

10th percentile
$82,460
25th percentile
$105,210
Median
$135,980
75th percentile
$171,980
90th percentile
$214,670

Job Growth (2024-2034)

+15.8%
Much faster than average

Annual Openings

115,200
jobs/year (growth + replacements)

Education Required

Bachelor's degree

Software Developer Career Guide

Interview questions, resume templates, and a career ladder written specifically for software developers.

Software developers write and maintain code that powers everything from websites to embedded systems to AI models. Compensation varies more by employer type than by title β€” a Senior at FAANG, a Staff at a series-B startup, and a Principal at a traditional enterprise can hold the same 8 years of experience and see a $200k+ TC gap. Employers screen hard for data-structures-and-algorithms fluency (LeetCode-style), system design at senior+, and behavioral fit. This guide covers new-grad interviews through senior negotiations, with a bias toward the L4β†’L5β†’L6 promotion window where lifetime earnings are made.

Core Skills Hiring Managers Screen For

Data structures & algorithms
Arrays, hashmaps, trees, graphs, heaps. Big-O analysis. LeetCode 'medium' problems solved live in 20 minutes. Still the primary interview screen at most large companies.
One language mastered deeply
Doesn't matter which. Employers want to see idiomatic, correct code in a language you know well β€” nulls, error handling, memory model, standard library. 'Comfortable in 8 languages' loses to 'expert in 2.'
System design (senior+)
Design URL shortener, chat, feed, rate limiter, ad exchange. Load estimation, storage choices, caching, sharding, consistency vs availability tradeoffs.
Git and code review
Rebasing, resolving merge conflicts, cherry-picking, writing PR descriptions reviewers can approve without context.
Testing discipline
Unit, integration, and end-to-end. Test-driven for new features. Ability to explain what tests you'd write for a given API β€” asked in interviews.
Debugging + observability
Reading stack traces, structured logging, distributed tracing, profiling under load. Separates senior from mid.
Communication and design docs
Writing a design doc that non-engineers can follow. Facilitating cross-team reviews. Increasingly weighted at senior+ levels.

How to Become a Software Developer

  1. 1
    Learn to build things people use
    Bootcamp, CS degree, or self-taught β€” pathway matters less than shipped projects. GitHub with 2-3 real projects beats a certificate every time.
  2. 2
    Grind LeetCode
    150 medium problems minimum before FAANG interviews. Focus on arrays/strings, hashmaps, two-pointers, BFS/DFS, DP basics. NeetCode.io has a good curated list.
  3. 3
    Land the first job
    Aim for a company that lets juniors ship real code, not just JIRA tickets. Startups (post-seed) or big tech grad programs. Avoid consultancies that put you on maintenance.
  4. 4
    Learn system design
    Around year 2-3. 'Designing Data-Intensive Applications' + 'System Design Interview' books. Practice with mock interviewees on Pramp / Interviewing.io.
  5. 5
    Pick a specialty
    Backend at scale, frontend + design systems, ML infra, security, distributed systems, mobile. Specialization compounds pay after L4/senior.
  6. 6
    Change jobs every 2-3 years (early career)
    The single fastest way to raise TC in the first 5-8 years. 20-40% jumps per move are normal. Staying loyal for tenure loses to job-hopping until you're L6+.

Career Progression

Software Engineer I / Junior (L3)
0-2 yrs$95k-$140k base Β· $120k-$180k TC at big tech
  • β€’Ship features scoped by senior engineers, with review on every PR
  • β€’Fix bugs and write tests
  • β€’Learn the codebase; onboard yourself to services and tooling
Next: Software Engineer II after 1-2 years demonstrating independent execution.
Software Engineer II / Mid (L4)
2-5 yrs$130k-$180k base Β· $180k-$300k TC at big tech
  • β€’Own features end-to-end from design to deployment
  • β€’Review PRs from junior engineers
  • β€’Debug production incidents
Next: Senior Engineer β€” the biggest promo in your career, usually 2-4 years to earn.
Senior Software Engineer (L5)
5-9 yrs$170k-$230k base Β· $300k-$550k TC at big tech
  • β€’Design and own systems that span multiple services
  • β€’Mentor L3/L4 engineers; unblock the team
  • β€’Drive cross-team technical decisions with design docs
Next: Staff (technical) or Engineering Manager (people).
Staff / Principal Engineer (L6/L7)
8-15+ yrs$230k-$350k base Β· $500k-$1M+ TC at big tech
  • β€’Own strategy for a technical area across multiple teams
  • β€’Drive architecture that affects the whole org
  • β€’Represent engineering to product, exec, and external audiences
Engineering Manager / Director
6+ (parallel path) yrs$180k-$300k base Β· $350k-$800k TC at big tech
  • β€’Manage 5-15 engineers; hire, calibrate, deliver
  • β€’Own team roadmap and business metrics
  • β€’Interface with product, design, and cross-functional partners

Interview Questions & Answers

5 free questions below. Career Kit unlocks 15 total plus resume bullets for every level.

Q1. Given an array of integers, return indices of the two numbers that add up to a target. (Two Sum)technical
Naive: O(nΒ²) nested loop. Better: one-pass hashmap β€” iterate through the array, at each index i check if (target - nums[i]) is in a hashmap of previously-seen values. If yes, return [previous_index, i]. If no, add nums[i] β†’ i to the map. O(n) time, O(n) space. Explain the tradeoff between the two approaches even if the interviewer only wants the optimal β€” they want to hear you reason about complexity.
Q2. Design a URL shortener like bit.ly.technical
Estimate: 100M writes/day β†’ 1160 writes/sec average, ~5000 peak. Reads dominate 100:1. Schema: {short_code, long_url, created_at, user_id}. Short code generation: base62 of an auto-increment ID (7 chars = 3.5T URLs). API: POST /shorten (auth optional), GET /:code redirects with 301. Storage: 100M/day Γ— 500B β‰ˆ 50GB/day, keep hot in cache. Caching: LRU in Redis for the 20% of URLs getting 80% of traffic. Analytics: separate pipeline (Kafka β†’ data warehouse). Discuss idempotency (same long URL β†’ same short code?), rate limiting, and abuse (spam URLs). Draw the diagram: client β†’ LB β†’ app tier β†’ Redis cache β†’ primary DB (sharded by short_code).
Q3. Tell me about a time you disagreed with your manager or a senior engineer.behavioral
STAR. Pick a technical disagreement where you brought data and the outcome was good regardless of who 'won.' Example structure: (Situation) proposed architecture X for a new feature. (Task) senior engineer pushed back preferring Y. (Action) I built a small prototype benchmarking both under expected load, wrote it up in a doc, brought it back for review. (Result) we picked a hybrid; my prototype revealed a corner case neither of us had spotted. Interviewers screen for: bringing data, not ego; willingness to change your mind; ability to disagree without conflict.
Q4. You get paged at 3am. Prod is down. Walk me through your first 10 minutes.situational
Acknowledge the page (someone else may join, coordinate). Check the alarm and dashboard β€” what's actually broken? Recent deploys in the last 2 hours? If yes, rollback candidate. Check dependencies β€” is upstream (auth, DB, third-party API) also degraded? Assess blast radius: how many users affected, what functionality is down. Post to the incident channel with a status: 'investigating X, symptoms Y, next step Z, will update in 15 min.' Silence isn't a strategy β€” communicate every 15 min minimum. Fix or rollback. Postmortem the next day (not in the moment).
Q5. Why do you want to work here specifically?behavioral
Don't say 'I love the product' unless you can name one specific engineering blog post, open-source contribution, or design doc from their team you actually read and can talk about. Best answers: (1) specific technical challenge their scale involves (X billion writes/day, Y ms p99 latency), (2) a person on the team whose work you follow, (3) a shift you want (product β†’ infra, startup β†’ scale, or vice versa). Do 30 minutes on their engineering blog before you walk in.

Resume Template β€” Software Engineer I / Junior (0-2 yrs)

Copy these bullets into your resume as a starting point. Career Kit includes bullets for every level of the ladder.

Software Engineer I / Junior (0-2 yrs)
  • β–ΈShipped 14 production features across a 400k-DAU consumer app; reduced average PR-to-merge cycle from 3.2 days to 1.4 days for my own PRs by pre-emptively addressing common review comments.
  • β–ΈMigrated the checkout flow from legacy jQuery to React + TypeScript, cutting bundle size by 32% and mobile time-to-interactive by 1.2s.
  • β–ΈOwned the alerting for a Tier-1 payments service; reduced page-worthy false positives by 68% by tuning threshold windows against 6 months of historical data.
  • β–ΈMentored two summer interns; both received return offers and one of my mentee's projects shipped to production.

What Gets You Rejected

  • βœ—Can't code a medium LeetCode problem live in 20 minutes. Immediate DQ at most tier-1 companies.
  • βœ—Big language claim ('expert in 10 languages') without depth in any one β€” interviewers will drill in.
  • βœ—Bad-mouthing previous employers or teams. Screening for judgment and discretion.
  • βœ—Overselling β€” junior engineers claiming they 'architected the system' when they wrote three files.
  • βœ—Ignoring hints during a live coding interview. Interviewers give hints; refusing to take them signals rigidity.
  • βœ—GitHub full of half-finished projects with no README or tests.

Salary Negotiation Levers

  • βœ“Competing offers β€” single largest lever. A single competing offer is worth 15-30% typically.
  • βœ“Levels.fyi data for the specific company and level β€” walk in knowing the band.
  • βœ“Sign-on bonus β€” often more negotiable than base. Ask for $30-80k at big tech senior+.
  • βœ“Equity refresh β€” for existing employees, ask for a refresher grant at year 2 not year 4.
  • βœ“Remote flexibility β€” worth negotiating explicitly, not assuming.
  • βœ“Specialty premium β€” ML infra, security, and compilers tend to command a 10-20% premium.
  • βœ“Level, not just pay β€” negotiating up one level (L4β†’L5) is worth $80-200k in TC over the tenure at that level.

Software Developer Resume Review β€” $29

Personalized resume review from someone who has hired software developers. Purchase, email your resume to support@weblabra.com, and receive detailed written feedback within 7 days.

  • βœ“ Occupation-specific critique (not generic)
  • βœ“ Rewrite suggestions for weak bullets
  • βœ“ Missing skills / keywords flagged
  • βœ“ Formatting + ATS-readability feedback
  • βœ“ 7-day turnaround, 100% refund if we miss it

Software Developer Career Kit β€” $19

  • βœ“ All 15 interview questions with expert answers
  • βœ“ 12 real questions aggregated from Glassdoor, Blind, Reddit, LinkedIn
  • βœ“ Interview format intel for 8 top employers
  • βœ“ 5 copy-paste salary negotiation emails
  • βœ“ Resume bullets for every level of the career ladder
  • βœ“ 30–60–90 day plan for your first role
  • βœ“ Cover letter templates specific to this occupation
  • βœ“ Detailed salary negotiation script
  • βœ“ Ranked list of certifications with cost + ROI
  • βœ“ Downloadable PDF for offline access
  • βœ“ Instant access, no expiration, no subscription
βœ“ 7-day money-back guarantee β€” no questions asked

One-time purchase. 7-day refund guarantee.

Sample reviews β€” real customer reviews will appear here as they come in.

β€œCopy-paste negotiation emails are worth the price alone. I used the 'accepting with counter' template and got an extra $8k signing bonus.”

β€” Anonymous, Software Developer

Software Developer Salary by State

Best Cities (cost-adjusted) β†’

Salary Map β€” Click a state for details

$95K
$174Kβ–  No data

Top Paying States

California
$174K
+28%
Washington
$167K
+22%
New York
$166K
+22%
Massachusetts
$165K
+21%
Oregon
$143K
+5%
New Hampshire
$140K
+3%
Maryland
$139K
+2%
Colorado
$138K
+2%
District of Columbia
$137K
+1%
Virginia
$136K
+0%
Vertical line = national median. Click a state for full details.
StateMedianvs. National
California$174,410+28.3%
Washington$166,540+22.5%
New York$166,180+22.2%
Massachusetts$165,210+21.5%
Oregon$142,720+5.0%
New Hampshire$139,720+2.8%
Maryland$138,680+2.0%
Colorado$138,390+1.8%
District of Columbia$136,880+0.7%
Virginia$136,460+0.4%
1–10 of 50

Software Developer Salary by Metro Area

Metro AreaMedianvs. National
San Jose-Sunnyvale-Santa Clara, CA$213,110+56.7%
San Francisco-Oakland-Fremont, CA$186,640+37.3%
Seattle-Tacoma-Bellevue, WA$167,280+23.0%
New York-Newark-Jersey City, NY-NJ$166,830+22.7%
Boston-Cambridge-Newton, MA-NH$166,090+22.1%
Boulder, CO$164,560+21.0%
San Diego-Chula Vista-Carlsbad, CA$163,270+20.1%
Bridgeport-Stamford-Danbury, CT$162,650+19.6%
Manchester-Nashua, NH$162,090+19.2%
Los Angeles-Long Beach-Anaheim, CA$160,920+18.3%
1–10 of 378
Data Source: U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics (OEWS). Data reflects the most recent annual survey.
How does this compare to pro athletes?
A software developer earning $135,980/year would need 438 years to match Stephen Curry's NBA salary, or 471 yearsto match Patrick Mahomes' NFL contract.
See all sports & celebrity salaries β†’
πŸ“ˆ See how software developer salaries have changed over the past decade.
View Software Developer salary trend (2011–2024) β†’