# Software Engineer II? 69.3% of Postings Want Senior. Show the Scope

_Software postings are up 34% from the low, but 69.3% are senior. How a Software Engineer II writes bullets that read as senior without changing the title._

- Canonical URL: https://www.refolk.ai/candidates/blog/software-engineer-ii-senior-scope-resume-bullets
- Published: 2026-11-08
- Reading time: 10 min
- Keywords: senior software engineer resume, how to get a senior engineer job without the title, mid level to senior software engineer, software engineer II vs senior resume, software engineer job market november 2026

If your title says Software Engineer II, the rebound in software hiring may not be reaching you. Nearly all of it went to senior roles, and a resume that reads as mid-level gets sorted out of most of the postings that came back.

Indeed's software development postings index closed October at 81.6, about 34% above its May 2025 low, and the November 6 jobs report confirmed that US postings just logged their first year-over-year gain in more than four years. That sounds like your moment. It only is if your bullets read as senior.

## The software engineer job market in November 2026 is recovering, mostly for seniors

Software postings are up roughly a third from the bottom, but in Q1 2026, 69.3% of them were senior-level and only 4.5% were entry-level. The recovery is real. It's aimed at people who can prove senior scope.

The numbers:

- Indeed's US software development postings index (February 2020 = 100) hit **81.58 on October 30, 2026**, up from a **61.1 low in May 2025**. That works out to about +33.5%.
- That's **up 25.4% from 65.06 a year earlier**, but still **65.2% below the February 2022 peak**.
- Indeed Hiring Lab's July 23, 2026 report, "The Labor Market Is Tilting Toward Seniority," found **69.3% of software postings in Q1 2026 were senior**. Across all occupations, only about 14% are.
- Since January 2025, senior-level postings rose **13.5%** while mid-level postings fell **6.7%**.
- Senior roles drove **71% of the increase** in software postings between May 2025 and May 2026. Jobs with AI in the title drove 37%.

> **69.3%** Share of US software postings that were senior-level in Q1 2026
>
> Across all occupations the senior share is about 14%, per Indeed Hiring Lab.

Put the posting mix next to who actually holds which title, and the squeeze is obvious.

| Segment (US) | Count / share | Source |
|---|---|---|
| "Software Engineer II" profiles | 24,242 | Refolk's index |
| "Senior Software Engineer" profiles | 182,927 | Refolk's index |
| Senior-to-SWE II ratio | 7.5x | Derived |
| SWE II profiles listing "System Design" | 59 (0.24%) | Refolk's index |
| Software postings: senior / mid / entry, Q1 2026 | 69.3% / ~26.2% / 4.5% | Indeed Hiring Lab (mid derived) |

Mid-level reqs are about a quarter of software postings, and mid-level postings are falling while senior ones rise. If you hold out for postings at your current level, you're fishing in a shrinking pool. Going from mid-level to senior software engineer is no longer only a promotion question. It's how you get access to most of the open roles.

## Senior is a job description, not a title

Indeed labels a posting senior based on the responsibilities and training it describes, not its title or the years of experience it asks for. Your resume gets read as senior the same way: by the scope it describes.

**Scope** is the size of the problem you were trusted to own. It might be a ticket, a feature, a service, or a system that several teams depend on. A req reads as senior because its text says things like "own the service," "drive technical design," "participate in on-call," and "mentor engineers." Bullets written in those terms speak the same language the req was classified in. The hiring manager then reads for proof behind the words.

So a Software Engineer II whose bullets say "implemented features per spec" gets read as mid-level, however good the engineering was. A Software Engineer II whose bullets say "owned the migration design and led the rollout across three teams" is describing the work the req describes. The title is one line on the page. The scope evidence is everywhere else.

## Your competition is 7.5x bigger and already has the word

In Refolk's index of professional profiles, 182,927 people in the US currently hold the title "Senior Software Engineer," compared with 24,242 titled "Software Engineer II." You won't win senior reqs on title match. You win by showing scope more clearly than the people who are leaning on the label.

Two details make this more winnable than it looks.

First, "II" means something specific at a lot of companies. Microsoft is the most common current employer in Refolk's Software Engineer II sample (a 25-profile sample, so treat it as directional), and it's a good example of a company where II is a formal mid-level rung. There, II describes where you sit on a defined ladder, not a shortfall.

Second, calibration works in both directions. Calibrated companies assign you the level your demonstrated scope supports, and that can land below the label on your resume. A "Senior" title from a small shop with thin bullets gets marked down by the same process that can mark a strong SWE II up. Some of the 182,927 coast on the word. Their bullets are where you beat them.

> The title gets you sorted. The bullets get you leveled. Write for the second reader.

That's the core of the software engineer II vs senior resume question: the senior candidate's advantage is one word, and you can offset it with evidence in every other line.

> **Senior engineering roles open now** - [see the open roles](https://www.refolk.ai/jobs/search?family=engineering&seniority=senior)
>
> Postings labeled senior by responsibilities, the same scope you're writing toward.

## The five scope signals that read as senior

Public engineering ladders from GitLab, Buffer, and Google and Meta's senior benchmarks point to five senior signals: owned decisions, cross-team work, on-call and incident ownership, mentoring, and system design. Each one needs at least one bullet with a concrete artifact behind it.

Where each signal comes from:

1. **Owned decisions.** GitLab's Infrastructure framework describes the senior engineer acting as **DRI for projects**. DRI means directly responsible individual, the single person accountable for an outcome. Buffer's Engineering Career Paths framework places levels by "the scope of influence they have, and the 'ownership' level."
2. **Cross-team work.** Buffer's framework has an explicit SWE II to Senior step, and it measures levels by scope of influence. A bullet that names another team, and what you got them to agree to, shows influence beyond your own.
3. **On-call and incident ownership.** GitLab's senior level **sets the standard for handling on-call rotations**. One public ladder guide puts the gap plainly: IC2 "joins on call," while IC3 Senior "owns a service, drives design, reduces incidents."
4. **Mentoring.** Google's L5 and Meta's E5 are the usual senior benchmark. L5 (Senior Software Engineer) "marks the transition to owning complex systems and mentoring others."
5. **System design.** Public ladders put "drives design" at the senior step. Plenty of mid-level engineers have done design work without ever writing it down. More on that below.

Here's how the same work reads at each level. Fill in the brackets with your real numbers. Never invent them.

| Signal | Reads as SWE II | Reads as senior |
|---|---|---|
| Ownership | Built payment retry logic | Owned payment retries as DRI; cut failed charges [X]% |
| Cross-team | Worked with platform team on auth | Aligned 3 teams on auth migration plan; shipped on [date] |
| On-call | Participated in on-call rotation | Led [N] incident reviews; fixes cut pages [X]% |
| Mentoring | Helped onboard new hires | Mentored [N] engineers; [name or role] took over the service |
| System design | Implemented caching layer | Wrote design doc choosing [A] over [B]; adopted by [team] |

The pattern in the right-hand column is a verb of ownership, then the decision or the people involved, then a result someone could check.

## System design is the cheapest gap to close

Only 59 of the 24,242 US Software Engineer II profiles in Refolk's index list System Design as a skill. That's 0.24%, even though ladders put "drives design" at the senior step. Almost nobody at your level is claiming it, so even a small amount of real evidence stands out.

> **0.24%** US Software Engineer II profiles that list System Design as a skill
>
> 59 of 24,242 in Refolk's index, while senior ladders put "drives design" at the core.

Adding "System Design" to your skills line won't do much on its own. A hiring manager reads a skills list as a claim and a bullet as proof. The design work has to show up in what you did. Things that count:

- **A design doc** you wrote, with the decision it led to.
- **An ADR.** An architecture decision record is a short document recording one technical choice, the options you considered, and why one won.
- **A tradeoff you decided**, such as a queue vs. a synchronous call, and what happened after.
- **A migration plan** you sequenced so other teams could cut over without downtime.

This kind of evidence tends to sit in a wiki page or a pull request description and get forgotten by the time you write a resume. This is the part where [Refolk](https://www.refolk.ai/candidates) helps most: I write your resume from your own history, so the design doc or the incident you ran ends up as a bullet instead of staying buried.

## More postings is not the same as more openings

Total software postings keep climbing, but new software ads fell 6.6% quarter over quarter and software-firm payrolls are still shrinking. A meaningful share of what you see on job boards has been open for a while.

What the latest data shows:

- New software postings (ads from the past week) averaged **82.8 in July to September 2026**, down **6.6%** from April to June, while total postings kept rising.
- Since January 2024, the software industry has lost **92,800 jobs (3.8%)** while total US payrolls grew **2.26 million (1.4%)**.
- CompTIA counted **51,944 new developer/engineer listings**, up 6.3% from September.
- Indeed's November 6 report says **unemployment duration is at its highest level since December 2021**. Indeed economist Cory Stahle: "much of the pain continues to be felt by unemployed workers seeking a way in."

The practical rule: expect a long search, favor postings from the last week, apply early, and treat a req that has sat open for a while as a long shot.

## Software Engineer II vs senior resume: what to actually change

Keep your real title. Change everything around it: the summary line, the verbs, and the order of your bullets so scope comes first. That's how to get a senior engineer job without the title, and without a title that falls apart under calibration.

1. **Keep the title exact.** "Software Engineer II, Microsoft" is what your employment record says. Calibrated companies level you by scope anyway, so an inflated "Senior" buys nothing and costs credibility.
2. **Write a one-line summary in scope terms.** Example: "Backend engineer who owns [service], leads its on-call, and wrote the design for [migration]." The first thing a reader sees should match the req's language.
3. **Lead each role with your biggest-scope bullet.** Ownership and design go above feature work, so the first thing under each role is the evidence that sets your level.
4. **Cover all five signals at least once.** One owned decision, one cross-team bullet, one incident, one mentoring outcome, one design artifact.
5. **Mirror the posting's verbs where they're true.** If the req says "drive technical direction" and you drove it, use those words. Senior postings are defined by that language.
6. **Cut task bullets.** "Wrote unit tests" and "participated in code reviews" read as SWE II by definition. They take space that scope bullets need.

Step 5 is where most people give up, because rewriting the whole resume for every posting is tedious. Refolk handles that: paste the senior posting, and I return your own resume rewritten in its language, plus a fit score. If the score comes back weak on design or incident ownership, the hiring manager will likely see the same gap. Better to know before you apply than after a month of silence.

## FAQ

### Should I change "Software Engineer II" to "Senior" on my resume?

No. Your title is the line an employer can check against your record, and calibrated companies assign the level your demonstrated scope supports, not the one on your label, so an inflated title gets marked down anyway. Keep the real title and let your bullets show senior scope.

### How do I get a senior engineer job without the title?

Show the responsibilities senior postings are classified by. Indeed labels postings senior based on the work they describe, and GitLab's and Buffer's frameworks and the Google L5 benchmark point to owned decisions, cross-team work, on-call and incident ownership, mentoring, and system design. Put at least one concrete, checkable bullet behind each, and prioritize fresh postings over ones that have sat open.

### Is it smarter to apply only to mid-level roles?

It limits you to a shrinking slice. Mid-level reqs are about 26% of software postings, and mid-level postings fell 6.7% since January 2025 while senior postings rose 13.5%. Apply to both. Mid-level roles are realistic matches, and senior roles where your scope evidence is strong are worth the shot, especially since almost nobody at your level documents design work.

### What is the fastest way to move from mid-level to senior software engineer on paper?

Start with system design, because almost nobody at your level claims it: only 0.24% of US Software Engineer II profiles in Refolk's index list it. Find one design doc, ADR, or tradeoff you decided, write it as a bullet with the outcome, and put it first under your current role. Then add an incident you led and someone you mentored.

---

_From the Refolk job search blog. More posts: https://www.refolk.ai/candidates/blog/index.md_
