How do I know what level I should apply to in tech?

Match four resume signals (titles, scope language, bullet verb shape, last reporting line) to four JD signals (verbs, scope, team size, reporting chain). Apply to roles where the four signals match. Roles a level above stretch the match; roles a level below trip the seniority filter.

What if my titles say senior but my work was mid-level?

Apply at the level the work supports, not the level the title claims. Hiring managers read the bullets; if the bullets describe mid-level work, the senior title alone will not carry you past the technical interview anyway. Apply where you can pass the interview, not where the title nominally fits.

Should I apply to roles a level above my current title?

One level above is a reasonable stretch if your bullets show scope at that level (architecture decisions, cross-team work, mentoring). Two levels above is a long shot and usually fails at technical interview. Apply where the gap is closeable.

How do title compressions across companies affect rung targeting?

Engineering and PM titles compress 1–2 levels across companies. A "Senior" at a Series-B may equal "Staff" at FAANG. Pick rungs by the actual altitude (read JD signals), not the title label, when applying across companies.

How to know which rung to apply to in tech — the level-targeting framework

Apply too high and your resume reads junior. Apply too low and the seniority filter trips. Here is the framework: read your altitude, read the role altitude, and pick the rung where they match.

The single most common applicant-side mistake in tech: applying to the wrong rung. Apply too high and your resume reads junior; apply too low and the seniority filter trips. Either way, no callback.

The framework that fixes it: read both your altitude and the role altitude on the same four-signal scale, then apply where they match.

The four-signal altitude scale

For both your resume and any JD:

Verb shape. What kind of verbs dominate the bullets/responsibilities — execution or strategic.
Scope. How many surfaces, systems, or teams are touched.
Team size. How many people are referenced (yours, theirs).
Reporting chain. Who you report to (yours), who the role reports to (theirs).

Score each on the same five-rung scale: junior, mid, senior, staff/lead, principal/director.

Your resume altitude

Score each of the four signals from your resume:

Signal	Score guide
Verb shape	70%+ execution = mid-senior IC. 70%+ strategic = staff+/lead. Mixed = senior IC.
Scope	One feature = mid IC. One surface = senior IC. Multi-surface = staff/lead. Org-wide = director+.
Team size	Solo = mid IC. 1–4 implied = senior IC. 5–12 = lead. 12+ = director.
Reporting line	Reports to TL = mid. Reports to EM = senior IC. Reports to Director = staff. Reports to VP = staff+/director.

Take the average. That’s your resume’s altitude.

The role’s altitude

Same four signals on the JD:

Signal	What to extract
Verbs	”Ship, build, design” → execution. “Drive, set the direction” → strategic.
Scope	”Own [feature]” → narrow. “Across the platform” → wide.
Team size	”4-engineer pod” → small team. “Multiple squads” → multi-team.
Reporting line	”Reports to EM” → senior IC. “Reports to VP” → staff/lead.

Find seniority signals in a JD and JD level cues — IC vs lead walk through the extraction in detail.

Pick the rung

If your resume altitude = the role altitude → apply with normal tailoring.

If your resume altitude is one level above the role:

Reposition the resume to the role altitude (drop scope language, drop team-size mentions, lead with execution-coded bullets).
Apply down a level deliberately.
Add a one-line cover-letter story.

If your resume altitude is one level below the role:

Stretch is reasonable but not guaranteed. Surface your highest-altitude work first.
Lead with architecture, cross-team work, or scope-establishing bullets.
Mirror the JD’s strategic verbs in 2–3 of your bullets.

If your resume altitude is two levels above or below the role:

Don’t apply. The math doesn’t recover. Find roles within one level of your altitude.

Common altitude mismatches we see

”I’m a Staff Engineer at a Series-B applying to Senior at FAANG”

Cross-company title compression. The roles are likely at the same actual altitude — Staff at Series-B = Senior at FAANG — so this is a lateral move, not a downshift. Apply normally.

”I’m a Senior Engineer with 8 years of experience applying to Staff”

If your bullets show Staff-coded work (architecture decisions, cross-team scope, mentoring), this is a one-level stretch and reasonable. If the bullets are mid-level shipped work, the gap is too wide. Pick the rung your bullets support.

”I’m a former EM applying to IC roles”

Apply at the IC level your hands-on work supports. If you spent 50%+ of your time coding, Senior IC is fair. If you were 90% management, the realistic landing is Tech Lead Manager or Principal-with-leadership, not pure IC. Manager to IC step-down is the playbook.

”I’m at a small company; my titles are inflated”

You’re likely a Senior Engineer in shape, even if your title is “Lead.” Apply at the actual altitude (Senior at most companies, Staff at smaller ones) and explain in one cover-letter line. Don’t lie about the title; do match the rung.

Run the rung check

The diagnostic scores your resume altitude and the JD’s altitude on the four-signal scale and tells you whether you’re applying to the right rung. If you’re not, the verdict tells you which direction to adjust.

Two free runs, no card.

Check the right rung — free →

Find seniority signals in a JD — the four-signal altitude read.
JD level cues — IC vs lead — IC vs lead distinction.
Is this job below my level? — pre-application check.
Software engineer overqualified rejection — the most common altitude mismatch case.