Director, Engineering (Business Strategy, Platform Roadmap & Client Experience)

We need to output HTML fragment with sections: About the role (already present), Responsibilities (What You'll Do), Qualifications (Required Experience, Preferred Experience, Leadership Competencies maybe), Benefits, Pay, maybe Success Measures? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content. So we need to decide which sections to include. We have content: - About The Role (description). That's a section heading "About the role". Use

About the role

then

with the paragraph(s). The text includes multiple paragraphs; we can combine into one

or multiple? Probably one

with line breaks? We'll keep as

containing the text. - Responsibilities: "What You'll Do" includes bullet points (list). So we need

Responsibilities

then

• items. - Qualifications: There's "Qualifications" heading with Required Experience, Preferred Experience, Leadership Competencies. Could combine into Qualifications section with subpoints? The instruction says use

  for section headings; we can have one Qualifications section and inside we can have

  for required and preferred? Or we could separate Required Experience and Preferred Experience as subheadings? But only allowed headings are those listed; we could still use

  for Qualifications and then inside have

  or

  . Probably best to have

  Qualifications

  then
  for required experience items, then another
  for preferred? But that would be multiple lists under same heading; acceptable. - Benefits: There's a "Be Well. Stay Well." section describing benefits. So we can have

  Benefits

  then
  listing benefits. - Pay: There's compensation disclosure with salary range. So

  Pay

  then

  with the salary range and maybe note about incentives. - Schedule: Not mentioned; we should not include. - Skills: There's "Critical Skills" section. Could be Skills heading. So

  Skills

  then
  of critical skills. - Success Measures: There's "Success Measures Within The First 12–24 Months". That could be considered Requirements? Not exactly. Could be a separate section like "Success Measures" but not in allowed headings list. The allowed headings list includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Success Measures not listed; maybe we could incorporate into Qualifications or Responsibilities? Probably better to omit as not a standard heading; but we could include as a section if we think it's substantive. However instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive list. So we could add other headings if needed, but better to stick to those. Success Measures could be considered under "Requirements" maybe? But it's more about outcomes. Might be okay to include as a separate section "Success Measures" but not in the list; risk of being considered not allowed. Safer to omit or incorporate into Qualifications? I'd omit. - Also there is "Purpose Statement" fluff at top; we should remove boilerplate like mission statements? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The purpose statement at top is not boilerplate but maybe considered fluff; but it's part of the posting's introductory culture description. It might be considered substantive? It's about company purpose. Might be okay to keep as part of About the role? But the About the role section already starts after "About The Role". The preceding paragraphs are generic purpose statements; they could be considered boilerplate? Not exactly legal/EEO. Might be okay to keep as part of About the role? However the instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." The purpose statement is not metadata; it's descriptive. I'd keep it as part of About the role? Actually the About the role section begins after "About The Role". The preceding text is more about company mission; we could include it as a separate section "About Voya" but not in allowed headings. Safer to include it as part of About the role? But the About the role heading expects description of the role; we could prepend the mission paragraphs to that section. However that would mix company purpose with role description; still okay. Better to keep the purpose statement as a separate

  before the headings? The instruction: Output ONLY the HTML fragment. It didn't forbid extra paragraphs not under headings. But they said use

  for section headings; use

  • for any list; use

    for prose. So we can have

    for prose sections not under headings. So we could have a leading

    with the purpose statement, then

    About the role

    etc. But we must preserve ALL substantive information; not invent or summarize away detail. So we need to include the purpose statement text. Let's extract purpose statement paragraphs: "Together we fight for everyone’s opportunity for a better financial future. We will do this together — with customers, partners and colleagues. We will fight for others, not against: We will stand up for and champion everyone’s access to opportunities. The status quo is not good enough … we believe every individual and every community deserves access to financial opportunities. We are determined to support both individuals and communities in reaching a better financial future. We know that reaching this future depends on our actions today. Like our Purpose Statement, Voya believes in being bold and committed to action. We are committed to a work environment where the differences that we are born with — and those we acquire throughout our lives — are understood, valued and intentionally pursued. We believe that our employees own our culture and have a responsibility to foster an environment where we all feel comfortable bringing our whole selves to work. Purposefully bringing our differences together to positively influence our culture, serve our clients and enrich our communities is essential to our vision. Are you ready to join a company with a strong purpose and a winning culture? Start your Voyage – Apply Now" That's a lot; includes call to action "Start your Voyage – Apply Now" which is application instruction; we should remove application instructions. So we need to remove that line. Also remove "Start your Voyage – Apply Now". Also maybe remove the repeated "Together we fight..." etc? It's substantive? It's company mission; we keep except the call to action. Thus we will have a

    with the purpose statement minus the final sentence. Now after that, we have "About The Role" heading. We'll make

    About the role

    then

    with the description paragraphs. Then Responsibilities:

    Responsibilities

    then
    with each bullet from "What You'll Do". Need to capture each bullet line. Let's list responsibilities bullets from the text: - Own the Business-to-Technology Roadmap - Develop and maintain a multi-year technology roadmap aligned with Voya's strategic growth priorities across Retirement, Wealth Management, Employee Benefits, and Investment Management. - Translate executive business objectives into actionable technology initiatives, investment plans, and engineering priorities. - Partner with Product, Engineering, Architecture, Operations, and business leaders to define sequencing, dependencies, and outcomes. - Ensure technology investments are prioritized based on business value, client impact, enterprise scalability, and regulatory requirements. - Lead the "One Front Door" Strategy - Drive development of a unified digital experience serving both B2B and B2C client segments. - Define capabilities that create a seamless experience across: - Retirement participants - Plan sponsors - Advisors - Employers - Individual investors - Wealth Management clients - Partner across business areas to eliminate client friction and create connected customer journeys. - Ensure clients can easily discover, access, and engage with relevant Voya products and services through a common platform experience. - Connect Enterprise Businesses Through Technology - Build alignment across Retirement, Employee Benefits, Investment Management, and Wealth Management teams. - Identify opportunities to leverage shared digital capabilities, customer data, AI solutions, and platform services. - Champion enterprise-wide thinking instead of line-of-business optimization. - Drive platform strategies that increase customer lifetime value and improve client retention. - Drive AI-Native Digital Transformation - Partner with Product and Engineering leaders to embed AI-driven experiences across the client lifecycle. - Identify opportunities for: - Intelligent recommendations - Personalized financial guidance - Conversational experiences - Digital onboarding - Cross-sell and next-best-action capabilities - Ensure AI investments remain aligned with business outcomes and customer needs. - Drive adoption of modern digital, cloud, data, and AI capabilities across the platform. - Deliver Business Outcomes - Define success metrics tied to client adoption, engagement, retention, cross-sell growth, digital utilization, and advisor productivity. - Establish governance mechanisms to monitor roadmap progress and business value realization. - Lead executive-level communications regarding priorities, progress, risks, and investment decisions. - Drive decision-making across highly matrixed stakeholder groups. - Stakeholder Leadership - Serve as the primary liaison between business executives and technology teams. - Facilitate prioritization discussions among competing business units and stakeholder groups. - Build consensus around strategic technology decisions. - Present roadmap recommendations and investment cases to senior leadership. We need to flatten into
    • items; could keep sub-bullets as separate
    • but maybe we should keep hierarchy? The instruction: use
      • for any list of duties/requirements/benefits. It doesn't forbid nested lists, but we can keep flat list for simplicity. However we risk losing some structure. Better to keep as flat list but include the sub-points as separate items; the meaning remains. Thus we will create a
        with each bullet as
        • . We'll include all the bullet points (including sub-bullets). Let's enumerate: 1. Own the Business-to-Technology Roadmap 2. Develop and maintain a multi-year technology roadmap aligned with Voya's strategic growth priorities across Retirement, Wealth Management, Employee Benefits, and Investment Management. 3. Translate executive business objectives into actionable technology initiatives, investment plans, and engineering priorities. 4. Partner with Product, Engineering, Architecture, Operations, and business leaders to define sequencing, dependencies, and outcomes. 5. Ensure technology investments are prioritized based on business value, client impact, enterprise scalability, and regulatory requirements. 6. Lead the "One Front Door" Strategy 7. Drive development of a unified digital experience serving both B2B and B2C client segments. 8. Define capabilities that create a seamless experience across: 9. Retirement participants 10. Plan sponsors 11. Advisors 12. Employers 13. Individual investors 14. Wealth Management clients 15. Partner across business areas to eliminate client friction and create connected customer journeys. 16. Ensure clients can easily discover, access, and engage with relevant Voya products and services through a common platform experience. 17. Connect Enterprise Businesses Through Technology 18. Build alignment across Retirement, Employee Benefits, Investment Management, and Wealth Management teams. 19. Identify opportunities to leverage shared digital capabilities, customer data, AI solutions, and platform services. 20. Champion enterprise-wide thinking instead of line-of-business optimization. 21. Drive platform strategies that increase customer lifetime value and improve client retention. 22. Drive AI-Native Digital Transformation 23. Partner with Product and Engineering leaders to embed AI-driven experiences across the client lifecycle. 24. Ident