Engineering management questions
These cards test work through people and teams. First-time managers may use transferable examples or labeled scenarios; do not convert those into a claim of prior management experience. Apply evaluation to the actual role. Directors should explain how they enable managers as well as contributors.
M01 — Why management, and what is your management approach?
Variants: Why become a manager? What do you believe a manager is responsible for?
Intent: Understand motivation, role understanding, and behavior behind a philosophy.
Strong answer target: Explain which management responsibilities attract you, what the team should gain, and how you know this work suits you. State a small number of operating principles and demonstrate one in an episode. Address delivery and people development together rather than defining management only as kindness, control, or leaving coding behind.
Profile inputs/adaptation: User motivation, actual responsibility, example, and target expectations. First-time manager: mentorship, coordination, feedback, and the gap to formal management. Experienced manager: changed practices and team effects. Director: how managers make decisions without becoming conduits.
Acceptable alternatives: Exploration is honest if accompanied by an understanding of the work. An IC career or a return to it remains valid; do not grade interest in management as more ambitious than other choices.
Probes: What would you miss about IC work? When did one of your principles need adapting? How would your team describe your behavior?
Failure modes: Title/status motivation alone, slogans without behavior, or treating the manager as the best engineer who approves everything.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Role understanding | Confuses management with status or technical control | Describes concrete delivery and people responsibilities |
| Motivation | Cannot connect interest to the actual work | Explains a considered reason supported by experience or exploration |
| Operating behavior | Philosophy consists only of labels | Demonstrates a principle and its contextual limits |
Provenance: Direct management-interview theme in F01; role definition informed by L01. Answer shape and anchors are ours.
M02 — How involved should you be technically?
Variants: How do you spend your time? How much should a manager code?
Intent: Test alignment with the role and effective allocation of attention.
Strong answer target: Define the target role's technical expectations and how you stay able to evaluate important work. Give an example of choosing to engage, coach, or step back. Explain which responsibilities would suffer if you became a critical-path implementer. Do not claim one percentage fits every team.
Profile inputs/adaptation: Actual team context, technical responsibilities, time tradeoffs, and an intervention example. Small-team EM: possibly hands-on delivery with explicit limits. Director: inspect decisions and develop technical leaders. Manager of managers: retain relevant judgment without bypassing managers.
Acceptable alternatives: Coding may be expected, optional, or rare. A specific deep dive can be valuable even when normal management work is indirect. The candidate should disclose a mismatch with the advertised role rather than pretending to prefer it.
Probes: When did your involvement become a bottleneck? How do you detect a technical issue without owning every implementation?
Failure modes: Blanket “managers never code,” manager as mandatory reviewer of everything, or coding used to avoid difficult people work.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Role alignment | Uses a universal rule despite target responsibilities | Explains involvement appropriate to this role |
| Technical judgment | Cannot describe how important work is understood | Shows an effective way to inspect or evaluate decisions |
| Attention tradeoff | Ignores bottlenecks or displaced responsibilities | Explains when to engage or step back and why |
Provenance: Practice extrapolation from L09, including changing expectations rather than a timeless coding rule.
M03 — Tell me about delegating important work
Variants: How do you delegate? What did you do when delegated work went off track?
Intent: Examine autonomy, support, and accountability.
Strong answer target: Explain why the work and person were suitable, define the outcome and authority, and describe the support you agreed. Show how progress and escalation were handled without dictating every step. Explain what the delegate decided and what you remained accountable for. Discuss the result and how the arrangement changed when needed.
Profile inputs/adaptation: Assignment, delegate's capacity and interests, constraints, decision rights, checkpoints, and result. EM: task or project. Director: a manager-owned team problem. Executive: a function or strategic initiative, with explicit business constraints. Do not disguise dumping unwanted work as development.
Acceptable alternatives: Closer support is appropriate for unfamiliar or high-risk work. Reclaiming a task can be defensible if the reason and effect on trust are addressed. Delegation need not wait for perfect readiness.
Probes: What could they decide without you? What would cause escalation? What did you change when the first approach failed?
Failure modes: Abdication, delegation without authority, hidden success criteria, or taking back every decision that differs from your preference.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Clear agreement | No understandable outcome or decision boundary | Agrees outcome, authority, and constraints |
| Support | Leaves the person unsupported or dictates all steps | Tailors support/checkpoints to readiness and risk |
| Accountability | Transfers blame or erases autonomy | Explains retained responsibility and proportionate course correction |
Provenance: Practice extrapolation from H02. Worked answer: examples.
M04 — How have you helped someone grow?
Variants: Describe coaching, mentoring, or sponsorship. How do you develop future leaders?
Intent: Understand individualized development and contribution to others' capability.
Strong answer target: Explain the person's goals as they expressed them, the opportunity or gap, and the support you supplied. Distinguish giving advice, helping them reason, opening opportunities, and offering feedback. Describe what they did and learned rather than taking ownership of their achievement.
Profile inputs/adaptation: Consented/anonymized episode, user actions, opportunities, follow-up, and outcomes. First-time manager: mentorship is transferable evidence. EM: growth within real job expectations. Director: manager judgment and succession. Executive: leaders and systemic access to development. Do not imply everyone should want promotion or management.
Acceptable alternatives: Supporting depth in an existing role, helping someone change tracks, or recognizing an ill-fitting opportunity can be good development. A promotion is not the only acceptable result.
Probes: What did they want? How did you know the support was useful? Who else received comparable opportunities?
Failure modes: Prescribing a career path, attributing their success to self, or offering a stretch assignment without support or capacity.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Individual understanding | Assumes goals without asking | Connects support to the person's stated needs and interests |
| Development action | Only says “I mentored them” | Describes relevant feedback, learning, or opportunity access |
| Capability and ownership | Claims their achievement without evidence | Shows what they learned/did and bounds the manager's contribution |
Provenance: Editorial development synthesis; opportunity/capacity context informed by H04.
M05 — How do you handle underperformance?
Variants: Describe a difficult performance situation. What if someone repeatedly misses expectations?
Intent: Examine diagnosis, fair expectations, support, and timely accountability.
Strong answer target: Define the gap using observable work and agreed role expectations. Check clarity, resources, workload, and other explanations rather than diagnosing character. Describe direct feedback, the person's perspective, support, follow-up, and what happened. If improvement did not occur, explain the decision and appropriate organizational process without disclosing private details.
Profile inputs/adaptation: Anonymized episode or scenario, expectations, observations, support, authority, and outcome. First-time manager: label a plan as hypothetical. Director: coach the responsible manager without bypassing them. Executive: examine systemic incentives and inconsistent expectations too.
Acceptable alternatives: Changing scope, improving support, recognizing role mismatch, formal escalation, or ending employment may be appropriate. Serious misconduct may require immediate action. There is no mandatory number of conversations or universal improvement-plan timeline in this rubric.
Probes: Did they understand the gap? What part of the environment or your management contributed? What changed the decision?
Failure modes: Surprise consequences, endless vague coaching, treating disagreement as underperformance, or making a legal conclusion from a mock scenario.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Diagnosis | Labels the person without a work-based gap | Establishes expectations and examines plausible causes |
| Fair support | No understandable feedback or chance to respond | Describes direct dialogue and proportionate support |
| Accountability | Avoids the issue or imposes unexplained consequences | Uses observable follow-up and a justified next decision |
Provenance: Practice extrapolation from R04, not employment-law guidance or a required process duration.
M06 — Give difficult feedback to this person
Variants: Role-play a missed commitment. How would you address harmful meeting behavior?
Intent: Observe actual feedback behavior rather than only a claim of being candid.
Strong answer target: State a concrete observation, explain the relevant effect, and invite their perspective or propose a clear next action. Check understanding and agree follow-up. Use a respectful, direct opening; avoid a long compliment preamble that obscures the concern. In a role-play, respond to the other person's information rather than delivering a memorized monologue.
Profile inputs/adaptation: Scenario facts, manager authority, relevant expectation, and privacy context. EM: report's behavior. Director: a manager's handling of a team problem. Executive: peer or senior leader, recognizing limits of unilateral authority. No invented observation should be added to the scenario.
Acceptable alternatives: Asking a diagnostic question before stating a request is sound when causes are unknown. Urgent safety issues may require clear immediate direction. Warmth need not mean euphemism.
Probes: What would you say verbatim? How would you respond if the person disagrees with your facts? What agreement would end the conversation?
Failure modes: Character labels, hearsay as fact, public humiliation, or empathy language without an understandable expectation.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Factual clarity | Opens with labels or vague disappointment | States a specific observation and relevant effect |
| Dialogue | Dictates a conclusion and ignores new information | Invites and responds to the person's perspective |
| Action | Leaves the desired change unclear | Establishes a relevant next step and follow-up |
Provenance: Practice extrapolation from H01; direct exercise rationale in L03. Worked wording: examples.
M07 — How do you run useful one-to-ones?
Variants: What happens in your 1:1s? What if the person says everything is fine?
Intent: Understand a dependable space for support, feedback, and development.
Strong answer target: Explain how you agree the purpose and cadence, make room for the other person's priorities, and follow through on commitments. Show an example where listening led to a useful action or understanding. Keep room for growth and concerns beyond project status; respect personal boundaries.
Profile inputs/adaptation: Actual routine, participant preferences, example, and follow-up. First-time manager: label proposed cadence as a plan. Director: support managers' judgment. Executive: reports and peer relationships, not a requirement to personally meet every employee every week.
Acceptable alternatives: Different frequencies, lengths, asynchronous preparation, or walking meetings can work if the agreed needs are met. A quiet conversation is not automatically failure or concealed dissatisfaction. Ask about concerns rather than diagnosing mood from body language.
Probes: What changed because of one conversation? How do you avoid solving everything for the person? What happens when you must reschedule?
Failure modes: Solely reading status updates, repeated cancellation, forcing private disclosure, or a meeting ritual without follow-through.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Purpose | Treats the meeting only as reporting to the manager | Provides space for individual needs, feedback, and growth |
| Listening | Assumes concerns or imposes only the manager's agenda | Uses questions and respects the person's choices |
| Reliability | Commitments disappear or meetings are routinely neglected | Demonstrates dependable access and relevant follow-through |
Provenance: Practice extrapolation from R06. Cadence flexibility and avoiding mood inference are our adaptations.
M08 — How would you build and improve a hiring process?
Variants: How have you hired? How do you address a weak candidate pipeline?
Intent: Examine role clarity, shared hiring responsibility, and usable assessment.
Strong answer target: Start with what the team needs someone to do, then define assessment and sourcing around it. Explain manager/recruiter/interviewer responsibilities, candidate communication, and how you detect process problems. Discuss barriers to a broader pipeline and consistent job-relevant criteria. Avoid treating “culture fit” or similarity to current staff as competence.
Profile inputs/adaptation: Actual hiring authority, role definition, pipeline, process observations, and changes. EM: team role and interviews. Director: manager consistency and resource constraints. Executive: portfolio needs and hiring system. No invented hire count or diversity improvement metrics.
Acceptable alternatives: Hiring fewer people, changing a poorly scoped role, developing internal talent, or improving retention may solve the underlying need. Candidates with no hiring history can analyze a scenario and state the boundary.
Probes: Which skill does this interview assess? Where are candidates lost? How would you notice interviewers disagreeing for irrelevant reasons?
Failure modes: Hiring as recruiting's problem alone, vague “raise the bar,” unrelated trivia, or treating candidate pedigree as the rubric.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Role definition | Cannot connect assessment to actual work | Defines important responsibilities and corresponding skills |
| Shared process | Relies on one person or unstructured impressions | Clarifies roles, consistent assessment, and candidate information |
| Improvement | Assumes more candidates fixes every problem | Diagnoses a bottleneck and proposes a measurable change |
Provenance: Direct pipeline theme in F01; assessment design informed by L02. Detailed process and anchors are editorial.
M09 — What tells you a team is healthy and effective?
Variants: How do you build a high-performing team? Can the team work without you?
Intent: Examine delivery, capability, trust, and sustainability together.
Strong answer target: Define the team's purpose and describe several observable signals: useful delivery, clear ownership, learning, candid feedback, manageable load, and the ability to resolve disagreement. Give an actual intervention and its effect. Explain how you would detect misleading signals such as apparent harmony accompanied by suppressed concerns.
Profile inputs/adaptation: Team context, observations, role, intervention, and outcome. EM: individuals and team practices. Director: dependencies and manager capability. Executive: operating systems across groups. Include customer and stakeholder outcomes where appropriate, not only internal sentiment.
Acceptable alternatives: Healthy teams can disagree and encounter incidents. Low attrition alone is insufficient; a necessary departure is not automatically failure. Different contexts require different checks.
Probes: What happens when you are away? Which signal has misled you? What would the least-heard person say about the team?
Failure modes: Delivery at any human cost, measuring health by agreement, leader heroics, or interpreting one survey number as a complete diagnosis.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Balanced definition | Equates health with speed or niceness alone | Combines purpose, capability, people, and sustainability |
| Observation | Uses only intuition or one proxy | Uses concrete signals and understands their limitations |
| Team capability | Success depends on constant manager intervention | Shows a durable improvement in team autonomy or functioning |
Provenance: Practice extrapolation from U01 and L09.
M10 — A strong employee is upset about not being promoted. What do you do?
Variants: Role-play a promotion conversation. How do you handle retention concerns?
Intent: Examine listening, fair expectations, and honest communication.
Strong answer target: First learn what the person expected, what matters to them, and what information is missing. Clarify criteria, evidence, decision ownership, and constraints. Acknowledge any manager failure to set expectations. Discuss credible next actions without guaranteeing an outcome outside your authority. If the decision was flawed, explain how you would seek correction.
Profile inputs/adaptation: Scenario facts, career expectations, actual criteria, evidence, and decision authority. EM: understand and support the report. Director: examine calibration and coach managers. Executive: inspect system fairness without making an exception solely to keep a favored employee.
Acceptable alternatives: A promotion, a delayed decision, a role change, or an honest disagreement may follow. Wanting more pay without broader scope is a valid preference; do not assume every concern is about title.
Probes: What if expectations were never documented? What can you actually promise? What would you do if comparable evidence was treated differently?
Failure modes: Instant reassurance, promises you cannot keep, dismissing the concern as entitlement, or retention bargaining without examining fairness.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Understanding | Assumes motives and defends the decision immediately | Explores the person's expectations and missing context |
| Fair explanation | Uses opaque authority or personal preference | Explains criteria, evidence, limits, and possible correction |
| Credible action | Makes empty promises or offers no path | Agrees realistic next steps within actual authority |
Provenance: Direct role-play theme in F01; listening adaptation informed by H03. Our scenario and anchors are original.