Principal Architect - Remote
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove things like "Application Deadline: ..." and EEO statements, drug test, etc.
We need to decide sections: About the role (intro description), Responsibilities (list), Requirements (maybe combine Required Qualifications?), Qualifications (maybe Preferred Qualifications?), Skills? Not explicit. Benefits? There's mention of benefits: "In addition to your salary, we offer benefits such as, a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution (all benefits are subject to eligibility requirements)." Also earlier: "You'll be rewarded and recognized for your performance in an environment that will challenge you and give you clear direction on what it takes to succeed in your role as well as provide development for other roles you may be interested in." That's more about rewards. Also "Come make an impact..." etc. But we need Benefits section only if posting actually states them. It does mention benefits package, incentive, equity, 401k. So we can include Benefits.
Pay: The posting says "The salary for this role will range from $134,600 - $230,800 annually based on full-time employment." Also "Pay is based on several factors including but not limited to local labor markets, education, work experience, certifications, etc." So we have pay info. So include Pay section.
Schedule: There's mention: "You'll enjoy the flexibility to work remotely from anywhere within the U.S. as you take on some tough challenges. For all hires in the Minneapolis or Washington, D.C. area, you will be required to work in the office a minimum of four days per week. Preference for MN and CT." That's schedule/location info. So we can include Schedule section.
We need to avoid repeating job title as heading. So no Principal Architect
. Use headings for sections.
We need to use - for any list of duties/requirements/benefits. For prose use
.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include all details from the posting, except boilerplate removed.
We need to be careful not to include duplicated lines. Also remove application instructions, EEO, drug test, etc.
Let's extract substantive content:
Intro paragraphs:
"Principal Architect Within Corporate Systems Optum is a global organization that delivers care, aided by technology to help millions of people live healthier lives. The work you do with our team will directly improve health outcomes by connecting people with the care, pharmacy benefits, data and resources they need to feel their best. Here, you will find a culture guided by inclusion, talented peers, comprehensive benefits and career development opportunities. Come make an impact on the communities we serve as you help us advance health optimization on a global scale. Join us to start Caring. Connecting. Growing together."
That's about the role/company.
Then role description: "As a Principal Architect within Corporate Systems, you will serve as a strategic architecture advisor defining target-state architecture and technology roadmaps primarily across Finance and Procurement platforms, while supporting broader Corporate Systems domains (HR, LCRA, Marketing) as needed. In this role, you will provide critical 'checks and balances' through architectural due diligence, vendor solution assessments, and capability validation before contracts and commitments are finalized. You will evaluate and apply enterprise-approved AI capabilities, automation technologies, and emerging trends to drive large-scale enterprise transformation and agentic workflow modernization. Working closely with business and technology leadership, you will align application and data architectures with enterprise capabilities to ensure scalable, cost-effective, and resilient technology solutions. You'll enjoy the flexibility to work remotely from anywhere within the U.S. as you take on some tough challenges. For all hires in the Minneapolis or Washington, D.C. area, you will be required to work in the office a minimum of four days per week. Preference for MN and CT."
That's responsibilities and schedule.
Then "Primary Responsibilities" bullet list:
- Define and drive architecture strategy, target-state architecture, and multi-year technology roadmaps primarily across Finance and Procurement platforms, while supporting broader Corporate Systems domains (such as HR, LCRA, and Marketing) as needed
- Lead architectural due diligence and technology assessments for vendor solutions, validating platform capabilities, implementation feasibility, architectural fit, and long-term business value before contracts are finalized
- Serve as a trusted architecture advisor to business and technology leaders, translating strategic objectives into executable technology roadmaps while providing objective architectural guidance, risk assessment, and decision support
- Support large-scale business and technology transformation initiatives, including AI-enabled and agentic workflow modernization across Corporate Systems platforms
- Evaluate and apply enterprise-approved AI capabilities, automation technologies, and emerging technology trends to inform architecture decisions and business transformation strategies
- Establish and enforce architecture guardrails, governance standards, and reference architectures to drive portfolio rationalization, simplify integration strategy, and reduce technical debt
- Use enterprise-approved AI tools to streamline workflows, automate technical analysis, and drive continuous architectural process improvement
- Provide technical leadership, strategic guidance, and mentorship to solution architects and engineering teams across cross-domain initiatives
Then reward paragraph: "You'll be rewarded and recognized for your performance in an environment that will challenge you and give you clear direction on what it takes to succeed in your role as well as provide development for other roles you may be interested in."
Then "Required Qualifications" list:
- 7+ years of experience in enterprise architecture, software engineering, or technical leadership roles within large-scale enterprise environments, including defining target-state architectures, integration strategies, and multi-year technology roadmaps
- 5+ years of domain expertise supporting Corporate Systems, with a primary focus on Finance and Procurement platforms (ERP, financial management, source-to-pay)
- 5+ years of experience managing vendor technical relationships, conducting technology evaluations, software selection processes, and architectural due diligence to assess platform fit, feasibility, and business value
- 3+ years of experience establishing architecture guardrails, reference architectures, governance standards, and enterprise portfolio rationalization frameworks
- 2+ years of experience leveraging enterprise-approved AI tools, productivity automation technologies, or emerging AI capabilities to streamline technical analysis, documentation, and architectural decision-making
Then "Preferred Qualifications":
- Bachelor's degree in Computer Science, Information Technology, or a related technical field
- Experience supporting large-scale enterprise transformation programs, including AI-enabled and agentic workflow modernizations
- Experience working in highly regulated environments such as healthcare or financial services
- Familiarity with enterprise architecture frameworks and methodologies (e.g., TOGAF, SAFe)
Then Pay paragraph: "Pay is based on several factors including but not limited to local labor markets, education, work experience, certifications, etc. In addition to your salary, we offer benefits such as, a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution (all benefits are subject to eligibility requirements). No matter where or when you begin a career with us, you'll find a far-reaching choice of benefits and incentives. The salary for this role will range from $134,600 - $230,800 annually based on full-time employment. We comply with all minimum wage laws as applicable."
Then there is application deadline etc which we remove.
Also there is mission statement etc after that: "At UnitedHealth Group, our mission is to help people live healthier lives and make the health system work better for everyone. We are committed to mitigating our impact on the environment and enabling and delivering equitable care that addresses health disparities and improves health outcomes - an enterprise priority reflected in our mission." That's maybe boilerplate? It's mission statement but could be considered substantive? It's generic but maybe we should keep as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Mission statement might be considered boilerplate? It's not EEO but it's a generic mission. Might be considered boilerplate but not explicitly listed. Safer to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Mission statement is not those. Could keep. However later there is EEO statement and drug test etc which we must remove.
Thus we need to include About the role section that includes the intro paragraphs and maybe the mission statement? But we already have intro about Optum. The mission statement is about UnitedHealth Group (parent). Might be considered part of About the role. We'll include it as prose.
We must not repeat job title as heading.
We need to decide sections:
- About the role (intro + mission statement)
- Responsibilities (the Primary Responsibilities list)
- Requirements (maybe combine Required Qualifications? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Required Qualifications and Preferred Qualifications. Could map Required Qualifications to "Requirements" and Preferred Qualifications to "Qualifications". Or we could have a single "Qualifications" section with both required and preferred? But instruction says prefer few substantive sections over many thin ones. We could have Requirements (required) and Qualifications (preferred). That seems okay.
- Benefits: we have benefits info.
- Pay: salary range and pay factors.
- Schedule: remote flexibility, office days.
We also have a reward paragraph about being rewarded and recognized; could be part of About the role or Benefits? It's about rewards and recognition, maybe part of Benefits? But Benefits section already covers benefits package; reward paragraph is about performance recognition and development. Could be included in About the role as prose.
We must not invent or summarize away detail. So we need to keep that sentence exactly.
Now we need to format.
We'll output HTML fragment:
About the role
... paragraphs ...
Then Responsibilities
- ... each bullet ...
Then Requirements
- ... required qualifications ...
Then Qualifications
- ... preferred qualifications ...
- for list.
Then
Benefits
... benefits paragraph ...
Then Pay
... pay paragraph ...
Then Schedule
... schedule paragraph ...
We need to ensure we don't include duplicated lines. Also ensure we don't include filler like "commensurate with experience". Not present.
Now let's craft the About the role paragraph(s). Combine the intro and mission statement and reward paragraph? The reward paragraph is separate; maybe include after intro.
Let's extract exact text:
Intro: "Principal Architect Within Corporate Systems Optum is a global organization that delivers care, aided by technology to help millions of people live healthier lives. The work you do with our team will directly improve health outcomes by connecting people with the care, pharmacy benefits, data and resources they need to feel their best. Here, you will find a culture guided by inclusion, talented peers, comprehensive benefits and career development opportunities. Come make an impact on the communities we serve as you help us advance health optimization on a global scale. Join us to start Caring. Connecting. Growing together."
Note: The first sentence seems to have odd formatting: "Principal Architect Within Corporate Systems Optum is a global organization..." Probably it's meant to be "Principal Architect Within Corporate Systems. Optum is a global organization..." We'll keep as is.
Then role description: "As a Principal Architect within Corporate Systems, you will serve as a strategic architecture advisor defining target-state architecture and technology roadmaps primarily
. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include all details from the posting, except boilerplate removed. We need to be careful not to include duplicated lines. Also remove application instructions, EEO, drug test, etc. Let's extract substantive content: Intro paragraphs: "Principal Architect Within Corporate Systems Optum is a global organization that delivers care, aided by technology to help millions of people live healthier lives. The work you do with our team will directly improve health outcomes by connecting people with the care, pharmacy benefits, data and resources they need to feel their best. Here, you will find a culture guided by inclusion, talented peers, comprehensive benefits and career development opportunities. Come make an impact on the communities we serve as you help us advance health optimization on a global scale. Join us to start Caring. Connecting. Growing together." That's about the role/company. Then role description: "As a Principal Architect within Corporate Systems, you will serve as a strategic architecture advisor defining target-state architecture and technology roadmaps primarily across Finance and Procurement platforms, while supporting broader Corporate Systems domains (HR, LCRA, Marketing) as needed. In this role, you will provide critical 'checks and balances' through architectural due diligence, vendor solution assessments, and capability validation before contracts and commitments are finalized. You will evaluate and apply enterprise-approved AI capabilities, automation technologies, and emerging trends to drive large-scale enterprise transformation and agentic workflow modernization. Working closely with business and technology leadership, you will align application and data architectures with enterprise capabilities to ensure scalable, cost-effective, and resilient technology solutions. You'll enjoy the flexibility to work remotely from anywhere within the U.S. as you take on some tough challenges. For all hires in the Minneapolis or Washington, D.C. area, you will be required to work in the office a minimum of four days per week. Preference for MN and CT." That's responsibilities and schedule. Then "Primary Responsibilities" bullet list: - Define and drive architecture strategy, target-state architecture, and multi-year technology roadmaps primarily across Finance and Procurement platforms, while supporting broader Corporate Systems domains (such as HR, LCRA, and Marketing) as needed - Lead architectural due diligence and technology assessments for vendor solutions, validating platform capabilities, implementation feasibility, architectural fit, and long-term business value before contracts are finalized - Serve as a trusted architecture advisor to business and technology leaders, translating strategic objectives into executable technology roadmaps while providing objective architectural guidance, risk assessment, and decision support - Support large-scale business and technology transformation initiatives, including AI-enabled and agentic workflow modernization across Corporate Systems platforms - Evaluate and apply enterprise-approved AI capabilities, automation technologies, and emerging technology trends to inform architecture decisions and business transformation strategies - Establish and enforce architecture guardrails, governance standards, and reference architectures to drive portfolio rationalization, simplify integration strategy, and reduce technical debt - Use enterprise-approved AI tools to streamline workflows, automate technical analysis, and drive continuous architectural process improvement - Provide technical leadership, strategic guidance, and mentorship to solution architects and engineering teams across cross-domain initiatives Then reward paragraph: "You'll be rewarded and recognized for your performance in an environment that will challenge you and give you clear direction on what it takes to succeed in your role as well as provide development for other roles you may be interested in." Then "Required Qualifications" list: - 7+ years of experience in enterprise architecture, software engineering, or technical leadership roles within large-scale enterprise environments, including defining target-state architectures, integration strategies, and multi-year technology roadmaps - 5+ years of domain expertise supporting Corporate Systems, with a primary focus on Finance and Procurement platforms (ERP, financial management, source-to-pay) - 5+ years of experience managing vendor technical relationships, conducting technology evaluations, software selection processes, and architectural due diligence to assess platform fit, feasibility, and business value - 3+ years of experience establishing architecture guardrails, reference architectures, governance standards, and enterprise portfolio rationalization frameworks - 2+ years of experience leveraging enterprise-approved AI tools, productivity automation technologies, or emerging AI capabilities to streamline technical analysis, documentation, and architectural decision-making Then "Preferred Qualifications": - Bachelor's degree in Computer Science, Information Technology, or a related technical field - Experience supporting large-scale enterprise transformation programs, including AI-enabled and agentic workflow modernizations - Experience working in highly regulated environments such as healthcare or financial services - Familiarity with enterprise architecture frameworks and methodologies (e.g., TOGAF, SAFe) Then Pay paragraph: "Pay is based on several factors including but not limited to local labor markets, education, work experience, certifications, etc. In addition to your salary, we offer benefits such as, a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution (all benefits are subject to eligibility requirements). No matter where or when you begin a career with us, you'll find a far-reaching choice of benefits and incentives. The salary for this role will range from $134,600 - $230,800 annually based on full-time employment. We comply with all minimum wage laws as applicable." Then there is application deadline etc which we remove. Also there is mission statement etc after that: "At UnitedHealth Group, our mission is to help people live healthier lives and make the health system work better for everyone. We are committed to mitigating our impact on the environment and enabling and delivering equitable care that addresses health disparities and improves health outcomes - an enterprise priority reflected in our mission." That's maybe boilerplate? It's mission statement but could be considered substantive? It's generic but maybe we should keep as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Mission statement might be considered boilerplate? It's not EEO but it's a generic mission. Might be considered boilerplate but not explicitly listed. Safer to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Mission statement is not those. Could keep. However later there is EEO statement and drug test etc which we must remove. Thus we need to include About the role section that includes the intro paragraphs and maybe the mission statement? But we already have intro about Optum. The mission statement is about UnitedHealth Group (parent). Might be considered part of About the role. We'll include it as prose. We must not repeat job title as heading. We need to decide sections: - About the role (intro + mission statement) - Responsibilities (the Primary Responsibilities list) - Requirements (maybe combine Required Qualifications? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Required Qualifications and Preferred Qualifications. Could map Required Qualifications to "Requirements" and Preferred Qualifications to "Qualifications". Or we could have a single "Qualifications" section with both required and preferred? But instruction says prefer few substantive sections over many thin ones. We could have Requirements (required) and Qualifications (preferred). That seems okay. - Benefits: we have benefits info. - Pay: salary range and pay factors. - Schedule: remote flexibility, office days. We also have a reward paragraph about being rewarded and recognized; could be part of About the role or Benefits? It's about rewards and recognition, maybe part of Benefits? But Benefits section already covers benefits package; reward paragraph is about performance recognition and development. Could be included in About the role as prose. We must not invent or summarize away detail. So we need to keep that sentence exactly. Now we need to format. We'll output HTML fragment:
About the role
... paragraphs ...
ThenResponsibilities
- ... each bullet ...
Requirements
- ... required qualifications ...
Qualifications
- ... preferred qualifications ...
- for list.
Then
Benefits
... benefits paragraph ...
ThenPay
... pay paragraph ...
ThenSchedule
... schedule paragraph ...
We need to ensure we don't include duplicated lines. Also ensure we don't include filler like "commensurate with experience". Not present. Now let's craft the About the role paragraph(s). Combine the intro and mission statement and reward paragraph? The reward paragraph is separate; maybe include after intro. Let's extract exact text: Intro: "Principal Architect Within Corporate Systems Optum is a global organization that delivers care, aided by technology to help millions of people live healthier lives. The work you do with our team will directly improve health outcomes by connecting people with the care, pharmacy benefits, data and resources they need to feel their best. Here, you will find a culture guided by inclusion, talented peers, comprehensive benefits and career development opportunities. Come make an impact on the communities we serve as you help us advance health optimization on a global scale. Join us to start Caring. Connecting. Growing together." Note: The first sentence seems to have odd formatting: "Principal Architect Within Corporate Systems Optum is a global organization..." Probably it's meant to be "Principal Architect Within Corporate Systems. Optum is a global organization..." We'll keep as is. Then role description: "As a Principal Architect within Corporate Systems, you will serve as a strategic architecture advisor defining target-state architecture and technology roadmaps primarily