# The Down-Level Risk Score, Read From Your Resume Before You Apply

*You will score each resume element against your target level, get one down-level risk rating, and know which exact lines to rewrite before you submit.*

- Canonical URL: https://www.refolk.ai/candidates/guides/down-level-risk-score-resume
- Pillar: Positioning and materials
- Format: Framework
- Published: 2026-08-21
- Last reviewed: 2026-08-21
- Reading time: 16 min

Your offers keep coming in a level low, and you suspect the interview is not the problem. This guide is for job seekers who have the experience for the higher band but whose resume, headline, and profile read a level below it, so a recruiter slots them into the lower interview track before anyone talks to them. It gives you a scoring model for each element of your materials, a single down-level risk rating, and the exact lines to rewrite before you submit.

The premise is uncomfortable but well supported: the level is often set before you interview. Leveling decisions are frequently made before the loop, based on your resume and perceived experience, so the document, not the conversation, is your true ceiling. Fixing the interview will not fix a resume that pegs you low.

## Why the resume, not the interview, sets your level

The resume sets your level because a recruiter must convert a flood of applications into a handful of screens in seconds, and they do it by pegging your band off the title before they read a word of scope. A mid-level role receives 150 to 300 applications, narrowed to 10 to 15 phone screens. At that ratio, nobody reads for nuance on the first pass.

The 2018 Ladders eye-tracking study clocked recruiters at 7.4 seconds skimming a resume, with roughly 80% of attention landing on six fixation areas. In that window the reviewer confirms your level, checks your stack, reads one strong bullet, and moves on. The title line does most of the leveling work, and everything below either confirms or contradicts it.

**17 of 20 - Recruiters who named most-recent title as their number one first-scan signal**

The single fastest read of whether you are in the right ballpark for the band.

This is why the resume is load-bearing in a way most guides miss. They score your skills against market demand, or grade your portfolio, or teach you to negotiate level after an offer lands. But the band is frequently locked before the loop, and it cannot be re-set once it is. The place to win a level is in the lines you submit, not the answers you give.

The cost of getting this wrong is not abstract. A one-level miss at a named large-cap is worth six figures a year.

## What a level miss costs

A single level below target costs six figures a year at named large-caps, and that gap is set by level, not by negotiation, so it is not something you claw back at the offer stage. The table below is built from levels.fyi company pages and a leonstaff summary, with gaps derived by subtraction.

| Company | Lower level (median TC) | Higher level (median TC) | Gap |
|---|---|---|---|
| Google | L5 $413,555 | L6 ~$614K | ~$191K |
| Amazon | L4 $187,230 | L6 $412,139 | $224,909 |
| Google | L3 $210,772 | L5 $413,555 | $202,783 |

Being leveled L4 instead of L5 at Google hire can cost more than $100,000 per year. Google pays senior engineers roughly $180K per year less than staff engineers. These are level differences, not negotiation differences, and they compound every year you sit in the wrong band.

> **Rule:** Level is decided once, and before the loop
>
> The band is often set from your resume before you interview, and it cannot be re-set after the loop locks. Score your materials at target before you submit, not after an offer lands.

There is a second reason the higher band is hard to reach: there is simply less of it. The pyramid narrows sharply above senior, so an over-target headline competes against a much smaller real pool, and reviewers default down under ambiguity.

## The talent pyramid above senior

The pool of roles and profiles narrows sharply above senior, which means a headline aimed one band too high competes against a thinner slice of real slots and gets pushed down when the evidence is not airtight. The counts below come from Refolk's index of professional profiles, with ratios derived from those counts.

| Segment | Profiles | Derived vs baseline |
|---|---|---|
| Senior SWE, US | 180,591 | 1.0x |
| Staff SWE, US | 32,302 | 0.18x of Senior |
| Senior SWE, Germany | 15,012 | 0.083x of US Senior |
| Senior PM, US | 27,424 | 0.15x of Senior SWE US |

In Refolk's index there is roughly one Staff software engineer for every 5.6 Senior software engineers in the US. Staff makes up about 15% of the combined Senior-plus-Staff US pool. Fewer higher-band slots means reviewers can afford to default down, which matches the field rule: when in doubt, people will put you at a lower level, and when in doubt, they will not hire you at all.

Market matters too. US Senior SWE supply runs about 12x Germany's in Refolk's index, so the same headline faces very different competition and leveling calibration depending on where you apply. Your down-level risk is partly a function of how crowded your target band is in your target market.

#### Application to locked level

| Stage | Figure | Note |
| --- | --- | --- |
| Applications received | 150-300 | mid-level role |
| Phone screens | 10-15 | pegged at a band on the way in |
| Shortlist to hiring manager | 3-8 | deep technical read |
| Level locked | 1 | band set for the offer |

*Level is pegged early and narrows fast, which is why the title line carries the decision.*

## The five dimensions that peg your level

Five elements of your materials carry the leveling decision: the title line, the trajectory, the verbs, the scope and metrics, and the credibility cross-check. Each proves something specific, and each has a distinct way of lying to the reviewer. Score every one against your target band.

**Title line and headline.** This is the fastest signal and the one that pegs your band. It proves the ballpark. It lies when a strong headline gets you pegged senior but the bullets underneath are thin, producing a title-peg false positive that collapses on the scope scan.

**Trajectory.** Your last three titles in sequence prove growth potential; a candidate showing steady progression signals upside even when current skill is comparable. It lies when senior titles are stacked above a lower target, leaving the reviewer unsure why the role makes sense. A design-associate applicant with prior CMO and Head of Design titles reads as confusing, not impressive.

**Verbs.** The first verb in each bullet encodes scope before the reviewer reaches the metric. It proves ownership versus execution: "owned," "oversaw," and "stewarded" read as most senior and imply you held the outcome without necessarily doing the hands-on work. It lies when "led" or "owned" sits over work that was execution.

**Scope and metrics.** Numbers on team size, budget, and business outcome prove the size of what you ran. Reviewers look for exactly these scope metrics. They lie through the vague-metric mirage: "improved significantly" reads as no metric at all, because words like "significantly" are filtered out by the human brain after a few seconds.

**Credibility.** The match between your title and everything beneath it proves the document is trustworthy. It lies when a reframed title is not earned in the four lines below it, because recruiters compare title against responsibilities, LinkedIn, and references, and a single contradiction taints the whole file.

> The reviewer infers your scope from the verb before they ever reach the number.

## The calibration norms for each band

Each band has a measurable signature in bullet count, verb type, and metric standard, and you score your recent role against the band you are targeting, not the one you currently hold. Bullet counts come from resume-now, verb types from mycvcreator and resumeoptimizerpro, and the metric standard from resumly.

| Band | Bullets/job | Verb type | Metrics |
|---|---|---|---|
| Entry | 3-5 | task ("scheduled," "tracked") | project/coursework ok |
| Mid | 5-7 | ownership ("owned," "led") | 1+ per bullet |
| Senior | 7-10 | accountability ("oversaw," "scaled") | 1+ per bullet, business outcome |

Read the row for your target band and check your most recent role against it. A senior target with five task-verb bullets and no numbers scores as mid, no matter what the title says. A mid target with three coursework bullets scores as entry.

Two named before-and-after rewrites show the calibration in practice. Weak: "Helped the marketing team with campaign planning." The word "helped" tells the reader you were not the decision-maker. Fixed at ownership: "Planned and executed 4 demand generation campaigns targeting mid-market CFOs, generating 280 MQLs in Q3." Same situation, described with ownership and a number.

Weak: "Led cross-functional product strategy sessions." Strong at accountability: "Orchestrated biweekly product strategy alignment across Engineering, Sales, and Customer Success for 18 months, reducing roadmap conflict escalations by 70%." The verb, the duration, the named functions, and the outcome all move the read up a band.

**Bullet rewrite pattern for a target band**

```
[accountability verb] [what you drove] across [named teams or systems]
for [duration or scale], [outcome verb] [metric] by [amount].

Example (senior):
Orchestrated the migration of billing infrastructure across
Payments, Data, and Platform for 14 months, cutting failed
transactions by 62% and saving $1.4M in annual chargeback cost.
```

*Fill each slot from your real work. Verb sets the band; number and outcome defend it.*

Company type shifts the reading of the same signature. Large-cap ladders read scope against defined level rubrics, while smaller companies judge by years or a specific stack and inflate titles. The biggest mistake companies make is tying levels to years, which is a tidy story and mostly wrong. A Senior Engineer at Google carries far more responsibility than the same title at a fifteen-person startup, so translate your scope into the target company's rubric rather than assuming the label travels.

## Score your resume and get one risk rating

Run the seven steps below in order. Each produces a flag or a pass, and the flags add up to your down-level risk rating. Do this before you submit, on the actual document you are about to send.

#### The down-level risk scoring pass

1. **Pin your target band and its rubric** - Name the exact level you want and write the band's bullet count, verb type, and metric standard from the calibration table as a one-line spec.
2. **Score the title line and headline** - Read your most-recent title and headline the way a recruiter does in two seconds and mark at, above, or below target, flagging any label the bullets do not support.
3. **Check the trajectory reads as a straight line** - Look at your last three titles in sequence and flag any drop or sideways move that muddies the "why this level" question.
4. **Score verbs on the recent role** - Underline the first verb in every recent bullet and flag each one that grades below your target band's verb type.
5. **Score scope and metrics** - Flag every recent bullet with no number, no team size, no budget, and delete vague words like "significantly."
6. **Run the credibility cross-check** - Compare title against the bullets and your public profile and flag any claim the evidence does not support.
7. **Tally the score and rewrite the pull-down lines** - Add the flags across all five dimensions into one rating, then rewrite flagged lines in priority order until the document reads at target.

Read the rating like this. Zero to one flag: the resume reads at target, submit it. Two to three flags: moderate down-level risk, fix the flagged lines before you send. Four or more flags, or any single credibility flag: high risk, the document will peg you low, and you rewrite before this posting sees it. A credibility flag is disqualifying on its own because a contradicted claim taints the whole file, not just one line.

The verb and scope scoring is mechanical enough to hand off. Refolk writes your resume from your own history and tailors it to every posting, which means it fits the verb and metric standard to the band each specific role is hiring for rather than a generic senior template. Use [Refolk](/candidates) when you are applying across bands and cannot hand-tune every draft.

#### Title strength against evidence strength

Horizontal axis runs from Weak evidence (thin bullets) to Strong evidence (scoped, quantified). Vertical axis runs from Under-target title to At-target title.

| Quadrant | What it means |
| --- | --- |
| Under-titled, thin | You read a level low; raise the title and add scope together. |
| At-target title, thin evidence | Title-peg false positive; earn the label in four bullets or get down-leveled on the scope scan. |
| Under-titled, strong scope | Undersold; your bullets prove the band your title hides, so fix the title line. |
| At-target title, strong evidence | Reads at target; submit. |

*The document only reads at target when the title and the lines beneath it agree.*

## How this goes wrong: the failure modes

Most down-level misses trace to one of seven predictable failures, and each has a specific check. Work through them on your actual document, because these are where a truthful resume still reads a band low.

**Title-peg false positive.** A strong headline pegs you senior, but thin bullets contradict it on the scope scan. Check: does each recent bullet name team size, budget, or a number? If not, the peg will not survive.

**Inflated-title downgrade.** You reframe a title without earning it in the lines below. Calling yourself a Product Manager when the record says Business Analyst is defensible only if the bullets make it obvious; if they read "gathered requirements" and "produced reports," the title contradicts your own evidence and you have made things worse. Check: read the four bullets under the title and ask whether they prove the label.

**Verb inflation.** "Led" or "owned" sits over work that was execution. The distinction is accountability versus execution. Check: can you name the specific decision you owned? If not, drop to an honest verb.

**Vague-metric mirage.** "Improved significantly" reads as no metric because the brain filters "significantly" out after a few seconds. Check: replace with a number or delete the claim.

**Trajectory misread.** Senior titles stacked above a lower target confuse the "why this level" question. Check: is the progression legible as a straight line toward the role?

**Cross-company scope mismatch.** Startup scope reads thin against big-tech rubrics, and big-tech experience gets discounted for slow process at startups. A big-tech Senior SWE often targets SWE II or Senior at a Series A or B startup. Check: translate your scope into the target company's rubric before you submit.

**Removing an inflated title entirely.** Deleting a title to hide inflation creates a record mismatch worse than the inflation, because it will not match your employment record. Check: keep the official title and add a scoping parenthetical rather than erasing it.

> **Watch out:** Inflation is cross-checked, not taken on faith
>
> Recruiters compare your title against your responsibilities, LinkedIn, references, and background checks. A claim your own bullets contradict raises questions about the whole document, so a title you cannot defend costs you more than the level it was reaching for.

The most common self-inflicted wound is the honest one: about 1 in 4 workers admit to inflating, and 23% specifically inflated responsibilities, per a 2025 Career.io survey of 1,000 workers. You do not need to inflate to read at target. You need to describe real scope with the verbs and numbers the target band uses, which is a calibration problem, not a lying problem.

## Calibrate against people already at your target level

The fastest way to know whether your materials read at target is to look at people who are already in the band and see how they describe the same scope. This is a calibration read, not a copying exercise: you are matching your verb type, metric density, and scope language to what the higher band actually shows.

Look specifically at people who made the move you are making, at the company type you are targeting. Their resumes will show you how big-tech scope gets translated into startup rubrics, or how a promotion from senior to staff was described on the way up. Refolk searches its index of professional profiles by exactly these attributes, so you can pull a live sample of people at your target band and study how their most recent role is written.

Ask me this: `Senior software engineers in the US with resumes showing team-size and budget ownership on their most recent role` - [run the search](https://www.refolk.ai/start?q=Senior%20software%20engineers%20in%20the%20US%20with%20resumes%20showing%20team-size%20and%20budget%20ownership%20on%20their%20most%20recent%20role).

*Returns senior profiles whose recent bullets name team size and budget, so you can calibrate your own scope language against people already read at the band.*

Compare their most recent role to yours line by line. If their bullets name team size and yours do not, that is a scope flag. If their verbs run to "oversaw" and "scaled" and yours run to "helped" and "supported," that is a verb flag. The gap between their calibration and yours is your down-level risk, made concrete.

## Before you submit: the final check

Run this checklist on the exact file you are about to send, for the specific band you are targeting. Every item is a pass-or-fail statement, not a topic, and any fail sends you back to the rewrite step.

#### Down-level risk clearance

- [ ] My most-recent title pegs at target and the four bullets beneath it earn the label.
- [ ] My last three titles read as a straight line toward the target level.
- [ ] Every recent bullet leads with a verb at or above my target band's verb type.
- [ ] Every recent bullet names a number, team size, or budget, with no vague "significantly."
- [ ] My recent role has the bullet count my target band expects (5-7 mid, 7-10 senior).
- [ ] No claim in the document is contradicted by my own bullets or my public profile.
- [ ] I kept every official title and added scoping parentheticals rather than deleting any.
- [ ] My scope is translated into the target company's rubric, not my current employer's.

Keep this scoring pass current, because your target band is a moving frame, not a fixed one. Each time you apply a level up, or across a company type, re-pin the rubric in step one and re-run the pass, since the calibration norms and the pool depth differ by band, market, and company size. The document that read at target for a large-cap senior role may read a level low for a startup lead role, and only a fresh pass will tell you which lines to move.

The payoff is worth the discipline. Level sets the band, the band is worth six figures a year at the top of the market, and it is decided from your resume before you ever speak to anyone. Score the document, fix the pull-down lines, and you change which interview track opens, not just how well you perform inside it.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/candidates/guides/down-level-risk-score-resume*