Bask Health alone put up 21 of the 86 backend engineer postings on the writecv.ai US board this week. One company making up that much of the feed is not what you picture when you imagine "the market".
This is a snapshot: 86 US postings tagged for backend engineer over the last 7 days, all from a single board. It is not the whole economy. It is still a useful mirror if you read it with that in mind.
One company dominates, everyone else is thinly spread
Here is how the top hiring companies shook out:
| Company | Postings |
|---|---|
| Bask Health | 21 |
| Ramp | 3 |
| mercor | 2 |
| Pavago | 2 |
| Roblox | 2 |
| micro1 | 2 |
| Clubhouse | 2 |
| RemoteJobsOne | 2 |
There were 57 distinct companies across 86 postings. So you get one big cluster around Bask Health, then a long tail of ones and twos.
If you skim feeds casually you might think "everyone" is hiring backend right now. Here it is more like: one company is hiring a lot, and many others are poking at it.
You can feel that in your resume strategy. If you are applying to Bask Health, read every single posting they put up, not just the one you click. Steal their own language back at them. If they say "Platform Engineer, APIs & Workflow Automation" in the sample listings, then "APIs" and "workflow automation" belong in your headline or the top of your summary if you do that work. You are writing into a very specific echo chamber there.
For everyone else, treat each company as a one-off. The odds that a template cover letter or generic "backend engineer" headline matches what they wrote are low.
Remote is real here, but titles are more split than you think
Out of 86 postings, 59 were tagged remote. That is 69. Remote is not a perk in this data, it is the default.
On the non-remote side, 27 listings were onsite or hybrid. The top repeat "locations" for those were "USA" with 12 postings, and then San Francisco, CA, New York, NY, Boston, MA, Seattle, WA, and San Mateo, CA, United States with 2 postings each.
Half of those are just "USA". So if you are trying to guess favoured cities from this set, you cannot. The data is too thin and too vague there.
The titles are more concrete. 38 postings used the word "backend" in the title. 28 used "senior". A few other terms popped up: "platform" in 6, "frontend" in 6, "staff" in 5, "ai" in 4, "principal" in 3, "junior" in 2, and rare terms like "infrastructure", "golang", "security", and "mobile" at 2 each.
If you like a short resume headline, this data gives you a simple move. If you are mid or senior, "Senior Backend Engineer" is doing pure keyword work for you here. Both words are common in the titles. No need to get cute with "Software Craftsman" or "Code Enthusiast" if you care about matching postings.
You can still mention specialities like "platform" or "security", but it helps to keep them as add-ons, not replacements. Something like "Senior Backend Engineer | APIs and platform" maps neatly onto what shows up in titles and in the sample listing from Bask Health for a "Platform Engineer, APIs & Workflow Automation".
Levels: mid is the center, entry is almost a rounding error
The spread by level is pretty blunt: mid sits at 43 postings (half the set), senior at 30, lead at 8, entry at 4, and intern at 1.
You might expect senior to dominate, based on how often you see "Senior" in feeds. Here, mid-level roles are actually the largest bucket.
If you are a few years in and you keep being told you are "not senior enough", you are not locked out just by level. Mid is where half of these roles live.
On the other side, entry and intern together make up 5 postings out of 86. That is barely there. If you are early in your path, this is not a friendly slice of the market.
This should affect how you spend resume space. If you are mid and applying to both mid and senior roles, do not bury your years of experience three lines down. Put a clean, factual line near the top like "5 years building backend APIs" or whatever your real number is. The listing writer is clearly thinking in these buckets. Help them put you in the right one fast.
If you are early, cut anything that smells like apology. No need for "aspiring backend engineer" in the headline. Just use "Backend Engineer" and let your projects do the talking further down. With only 4 entry listings and 1 intern listing in this data, nobody is shopping for humility.
Salaries: wide bands and not much transparency
Salaries were posted in 26 out of 86 listings. That is 30. Most companies kept numbers to themselves.
From the ones that did, the low ends had a median of 180k and the high ends had a median of 265k. The lowest low end was 90k. The highest high end was 600k. That top number is inflated by outlier ranges like "USD 130,000 to 500,000 Year" and "USD 180,000 to 500,000 Year" in the sample listings from mercor.
With only 26 ranges, you cannot build a clean mental model of pay for backend work off this alone. The bands are too wide and the sample is too short.
So I would not anchor your salary line on your resume on these numbers. What you can do is mirror the format. If you want to show progression, writing "Increased base from 90k to 600k across 2 roles" would sound like these postings more than vague claims like "highly compensated".
You can also read the absence of numbers as a small signal. Only 30 of postings show them. When you see a concrete range like "USD 190,800 to 267,100 Year" in the Reddit listing, take that seriously. It is rarer than you might think when you scroll.
The postings behind this article are searchable at https://writecv.ai/jobs?q=backend+engineer
Top comments (1)
The Bask Health number is the part I would act on. 21 of 86 postings from one company means the feed is not the market. It is one hiring push. A generic resume aimed at the feed would really be aimed at Bask Health. Your entry number is the starkest one for me. 5 of 86 for entry and intern combined. That changes how much time an early-career applicant should spend on this board at all.