Head of Engineering Job Description: Scope, Impact & Qualifications Reports to: CEO Level: Executive (CTO-equivalent scope) Org size: ~25 engineers Time split: 70% Product / 30% Discipline ROLE SUMMARY The Head of Engineering owns the technical outcomes of Maestro's entire product suite while also serving as the top of the engineering discipline ladder: every engineering manager and individual contributor ultimately ladders up to this role. The position deliberately splits attention: 70% product execution, 30% discipline accountability. Product delivery is the immediate, ongoing accountability; discipline work compounds over time and requires protected but smaller blocks of focus so it doesn't get crowded out by delivery pressure. This role sits at the center of Maestro's matrix structure, accountable for craft quality and standards company-wide, while ensuring embedded engineering talent on each product team is pointed at the right priorities. SCOPE • Org reach: all engineering leads across all product lines report into this role (directly or via a lead layer), the senior-most engineering accountability in the company. • Product surface: full product suite, every active product line's engineering output. • Discipline surface: engineering-wide standards, tooling, and process, independent of which product team an engineer sits on. THE 70%: PRODUCT ACCOUNTABILITY The Head of Engineering is the single accountable owner for engineering execution across Maestro's product portfolio. What this looks like day to day: • Partners with the engineering leads of every product line to ensure their teams are resourced against the right priorities: not just busy, but correctly sequenced. • Accountable for ensuring product strategy and roadmap direction are translated into clear, actionable engineering plans, serving as the connective layer between Product and Delivery leadership and the engineering organization, primarily through engineering leads embedded within product teams. • Accountable for applying technical judgment to turn high-level strategic priorities into concrete technical execution plans, enabling and guiding engineering leads to scope, sequence, and de-risk delivery across their product areas. • Identifies where product priorities and engineering capacity are misaligned across teams and resolves the tradeoff, including cross-team resourcing calls. • Is the escalation point when a product line's engineering execution is off track, and is accountable for getting it back on track. Impact: Every product line ships against strategy, not just against what's easiest to build. Product and Delivery leaders have one accountable engineering partner instead of negotiating separately with each product line's lead. THE 30%: DISCIPLINE ACCOUNTABILITY The Head of Engineering owns what "good engineering" means at Maestro, independent of the product line. What this looks like day to day: • Sets and maintains company-wide engineering standards (code quality, architecture principles, technical debt posture). • Owns cross-cutting technical initiatives that no single product team should solve independently, e.g. product suite services and universal QA automation. • Defines how AI tooling is used across engineering, including guardrails to ensure AI usage improves output quality and velocity rather than introducing risk or degrading craft. • Identifies and removes friction in how engineering work gets done company-wide, streamlining processes that slow every team down in the same way. • Is the ultimate accountable owner for engineering management practice (how EMs lead, how performance is evaluated, how the craft is grown) even where day-to-day people management is embedded in product teams. Impact: Engineering quality, velocity, and management practice don't fragment by product line. An engineer's experience of "how we build software here" is consistent no matter which team they're on, and the org gets the benefits of scale (shared tooling, shared standards) instead of each team reinventing its own. SUCCESS LOOKS LIKE • Engineers across the organization deliver flawless technical execution that earns long-term client retention and supports growth. • Product lines are resourced against strategic priority, with tradeoffs made explicitly rather than by default. • Engineering leads across product lines operate with a shared technical bar and shared tooling. • Company-wide initiatives (QA automation, AI usage standards) ship and get adopted, not just get designed. • Engineering management practice is consistent and healthy across the org, even though EMs are embedded in product teams day to day. QUALIFICATIONS Maestro hires for demonstrated capability, not years-of-service checkboxes. The bar below is competency-based: what someone needs to be able to do, not how long they've been doing it. Required competencies: • Has personally carried end-to-end accountability for engineering delivery across more than one product or team simultaneously: not just led a single team, but balanced competing priorities across several. • Can translate ambiguous, high-level strategy (from product, business, or leadership) into a technical execution plan that engineers can actually build against, without needing someone else to do that translation. • Has designed or materially improved an engineering standard, process, or tooling investment that worked across teams (not a single-team fix) and can point to the before/after. • Comfortably operates in a matrixed environment, influencing and aligning engineering leads, their teams, and cross-functional stakeholders without relying on formal authority. • Has hands-on technical depth sufficient to earn credibility with senior engineers and to personally evaluate technical tradeoffs. This is not a purely managerial role. • Has direct experience managing or mentoring engineering managers, not only individual contributors. • Demonstrates sound judgment on when to standardize company-wide versus when to let product teams operate with autonomy. Strongly preferred: • Experience operating at this scope inside a company of comparable size (roughly 15 to 50 engineers), where formal process is lighter and judgment calls happen more often than policy lookups. • Direct experience setting a company's approach to AI-assisted engineering (tooling choices, guardrails, or usage standards) rather than just using AI tools personally. • A track record of building or scaling QA automation, testing strategy, or release process across multiple teams. • Experience partnering directly with Product and Delivery leadership as a peer, not just receiving requirements from them. • Experience leading engineering for always-on, customer-facing digital products or live-service platforms, where availability, release discipline, observability, incident response, and rapid cross-functional coordination directly affect the end-user experience and client retention. What we're explicitly not requiring: • A specific prior title (VP Engineering, CTO, etc.). We care about scope actually carried, not the title it came with. • A minimum years-of-experience threshold. Competency and evidence of impact matter more than tenure. • Deep expertise in every technology in Maestro's stack. Technical judgment and the ability to evaluate tradeoffs matter more than hands-on fluency in any one language or framework.