Engineering Management: Interviews & Hiring ft. Google Engineering Director

Bad vs. Great Engineering Management

• Bad engineering manager: repeatedly misses delivery deadlines; breaks team promises and/or consistently loses people.
• Acceptable manager: roughly keeps promises, delivers on time, and doesn’t lose people.
• Great manager: optimizes for building people to take over their job (“work themselves out of a job”) while still delivering reliably.

Core “Work Themselves Out of a Job” Strategy

• Managers should invest in identifying who on the team can grow into their role over the next couple of years.
• Key tradeoff: you can optimize for only one thing at a time (subject to constraints).
  • Dave’s desired optimization target is people growth, bounded by promises/delivery.

Engineering Manager Interview Assessment (What to Look For)

When an Engineer Shows Interest in Management

• Dave’s question: “Why?” (looking for specific motivation)
• Desired answer traits:
  • Personal satisfaction from growing/mentoring others similar to (or as much as) shipping product.
  • Enjoyment of mentoring.
  • Awareness that management includes “tax” (performance reviews, compensation, hiring/firing, etc.).
• If they don’t show that motivation: “find another way to grow” rather than forcing management.

When Interviewing External Engineering Managers

High-signal “Pride story” prompt

• Ask: “The person you’re most proud to have ever managed—how you grew them and why you’re proud.”
• Red flag: if they can’t answer quickly (takes more than ~5 seconds).

“Jerk employee” behavioral prompt

• Ask about a time managing an excellent but difficult employee:
  • How they handled it
  • Did it resolve?
  • How long before realizing it wasn’t worth the friction and encouraging them to leave elsewhere.

Conflicting goals / dispute resolution

• Ask for a story where they had to reconcile two business goals that couldn’t both be done.

Delivery failure / “step into a dumpster fire”

• Ask about missing a promise: what they did afterward.

Biggest failure with learning

• Ask: “Where did you fail most, and what did you learn?”
• Emphasis: not whether they can deliver perfectly, but whether they notice and correct mistakes and don’t repeat the same one.

Management Operating System: Cadence and Practices

1:1s as a Growth Mechanism (Not Status Updates)

• Dave runs:
  • Weekly 1:1s with direct reports
  • At least bi-weekly 1:1s with “skips” (managers above)
• Purpose:
  • No project/tactical updates in those meetings (except “burning” issues).
  • Focus on how the direct is growing and how close they are to “working themselves out of a job.”
• Expected outcome in each 1:1:
  • The employee should report how much closer they are to being able to replace the manager’s role over time (even if it’s ~2 years out).
  • Manager and employee discuss growth opportunities and experiments for validation.

Assignment Principle for Growth

• If there are tasks a manager doesn’t like doing, it’s often a growth opportunity for someone else.
• Ask for volunteers to learn—often someone wants to.

Postmortems / Retrospectives

When discussing failures, Dave expects concrete process:

• Prompt stakeholders after missing an estimate/promise
• Use dashboards, weekly updates, face-to-faces (as needed) to rebuild trust
• Conduct a retrospective/postmortem with pointed questions to reveal whether it’s real vs. improvised

Organizational Tactics: Meeting Discipline

Meetings Are a “Bug,” Not a “Feature”

• The only legitimate purposes for group meetings:
  • Make a decision
  • Resolve a dispute
• Everything else should happen “in the dock” (i.e., not in a meeting), because:
  • Decisions affect people who may not be in the meeting
  • Fewer meetings = less time waste; avoid unnecessary synchronization

Communication and Technical Competence (Leadership Requirements)

Technical Competence Is Required (Principled Engineering Management View)

Dave argues every engineering manager must maintain enough technical confidence to:

• Have principled architecture discussions
• Explain how work connects to user value
• Communicate what it costs to do things

Rationale:

• If managers drift from technical grounding, they lose effectiveness.
• Even admired managers sometimes “step back” to be an IC periodically to reset technical understanding.

Trust-Building Communication Rules

• Don’t “hand-wave” unclear answers; provide boundaries:
  • “I know”
  • “I don’t know”
  • Or “I can answer up to here but can’t/ won’t beyond due to valid reasons.”
• If wrong, raise your hand quickly and admit it in the same context:
  • In small meetings → follow up with email/text
  • In larger/all-hands contexts → notify appropriately to correct the record

Leadership Traits / Hiring Signals (3 Traits Framework)

Dave frames hiring/interviewing around three traits common to successful people:

• Conscientious
• Intelligent
• Naive (willingness to attempt hard things before fully realizing difficulty)

Also seeks “best human” traits:

• Ruthlessly honest with themselves and open to feedback
• Willing to adjust and grow

Actionable Recommendations for Candidates (Interview + Transition)

For Engineering Manager Interviewees

• Prepare 5–6 failure stories/examples in advance.
• Don’t recycle the same 1–2 examples across interviews; it looks “an inch deep” in written feedback.

For Individual Contributors Transitioning to Management

• Treat management as an experiment (not an irreversible commitment).
• Propose a ~6-month trial:
  • Define it explicitly to reduce risk for both the employee and the org
  • Set an “off-ramp” back to IC if it’s not working
  • Hold a frank check-in after the trial

Metrics / KPIs / Targets Mentioned

• No numeric business metrics (revenue, CAC, churn, etc.) were discussed.
• Operational targets implied:
  • Deliver on promises / on-time delivery
  • Retention (“not losing their people”)
  • Growth milestones tracked in 1:1s via progress toward “working themselves out of a job” (no specific quantified targets beyond cadence and qualitative progress)

Presenters / Sources

• Dave Renson (former Director of Engineering at Google and Amazon; now SVP of Engineering at Pendo)
• Jacob (interviewer/moderator; referenced in dialogue)