Engineering Manager ATS Checklist for Tech Companies (2026)

Engineering Manager ATS Checklist for Tech Companies (2026)

Engineering Manager (EM) resumes get filtered by the same ATS engines as IC resumes — Greenhouse, Lever, Workday, Ashby, SmartRecruiters, iCIMS — but the failure modes are inverted. Where an IC resume gets rejected for missing technology keywords, an EM resume gets rejected for reading like an IC resume with "manager" in the title: no team-size numbers, no hiring evidence, no business outcomes, no cross-functional partnership signal [1][2][3]. This 22-item checklist walks every Engineering Manager through the pre-submission audit specific to leadership roles at tech companies — format, structure, scope numbers, hiring signal, EM-vs-IC framing, and verification — and names the EM-specific failure modes that take down even strong candidates.

Key Takeaways

• 97.4% of Fortune 500 companies use ATS to filter resumes, and the EM keyword target is fundamentally different from the IC target — leadership scope, hiring evidence, business outcomes, and cross-functional partnership replace the IC technology-stack scan [1][2].
• The single most common EM resume failure is the "tech-lead-with-fancy-title" pattern: 80% of bullets are IC implementation work, 20% are mentoring — recruiters configured to filter for "managed direct reports" auto-reject these [3][4].
• Team-size numbers are non-negotiable on every recent role. "Led a team" without a number reads as IC-still; "Led 7-engineer team across 2 squads" passes [3][4].
• Per the Pragmatic Engineer newsletter's coverage of EM hiring at top-tier tech companies, hiring competence is the rarest and most-valued EM signal — resumes that don't surface a hire count or hiring-loop role read as title-only [3].
• Director-and-up roles screen for "manager of managers" or "second-line" explicitly; the level signal lives in the literal phrasing, not in the title alone [3][5].
• BLS reports the median annual wage for Computer and Information Systems Managers was $171,200 in May 2024, with 9% projected job growth through 2034 — competition for senior EM roles at top-tier tech companies is high, and the ATS screens are commensurately strict [6].
• The recruiter screen for EM resumes lasts 9–12 seconds on average — slightly longer than the 7.4-second IC average — because the recruiter is scanning multiple signal classes (scope, hiring, outcomes, partnership) instead of a single technology-stack list [7].

Stage 1 — Format and File Prep (Items 1–5)

1. Single-column layout, no exceptions.

Greenhouse and Workday inconsistently parse two-column resumes; the parsed-text version recruiters see often appends the right column after the left, scrambling experience bullets [1][2]. EM resumes are particularly vulnerable because many "leadership-friendly" templates put a sidebar for direct-report counts and team metrics — exactly the column most likely to mis-parse. Use single-column with vertical sections: Header → Summary → Skills → Experience → Education → Optional (Speaking, Writing). Verify by copy-pasting into a plain-text editor; if the order is wrong there, it's wrong in the ATS.

2. Submit as .docx or PDF — both work, with caveats.

.docx is the safer default across Workday and Taleo. PDF works on Greenhouse, Lever, and Ashby with high parse fidelity. The trap: PDFs exported from non-Word tools (LaTeX, Pages, design tools) sometimes embed text as glyphs rather than parseable characters, breaking ATS extraction [2]. EMs are less likely than ICs to use LaTeX — a Word-based template is the right default. If you do use LaTeX, verify the output with pdftotext to confirm the extracted text matches the rendered document.

3. Keep file size under 2 MB.

EM resumes typically run 1–2 pages and don't include images, so this is rarely an issue. Watch for embedded company logos in side projects, headshot photos (skip these — not standard in US tech), or screenshot exhibits. Pure-text EM resumes should be 50–150 KB. Anything over 2 MB has embedded media that should come out.

4. Use system fonts only — Calibri, Arial, Helvetica, Georgia, or Times New Roman.

Custom fonts get substituted during ATS parsing, sometimes shifting line breaks and section boundaries unpredictably [2]. EM resumes don't need typographic personality — the leadership signal is in the words. Save the custom font for your personal site or speaking-deck template.

5. Avoid headers/footers, text boxes, and tables.

Document headers/footers on Workday and older Greenhouse parsers can be ignored entirely [1][2]. EM resumes sometimes use tables to lay out the team-scope summary ("Team size: 14 | Direct reports: 9 | Hires: 7 | Quarters: 8") — this fails ATS parsing universally because the table tokenizer scrambles the cells. The fix: write the same scope summary as a single line of text in the role's first bullet, e.g., "Senior EM, Platform Org — managed 14 engineers (9 direct reports + 5 indirect via 2 EMs); hired 7 across 8 quarters."

Stage 2 — Structure and Section Order (Items 6–10)

6. Standard section headers — exactly these names.

Use: "Summary" (or "Professional Summary"), "Skills" (or "Core Competencies"), "Experience" (or "Professional Experience"), "Education," "Speaking" or "Writing" (optional, only if substantial), "Certifications" (optional, rarely relevant for EM). ATS parsers — especially Taleo and older Workday — pattern-match on exact section names [1][2]. Creative section names ("Where I've Led," "What I've Built") cause the parser to skip those sections. EM resumes that lean rebellious here lose ATS points without any compensating gain.

7. Header line: name, location, contact, LinkedIn — and that's it.

Format: "Name | City, ST | email | (xxx) xxx-xxxx | linkedin.com/in/firstname-lastname." For EMs, GitHub and personal sites are optional — most EMs above first-line don't ship public code, and a stale GitHub is worse signal than no GitHub. The exception: EMs who've published technical writing or maintained an open-source project, where the link adds direct credibility. Do not include a headshot, address line, or "Open to Work" banner — these read as junior-resume conventions.

8. Lead with a 3–4 line Professional Summary that names scope, hiring, and partnership.

The summary gets the highest scan-weight per word [1][2]. For EM, pack 5–6 Tier-1 EM keywords. Example: "Senior Engineering Manager with 9 years in management — led 14-person platform org across 3 squads, hired 9 across L4–L6 over 18 months, partnered with PM/Design on quarterly roadmap, and authored the team's engineering strategy. Recent: drove the post-mortem process redesign org-wide; pendulum-aware (Charity Majors framing) — 6 years EM, 1 IC sabbatical." That's 6 Tier-1 EM keywords (managed, led, hired, partnered, roadmap, engineering strategy) plus 3 Tier-2 (post-mortem, pendulum, scope-org-wide) in 4 lines.

9. Skills section organized for EM, not for IC.

EM skills sections should NOT be a 25-item language/framework dump — that's the most common failure mode. Recommended grouping (4 categories, 18–22 items): Leadership (1:1s, performance reviews, calibration, coaching, hiring, career development, delegation, decision-making), Strategy (OKRs, roadmap, prioritization, engineering strategy, hiring plan, headcount budget), Cross-functional (PM partnership, design partnership, executive communication, stakeholder management), Team Tech Stack (one line on what the team builds — "Python/Go/Kotlin services on Kubernetes; Postgres + Kafka + Snowflake"). The IC-style 25-item skills dump triggers spam-detection on Greenhouse and Ashby and reads as IC-not-yet-transitioned [1][8].

10. Experience section: reverse-chronological, 5–7 bullets per recent role.

Reverse-chronological is the ATS expectation. For senior EMs and director-and-up, 5–7 bullets at the most recent role, 4–5 at recent prior roles, 3 at older roles. EM bullets carry more signal density than most software roles because each bullet should reference a leadership verb, a quantified scope, and a measured outcome. Don't skimp on bullet count for the most recent role — recency-weighted scoring on Lever and Greenhouse pushes the recent role to the top of recruiter screens [1][9].

Stage 3 — EM-Specific Content Audit (Items 11–16)

11. Every recent role names team size and direct-report count.

This is the single highest-leverage check on the entire EM checklist. For each role in the last 5 years that was a management role, the bullet cluster must include: team size, direct-report count, indirect-report count if applicable, and tenure of the team under your management. Pattern: "Senior EM, Platform Team — 14 engineers (9 direct + 5 indirect via 2 EMs), 18-month tenure as second-line." Vague phrasing ("led the team") fails the screen because the recruiter is calibrating level on the number, not on the verb [3][4].

12. Every recent role surfaces hiring evidence.

Hiring is the rarest and most-scanned EM signal [3][5]. For each EM role, name a hire count, an interview-loop role, or a hiring-loop redesign you owned. Pattern: "Hired 9 engineers across L4–L6 over 18 months as primary hiring manager; ran 47 onsite-loop debriefs; partnered with the recruiting team on a sourcing-pipeline rebuild." If you've genuinely never hired (e.g., new EM in headcount-frozen org), name the equivalent process work: "owned the loop calibration framework rewrite," "ran 14 hiring-debrief norming sessions," "wrote and shipped the engineering interview rubric for the platform team."

13. Every recent role names a quantified business outcome.

EM bullets without numbers are deprioritized by recruiters specifically trained to scan for outcome metrics [3][4][7]. Patterns that pass: "drove p99 latency from 480ms to 120ms across the auth service," "reduced AWS infra spend 38% across the platform org," "delivered 11 of 11 quarterly milestones across 2 years," "scaled the team from 5 to 14 engineers across 18 months," "drove team retention to 95% over 24 months across 9 senior ICs." If a bullet has no number, ask whether it deserves to be on the resume at all.

14. Bullets show range across the four EM domains.

Senior-EM and director resumes need range across four domains in each recent role [3][4]: People (1:1s, coaching, performance, career development), Hiring (loops, calibration, sourcing partnership), Strategy / Process (OKRs, roadmap, engineering strategy, post-mortems), Cross-functional (PM partnership, design partnership, executive communication). An all-people resume reads as first-line manager. An all-strategy resume reads as IC-strategist with delusions of management. The senior signal is balance — at least one bullet in each domain per recent role.

15. The IC-vs-EM split is intentional and explicit.

If you've been operating as a player-coach EM (still coding 25%+), the resume should make the split explicit and lead with management. Pattern: 4 management/strategy/scope bullets, then 1 closing bullet like "Maintained ~25% IC capacity on the most ambiguous architecture work — co-authored the auth-service migration design doc and paired with the staff engineer through the rollout." If you've been a pure people-manager (zero coding), don't fake IC bullets — own the management focus. The mistake is mixing IC and EM framing without intentionality, which reads as confused career level [3][4][5].

16. Education compressed; non-EM credentials trimmed.

EMs more than 5 years out of school should compress Education to 1–2 lines. Degree, school, year. Cut: GPA (irrelevant for EM regardless of value), coursework, dean's list, undergrad clubs. MBAs are uncommon on EM resumes at top-tier tech companies and add no ATS-screen value — the screen is on scope, hiring, OKRs, and roadmap, not on degree. Include the MBA only if it's recent (under 5 years) and you came from a non-engineering background. Many strong EMs have non-CS degrees — own that with a clean one-line entry.

Stage 4 — EM Keywords and Mechanics (Items 17–19)

17. Mirror the JD's exact phrasing — title, scope, and process.

If the JD says "Senior Engineering Manager," use that exact title in your summary even if your formal title is different. If the JD says "manager of managers" or "second-line manager," use those exact phrases somewhere in the resume to pass strict-match Workday and Taleo screens [2][5]. If the JD names specific frameworks ("OKRs," "performance calibration," "engineering strategy"), mirror them. The fix: read the JD twice, list the 12–16 highest-frequency leadership/process terms, and verify each appears in your resume in the canonical form.

18. Don't claim a scope you can't defend in a 30-minute interview.

The ATS rewards scope claims; the EM interview punishes false claims hard. EM hiring loops are notoriously deep — questions about hiring decisions, perf-review patterns, conflict resolution, organizational design, and specific incidents you led through. A candidate who claims "managed 18 engineers" but turns out to have had 4 direct reports and a vague "dotted line to 14 others" fails the first hiring-manager interview. Limit scope claims to what you've actually done. If your direct-report count is 4, say 4. If your hires are 3, say 3. The numbers don't have to be big — they have to be true.

19. Avoid the "kitchen sink leadership" dump.

EM Skills sections should not list every leadership concept that exists. A skills line that reads "Leadership, Coaching, Mentoring, Performance Management, Career Development, Change Management, Conflict Resolution, Delegation, Decision-Making, Strategic Thinking, Vision Setting, Roadmap Planning, Stakeholder Management, Cross-Functional Collaboration, Executive Communication, Influencing, Negotiating, Hiring, Onboarding, Offboarding, Team Building, Culture Building, Diversity & Inclusion, Remote Leadership, ..." triggers spam-detection on Greenhouse and Ashby and reads as buzzword-stuffing [1][8]. Pick the 12–16 leadership skills you actually do and ship them deep in experience bullets, not as a flat list.

Stage 5 — Verification and Submission (Items 20–22)

20. Run your resume through Jobscan or Resume Worded against the EM JD.

Both tools simulate ATS parsing and produce a match score against the specific JD [10]. EM matches are typically harder than IC matches because the keyword surface is narrower and the level distinctions (first-line vs. second-line vs. director) are tighter — target 75%+ match score for EM roles, with most missing-keywords being legitimate scope-clarification gaps you can fix by adding numbers to bullets. Under 65% match means the resume needs structural rework before submitting. The 10 minutes of running this check is the single highest-ROI step in the entire submission process.

21. LinkedIn matches the resume on scope, title, and tenure.

Recruiters at every modern tech company cross-reference LinkedIn during pre-screen [3][9]. The three checks before submitting: (a) every job title on the resume matches the LinkedIn title exactly (or differs only in the "Senior" / "Staff" / "Principal" prefix in a way you can defend), (b) every team-size and hire-count number on the resume is consistent with what LinkedIn says about the company headcount and your role, (c) every dated achievement on the resume falls within your LinkedIn employment dates. Inconsistency between the two reads as a trust failure, and recruiters are explicitly trained to look for it.

22. Final manual parse-test by copying into a plain-text editor.

Open your .docx in Word or Google Docs, select all, copy, paste into TextEdit (Mac), Notepad (Windows), or a plain-text editor. The result approximates what the ATS sees post-parse. Verify: section order is right, bullets aren't scrambled, scope numbers (team size, direct reports, hire counts) are intact and correctly attached to their roles, percentage and dollar signs render correctly (no "%" → "â%" artifacts), all links are still readable as text. If anything looks wrong here, it'll look wrong in the ATS. Fix the source until the plain-text version reads cleanly.

Bonus — EM Resume Failure Modes Beyond the ATS

Even resumes that pass the ATS can fail the recruiter and hiring-manager screens that follow. Six failure modes specific to EM resumes:

1. The "title-without-scope" resume. The candidate has been an EM for 3 years. The resume says "Engineering Manager." Then every bullet describes IC implementation work. Fails the recruiter screen because the level signal in the bullets is junior. Fix: rewrite with team-size numbers, hire counts, and outcome metrics in every recent bullet.
2. The "led / managed" verb monoculture. Every bullet starts with "Led" or "Managed." Reads flat and unspecific. Recruiters skip past it. Fix: rotate verbs aggressively — Hired, Restructured, Drove, Delivered, Scaled, Reduced, Owned, Influenced, Negotiated, Coached, Authored.
3. The "people only" resume. All bullets are about 1:1s, performance reviews, and coaching. No business outcomes, no roadmap, no strategy. Reads as first-line manager and ceiling-stuck. Fix: add at least one strategy/process bullet and one cross-functional bullet per recent role.
4. The "strategy only" resume. All bullets are about OKRs, roadmaps, and engineering strategy. No 1:1 mechanics, no hiring, no perf calibration. Reads as IC-strategist or product-manager-pretending-to-be-EM. Fix: add at least one people-management bullet per recent role.
5. The "I personally" voice. Bullets read like the EM did everything themselves: "I built," "I shipped," "I decided." EM resumes work in implicit-third-person voice describing the team work the EM enabled, not what the EM personally did. Fix: rewrite with the team or org as the implicit subject ("Drove the team to ship 11 quarterly milestones," not "I shipped 11 milestones").
6. The "title inflation" resume. The title says "Engineering Manager" or "Director." The scope describes 2 direct reports, no hiring, no headcount budget. The hiring-manager interview catches this within 5 minutes. Fix: own the actual scope. A "Tech Lead with 2 direct reports" framing reads stronger than an inflated EM title with weak supporting evidence.

FAQ

How do I handle an engineer/manager pendulum on my resume?

Charity Majors' "Engineer/Manager Pendulum" frames the move as cyclical and deliberate, not as a regression [11]. On the resume: name the IC sabbatical explicitly, frame it as deliberate ("Stepped back to senior IC for 14 months to rebuild technical depth on the new platform stack — returned to management with 8-engineer team Q3 2024"), and don't apologize for it. Recruiters at modern tech companies (Stripe, Anthropic, Linear) read pendulum moves as senior-engineer signal, not as a red flag. The trap is hiding the IC period or framing it as failure — that reads worse than naming it.

I'm applying to my first EM role from an IC position. What goes on the resume?

Surface every proto-management element from your senior-IC work, framed in EM-resume language. Tech-lead scope (with team size), interview-loop participation (with hire count), mentoring (with promotion outcomes), project leadership (with cross-functional partnership), incident leadership (with post-mortem ownership). Camille Fournier's Manager's Path Chapter 3 is the canonical scaffolding [4]. Then run the resume through Jobscan against an EM JD; aim for 70%+ match by adjusting bullets to mirror the JD's leadership phrasing.

How many years of EM experience do I need for "Senior EM" titles?

The honest range is 4+ years of sustained management work, with at least one full hiring cycle, two performance cycles, and one team-restructuring under your direct ownership. Below that, "Senior EM" reads as inflated even if the company gave you the title. Above 6 years, "Senior EM" is the floor; second-line / "manager of managers" or director becomes the next step. The Pragmatic Engineer's coverage of EM-leveling at top-tier companies maps these tenure expectations clearly [3].

Should I include team tenure and retention numbers?

Yes, when the numbers are good. "Maintained 95% retention across 14 reports over 24 months in an industry market with 18% average attrition" is a strong bullet. If retention was poor, address the context elsewhere — recruiters interview on retention regardless of whether the number appears, and an unaddressed gap reads worse than a contextualized one. The Pragmatic Engineer's 2024 retention coverage gives industry-average benchmarks to anchor against [3].

Do I need an MBA for EM roles?

No. MBAs are uncommon on EM resumes at top-tier tech companies and add no ATS-screen value — the screen is on scope, hiring, OKRs, and roadmap, not on degree. The candidates who land senior-EM roles at Stripe, Anthropic, Snowflake, and Datadog overwhelmingly come from IC engineering backgrounds with deliberate management transitions. Skip the MBA line if it crowds out an EM bullet. The exception: career-changers from non-engineering backgrounds where the MBA is the credible bridge into engineering management.

How do I handle a layoff on my EM resume?

Don't put "laid off" on the resume itself — that's interview-conversation context, not resume copy. Instead, end the role at the layoff date and let the date do the work. If the gap is more than 6 months, name what you did during the gap (consulting, technical writing, advisory work, sabbatical) in 1 line. The Pragmatic Engineer's coverage of the 2022–2024 tech-industry layoff cycle (cross-referenced against layoffs.fyi) confirms recruiters at modern tech companies are calibrated to read layoff gaps as market signal, not candidate signal [3]. The framing matters more than the gap length.

Should I list direct reports by level (L4, L5, L6) or just the count?

Both, when relevant. Pattern: "9 direct reports across L3–L5" or "managed L4–L6 ICs and 1 staff engineer." The level distribution signals the scope of leveling and calibration work the EM has done. For director-and-up roles, list the EM levels under you ("2 EMs (M1 and M2) and 16 indirect IC reports across L3–L6"). For first-line EM roles, the count alone is fine if the levels aren't differentiating.

How do I show incident and on-call leadership on an EM resume?

Operations work is high-signal for EM resumes at infrastructure / platform / SaaS companies [3][5]. Patterns: "Owned on-call rotation for 4 services across 14 engineers; reduced incident rate 60% over 18 months through systematic post-mortem follow-through" or "Led incident command for 11 P0/P1 outages over 2 years; drove the org-wide incident-review process redesign." Pair with metrics: incident count, MTTR, action-item closure rate. Operational EMs rank these highly, and it's an easy keyword cluster to surface.

What do I do if my most recent role was IC but I'm applying EM?

Be explicit about the pendulum framing in the summary line: "Senior Engineering Manager (currently IC sabbatical) returning to management with 6 years EM experience prior; 14-month IC stretch deliberately rebuilt technical depth on the new platform stack." Then structure the experience section to surface the prior EM roles prominently — title, team size, hire count, outcomes — even though they're not the most recent. The recency-weighted scoring on Lever and Greenhouse will still surface the older roles enough for recruiters to see the EM signal [1][9]. The framing carries the resume.

References

[1] Greenhouse Software. "Sourcing and Filtering Best Practices — Greenhouse Help Center." https://support.greenhouse.io/hc/en-us/articles/360051506331-Sourcing-best-practices

[2] Workday. "Workday Recruiting — Candidate Search Documentation." https://doc.workday.com/admin-guide/en-us/staffing/recruiting/candidate-experience.html

[3] Gergely Orosz. "The Pragmatic Engineer Newsletter — Engineering Management Coverage." https://newsletter.pragmaticengineer.com/

[4] Camille Fournier. "The Manager's Path — A Guide for Tech Leaders Navigating Growth and Change" (O'Reilly, 2017). https://www.oreilly.com/library/view/the-managers-path/9781491973882/

[5] Will Larson. "An Elegant Puzzle — Systems of Engineering Management" (Stripe Press, 2019). https://lethain.com/elegant-puzzle/

[6] U.S. Bureau of Labor Statistics. "Computer and Information Systems Managers — Occupational Outlook Handbook." https://www.bls.gov/ooh/management/computer-and-information-systems-managers.htm

[7] Ladders. "Ladders Eye-Tracking Study: How Recruiters Read Resumes." https://www.theladders.com/career-advice/you-only-get-6-seconds-of-fame-make-it-count

[8] Ashby HQ. "How Ashby's AI-Powered Sourcing Works." https://www.ashbyhq.com/resources/guides/ai-powered-sourcing

[9] LinkedIn Talent Solutions. "Recruiter Search Best Practices." https://business.linkedin.com/talent-solutions/recruiter

[10] Jobscan. "ATS Resume Test — Run Your Resume Through Our Free Scanner." https://www.jobscan.co/

[11] Charity Majors. "The Engineer/Manager Pendulum" (charity.wtf, 2017). https://charity.wtf/2017/05/11/the-engineer-manager-pendulum/

[12] Michael Lopp. "Rands in Repose / Managing Humans" (blog and book series). https://randsinrepose.com/

[13] Lara Hogan. "Resilient Management" (A Book Apart, 2019). https://abookapart.com/products/resilient-management