Lead Architect - Enterprise & AI Enablement
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for lists. Use
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Keep substantive info.
We need to parse the posting.
Key sections:
- Intro paragraph: "When you join MetLife’s Global Technology team..." etc. That's about the role. Could be "About the role" heading.
- Then "The Opportunity Enterprise Architecture ensures a holistic strategy..." That's description of team/role. Could be part of About the role.
- Then "MetLife is seeking a Lead Architect to enable AI-powered development platforms for Citizen Developers across the enterprise." That's role description.
- Then "Key Responsibilities" list.
- Then "Required Qualifications" list.
- Then "Preferred Qualifications" list.
- Then "Location Expectation: This is a hybrid role requiring a minimum of 3 days per week in office." That's schedule info.
- Then "The expected salary range for this position is $105,000 - $161,600. This role may also be eligible for annual short-term incentive compensation and stock-based long-term incentives." That's pay.
- Then "Benefits We Offer Our U.S. benefits address holistic well-being..." That's benefits.
- Then "About MetLife" paragraph about company.
- Then maybe "MetLife is an Equal Opportunity Employer..." is EEO boilerplate to remove.
- Also "If you need an accommodation..." etc remove.
- Also "MetLife maintains a drug-free workplace..." remove.
- Also "This posting is for a current vacancy..." remove.
Thus we need sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications as Requirements), Qualifications (maybe Preferred Qualifications as Qualifications?), Skills (maybe not explicit), Benefits, Pay, Schedule.
We need to decide which headings to include based on content.
We have:
- About the role: intro paragraphs.
- Responsibilities: list under Key Responsibilities.
- Requirements: Required Qualifications.
- Qualifications: Preferred Qualifications (could be separate heading "Preferred Qualifications" but instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map Required Qualifications to Requirements, Preferred Qualifications to Qualifications (or Skills?). But we also have Skills maybe not explicit; we could omit Skills if no specific skill list beyond qualifications. However we could treat some items as skills: e.g., "Experience with modern AI concepts, including agentic AI, MCP servers, and/or the creation of AI plugins and skills." That's a skill. But we can keep under Requirements.
Better to follow instruction: Use headings only when posting has real specific content. So we will include:
About the role
with paragraphs.
Responsibilities
with - list.
Requirements
with - list (Required Qualifications).
Qualifications
with - list (Preferred Qualifications).
Benefits
with describing benefits.
Pay
with salary range and incentives.
Schedule
with hybrid expectation.
We should not include Skills heading if no explicit skill list separate.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include all bullet points exactly as given (maybe rephrase slightly but preserve meaning). Must not add filler.
We need to strip boilerplate: EEO, accommodation, drug-free workplace, posting duration, etc.
Also need to remove duplicated lines: there may be duplicate sentences? Not seeing.
Now craft HTML.
We'll need to escape any special characters? Not needed.
Let's extract content.
About the role paragraphs:
Paragraph 1: "When you join MetLife’s Global Technology team, you’ll be part of a forward-thinking group dedicated to shaping the future of digital solutions for customers worldwide. You’ll develop, maintain and support technology applications and delivery, leveraging AI, automation, and contemporary ways of working to enhance experiences and drive business outcomes. Your work will simplify complex processes, improve tech resiliency, and ensure high-performing, seamless solutions that power life’s most important moments. In this dynamic environment, you’ll collaborate with talented peers across teams and functions, expanding your skills in impactful ways. Ready to push boundaries and set new industry standards? Join us and help drive the future of technology forward."
Paragraph 2: "The Opportunity Enterprise Architecture ensures a holistic strategy and approach to technology solutions by working broadly and globally across the company. We drive MetLife toward a simplified and consistent architecture, enabling quality, agility, and cost-effectiveness. We support all areas of MetLife in developing and implementing enterprise strategies across Business Units, Global Operations, Application Development, Information Security, Data & Analytics, and Infrastructure."
Paragraph 3: "MetLife is seeking a Lead Architect to enable AI-powered development platforms for Citizen Developers across the enterprise. This role focuses on making AI tools and platforms easy to use, while ensuring they meet enterprise standards for security, transparency, and responsible use. The architect will design platforms, guardrails, and reusable patterns that allow Associates and Citizen Developers to quickly build solutions without creating hidden risk, technical debt, or compliance issues. The role balances ease of use with strong governance, ensuring AI capabilities can scale safely across the organization. You will work closely with architecture, security, privacy, and platform teams to define how AI and agent-based capabilities are delivered consistently and responsibly."
We can combine these into About the role section as multiple
elements.
Now Responsibilities list (Key Responsibilities):
- Domain expertise in AI platforms, agent frameworks, low-code/no-code ecosystems, and enterprise integration patterns.
- Design and define reference architectures, reusable patterns, and guardrails for AI-enabled associate and citizen development.
- Establish governance-by-design capabilities, including embedded controls for security, compliance, explainability, and transparency.
- Research and hands-on testing of new technologies and techniques for use with agent platforms.
- Participant and core contributor to the Center of Excellent for citizen agent development.
- Partner with engineering, security, and architecture teams to validate solutions and drive adoption.
- Enable reuse through templates, components, and accelerators that reduce complexity and technical debt.
- Promote adoption through training, guidance, and mentoring across both technical and business teams.
Note: "Center of Excellent" maybe typo but keep as is.
Now Required Qualifications list:
- Bachelor’s degree in engineering discipline or equivalent experience.
- 5+ years of experience in software engineering or architecture in enterprise environments.
- Experience with modern AI concepts, including agentic AI, MCP servers, and/or the creation of AI plugins and skills.
- Knowledge of cloud-native architectures, APIs, and secure integration patterns.
- Demonstrated expertise in security, operational, and resiliency architecture principles.
- Experience with platforms like Claude AI, Copilot Studio, or similar ecosystems.
- Demonstrated ability to lead technical initiatives requiring engagement and support from partner organizations.
Now Preferred Qualifications list:
- Experience with citizen developer platform enablement at scale.
- Familiarity with responsible AI concepts such as explainability and auditability.
- Cloud PaaS technologies, Power BI, Kubernetes, web APIs, API security protocols, etc., with preferred experience in Azure.
- Experience working in large enterprise environments, preferably in financial services.
- Demonstrated influencing and negotiation skills.
- Demonstrated experience with enabling technology adoption in an Enterprise environment.
Now Location Expectation (Schedule): "This is a hybrid role requiring a minimum of 3 days per week in office."
Now Pay: "The expected salary range for this position is $105,000 - $161,600. This role may also be eligible for annual short-term incentive compensation and stock-based long-term incentives."
Now Benefits: paragraph: "We Offer Our U.S. benefits address holistic well-being with programs for physical and mental health, financial wellness, and support for families. We offer a comprehensive health plan that includes medical/prescription drug and vision, dental insurance, and no-cost short- and long-term disability. We also provide company-paid life insurance and legal services, a retirement pension funded entirely by MetLife and 401(k) with employer matching, group discounts on voluntary insurance products including auto and home, pet, critical illness, hospital indemnity, and accident insurance, as well as Employee Assistance Program (EAP) and digital mental health programs, parental leave, paid time off, paid holidays, volunteer time off, tuition assistance and much more! For more information regarding MetLife’s U.S. benefits, please click here."
We should keep that but maybe remove the "For more information regarding MetLife’s U.S. benefits, please click here." as it's an instruction/link? It's not boilerplate but it's a call to action; maybe we keep it as it's substantive? The instruction says remove application instructions. This is a link for more info about benefits, not application. Might be okay to keep. But we could keep it as part of benefits description. However it's a directive to click; maybe considered application instruction? It's not about applying. Safer to keep.
Now About MetLife paragraph: "Recognized on Fortune magazine's list of the "World's Most Admired Companies", Fortune World’s 25 Best Workplaces™, as well as the Fortune 100 Best Companies to Work For®, MetLife, through its subsidiaries and affiliates, is one of the world’s leading financial services companies; providing insurance, annuities, employee benefits and asset management to individual and institutional customers. With operations in more than 40 markets, we hold leading positions in the United States, Latin America, Asia, Europe, and the Middle East. As part of our New Frontier strategy, MetLife is building an AI-enabled, people-centered future. We’re looking for people who bring curiosity, adaptability, and a growth mindset as we use AI to enhance how we serve customers, support communities, and evolve the way work gets done. At MetLife, AI is a responsible partner that supports human judgment, creativity, and continuous improvement while helping us build trust, inclusion, and long-term value. Our purpose is simple - to help our colleagues, customers, communities, and the world at large create a more confident future. United by purpose and guided by our core values - Win Together, Do the Right Thing, Deliver Impact Over Activity, and Think Ahead - we’re inspired to transform the next century in financial services. At MetLife, it’s #AllTogetherPossible. Join us!"
We can include this as About MetLife maybe not required heading but could be part of About the role? The instruction says use headings for sections like About the role, Responsibilities, etc. About MetLife is company overview; could be included under About the role or separate heading "About MetLife". But not in list of headings; but we could still include as a paragraph under About the role? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. It says "include a section ONLY when the posting has real, specific content for it". So we could add an "About MetLife" heading if we want, but it's not in the examples. Safer to stick to the given headings; we can incorporate the About MetLife content into About the role section as additional paragraphs.
Thus About the role will have multiple paragraphs: intro, Opportunity Enterprise Architecture, MetLife seeking Lead Architect, and About MetLife description.
Now we need to output only HTML fragment, no /, no markdown fences.
Let's construct.
We'll need to ensure proper escaping of any apostrophes etc. It's fine.
Now produce:
About the role
When you join MetLife’s Global Technology team, you’ll be part of a forward-thinking group dedicated to shaping the future of digital solutions for
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Keep substantive info. We need to parse the posting. Key sections: - Intro paragraph: "When you join MetLife’s Global Technology team..." etc. That's about the role. Could be "About the role" heading. - Then "The Opportunity Enterprise Architecture ensures a holistic strategy..." That's description of team/role. Could be part of About the role. - Then "MetLife is seeking a Lead Architect to enable AI-powered development platforms for Citizen Developers across the enterprise." That's role description. - Then "Key Responsibilities" list. - Then "Required Qualifications" list. - Then "Preferred Qualifications" list. - Then "Location Expectation: This is a hybrid role requiring a minimum of 3 days per week in office." That's schedule info. - Then "The expected salary range for this position is $105,000 - $161,600. This role may also be eligible for annual short-term incentive compensation and stock-based long-term incentives." That's pay. - Then "Benefits We Offer Our U.S. benefits address holistic well-being..." That's benefits. - Then "About MetLife" paragraph about company. - Then maybe "MetLife is an Equal Opportunity Employer..." is EEO boilerplate to remove. - Also "If you need an accommodation..." etc remove. - Also "MetLife maintains a drug-free workplace..." remove. - Also "This posting is for a current vacancy..." remove. Thus we need sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications as Requirements), Qualifications (maybe Preferred Qualifications as Qualifications?), Skills (maybe not explicit), Benefits, Pay, Schedule. We need to decide which headings to include based on content. We have: - About the role: intro paragraphs. - Responsibilities: list under Key Responsibilities. - Requirements: Required Qualifications. - Qualifications: Preferred Qualifications (could be separate heading "Preferred Qualifications" but instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map Required Qualifications to Requirements, Preferred Qualifications to Qualifications (or Skills?). But we also have Skills maybe not explicit; we could omit Skills if no specific skill list beyond qualifications. However we could treat some items as skills: e.g., "Experience with modern AI concepts, including agentic AI, MCP servers, and/or the creation of AI plugins and skills." That's a skill. But we can keep under Requirements. Better to follow instruction: Use headings only when posting has real specific content. So we will include:
About the role
with paragraphs.Responsibilities
with- list.
Requirements
with- list (Required Qualifications).
Qualifications
with- list (Preferred Qualifications).
Benefits
withdescribing benefits.
Pay
withsalary range and incentives.
Schedule
withhybrid expectation. We should not include Skills heading if no explicit skill list separate. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all bullet points exactly as given (maybe rephrase slightly but preserve meaning). Must not add filler. We need to strip boilerplate: EEO, accommodation, drug-free workplace, posting duration, etc. Also need to remove duplicated lines: there may be duplicate sentences? Not seeing. Now craft HTML. We'll need to escape any special characters? Not needed. Let's extract content. About the role paragraphs: Paragraph 1: "When you join MetLife’s Global Technology team, you’ll be part of a forward-thinking group dedicated to shaping the future of digital solutions for customers worldwide. You’ll develop, maintain and support technology applications and delivery, leveraging AI, automation, and contemporary ways of working to enhance experiences and drive business outcomes. Your work will simplify complex processes, improve tech resiliency, and ensure high-performing, seamless solutions that power life’s most important moments. In this dynamic environment, you’ll collaborate with talented peers across teams and functions, expanding your skills in impactful ways. Ready to push boundaries and set new industry standards? Join us and help drive the future of technology forward." Paragraph 2: "The Opportunity Enterprise Architecture ensures a holistic strategy and approach to technology solutions by working broadly and globally across the company. We drive MetLife toward a simplified and consistent architecture, enabling quality, agility, and cost-effectiveness. We support all areas of MetLife in developing and implementing enterprise strategies across Business Units, Global Operations, Application Development, Information Security, Data & Analytics, and Infrastructure." Paragraph 3: "MetLife is seeking a Lead Architect to enable AI-powered development platforms for Citizen Developers across the enterprise. This role focuses on making AI tools and platforms easy to use, while ensuring they meet enterprise standards for security, transparency, and responsible use. The architect will design platforms, guardrails, and reusable patterns that allow Associates and Citizen Developers to quickly build solutions without creating hidden risk, technical debt, or compliance issues. The role balances ease of use with strong governance, ensuring AI capabilities can scale safely across the organization. You will work closely with architecture, security, privacy, and platform teams to define how AI and agent-based capabilities are delivered consistently and responsibly." We can combine these into About the role section as multiple
elements. Now Responsibilities list (Key Responsibilities): - Domain expertise in AI platforms, agent frameworks, low-code/no-code ecosystems, and enterprise integration patterns. - Design and define reference architectures, reusable patterns, and guardrails for AI-enabled associate and citizen development. - Establish governance-by-design capabilities, including embedded controls for security, compliance, explainability, and transparency. - Research and hands-on testing of new technologies and techniques for use with agent platforms. - Participant and core contributor to the Center of Excellent for citizen agent development. - Partner with engineering, security, and architecture teams to validate solutions and drive adoption. - Enable reuse through templates, components, and accelerators that reduce complexity and technical debt. - Promote adoption through training, guidance, and mentoring across both technical and business teams. Note: "Center of Excellent" maybe typo but keep as is. Now Required Qualifications list: - Bachelor’s degree in engineering discipline or equivalent experience. - 5+ years of experience in software engineering or architecture in enterprise environments. - Experience with modern AI concepts, including agentic AI, MCP servers, and/or the creation of AI plugins and skills. - Knowledge of cloud-native architectures, APIs, and secure integration patterns. - Demonstrated expertise in security, operational, and resiliency architecture principles. - Experience with platforms like Claude AI, Copilot Studio, or similar ecosystems. - Demonstrated ability to lead technical initiatives requiring engagement and support from partner organizations. Now Preferred Qualifications list: - Experience with citizen developer platform enablement at scale. - Familiarity with responsible AI concepts such as explainability and auditability. - Cloud PaaS technologies, Power BI, Kubernetes, web APIs, API security protocols, etc., with preferred experience in Azure. - Experience working in large enterprise environments, preferably in financial services. - Demonstrated influencing and negotiation skills. - Demonstrated experience with enabling technology adoption in an Enterprise environment. Now Location Expectation (Schedule): "This is a hybrid role requiring a minimum of 3 days per week in office." Now Pay: "The expected salary range for this position is $105,000 - $161,600. This role may also be eligible for annual short-term incentive compensation and stock-based long-term incentives." Now Benefits: paragraph: "We Offer Our U.S. benefits address holistic well-being with programs for physical and mental health, financial wellness, and support for families. We offer a comprehensive health plan that includes medical/prescription drug and vision, dental insurance, and no-cost short- and long-term disability. We also provide company-paid life insurance and legal services, a retirement pension funded entirely by MetLife and 401(k) with employer matching, group discounts on voluntary insurance products including auto and home, pet, critical illness, hospital indemnity, and accident insurance, as well as Employee Assistance Program (EAP) and digital mental health programs, parental leave, paid time off, paid holidays, volunteer time off, tuition assistance and much more! For more information regarding MetLife’s U.S. benefits, please click here." We should keep that but maybe remove the "For more information regarding MetLife’s U.S. benefits, please click here." as it's an instruction/link? It's not boilerplate but it's a call to action; maybe we keep it as it's substantive? The instruction says remove application instructions. This is a link for more info about benefits, not application. Might be okay to keep. But we could keep it as part of benefits description. However it's a directive to click; maybe considered application instruction? It's not about applying. Safer to keep. Now About MetLife paragraph: "Recognized on Fortune magazine's list of the "World's Most Admired Companies", Fortune World’s 25 Best Workplaces™, as well as the Fortune 100 Best Companies to Work For®, MetLife, through its subsidiaries and affiliates, is one of the world’s leading financial services companies; providing insurance, annuities, employee benefits and asset management to individual and institutional customers. With operations in more than 40 markets, we hold leading positions in the United States, Latin America, Asia, Europe, and the Middle East. As part of our New Frontier strategy, MetLife is building an AI-enabled, people-centered future. We’re looking for people who bring curiosity, adaptability, and a growth mindset as we use AI to enhance how we serve customers, support communities, and evolve the way work gets done. At MetLife, AI is a responsible partner that supports human judgment, creativity, and continuous improvement while helping us build trust, inclusion, and long-term value. Our purpose is simple - to help our colleagues, customers, communities, and the world at large create a more confident future. United by purpose and guided by our core values - Win Together, Do the Right Thing, Deliver Impact Over Activity, and Think Ahead - we’re inspired to transform the next century in financial services. At MetLife, it’s #AllTogetherPossible. Join us!" We can include this as About MetLife maybe not required heading but could be part of About the role? The instruction says use headings for sections like About the role, Responsibilities, etc. About MetLife is company overview; could be included under About the role or separate heading "About MetLife". But not in list of headings; but we could still include as a paragraph under About the role? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. It says "include a section ONLY when the posting has real, specific content for it". So we could add an "About MetLife" heading if we want, but it's not in the examples. Safer to stick to the given headings; we can incorporate the About MetLife content into About the role section as additional paragraphs. Thus About the role will have multiple paragraphs: intro, Opportunity Enterprise Architecture, MetLife seeking Lead Architect, and About MetLife description. Now we need to output only HTML fragment, no /, no markdown fences. Let's construct. We'll need to ensure proper escaping of any apostrophes etc. It's fine. Now produce:
About the role
When you join MetLife’s Global Technology team, you’ll be part of a forward-thinking group dedicated to shaping the future of digital solutions for
- list (Preferred Qualifications).
- list (Required Qualifications).