Build an Engineering Manager Hiring Plan
Paste a job description, intake notes, table stakes, or bar-raising criteria -- the skill maps them to a 5-stage EM interview process, generates questions with role-specific language, and outputs a formatted doc with answer guides and red flags per question.
Overview
Building a consistent, equitable interview process for Engineering Manager roles is time-consuming -- especially when you need to adapt questions to a specific domain, level, or set of hiring bar criteria without losing the standard evaluation structure. This MCP template takes any combination of job description, kickoff notes, buy-raising criteria, table stakes, and areas of growth, and turns them into a complete stage-by-stage hiring evaluation framework with questions, competency mapping, and per-question guidance on what strong looks like and what to watch out for.
How it works
Provide your inputs -- a job description plus at least one of kickoff notes or bar-raising criteria. The skill parses them into core competencies, maps each to the appropriate stage in the standard 5-stage EM interview process (Recruiter Screen, Job Fit, Architectural Presentation, Stakeholder Interview, Bar Raiser), and generates questions that blend a consistent baseline with role-specific language. For each question, it adds what a strong answer looks like and what red flags to watch for, drawn from an EM evaluation rubric covering quality traits, AI fluency levels, and impact behaviours. The output is a formatted Google Doc ready to share with the hiring team.
Who this is for
Built for technical recruiters and hiring managers who run Engineering Manager searches and want a unified, consistent interview process across all EM roles -- with enough flexibility to assess domain-specific skills and stakeholder needs without rebuilding the process from scratch each time.
Suggested prompt
Build me a hiring plan for [Role Name] -- here is the JD and our key bar-raising criteria: [paste]
Frequently asked questions
What inputs does this need to generate the plan?
Any combination of: job description, kickoff notes, buy-raising criteria, table stakes or must-haves, areas of growth, and historical examples from past strong or weak candidates. The minimum to get started is a job description plus at least one of kickoff notes or buy-raising criteria. The more context you provide, the more role-specific the questions and answer guides will be.
What does the output document include?
A stage-by-stage interview plan covering all five standard EM interview stages: Recruiter Screen, Job Fit, Architectural Presentation, Stakeholder Interview, and Bar Raiser. Each stage includes the competencies being evaluated, baseline questions with role-specific adaptations, what a strong answer looks like per question, and red flags to watch for. The document also includes a role context summary and optional competency evaluation table.
Can I use this for roles other than Engineering Manager?
This skill is specifically calibrated for Engineering Manager hiring -- the five-stage structure, question bank, and evaluation rubric are all built around EM-specific competencies like people leadership, technical depth, cross-functional influence, and AI fluency. For other roles, the output structure will still be generated but the question bank and rubric anchors are EM-specific.
How does it handle role-specific customization?
The skill keeps the interview structure and question format consistent across all EM roles -- so every candidate gets an equitable process -- but injects role-specific language where your inputs call for it. For example, if platform experience is a table stake, it adapts the relevant baseline questions to surface that context explicitly rather than replacing them entirely.