Backend Engineer job market, August 2026

Which skills postings mention

Share of the 198 Backend Engineer postings we have read that name each skill. Ranked by how often it appears, not by how important anyone thinks it is.

These are mentions, not requirements. Our extraction returns one list per posting and does not separate “5+ years required” from “a plus”, so both are counted here. Read a percentage as how often a skill comes up, never as how often it is mandatory.

From 211 postings (45.9% of this role) whose full description we have read. That subset was selected by our job-matching system rather than at random, so treat this as describing the subset rather than the whole market. Why.

1. 1python39.4%
2. 2aws36.9%
3. 3distributed systems30.3%
4. 4kubernetes29.3%
5. 5postgresql28.3%
6. 6go23.7%
7. 7rest apis21.7%
8. 8docker19.7%
9. 9gcp19.2%
10. 10microservices18.7%
11. 11java18.2%
12. 12ci/cd17.2%
13. 13redis16.2%
14. 14sql15.2%
15. 15typescript15.2%
16. 16nodejs14.6%
17. 17kafka13.1%
18. 18backend engineering11.6%
19. 19terraform11.1%
20. 20api design10.6%
21. 21graphql9.6%
22. 22llm9.6%
23. 23grpc9.1%
24. 24observability9.1%
25. 25azure8.6%

python leads at 39.4%, then aws at 36.9% and distributed systems at 30.3%. A skill appearing in a third of postings is worth learning; one appearing in 5% is worth knowing exists.

How much experience is expected

The seniority mix below covers all 460 postings. Among the ones we have read, half of those stating a number ask for 5+ years, and the middle 50% sit between 4 and 6.

1. 1Senior48.3%
2. 2No level in title27.6%
3. 3Staff17.8%
4. 4Lead2.4%
5. 5Principal1.5%
6. 6Director+1.1%
7. 7Entry level / junior0.7%
8. 8Internship0.4%
9. 9Manager0.2%

What it pays

Annual base ranges as stated by employers. Read the caveats at the bottom before quoting any of these — the disclosing minority is not a random sample.

From 211 postings (45.9% of this role) whose full description we have read. That subset was selected by our job-matching system rather than at random, so treat this as describing the subset rather than the whole market. Why.

Where the jobs are

Share of postings by metro. Postings we could not place to a metro are not counted here, so these shares describe the located subset.

1. 1Remote28.7%
2. 2New York, NY11.7%
3. 3San Francisco, CA9.8%
4. 4Silicon Valley, CA6.5%
5. 5Other — CA3.7%
6. 6Seattle, WA2.8%
7. 7Dallas, TX2%
8. 8Chicago, IL1.7%
9. 9Austin, TX1.5%
10. 10Boston, MA1.5%
11. 11Other — VA1.3%

Remote, hybrid or on-site

41.7% of these postings are explicitly remote and 10.9% are explicitly on-site. A large "not stated" share is normal — many descriptions simply never say.

1. 1Remote41.7%
2. 2Not stated30.3%
3. 3Hybrid17.1%
4. 4On-site10.9%

From 211 postings (45.9% of this role) whose full description we have read. That subset was selected by our job-matching system rather than at random, so treat this as describing the subset rather than the whole market. Why.

Who is hiring

Employers with the most open Backend Engineer postings this month. The number beside each is their posting count.

• Brightvisiontechnologies17
• Coupang11
• Stripe11
• Verkada11
• Gitlab9
• Coupang8
• Launchdarkly8
• Polymarket7
• Kalepa6
• Lemonade5
• Grafanalabs4
• Scribe4
• Sphinx Defense4
• Altruist3
• Bedrock Talent3

Visa sponsorship

30.7% of Backend Engineer postings sit at employers that appear in US government H-1B approval records for the last three fiscal years. That is a property of the employer, not a promise about this role.

Employers hiring most for this role who appear in those filings:

• Brightvisiontechnologies17
• Stripe11
• Verkada11
• Launchdarkly8
• Kalepa6
• Lemonade5
• Altruist3
• Comcast3
• Foratravel3
• Reddit3
• Tatari3
• Airbnb2

A further 1.1% of these postings are at employers whose job descriptions state that they sponsor, but which we could not find in the approval records. That is a weaker signal, so we count it separately rather than adding it to the figure above. It may simply mean the employer sponsors under a different legal name.

Separately, 1.4% of these postings require a security clearance, which in practice means US citizenship. If you need sponsorship, that slice of the market is closed to you regardless of the employer’s history — worth filtering out early rather than discovering at the final stage.

How to prepare, based on the above

Nothing in this section is generic advice. Every line is read off this month's numbers for this role.

1. Learn python, aws, distributed systems first. They appear in 39.4%, 36.9% and 30.3% of postings respectively. Anything below roughly 10% on the list above is a differentiator, not a prerequisite — useful once the top of the list is solid, and a poor use of your time before that.
2. Expect to be asked for 5 years. A stated minimum is a filter, not a rule, and the 4-year figure at the 25th percentile is the realistic target for the most reachable quarter of this market. Apply to those before the ones asking 6+.
3. Apply to far more postings than feels reasonable. With 1.1% of postings open to entry level, the addressable market for a new graduate this month is roughly 5 postings nationally. That is a volume problem before it is a quality problem.
4. Anchor on $156k–$217k when pay comes up — the middle half of disclosed ranges. Below the 10th percentile of $110k you are being underpaid relative to what employers in this corpus publish for the role.
5. If you need sponsorship, start from the employer, not the posting. 30.7% of this role’s postings are at companies that appear in H-1B approval records. Filtering by employer history first is a far better use of your time than applying broadly and asking later.