Director, Engineering Operations

We need to output HTML fragment with sections: About the role? The posting includes description of company and role. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We have content: company description (Order.co is...). That could be "About the role" or maybe "About the company". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include the description of role and company? The role description is under "The Role As Director, Engineering Operations...". So we can put that under About the role. Responsibilities: we have a big list under "Responsibilities" with subheadings like Executive Communication Impact, Outcome & KPI Definition, etc. We need to list duties as

• . Should we keep subheadings? Probably we can just list each bullet as a responsibility. The subheadings could be considered part of responsibilities but we can incorporate them into bullet text. Must preserve all substantive information. So we need to extract each responsibility bullet. Let's parse responsibilities section: Executive Communication Impact - Create a clear, executive-ready narrative connecting Product, Engineering, and Data investments, delivery, and operational performance to customer and business outcomes - Own recurring executive updates, company communications, and board-level inputs, supported by a reliable source of truth for commitments, outcomes, and delivery health - Surface material changes, trade-offs, risks, and decisions early, with concise context and clear recommendations Outcome & KPI Definition - Translate company and product strategy into measurable outcomes, objectives, key results, and operating KPIs with clear owners, baselines, targets, data sources, and review cadences - Develop a balanced view of customer and business impact, delivery effectiveness, quality, reliability, security, efficiency, and organizational health - Partner with Data, Finance, Product, and Engineering to improve instrumentation and use KPI trends to guide decisions and evaluate results Portfolio & Planning Cadence - Design and operate annual, quarterly, and ongoing portfolio-planning cadences across Product and Engineering - Maintain a current portfolio view connecting strategic outcomes, initiatives, ownership, dependencies, milestones, capacity, and risk - Facilitate prioritization and sequencing decisions so assumptions, trade-offs, decision rights, and changes are explicit SDLC Process & Operating Reviews - Define and continuously improve a lightweight, consistent software delivery lifecycle from discovery through release, adoption, measurement, and learning - Establish operating reviews focused on outcomes, delivery confidence, quality, reliability, customer impact, constraints, risks, and decisions - Use operating data, retrospectives, automation, and appropriately governed AI-enabled practices to remove friction and improve delivery without adding unnecessary process Resource & Capacity Planning - Build a practical capacity model connecting portfolio demand with available teams, critical skills, hiring plans, external partners, and operational obligations - Partner with Finance, Product, and Engineering leaders on headcount planning, allocation trade-offs, capability gaps, and investment choices - Model alternative portfolio and staffing scenarios and compare planned versus actual capacity to improve future decisions without creating false precision Cross-Functional Risk & Decision Tracking - Establish a clear system for identifying, owning, escalating, and resolving cross- functional risks, dependencies, and decisions - Facilitate difficult discussions where business goals, customer needs, technical constraints, security, compliance, cost, or timing compete - Close the loop by documenting decisions, updating plans, confirming accountable owners, and addressing recurring root causes Organizational Leadership & Collaboration - Serve as a trusted operating partner to the CTO, Engineering leadership, Product leadership, and the Engineering Leadership Team - Strengthen cross-functional relationships, ownership, and accountability through structured thinking, sound judgment, influence, and consistent follow-through We need to include all these as list items under Responsibilities. Qualifications & Experience: we have bullet list. Qualifications & Experience - Leadership experience in Engineering Operations, Product Operations, Technical Program Management, Business Operations, a technical Chief of Staff role, or a comparable function within a SaaS or product-led technology company - Exceptional executive communication skills and demonstrated success connecting Product and Engineering work to customer and business impact - Experience defining outcomes, OKRs, KPIs, scorecards, portfolio-planning processes, and operating-review cadences across multiple teams - Working knowledge of modern product development and software delivery lifecycles, including platform, reliability, security, and technical investment trade-offs - Experience with resource, headcount, budget, and capacity planning in partnership with Finance and functional leaders - Strong analytical judgment and the ability to build trustworthy reporting from product, engineering, financial, and customer data - Proven ability to facilitate difficult cross-functional decisions, manage material risks and dependencies, and bring structure to ambiguity - Pragmatic experience using AI-assisted tools to improve synthesis, planning, and analysis while verifying outputs and protecting sensitive information We can put these under Requirements or Qualifications. The instruction says use headings like Requirements, Qualifications, Skills. We need to decide which to use. Probably combine qualifications and experience under "Qualifications". Could also have "Requirements" for mandatory and "Qualifications" for preferred, but we only have one list. We'll use "Qualifications". Could also add "Skills" but not needed. What Great Looks Like: that's descriptive but not a standard heading; we could maybe include under "About the role" or separate? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. This section is substantive; we could make a section "What Great Looks Like". But not in the allowed headings list. The allowed headings are examples; we can use others? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should stick to those. So we should not create a section for What Great Looks Like; we could incorporate that content into About the role or Qualifications? Probably incorporate into About the role as part of description. Interview Process and What You'll Receive: we have compensation and benefits. Benefits: "A competitive compensation packageEmployer-sponsored 401(k) with matchComprehensive medical, dental, and vision coverageFlexible time off and hybrid / remote work environmentThe anticipated annual salary range for this role is $200,000 - $230,000. Actual compensation and title will be commensurate with experience, qualifications, knowledge, and skills." We need to include Pay and Benefits sections if posting actually states them. Pay: we have salary range. Benefits: we have list of benefits. So we should create Benefits section with

  • items: competitive compensation package, employer-sponsored 401(k) with match, comprehensive medical, dental, and vision coverage, flexible time off, hybrid/remote work environment. Pay section: we can include the salary range. Should we include "Actual compensation and title will be commensurate with experience..."? That's filler; we should not include placeholder like "commensurate with experience". The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. So we can include Pay section with the salary range; we should avoid the commensurate sentence. So Pay:

    The anticipated annual salary range for this role is $200,000 - $230,000.

    Benefits: list items. Schedule: not mentioned; we should not create Schedule section. We also need to include About the role section: combine company description and role description. Let's craft About the role: include the introductory paragraph about Order.co and then the role description. We must not repeat the job title as a heading. So we won't have a heading for Director, Engineering Operations. We need to output only HTML fragment, no /, no markdown. Let's structure:

    About the role

    Order.co is the System of Action for the Office of the CFO, transforming the way businesses purchase and pay into an intuitive, B2C-like shopping experience. Order.co leverages embedded AI agents and embedded financial products to reinvent the way businesses connect with their vendors. End users enjoy a seamless, zero-training buying experience, while finance and procurement leaders gain a single platform to orchestrate how the business “should operate”. The result is an all-in-one solution that serves as a gravitational pull for spend and data, automating and eliminating procurement and finance workflows from requisition to reconciliation along the way. Order.co is on the cutting edge of B2B Agentic Commerce, poised to be the market leader in creating a more predictive, prescriptive, and personalized experience for users. Founded in 2016 and headquartered in New York City, Order.co oversees nearly half a billion in annualized spend across hundreds of customers like WeWork, SoulCycle, Lume, and [solidcore]. Order.co has raised $75M in funding from industry-leading investors like MIT, Stage 2 Capital, Rally Ventures, 645 Ventures, and more. Order.co has been proudly named a 50 to Watch by Spend Matters and a Best Place to Work by BuiltIn and Inc. Magazine. As Director, Engineering Operations, you will build and run the operating system that helps Product and Engineering translate strategy into measurable business and customer impact. You will create clarity across outcomes, priorities, capacity, delivery health, risks, and decisions, then turn that clarity into concise executive communication and disciplined organizational action. This high-leverage leadership role partners closely with Product, Engineering, Data, Operations, Finance, Go-to-Market, Customer Success, Security, and other business functions. You will play a critical role in ensuring all functions are aligned and understand the expected outcomes.

    Then Responsibilities:

    Responsibilities

    • Create a clear, executive-ready narrative connecting Product, Engineering, and Data investments, delivery, and operational performance to customer and business outcomes
    • Own recurring executive updates, company communications, and board-level inputs, supported by a reliable source of truth for commitments, outcomes, and delivery health
    • Surface material changes, trade-offs, risks, and decisions early, with concise context and clear recommendations
    • Translate company and product strategy into measurable outcomes, objectives, key results, and operating KPIs with clear owners, baselines, targets, data sources, and review cadences
    • Develop a balanced view of customer and business impact, delivery effectiveness, quality, reliability, security, efficiency, and organizational health
    • Partner with Data, Finance, Product, and Engineering to improve instrumentation and use KPI trends to guide decisions and evaluate results
    • Design and operate annual, quarterly, and ongoing portfolio-planning cadences across Product and Engineering
    • Maintain a current portfolio view connecting strategic outcomes, initiatives, ownership, dependencies, milestones, capacity, and risk
    • Facilitate prioritization and sequencing decisions so assumptions, trade-offs, decision rights, and changes are explicit
    • Define and continuously improve a lightweight, consistent software delivery lifecycle from discovery through release, adoption, measurement, and learning
    • Establish operating reviews focused on outcomes, delivery confidence, quality, reliability, customer impact, constraints, risks, and decisions
    • Use operating data, retrospectives, automation, and appropriately governed AI-enabled practices to remove friction and improve delivery without adding unnecessary process
    • Build a practical capacity model connecting portfolio demand with available teams, critical skills, hiring plans, external partners, and operational obligations
    • Partner with Finance, Product, and Engineering leaders on headcount planning, allocation trade-offs, capability gaps, and investment choices
    • Model alternative portfolio and staffing scenarios and compare planned versus actual capacity to improve