Engineering executive questions
Evaluate executive responsibilities as the employer actually defines them. CTO and VP Engineering titles differ between companies. These cards assume business and organizational responsibility, not merely a senior technical title. Apply evaluation; strategies and plans are not past accomplishments.
E01 — How do you develop and evaluate engineering strategy?
Variants: Describe a strategy you led. What would your strategy be here?
Intent: Examine diagnosis, focus, coherent action, and adaptation.
Strong answer target: Describe the business need and observed constraints, then explain your diagnosis and the few choices that followed. Show what you deliberately did not pursue, how engineering and other functions aligned, and how the actions addressed the diagnosis. Explain evidence of progress and how the strategy was revised. Separate a hypothetical company diagnosis from known facts.
Profile inputs/adaptation: Strategy episode, business context, resources, decision authority, peer input, actions, and observations. Director moving to executive: state the boundary of prior authority. CTO defined as technical leader: focus on technical strategy and its business connection without inventing financial control.
Acceptable alternatives: Stabilization, simplification, cost reduction, selective investment, or stopping initiatives can be valid strategies. Avoid preferring novelty or expansion by default. A strategy may evolve without failing.
Probes: What is the diagnosis? Which choice was hardest? What evidence would invalidate the plan? How much did learning cost?
Failure modes: Roadmap presented as strategy, imported playbook, everything a priority, or invented certainty about the prospective employer.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Diagnosis | Solutions are disconnected from an observed problem | Links context and constraints to a clear diagnosis |
| Coherent choices | Broad aspirations without tradeoffs | Describes focused choices and reinforcing actions |
| Learning and impact | Claims success from activity alone | Uses relevant outcomes and a credible revision process |
Provenance: Practice extrapolation from L07 and L08.
E02 — What would you do in your first 90 days?
Variants: How would you enter this organization? Where would you start?
Intent: Examine learning, urgency, relationships, and credible initial action.
Strong answer target: Clarify success expectations, learn the business and how work gets done, build peer/report relationships, and test a diagnosis. Identify what might need immediate attention and how you would check that. Propose a small number of initial actions with assumptions and success checks. Adapt the pace to company size and actual urgency instead of a rigid calendar.
Profile inputs/adaptation: Known employer facts, role mandate, uncertainties, user experience, and hypothetical assumptions. New external executive: avoid importing the previous company's solution. Internal promotion: explain which assumptions still need revisiting. Technical CTO: adapt to actual authority.
Acceptable alternatives: Immediate mitigation can coexist with learning. A small organization may not need three months of discovery. An incomplete plan with useful questions is stronger than false insider certainty.
Probes: What would you ask the CEO? Which evidence would make you act in week one? What would you share as an observation rather than a conclusion?
Failure modes: Preselected reorganization, 90 days of passive observation, or arbitrary promises of improved business metrics.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Learning agenda | Does not investigate business or expectations | Proposes targeted learning tied to the mandate |
| Urgency judgment | Always waits or always transforms immediately | Distinguishes urgent known risks from uncertain changes |
| Initial action | Promises change without assumptions or checks | Names proportionate actions and observable success conditions |
Provenance: Practice extrapolation from L12. Worked plan: examples.
E03 — How do you allocate engineering resources?
Variants: How would you cut a budget? How do you decide whether to hire, buy, or build?
Intent: Examine financial reasoning and explicit opportunity costs.
Strong answer target: Establish the objective, constraints, and reliability of the available financial/workload information. Compare realistic options, including stopping work, and connect costs to expected value and risk. Explain who owns the decision, how affected peers participate, and how you revisit the allocation. Do not claim that adding headcount automatically increases delivery.
Profile inputs/adaptation: User's actual budget authority, business goals, estimates with assumptions, dependencies, and consequences. Prior director: state whether you proposed or approved spending. Executive: address cash/time constraints and effects beyond engineering. No invented financial metrics.
Acceptable alternatives: Reducing scope, investing in an enabling system, retaining capability during a contraction, or purchasing a solution can be defensible. A hiring freeze is not automatically poor leadership; cuts require understanding what capacity or risk is being accepted.
Probes: What stops if we choose this? What assumption drives the estimate? How will you know the investment is useful? What if the budget changes?
Failure modes: Spreadsheet precision without reliable inputs, distributing cuts mechanically without consequences, or treating engineering spend in isolation.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Business framing | No objective or understanding of constraints | Connects allocation to business needs and actual authority |
| Options and uncertainty | Offers one option with unjustified estimates | Compares options and names material assumptions/risks |
| Accountable allocation | Ignores effects and review | Makes opportunity costs explicit and defines a revision check |
Provenance: Editorial resource-allocation rubric. L04 explicitly identifies financial planning as an executive assessment area; it does not supply these anchors.
E04 — When and how would you change the organization?
Variants: How do you manage managers? How would you assess a troubled engineering organization?
Intent: Examine system diagnosis, organizational design, and leadership capability.
Strong answer target: Define the problem through evidence about work, decisions, accountability, or dependencies. Compare structural change with better expectations, interfaces, or support. Explain authority, manager involvement, disruption risks, transition, and success checks. Show how managers gain usable responsibility rather than requiring your approval for everything.
Profile inputs/adaptation: Actual organization, symptoms, user authority, stakeholder perspectives, options, actions, and outcomes. Historical answer: include what the redesign did not fix. Situational answer: seek missing context before prescribing layers or reporting lines. No universal span-of-control rule.
Acceptable alternatives: Keeping the structure and changing its operation can be strongest. A reorganization, leadership change, or temporary incident structure may be warranted. Support and inspection can coexist with autonomy.
Probes: Why would an org-chart change solve this? Who loses clarity during the transition? How do you know your managers can lead without you?
Failure modes: Reorganization as a first reflex, bypassing managers, optimizing title hierarchy, or declaring success on announcement day.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| System diagnosis | Prescribes structure without understanding the problem | Uses evidence and competing explanations |
| Design judgment | Changes reporting lines without examining effects | Compares options and addresses decision flow and disruption |
| Leadership capability | Executive remains the necessary decision center | Defines manager authority, support, and outcome checks |
Provenance: Editorial organization rubric. L03 supports using organization-health exercises; the particular answers are ours.
E05 — How do you know engineering is creating value?
Variants: What do you measure? How do you communicate engineering performance to the CEO?
Intent: Examine decision-useful measurement and business accountability.
Strong answer target: Start with the decision and audience, then identify the outcomes and operational signals that inform it. Explain definitions, limitations, and qualitative checks. Connect engineering's contribution to the business without claiming sole causality. Give an example where a measure changed a decision, or a scenario with a clear intended use.
Profile inputs/adaptation: Actual goals, audience, measure definitions, sources, decision, and observed effects. Delivery metrics inform execution; customer and business outcomes inform value. Technical CTO: explain shared ownership with product and business peers. Do not fabricate attribution from correlation.
Acceptable alternatives: Sparse but useful measures, qualitative evidence, or replacing a misleading metric can be good judgment. Different stages and audiences warrant different views. More dashboards do not imply more control.
Probes: Which decision changes if this number moves? How could teams game it? Which important work is invisible? What does the metric not establish?
Failure modes: Individual code-output leaderboard, one universal velocity number, business-causality claims without evidence, or metrics no one uses.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Decision purpose | Collects numbers without a use | Connects measures to a concrete audience and decision |
| Measurement judgment | Treats proxies as complete truth | Defines signals, limitations, and corroborating checks |
| Value and action | Claims value from activity alone | Explains contribution and resulting decisions honestly |
Provenance: Practice extrapolation from L11.