How do I tell if a job posting is for IC or lead?

Read the verbs in the first three responsibility bullets. IC: ship, build, design, implement, debug. Lead: drive, set the direction, mentor others, define standards, align across teams. If the lead verbs dominate, the role is lead even if the title says Senior.

Can a Senior IC role include some leadership work?

Yes — about 20–30% leadership work is normal at Senior+ IC levels (mentoring, code review, architecture leadership). The line that distinguishes IC from lead is direct reports plus team scope: lead roles have direct reports or run a team; senior IC roles have peer-level technical leadership without people management.

Why do JDs blur the IC/lead distinction?

Recruiters often write JDs from templates, and the templates lean toward leadership-coded language because it sounds impressive. Hiring managers know what they want; the JD is sometimes a sloppy proxy. Read for the team size and reporting chain to cut through the template.

What if the JD says "Senior Engineer / Tech Lead"?

Hybrid role. Expect 50–60% IC work plus light technical leadership (mentor 2–3 ICs, drive technical direction within a small team, no direct reports). Position the resume with mostly IC bullets plus 2–3 leadership-coded bullets.

Job description level cues — IC vs lead, decoded line by line

IC and lead JDs use different verbs, different scope language, and different team-size cues. Here is the line-by-line distinction so you stop applying to the wrong altitude.

The IC-vs-lead distinction is the most common altitude mismatch we see. A candidate applies to “Senior Engineer” thinking IC; the role is actually a tech lead with a 5-person team. Or applies to “Staff Engineer” expecting lead work; the role is a pure IC with a Staff title.

Title doesn’t tell you. The verbs do.

The IC vs lead verb split

IC verbs (read as “this person ships”)

Ship, build, design, implement, deploy
Debug, fix, refactor, optimize
Write (code, specs, designs)
Own (a feature, a system, a service)
Drive (a technical area, a migration, a refactor) — when paired with “the build of” or “the design of”

Lead verbs (read as “this person leads ICs”)

Mentor, coach, grow, develop (people)
Manage, run, lead (a team, a function)
Set (the direction, the standards, the strategy)
Align (across teams, with stakeholders)
Define (the architecture, the practices, the OKRs)
Drive (the roadmap, the strategy) — when not paired with build/design

If the responsibilities are 70%+ IC verbs, the role is IC. If they’re 70%+ lead verbs, the role is lead. If mixed, it’s a Senior IC with light leadership (sometimes called “tech lead” or “staff engineer”).

Scope language as a confirmer

Verb shape isn’t enough alone. Confirm with scope:

IC scope cues

“Own the [feature/surface]” → one surface, IC.
“Designing for [a specific user flow]” → one surface, IC.
“Improving [a system metric] for [a system]” → one system, senior IC.

Lead scope cues

“Set the standards across [multiple teams/the platform/the org]”
“Drive technical direction for [a function]”
“Mentor a team of 4–6 engineers”
“Run the architecture review process”

If verb shape and scope agree, the altitude is clear. If they disagree, the role is in transition or the JD is sloppy.

Reporting chain as final confirmation

The reporting line settles ambiguous cases:

Reports to Senior Engineer or Tech Lead → IC.
Reports to Engineering Manager → senior IC or first-line lead.
Reports to Director or VP → lead, principal, or director.

Reporting structure clues in job postings covers the patterns.

Three example reads

Example 1: “Senior Engineer” at a Series-B startup

You’ll own the activation and onboarding flows end-to-end, ship features in 2-week cycles, work closely with our PM and designer, and report to the Engineering Manager.

Verbs: own, ship, work closely → IC.
Scope: activation and onboarding (two surfaces) → senior IC.
Reports to: EM → IC chain.

Verdict: senior IC. Position your resume with execution-coded bullets at one-surface depth.

Example 2: “Senior Engineer” at a Series-A startup

You’ll set the technical direction for the platform team, mentor 3 junior engineers, drive the migration from monolith to services, and align cross-functional partners on quarterly priorities.

Verbs: set the direction, mentor, drive, align → lead.
Scope: the platform team → multi-team.
Reports to: not stated, likely CTO at a Series-A.

Verdict: actually lead/staff role despite “Senior” title. Position your resume with leadership bullets and senior-IC technical work.

Example 3: “Staff Engineer” at FAANG

Design and build [feature area]. Partner with PM and design to ship features in [domain]. Mentor 1–2 junior engineers as needed.

Verbs: design, build, ship → IC. “Mentor” is light leadership.
Scope: one feature area → senior IC.
Reports to: implicit (Senior EM or higher in FAANG hierarchy).

Verdict: senior IC at FAANG. Maps to Senior at non-FAANG, Staff at FAANG. Title is FAANG-specific.

What to do with the verdict

Once you’ve decoded IC vs lead:

If IC-coded: position your resume with execution-coded bullets, drop scope language, lead with shipped work.
If lead-coded: position your resume with leadership bullets, scope language, mentorship signals, and team-size mentions.
If hybrid (Senior IC / Tech Lead): balance — 60% execution bullets, 30% technical leadership, 10% scope.

Position wrong and the seniority filter trips. Position right and the application reads at the role’s altitude.

Run the IC-vs-lead check

The diagnostic reads the JD for the verb shape and scope, then compares to your resume’s altitude. The verdict tells you whether the role is IC or lead and whether your resume reads at the right altitude.

Decode the IC vs lead — free →

Find seniority signals in a JD — the four-signal altitude read.
How to read a JD like a hiring manager — the seven implicit signals pillar.
Which rung to apply to in tech — the level-targeting framework.
Resume reads too strategic for an execution role — the verb-shape conversion.