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

We need to output HTML fragment only, with sections for headings: About the role, Responsibilities (What You'll Do), Qualifications (Required Experience, Preferred Experience, Leadership Competencies, Success Measures?), Benefits, Pay, Schedule? We must include sections only if posting has real specific content. Pay is given: salary range $130,970 - $183,680 USD. Benefits: described. Schedule not mentioned, so omit. Also need to include maybe "About The Role" heading. Use

for each section heading. We must not repeat job title. No Job ID. Remove boilerplate like EEO, etc. Also remove "Learn More About Voya Benefits (download PDF)" maybe considered boilerplate? It's a link but it's part of benefits description; we can keep description but maybe drop the link text? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn More About Voya Benefits (download PDF)" is not exactly boilerplate but could be considered a link; but it's part of benefits description. Safer to keep the benefits description but maybe drop that line? It's not essential; but we can keep it as part of benefits description. However it's a call to action; maybe considered application instruction? Not exactly. I'd keep it. We need to preserve all substantive information. So we need to include the purpose statement at top? The first paragraph is about company purpose; that's substantive but not a section heading. Should we include it as a

before sections? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we should output an HTML fragment that includes the purpose statement as a

  maybe, then sections. We need to decide which sections to include: About The Role (the paragraph after "About The Role"), Responsibilities (What You'll Do), Qualifications (maybe combine Required Experience, Preferred Experience, Leadership Competencies, Success Measures), Benefits, Pay. Possibly also Skills? The posting includes "Critical Skills" section; we could make a Skills section. The instruction says use headings like Skills. So we should include a Skills section for Critical Skills. Thus sections: About The Role, Responsibilities, Qualifications, Skills, Benefits, Pay. We must not include Schedule (no info). Also not include Requirements separate if covered in Qualifications. We need to format lists where appropriate. Let's extract content. 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" We should keep that as prose

  . The "Start your Voyage – Apply Now" is application instruction; we should remove that line. So remove that sentence. Also maybe remove "Start your Voyage – Apply Now". So we keep up to "essential to our vision." Then maybe a sentence about readiness? "Are you ready to join a company with a strong purpose and a winning culture?" That's not application instruction, it's a rhetorical question; we can keep. But the instruction says remove application instructions. That sentence is not an instruction to apply; it's a question. Might keep. Safer to keep it. Thus purpose paragraph: combine all except the "Start your Voyage – Apply Now". We'll produce a single

  with that text (maybe two paragraphs). We'll keep as one

  . Now About The Role section: heading

  About The Role

  . Then prose: the paragraph(s) after that heading until "What You'll Do". Let's extract: "Voya is building a next-generation, AI-native Wealth Management platform designed to serve as the digital front door for the enterprise. This platform will create a unified client experience across Retirement, Employee Benefits, Wealth Management, and Investment Management, enabling clients to seamlessly discover, engage, and transact across Voya's full suite of solutions. The Director, Engineering (Business Strategy, Platform Roadmap & Client Experience) serves as the critical bridge between business strategy, product management, customer experience, and engineering execution. This leader translates enterprise priorities into technology roadmaps and ensures delivery of a scalable platform that connects participants, plan sponsors, advisors, employers, and individual investors through a single, integrated ecosystem. This role is ideal for a technology leader who understands both business growth objectives and modern digital platform architectures. The successful candidate will help shape the future of Voya's digital experience by creating technology capabilities that drive client acquisition, retention, cross-sell expansion, and long-term relationship growth." We'll put that in

  . Now Responsibilities: heading

  Responsibilities

  . Then we need to list the bullet points under "What You'll Do". The content includes several bold headings: Own the Business-to-Technology Roadmap, Lead the "One Front Door" Strategy, Connect Enterprise Businesses Through Technology, Drive AI-Native Digital Transformation, Deliver Business Outcomes, Stakeholder Leadership. Each has sub-bullets. We need to represent as
  • for any list of duties/requirements/benefits. So we can make a top-level
    with each main duty as
    • , and inside each li we can have
      for subpoints? The instruction says use
      • for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do nested. Thus:

        Responsibilities

        • 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.
        Now Qualifications: heading

        Qualifications

        . We have Required Experience, Preferred Experience, Leadership Competencies, Success Measures. Could combine into sections? The instruction says use headings like Qualifications. Could also have subheadings? But we only allowed

        for section headings. Could we use

        for Qualifications and then inside have

        ? Not allowed? The instruction only mentions

        for section headings; doesn't forbid other headings but says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those exact headings for sections. So we should have a Qualifications section, and inside we can have paragraphs and lists. Thus we need to include all qualification details inside Qualifications section. We'll structure:

        Qualifications

        Required Experience

        • 10+ years of progressive experience spanning technology, product, strategy, digital transformation, or engineering leadership.
        • Experience leading large-scale digital platform or customer experience initiatives.
        • Experience operating within highly regulated industries, preferably financial services, retirement, wealth management, insurance, or investment management.
        • Proven ability to translate business strategy into technology execution.
        • Demonstrated success leading complex cross-functional programs with multiple stakeholders.

        Preferred Experience

        • Experience supporting Wealth Management, Retirement Services, Employee Benefits, Investment Management, or FinTech platforms.
        • Experience building platform-based ecosystems serving multiple customer segments.
        • Knowledge of advisor technology, participant experience platforms, client onboarding, customer portals, or wealth management solutions.
        • Experience leveraging AI, analytics, and automation to improve customer outcomes.
        • Familiarity with cloud-native digital platforms, APIs, data ecosystems, and modern engineering delivery models.

        Leadership Competencies

        • Enterprise mindset with strong business acumen
        • Strategic thinker with exceptional execution discipline
        • Influential leader