Engineering Manager ATS Keywords for Tech Companies (2026)

Engineering Manager ATS Keywords for Tech Companies (2026)

Engineering Manager (EM) hiring is a different keyword target than Software Engineer hiring, and most resume advice conflates the two. Recruiters at tech companies — Stripe, Airbnb, Meta, Anthropic, Datadog, Snowflake, Shopify — configure ATS searches for EM roles around four signal classes that don't appear on IC resumes: scope nouns (team size, budget, headcount), leadership verbs (hired, restructured, scaled, coached), cross-functional collaboration (partnered with PM/Design/Data, aligned with Sales, influenced executive staff), and business-outcome language (revenue, retention, OKRs, roadmap, cost). A resume that reads like an IC resume with "manager" in the title gets filtered out for EM roles because the keyword density in those four classes is too low [1][2]. This page lists the EM keywords that pass screens in 2026, grouped by signal class, with worked rewrites and a counter-list of IC keywords that backfire when an EM resume leans on them.

Key Takeaways

• EM resumes are scanned for four signal classes — leadership scope, business-impact verbs, cross-functional partnership, and strategy/process — that most IC resumes have zero density on; missing all four is the #1 reason senior IC candidates get filtered out of EM searches [3][4].
• Team-size numbers ("led 7-engineer team," "managed 14 across 3 squads") are the highest-leverage Tier-1 EM keywords because Greenhouse, Lever, and Ashby all weight quantified scope above unquantified leadership prose [2][5].
• The Pragmatic Engineer 2024 EM hiring deep-dive notes that recruiters at top-tier tech companies explicitly filter for "manager-of-managers" vs. "first-line manager" via keywords like "managed managers," "managed leads," "second-line manager," and "director" — the level signal lives in the words, not the title [3].
• IC verbs ("implemented," "coded," "fixed bugs," "shipped feature X") backfire on EM resumes after the first 1–2 bullets — they signal the candidate hasn't actually transitioned to management work, even if the title says manager [4][6].
• "OKRs," "roadmap," "hiring plan," "performance reviews," and "calibration" are the Tier-1 process keywords that distinguish EM resumes from senior-IC resumes; their absence reads as "tech-lead-with-a-fancy-title," not EM [3][4].
• BLS reports the median annual wage for Computer and Information Systems Managers was $171,200 in May 2024, with the top 10% earning more than $239,200 — the EM/director track is one of the highest-paid software roles, and ATS screens at top-tier companies are commensurately strict [7].
• "Hiring" as a verb is itself a Tier-1 EM keyword — recruiters scan for evidence of headcount ownership ("hired 9 engineers across L4–L6," "owned hiring loop for 11 months") because hiring competence is the rarest EM signal [3][6].

How Engineering Manager ATS Screens Work

EM hiring runs through the same ATS engines as IC software hiring — Greenhouse, Lever, Workday, Ashby, SmartRecruiters, iCIMS — but the keyword matrix is inverted. Where an IC search filters on technology (Python, Kubernetes, React, Swift), an EM search filters on leadership scope, business outcomes, and process, with technology context as a secondary check. The EM ATS scan is mostly looking for evidence that the candidate operates at the right level of abstraction: a candidate whose top three bullets describe technical implementation will be filtered out for senior EM roles, even if the title is right [3][4].

Engine-specific behavior for EM hiring:

Greenhouse (used at Stripe, Airbnb, Notion, Robinhood, and most Series-B-and-up startups) supports semantic matching, so "managed a team of 8" registers as related to "led 8 engineers" or "8-person team" [2]. Greenhouse weights experience-bullet keywords more than skills-section keywords for EM roles — the bullets carry the load. The recruiter UI lets the filter "managed direct reports within last 2 years" return only candidates whose most recent role had reporting structure [2].

Lever (used at Eventbrite, Shopify, parts of Lyft) emphasizes recency. For EM roles specifically, Lever recruiters often filter by "currently or recently in management" — a candidate who pivoted from EM back to IC and is now applying to EM roles needs to surface management work in the most recent 24 months prominently [2]. The "people-management within last 2 years" filter is the EM equivalent of the IC "iOS within last 2 years" filter.

Workday (used at Disney, Salesforce, Adobe, large-enterprise EM hires) is the strictest exact-match parser. For EM, Workday filters often require the literal phrase "Engineering Manager," "Senior Engineering Manager," "Director of Engineering," or "Head of Engineering" in the title block — a candidate titled "Tech Lead" who has been operating as an EM for two years gets filtered out unless the resume explicitly clarifies the de-facto management work [5]. The fix: write the company entry as "Tech Lead (Acting Engineering Manager — 6 direct reports)" or similar.

Ashby (used at Notion, Linear, Ramp, Anthropic, and most modern AI-era startups) is the friendliest ATS for nuanced EM resumes because its LLM-based scoring reads bullets and infers level from context. A bullet that describes "ran weekly 1:1s with 7 engineers, drove perf calibration across 2 cycles, partnered with PM on quarterly roadmap" registers as EM signal even if the title is ambiguous [6]. Ashby is where mid-career IC-to-EM transitions get the fairest read.

SmartRecruiters (Visa, Atlassian) and iCIMS (Capital One, Disney non-engineering) lean stricter and more exact-match. Both score the title block heavily for EM searches, and both penalize creative titles ("Engineering Lead," "Tribe Lead," "Group Lead") for not matching the canonical "Engineering Manager" string. Taleo (legacy enterprise, Oracle) is the oldest and the strictest; for EM Taleo searches, write defensively with explicit phrases like "people manager," "direct reports," "headcount," "performance reviews" [5].

Tier 1 — Leadership Scope (the non-negotiables)

These keywords appear in 80%+ of mid-to-senior EM postings sampled from LinkedIn, Built In, and direct careers pages at Stripe, Airbnb, Anthropic, Datadog, and Snowflake in Q1 2026 [3][4]. If the resume is missing scope numbers or the leadership-verb cluster, it reads as IC even with the right title.

Team size / headcount — Quantify on every recent role. Patterns: "led 7-engineer team," "managed 14 engineers across 3 squads," "second-line managing 2 EMs and 18 ICs." Vague phrasing ("led a team," "managed engineers") fails the screen because the recruiter is calibrating level on the number, not on the verb [3][4].

Direct reports — The literal phrase "direct reports" is heavily scanned [3]. Pattern: "9 direct reports across L3–L5" or "direct-reported 6 ICs and 1 tech lead." Pairs with "skip-level" for second-line managers: "ran skip-level 1:1s with 16 engineers across 2 EMs."

Hired / hiring — Tier-1 EM verb. Patterns: "hired 9 engineers across L4–L6 over 18 months," "owned hiring loop for the platform team for 11 months," "ran 47 onsite loops as hiring-manager interviewer." Hiring competence is the rarest and most-scanned EM signal because most candidates can't name numbers [3][6].

Performance reviews / calibration — Process keyword cluster [3][4]. Patterns: "ran semi-annual perf calibration for 14 ICs across 2 cycles," "wrote and delivered 28 performance reviews," "partnered with skip on calibration outcomes." Distinguishes EM from senior-IC.

1:1s — Specific management mechanic [3]. Patterns: "ran weekly 1:1s with 7 engineers using Lara Hogan's feedback equation," "structured 1:1 cadence (career + project + personal) across 9 reports." The keyword "1:1s" itself is what the ATS catches; the depth of the bullet is what the recruiter reads.

Coaching / mentoring / career development — Coaching-stack keywords [3][4]. Patterns: "coached 3 senior ICs through promotion to staff (L5→L6)," "mentored 2 EMs through their first year of management." Promotion-outcome numbers are the highest-signal version.

Headcount / budget — Resource-ownership keywords. Patterns: "owned 12-headcount budget across two squads," "managed $X annual contractor budget for platform tooling." Senior+ EM signal — first-line managers usually don't own budget [3].

Manager of managers / second-line — Director-level signal [3]. Patterns: "second-line EM with 2 EM reports and 16 IC indirect reports," "manager of managers for the data-platform org." Recruiters at top-tier companies explicitly filter for this distinction.

Tier 1 — Business-Impact Verbs (the outcome layer)

EM resumes that read well lead bullets with business-outcome verbs, not implementation verbs. The pattern is verb + scope + outcome [3][4][6].

Delivered — Outcome verb. Pattern: "delivered the cross-team migration to async-pipeline architecture across 4 services and 6 months, hitting the planned Q2 milestone." Better than "managed the migration."

Scaled — Growth verb. Patterns: "scaled the platform team from 5 to 14 engineers across 18 months," "scaled the on-call rotation from 3 services to 11 without increasing pager load." Pairs with team-size or system-scope numbers.

Restructured / reorganized — Org-design verbs [3]. Patterns: "restructured the data-platform org from 1 squad to 3 verticals to align with product strategy," "reorganized 14 engineers across 4 newly-defined product surfaces." Senior-EM and director-level signal.

Drove / drove down / drove up — Outcome verb [4]. Patterns: "drove p99 latency from 480ms to 120ms across the auth service over Q3," "drove team retention to 95% over 24 months across 9 senior ICs." Numbers are the requirement.

Reduced / cut — Cost / efficiency verbs [4]. Patterns: "reduced AWS infra spend 38% across the platform org by re-architecting batch pipelines," "cut on-call incident rate by 60% through systematic post-mortem follow-through." Cost numbers are EM-level signal that ICs rarely surface.

Owned — Accountability verb [3][4]. Patterns: "owned the platform reliability roadmap across 4 quarters," "owned hiring outcome for the ML platform team." "Owned" reads as EM; "contributed to" reads as IC.

Shipped — Output verb. Patterns: "shipped 11 quarterly milestones across 2 years with no missed dates," "shipped the multi-tenant rewrite on time across 3 squads." OK on EM resumes when the scope is team-level, not feature-level.

Tier 1 — Cross-Functional Collaboration

The cross-functional dance is the bulk of EM work past the first-line level [3][4][6]. The keyword cluster is heavily scanned at director-and-up roles.

Partnered with — Cross-functional verb [3]. Patterns: "partnered with Product to land the Q2 platform roadmap," "partnered with Data Science on the ML evaluation framework." Pairs with the partner function name.

Worked with / aligned with — Collaboration verbs. Patterns: "aligned engineering and design on the component-library migration across 3 squads," "worked with Sales engineering on the enterprise rollout." "Aligned with" reads stronger than "worked with."

Influenced / negotiated — Higher-altitude verbs [3]. Patterns: "influenced executive staff on the platform-investment thesis," "negotiated headcount allocation across 3 EM peers in the platform org." Director-and-up signal.

Stakeholder management — Process keyword [4]. Patterns: "managed stakeholder communication across 4 product orgs and 1 executive sponsor," "ran weekly cross-functional stand-up with PM/Design/Data leads." More common at large-company / enterprise-EM roles.

Executive / VP / leadership team — Altitude keywords [3]. Patterns: "presented quarterly strategy to VP of Engineering," "drove leadership-team consensus on platform-vs-product investment split." Senior-EM and director signal.

Tier 1 — Strategy and Process

OKRs / KRs — Goal-setting keyword [3][4]. Patterns: "drafted and delivered 11 team OKRs across 4 quarters with 78% hit rate," "owned KR cascade across 3 squads." OKR fluency is a Tier-1 EM signal even at companies that don't use OKRs by name.

Roadmap / roadmapping — Strategy keyword [3][4]. Patterns: "owned the platform-team roadmap across 4 quarters," "co-authored the engineering-org annual roadmap with PM and design partners." Distinguishes EM from senior-IC.

Hiring plan / headcount plan — Director-and-up keyword. Patterns: "wrote and executed the platform-org hiring plan (12 hires across L3–L6 over 18 months)," "owned 9-headcount allocation negotiation with finance." Senior signal.

Strategy / engineering strategy — Per Larson's framework — the engineering-strategy artifact is itself a senior-EM keyword cluster [3]. Patterns: "authored the platform-team engineering strategy (2-page Rumelt-style brief)," "drove org-wide strategy alignment across 4 EMs and 1 director." Cite "engineering strategy" once if you've actually written one.

Prioritization / trade-offs — Decision-making keywords [3][4]. Patterns: "prioritized 11 candidate workstreams down to 4 quarterly bets across 3 squads," "made the explicit trade-off between platform-investment and product-shipping for Q3." Pairs with the verb "explicitly" — recruiters read "explicitly traded off X for Y" as senior-EM signal.

Post-mortem / incident review — Operational keyword [4]. Patterns: "ran 14 post-mortems over 18 months, with 80% of action items closed within 60 days," "drove the org-wide incident-review process redesign." Operational EMs rank these highly.

Coaching framework / feedback equation — Specific-method keywords [3]. Patterns: "applied Lara Hogan's feedback equation across 9 reports," "used Camille Fournier's tech-lead-to-manager scaffolding for 2 first-time-EM transitions." Citing a named framework reads as deliberate, not generic.

Tier 2 — Technology Context (the secondary check)

EMs still get scanned for technology context, but secondarily — the recruiter has already filtered on leadership signal first [3][4]. Surface the team's tech, not the EM's IC skills.

Pattern: "led the platform team building a Python / Kotlin / Go services stack on Kubernetes, with Postgres, Kafka, and Snowflake for analytics." Names what the team builds, not what the EM personally codes. Avoid leading with "Senior Engineering Manager skilled in Python, Java, React, Kubernetes" — that's an IC stack-list and reads junior for EM. The same keywords belong in a "Team Tech Stack" or a phrase inside an experience bullet.

Allowed Tier-2 technology mentions on EM resumes: the team's primary languages (Python, Go, Kotlin, Swift, TypeScript), the team's infrastructure (Kubernetes, AWS, GCP, Terraform), the team's data systems (Postgres, Kafka, Snowflake, BigQuery, Spark), and ML platform (PyTorch, TensorFlow, JAX, MLflow, Sagemaker) when relevant. Cite these once or twice across the resume, not in the summary, not as a Skills-section dump.

Counter-List — Keywords That Backfire on EM Resumes

This is the part most resume advice misses. EM resumes can be sunk by IC keywords that read as career-regression signal [3][4][6].

"Implemented" — IC verb. On a senior EM resume, more than 1 bullet leading with "implemented" reads as IC-still-pretending-to-be-EM. Replace with "delivered," "owned," "drove."

"Coded" / "Wrote code" / "Shipped feature X" — IC framing. Even an EM who codes 20% of the time should not lead bullets with these. Pattern fix: "Set the technical direction for [feature X] and unblocked the team through 2 architecture-decision documents and pairing on the most ambiguous module" — owns the technical leadership without falsely claiming the IC work.

"Fixed bugs" / "Debugged" / "Refactored" — Pure IC verbs. Skip entirely on EM resumes for senior+ roles.

Long technology Skills lists (15+ items) — IC-resume convention. EM resumes that include a 25-item Skills section ("Python, Java, Go, Kubernetes, Docker, Postgres, Redis, Kafka, AWS, GCP, Terraform, ...") trigger spam-detection on Greenhouse and Ashby and read as IC-not-yet-transitioned [2][6].

"Led the team" without a number — Vague leadership. Always pair "led" with a number: "led 7-engineer team" not "led the team."

"Was promoted to manager" — Title-only signal. Replace with the actual scope you took on: "Promoted to EM with 6 direct reports across the auth and infra squads."

Heavy-use of first-person singular ("I built," "I owned") — IC framing. EM bullets read better in implicit-third-person voice describing the team work the EM enabled, not what the EM personally did.

Worked Examples — EM Keywords in Experience Bullets

Example 1 — Hiring scope

Before (C-grade): Helped hire engineers for the team.

After (A-grade): Hired 9 engineers across L4–L6 over 18 months as primary hiring manager — owned the loop calibration with the broader org, ran 47 onsite-loop debriefs, and partnered with the recruiting team on a sourcing-pipeline rebuild that doubled the qualified-candidate rate.

Keywords hit: Hired, hiring manager, loop, calibration, recruiting, pipeline, partnered.

Example 2 — Cross-functional partnership

Before: Worked with PM and Design on the roadmap.

After: Partnered with the PM and Design leads to land the Q2 platform roadmap — co-authored the 2-page strategy brief, drove explicit prioritization of 4 bets out of 11 candidate workstreams, and ran weekly cross-functional standup with sales-engineering and data-science partners across 3 squads.

Keywords hit: Partnered, PM, Design, roadmap, strategy, prioritization, cross-functional, standup, squads.

Example 3 — Performance and calibration

Before: Did performance reviews for the team.

After: Ran semi-annual performance calibration for 14 ICs across 2 cycles — wrote and delivered 28 performance reviews using Lara Hogan's feedback equation, coached 3 senior ICs through promotion to staff (L5→L6), and partnered with my skip on cross-EM calibration outcomes.

Keywords hit: Performance calibration, performance reviews, feedback equation, coached, promotion, partnered, skip.

Example 4 — Strategy and outcome

Before: Owned the team's tech direction and shipped projects on time.

After: Authored the platform-team engineering strategy (2-page Rumelt-style brief) and owned the roadmap across 4 quarters — delivered 11 of 11 quarterly milestones, drove p99 latency from 480ms to 120ms on the auth service, and reduced AWS infra spend 38% via batch-pipeline re-architecture.

Keywords hit: Engineering strategy, roadmap, delivered, drove, reduced, AWS, infra, milestones.

Example 5 — Org design

Before: Reorganized the team to align with product priorities.

After: Restructured the data-platform org from 1 horizontal squad to 3 product-aligned verticals over Q3 — managed the change with 14 engineers across 4 newly-defined product surfaces, partnered with HR on the rebalancing of reporting lines, and drove leadership-team consensus on the new structure.

Keywords hit: Restructured, org, squad, verticals, partnered, HR, leadership team, consensus.

Example 6 — Coaching and retention

Before: Maintained team morale and retention.

After: Drove team retention to 95% over 24 months against a backdrop of significant senior-IC attrition — owned career-development conversations across 9 reports, coached 2 EMs through their first year of management, and partnered with my skip on a comp-review escalation that retained 3 senior ICs.

Keywords hit: Drove, retention, attrition, career development, coached, EMs, partnered, skip, comp.

Density and Placement Rules for EM

1. Professional Summary: Pack 5–6 Tier-1 EM keywords here. Example: "Senior Engineering Manager with 8 years of management experience — led 14-person platform org, hired 9 across L4–L6, partnered with PM/Design on quarterly roadmap, and drove the org-wide post-mortem process redesign. Pendulum-aware: 5 years EM, 1 year IC sabbatical (Charity Majors framing), now back in management."
2. Skills section: For EM, skip the long-tech-stack-list and replace with: Leadership (1:1s, performance reviews, calibration, coaching, hiring, career development), Strategy (OKRs, roadmap, prioritization, engineering strategy, hiring plan), Cross-functional (PM partnership, design partnership, executive communication), Team tech stack (1 line on what the team builds). 4 categories, 18–22 items total.
3. Experience bullets: Each recent bullet should pair a leadership verb with a quantified scope (team size, hire count, scope number, business outcome). Aim for 1 Tier-1 EM keyword per bullet, embedded naturally.
4. Don't: Mix IC implementation bullets with EM scope bullets in the same role. Pick one framing per role and commit. Mixed framing reads as confused career level.

Density rule of thumb for EM: Tier-1 leadership-scope keywords (team size, direct reports, hired) appear 4–6 times across the resume. Tier-1 business-impact verbs (delivered, scaled, drove) appear 6–10 times. Tier-1 strategy keywords (OKRs, roadmap, hiring plan) appear 2–3 times. Tier-2 technology mentions appear 3–5 times total — not 30.

Anti-Patterns That Fail EM Screens

• The "tech-lead-with-fancy-title" resume: Bullets are 80% IC implementation, 20% mentoring. Reads as senior IC, not EM. Recruiters filter against this aggressively for L6+ EM roles [3].
• No team size: "Led a team of engineers building the platform." How many? The number is the signal. Vague phrasing is a screen failure [3][4].
• No hiring evidence: The resume describes 3 years of EM work but never names a hire count, an interview-loop role, or a hiring-loop redesign. Reads as "got the title, didn't do the hiring work" — and hiring is the rarest, most-scanned signal [3][6].
• Vague "led / managed" without outcome: "Led the team to ship features." What features? What outcome? EM bullets need both the verb and the measured result [4].
• IC-stack Skills dump: A 25-item skills list (Python, Go, Kotlin, Kafka, Kubernetes, Postgres, Redis, ...) on an EM resume is anti-signal. Replace with the EM-keyword skill categories above [6].
• Title inflation: Calling a 2-direct-report tech-lead role "Engineering Manager" without clarifying scope, then applying to L7 director roles. Hiring managers cross-check at interview, and the gap shows fast.
• "I personally": First-person singular IC-style framing on a management resume. EM bullets work better in implicit voice describing what the team did under your direction.

FAQ

I'm an IC applying for my first EM role — how do I write this resume?

Lead with the proto-management work you've already done — tech-lead scope, mentoring, interview loops, project leadership — and frame each in EM-resume language. "Tech-led 4-engineer feature pod across 3 quarters; ran weekly project syncs, owned the prioritization conversation with PM, and mentored 2 junior engineers through their first quarter." That bullet hits "tech-led," "prioritization," "PM partnership," "mentored" — Tier-1 EM keywords from a senior-IC role. Camille Fournier's Manager's Path Chapter 3 (Tech Lead) is the canonical scaffolding for this transition framing [4].

Should I list my coding skills on an EM resume?

Once, briefly, in a "Team Tech Stack" line — not as a 25-item Skills dump. The EM ATS scan does not weight coding skills heavily, and a long IC-style skills list reads as career-regression. The exception: small startups (<30 engineers) where the EM is expected to ship code 30%+ of the time. For those roles, list the 5–7 languages/frameworks you actually use, but still as a single line, not a section.

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

Charity Majors' "Engineer/Manager Pendulum" frames it as cyclical, not linear [8]. 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. Recruiters at modern tech companies (Stripe, Anthropic, Linear) read pendulum moves as senior-engineer signal, not as a red flag — but only if framed as deliberate and recent management work is current.

How many direct reports do I need to claim "EM"?

The honest floor is 4 direct reports, sustained for at least 6 months. Below that, the role is closer to "tech-lead with people-management responsibilities" and the resume should frame it accordingly. The signal hiring managers want is "has run a team through at least one hiring cycle, one performance cycle, and one outage" — that's roughly the 12-month, 4-direct-report mark. Below it, the resume reads as transitional, which is fine if framed honestly.

Should I include team tenure / retention numbers?

Yes, when the numbers are good. "Maintained 95% retention across 14 reports over 24 months" is a strong bullet. If retention was poor, address it through context elsewhere — recruiters interview on retention regardless of whether the number is on the resume, 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].

How do I list an EM role where I also coded?

Lead the bullet cluster with management work; close with one bullet on technical contribution if it's relevant. Pattern: 4 management/strategy/scope bullets, then 1 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." Don't lead with the IC work; doing so signals EM-pretending-to-be-IC.

What about EM-of-EM or director roles?

The resume needs to surface "second-line" or "manager of managers" explicitly — recruiters filter on those literal phrases [3]. Pattern: "Senior Engineering Manager (Manager of Managers) — second-line for 2 EMs and 16 IC indirect reports across the platform org. Owned 18-headcount budget, drove org-wide hiring plan, ran cross-EM calibration with 2 peer second-lines." Director-level signal lives in: org size, budget ownership, peer-EM negotiation, executive communication.

Do I need an MBA to show up on EM screens?

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, Stripe, Snowflake, etc., overwhelmingly come from IC engineering backgrounds with deliberate management transitions, not from MBA programs. Skip the MBA line if it crowds out an EM bullet.

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] Ashby HQ. "How Ashby's AI-Powered Sourcing Works." https://www.ashbyhq.com/resources/guides/ai-powered-sourcing

[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] Workday. "Workday Recruiting — Candidate Search Documentation." https://doc.workday.com/admin-guide/en-us/staffing/recruiting/candidate-experience.html

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

[7] 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

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

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

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