Corporate Vice President - Solution Architect & Distinguished Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invented summary. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove application instructions. We need to parse the posting. Let's extract relevant content. First paragraph: "Location Designation: Hybrid - 3 days per week Technology, Data, AI And Ventures Within the Tech, Data, AI, Ventures (TDAV) organization, our work is guided by a shared vision: deploying the power of technology, data, AI and ventures to accelerate sustainable competitive advantage for New York Life's businesses. We build solutions that power how we serve policy owners, agents, advisors and employees while delivering measurable business outcomes. Across technology, data, AI, cyber, product, digital experience, architecture and infrastructure, TDAV combines the scale and investment of an industry leader, access to leading-edge technologies and the opportunity to help shape how a world-class financial services company competes in the AI era - all backed by the stability and purpose of a mutual company built to last." That's about the organization. Could be "About the role" or maybe "About the team". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. "Role Overview New York Life is seeking an accomplished Solution Architect & Distinguished Engineer to provide senior, hands-on technical leadership across Field Experience. You will shape the architecture of intelligent, connected, and composable experiences that help our field professionals serve clients, grow their practices, and operate effectively. This role combines modern application architecture, cloud, data, APIs, events, Generative AI, and agentic AI. You will set cross-domain technical direction, create reusable patterns and reference architectures, build prototypes and reference implementations, and solve complex challenges that span products, platforms, data domains, and engineering teams. A major area of impact will be helping New York Life reimagine Field experience, productivity and planning in the new world - moving beyond the digitization of today's processes to rethink how discovery, planning intelligence, recommendations, specialist expertise, advisor workflows, trusted data, NYL360, Generative AI, and governed agentic capabilities can work together. As a member of the Field Experience Forward Leading team, you will help shape the future of the organization by identifying emerging technologies, defining transformational architecture strategies, and turning innovative ideas into scalable solutions. You will operate at the intersection of business strategy, modern engineering, AI, and advisor experience to help New York Life lead in a rapidly evolving industry. This is a senior individual-contributor position. You will lead through technical authority, hands-on expertise, influence, innovation, and mentorship rather than direct people-management responsibility." That's role overview; could go under About the role. Then "What You'll Do" with bullet points (list). That's Responsibilities. Then "What You'll Bring" with bullet points (list). That's Requirements/Qualifications/Skills? The instruction: Use headings for Requirements, Qualifications, Skills. We need to decide where to put content. The "What You'll Bring" includes experience, expertise, etc. Could split into Requirements (years of experience), Qualifications (education), Skills (technical). But we must not invent sections if content is thin. However we have enough detail to fill each. Let's parse "What You'll Bring": - 15+ years of progressive experience in software engineering, enterprise architecture, AI/ML engineering, platform engineering, or related technical disciplines. - Demonstrated success setting technical direction across complex enterprise environments involving multiple applications, platforms, data domains, and engineering teams. - Deep expertise in modern application and distributed-system architecture, including cloud, APIs, services, events, integration, data, security, resilience, observability, and DevSecOps. - Strong experience with Generative AI and agentic AI, including LLM-based systems, retrieval and grounding, context engineering, agent orchestration, tool integration, evaluation, guardrails, and observability. - Proven ability to translate business strategy into target architectures, reusable patterns, prototypes, and practical implementation guidance. - Strong hands-on technical credibility and the ability to engage deeply in architecture, design, experimentation, and complex engineering decisions. - Exceptional systems thinking and the ability to solve ambiguous problems that cross organizational and technology boundaries. - Demonstrated ability to influence senior business and technology leaders through clear communication, sound judgment, technical credibility, and pragmatic decision-making. - A record of mentoring senior technical talent and elevating engineering practices without relying on direct reporting authority. - Bachelor's degree in computer science, engineering, or a related discipline, or equivalent practical experience. Then "Preferred Experience" bullet list: - Experience in financial planning, insurance, wealth management, advisor technology, or another highly regulated environment. - Experience modernizing complex enterprise ecosystems into composable, API- and event-enabled architectures. - Experience designing AI-enabled experiences that combine enterprise data, workflow, decision support, and human judgment. - Experience with responsible AI architectures where security, privacy, explainability, traceability, auditability, and human accountability are essential. - Familiarity with advisor and client journeys, household data, planning and calculation engines, CRM, specialist-support workflows, or enterprise experience platforms. Then "What Success Looks Like" bullet list (outcomes). Could be considered as part of Responsibilities? Might be separate but not required heading. We could include under Responsibilities or maybe a separate section like "Impact". But only allowed headings are the listed ones. We could incorporate into Responsibilities or maybe under "What Success Looks Like" as part of Responsibilities (makes sense). We'll keep it under Responsibilities as additional bullet points. Then "Job Level: LEVELPF6 Pay Transparency Salary Range: $185,000-$264,500 Overtime eligible: Exempt Discretionary bonus eligible: Yes Sales bonus eligible: No Actual base salary will be determined based on several factors but not limited to individual’s experience, skills, qualifications, and job location. Additionally, employees are eligible for an annual discretionary bonus. In addition to base salary, employees may also be eligible to participate in an incentive program." That's Pay info. Also maybe Benefits? There's a section "Our Benefits" later: "We provide a full package of benefits for employees – and have unique offerings for a modern workforce, including leave programs, adoption assistance, and student loan repayment programs. Based on feedback from our employees, we continue to refine and add benefits to our offering, so that you can flourish both inside and outside of work. Click here to discover more about our comprehensive benefit options or visit our NYL Benefits Site." That's Benefits content. Also "Our Commitment to Inclusion" is boilerplate EEO? Might be considered EEO boilerplate; instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove that section. Also "Company Overview" maybe could be part of About the role? But we already have About the role covering role overview. Could also include company overview under About the role? Might be okay but we need to avoid duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep company overview content as well. Where to put? Could be under About the role as a paragraph describing the company. Or we could create a separate section like "About the company" but not allowed headings. So we must fit into allowed headings. Perhaps we can put company overview under About the role as additional paragraph. Also "Location Designation: Hybrid - 3 days per week" is location info; could be included in About the role or maybe under Schedule? Schedule heading is for work schedule (e.g., hybrid, remote). The location designation indicates hybrid - 3 days per week. That's schedule info. So we can put under Schedule heading. Pay heading we have salary range etc. Benefits heading we have benefits description. Now we need to ensure we don't include filler like "commensurate with experience". Not present. We must not repeat job title as heading. So no heading for Solution Architect & Distinguished Engineer. We must not put Job ID/requisition numbers as headings; none present. We must output only HTML fragment, no /, no markdown. We'll structure:

About the role

... (organization description + role overview + company overview)

Responsibilities

• ... each bullet from What You'll Do and What Success Looks Like

Requirements

• ... from What You'll Bring (mandatory)

Qualifications

• ... Bachelor's degree etc (maybe separate)

But we have both requirements and qualifications overlapping. Could combine? The instruction says use headings for Requirements, Qualifications, Skills. We have content for each. We could assign: - Requirements: mandatory experience items (15+ years, demonstrated success, deep expertise, strong experience with GenAI, proven ability to translate business strategy, strong hands-on technical credibility, exceptional systems thinking, demonstrated ability to influence, record of mentoring). That's a lot. - Qualifications: Bachelor's degree. - Skills: maybe list specific technical skills: cloud, APIs, services, events, integration, data, security, resilience, observability, DevSecOps, Generative AI, agentic AI, LLM-based systems, retrieval and grounding, context engineering, agent orchestration, tool integration, evaluation, guardrails, observability, etc. But we already covered many in requirements. Could split. But we must not create thin sections. Let's see if we have enough for each. Requirements: we have many bullet points; good. Qualifications: Bachelor's degree; that's a single item but still substantive. Skills: we could list technical skills: modern application and distributed-system architecture, cloud, APIs, services, events, integration, data, security, resilience, observability, DevSecOps, Generative AI, agentic AI, LLM-based systems, retrieval and grounding, context engineering, agent orchestration, tool integration, evaluation, guardrails, observability, etc. That's a decent list. Alternatively we could put all "What You'll Bring" under Requirements and skip Qualifications and Skills. But instruction says prefer a few substantive sections over many thin ones. Having three sections (Requirements, Qualifications, Skills) might be okay if each has substantive content. Qualifications only has one line; might be considered thin but still substantive (Bachelor's degree). Could combine Qualifications and Skills into one? But headings are prescribed; we can omit a section if no real specific content. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we think Qualifications content is just "Bachelor's degree in computer science, engineering, or a related discipline, or equivalent practical experience." That's specific content, not filler. So we can include Qualifications heading with that content. Skills: we need to extract specific skills from the posting. The "What You'll Bring" includes deep expertise in modern application and distributed-system architecture, including cloud, APIs, services, events, integration, data, security, resilience, observability, and DevSecOps. Strong experience with Generative AI and agentic AI, including LLM-based systems, retrieval and grounding, context engineering, agent orchestration, tool integration, evaluation, guardrails, and observability. Also ability to translate business strategy, hands-on technical credibility, systems thinking, influencing, mentoring. Those are more competencies than skills. But we can still list technical skills: cloud, APIs, services, events, integration, data, security, resilience, observability, DevSecOps, Generative AI, agentic AI, LLM-based systems, retrieval and grounding, context engineering, agent orchestration, tool integration, evaluation, guardrails. That's specific. Thus we can create Skills section with a list. Now Responsibilities: need to capture all bullet points from "What You'll Do" and "What