The reporting line is the most reliable altitude signal in a JD. Titles compress, scope language is fuzzy, but the chain is concrete: who you report to tells you exactly where the role sits.
Most candidates skim the reporting line. Hiring managers read it carefully — and the gap between your last reporting line and the role’s reporting line is one of the seven silent filters.
The reporting-chain altitude map
| Reports to | Likely role altitude | Implied scope |
|---|---|---|
| Senior Engineer / Tech Lead | Junior to mid IC | Single squad, single feature |
| Engineering Manager | Mid to senior IC | Single team, full feature ownership |
| Senior EM / Staff Eng | Senior IC | Multi-feature within a team |
| Director of Engineering | Senior to Staff IC, or first-line EM | Cross-team scope |
| VP of Engineering | Staff/Principal IC, or Director EM | Function-level scope |
| CTO | Varies wildly: senior IC at a Series-A, executive at a Series-D | Depends on company stage |
| CEO | Founding engineer, head-of-eng at small co, executive at scale | Company stage dependent |
The same title can map to wildly different altitudes depending on the company stage. Reports to the CEO at a 12-person company = founding engineer scope (probably senior IC). Reports to the CEO at a 1,000-person company = executive scope (VP+).
How to extract the reporting line
Direct mention
The clearest case. Look for:
- “Reports to the Engineering Manager.”
- “You’ll work directly with the VP of Engineering.”
- “Sitting alongside the CTO.”
These tell you the chain explicitly.
Indirect mention
When the JD doesn’t state it, look for:
- “Joining the team led by [name].” → check that person’s LinkedIn for their title.
- “Working with our Engineering Manager on…” → likely the EM is your manager.
- “You’ll partner with the Director of Product on roadmap.” → the Director is your peer’s manager, not necessarily yours.
Inferred from company stage
When the chain is silent:
- Series A/B (5–50 people): Most ICs report to a Tech Lead or directly to CTO. Multiple-layer chains are rare.
- Series C/D (50–200 people): Engineering Managers exist; ICs report to EMs. Senior IC roles may report to Senior EMs.
- Late stage / public: Standard 4-layer chains (IC → Staff/Tech Lead → EM → Senior EM → Director → VP).
If the JD doesn’t specify, use the company stage to infer.
Why the gap matters for your resume
Your last role reported to someone. The new role reports to someone. The hiring manager reads both and compares.
Gap 1: down the chain (you reported higher than the new role)
You reported to the VP of Engineering. The new role reports to a Senior EM.
How it reads: “This person is used to higher access. They will find this role limiting and leave.”
Fix: don’t lead the resume with the high reporting line. Lead with the work you did. The reporting line, if visible, can move to position 4 or 5 of the role description, or be implied through other scope language.
Gap 2: up the chain (you reported lower than the new role)
You reported to a Senior Engineer. The new role reports to a Director of Engineering.
How it reads: “This person hasn’t operated at executive-adjacent altitude. They will get crushed.”
Fix: surface the highest-altitude work you did, even if the reporting line was technically lower. Architecture decisions, cross-team work, exec presentations — these establish altitude in ways the reporting line alone doesn’t.
The “reports to the CTO” small-company nuance
A common pattern: candidates from Series-A or Series-B companies who reported to the CTO. On their next application:
- At a similar-stage company → “reported to CTO” reads as senior IC scope. Fine.
- At a late-stage company → “reported to CTO” reads as either highly senior or naive. The hiring manager has to do work to figure out which.
Fix: name the company stage in the role description. “Senior Engineer, AcmeCo (Series-A, ~25 engineers, reported to CTO).” This sets the context honestly.
When to include “reports to” explicitly on your resume
Most of the time: don’t. The work in the bullets establishes altitude better than a literal reporting line.
Three exceptions:
- Small-company CEO/CTO chain. “Reported to CTO” at a Series-A is a real signal of scope and is worth one phrase.
- Big-company executive chain. “Reported to the SVP of Engineering” at a public company implies executive-adjacent altitude.
- The new role asks for it. Some JDs explicitly ask candidates to indicate their reporting line. Comply.
In all other cases, the bullets do the work.
Run the reporting-chain check
The diagnostic reads the JD for the implied reporting chain and compares to your resume’s last reporting line. If the gap is large in either direction, the verdict tells you which framing to adjust.
Two free runs, no card.
Check the reporting fit — free →
Related reading
- Find seniority signals in a JD — the four-signal altitude read.
- Tacit disqualifiers in job postings — the broader signal set.
- Team size and reporting structure in resume — the resume-side framing.
- How to read a JD like a hiring manager — the seven implicit signals pillar.