Lead IT Architect
CoverMyMeds · Columbus, OH · Yesterday
Engineering$151k–$251k/yrFull-time
The user wants me to convert this job posting into clean, well-structured semantic HTML. Let me analyze the content and structure it according to the rules:
1. Use for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists
3. Use
for prose
4. Don't repeat job title as heading
5. Don't put Job ID/requisition numbers as headings
6. Preserve ALL substantive information
7. Remove boilerplate (cookie/navigation/legal/EEO/scam-warning)
8. Only include sections with real content
9. No filler/placeholder text
10. Output ONLY HTML fragment
Looking at the content:
- There's an intro paragraph about McKesson
- Job Summary section
- Key Responsibilities with multiple sub-sections
- Minimum Qualifications with education and critical skills
I need to organize this into logical sections. The posting has:
1. About the role / Job Summary (the intro + job summary)
2. Responsibilities (the Key Responsibilities section with multiple sub-areas)
3. Requirements / Qualifications (Minimum Qualifications)
Let me structure it:
- About the role: combine the McKesson intro and Job Summary
- Responsibilities: break down the Key Responsibilities into sub-sections or keep as one big list? The rules say use
- for lists of duties. The responsibilities are quite detailed with multiple sub-categories. I could make each sub-category a separate list or combine. Since they're all responsibilities, I'll create one Responsibilities section with the sub-categories as nested lists or separate lists with headings. But the rules say use
for section headings only. I could use for sub-sections? The rules only mention for section headings. I'll keep it simple: one Responsibilities section with all the bullet points, but that's a lot. Better to group by the sub-headings in the original.
Actually, looking at the original, the Key Responsibilities has 7 sub-sections:
1. Architectural Runway & Value Stream Leadership
2. AI & Agentic Engineering Leadership
3. Solution Architecture & Technical Design
4. Agile Delivery & Technical Leadership
5. Enterprise Architecture Alignment & Governance
6. Architecture Documentation & Knowledge Management
7. Security, Compliance & Operational Excellence
8. Cloud, Platform & Engineering Excellence
That's 8 sub-sections. I could make each a separate ? But the rules say use for section headings like "Responsibilities". Maybe I should have one "Responsibilities" and then use for sub-sections? The rules don't forbid . But they say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So they expect those main sections. I'll create a Responsibilities section with the sub-sections as nested lists or separate lists with bold labels.
Better: Use for "Responsibilities" and then for each sub-area, use a label followed by . That keeps semantic structure.
Similarly for Qualifications: there's Education and Critical Skills (which is a list). I'll make a "Qualifications" section.
No mention of Benefits, Pay, Schedule - so omit those sections.
Now, let's write the HTML.
First, the About the role section: combine the McKesson intro paragraph and the Job Summary paragraph.
Then Responsibilities: list all the bullet points from each sub-section.
Then Qualifications: Education and Critical Skills.
I need to preserve ALL substantive information. So I must include all bullet points.
Let me extract all bullet points:
From Architectural Runway & Value Stream Leadership:
- Plan the architectural runway for an Agile Release Train (ART), proactively defining solution approaches, technical enablers, architecture patterns, dependencies, and future-state designs that enable teams across the Value Stream to deliver effectively at scale.
- Partner with Product Management, Engineering Leadership, and Enterprise Architecture to ensure upcoming features, epics, and initiatives have a clear architectural path prior to implementation.
- Develop and maintain technology and architecture roadmaps that support Value Stream objectives while balancing scalability, technical debt reduction, reliability, security, compliance, and delivery velocity.
- Identify capability gaps, modernization opportunities, architectural risks, and cross-team dependencies before they become delivery impediments.
- Establish architectural direction across multiple teams and applications, ensuring alignment on technology strategy and implementation approaches.
- Ensure teams are never waiting on architecture guidance, standards, patterns, technical decisions, architecture artifacts, or technical enablers required to execute delivery commitments.
From AI & Agentic Engineering Leadership:
- Partner with the CoverMyMeds AI Enablement team to evaluate, adopt, and operationalize AI-assisted software delivery practices across the ART.
- Serve as the primary architecture lead for AI adoption within the Value Stream, driving practical implementation of approved AI capabilities, tools, patterns, and engineering practices.
- Identify opportunities to improve engineering productivity, software quality, documentation, testing, knowledge management, architecture governance, operational support, and delivery effectiveness through AI-enabled workflows and automation.
- Develop adoption roadmaps and implementation plans that accelerate AI-assisted software delivery across engineering teams.
- Partner with Engineering Managers, Technical Leads, and development teams to increase adoption of AI-assisted development practices using platforms such as Microsoft Copilot, Claude, GitHub Copilot, and future enterprise-supported solutions.
- Define and maintain the architectural context, Architecture Decision Records (ADRs), repository standards, architecture artifacts, and knowledge-management practices required to effectively support agentic engineering.
- Drive adoption of architecture-as-code, AI-assisted documentation, automated architecture validation, and agent-enabled engineering workflows.
- Collaborate with the AI Enablement team to evaluate emerging agentic engineering capabilities and determine how they can be safely and effectively operationalized within the Value Stream.
- Serve as a champion for modern engineering practices and help teams evolve how software is designed, built, tested, documented, and supported.
From Solution Architecture & Technical Design:
- Lead the design of scalable, secure, resilient, and maintainable enterprise solutions.
- Create detailed architecture artifacts including system context diagrams, solution architecture diagrams, integration diagrams, deployment topologies, sequence diagrams, data flow diagrams, domain models, reference architectures, and implementation-ready design materials.
- Translate business and product objectives into actionable technical designs that can be executed consistently across multiple delivery teams.
- Evaluate architectural alternatives and recommend solutions based on business, operational, compliance, security, and technical tradeoffs.
- Develop implementation-ready architectural guidance that accelerates delivery and reduces ambiguity.
- Establish architecture patterns that promote reuse, consistency, maintainability, and operational excellence across the ART.
- Create current-state and future-state architecture views used to drive portfolio planning and modernization activities.
From Agile Delivery & Technical Leadership:
- Actively participate in Agile, Scrum, and SAFe planning and delivery activities, providing architectural guidance throughout the delivery lifecycle.
- Partner with Product Managers, Product Owners, Scrum Masters, Engineering Managers, and Technical Leads to ensure architectural priorities and technical enablers are reflected in team backlogs and delivery plans.
- Guide decomposition of large initiatives into implementable capabilities, features, and architectural enablers aligned with Agile delivery practices.
- Mentor engineers and technical leaders, helping elevate architectural maturity and engineering excellence across the ART.
- Influence technical decision-making and technology adoption across teams without direct managerial authority.
- Foster a culture of architectural thinking, engineering excellence, continuous learning, and innovation.
From Enterprise Architecture Alignment & Governance:
- Serve as the primary architecture representative for the ART, preparing, presenting, and defending solution designs, architecture decisions, technology strategies, and exception requests through Architecture Review Board (ARB) governance processes.
- Partner with Enterprise Architecture to operationalize enterprise standards, approved reference architectures, architectural guardrails, and strategic platform direction within the ART.
- Promote and govern adherence to enterprise architecture standards, ensuring solutions align with enterprise technology direction and approved patterns.
- Drive adoption of approved architectural patterns, shared services, platform capabilities, reusable solutions, and strategic technology platforms across teams and applications within the Value Stream.
- Partner effectively with Enterprise Architecture, Security, Platform Engineering, Compliance, Infrastructure, Cloud Operations, Developer Experience, AI Enablement, and other shared service organizations.
- Advocate for Value Stream needs while leveraging enterprise platforms, shared services, and reusable capabilities whenever possible.
- Track and communicate architectural risks, technical debt, modernization opportunities, major technology decisions, and cross-team dependencies.
- Maintain visibility into enterprise and platform dependencies that could impact delivery outcomes across the ART.
From Architecture Documentation & Knowledge Management:
- Own the architecture repository for the ART and application portfolio.
- Accountable for maintaining the architectural context, Architecture Decision Records (ADRs), architecture artifacts, and solution documentation for all applications and platforms within the ART.
- Establish and maintain architectural context including system boundaries, integrations, dependencies, data flows, technology selections, technical constraints, and historical decision records.
- Create and maintain current-state and future-state architecture documentation for applications and platforms owned within the Value Stream.
- Maintain architecture diagrams including system context diagrams, integration diagrams, deployment topologies, application interaction diagrams, domain models, sequence diagrams, and solution blueprints.
- Ensure architecture documentation remains current, accurate, discoverable, and accessible to engineers, architects, leadership, and stakeholders.
- Establish documentation standards and review processes that institutionalize architecture knowledge and reduce dependency on individual contributors.
- Maintain architectural knowledge in a manner that enables both engineers and AI-assisted tools to effectively understand and operate within the application portfolio.
From Security, Compliance & Operational Excellence:
- Ensure solutions adhere to enterprise security, privacy, audit, regulatory, and compliance requirements.
- Design architectures that support appropriate handling of Protected Health Information (PHI), Personally Identifiable Information (PII), and other sensitive data assets.
- Incorporate requirements associated with HIPAA, HITRUST, SOC, SOX, and related compliance frameworks into architectural designs and technology decisions.
- Partner with Security, Risk, Compliance, and Enterprise Architecture teams to proactively identify and mitigate architectural risks.
- Ensure security, resiliency, observability, and compliance requirements are incorporated into architectural runway planning and solution design activities.
- Promote secure-by-design and compliance-by-design practices throughout the software development lifecycle.
From Cloud, Platform & Engineering Excellence:
- Design and implement cloud-native architectures utilizing Azure and modern platform services.
- Promote CoverMyMeds standards for platforms, APIs, integrations, distributed systems, platform services, observability, resiliency, scalability, security, and operational excellence.
- Collaborate with Security, Platform Engineering, Enterprise Architecture, and Operations teams to align solutions with organizational standards.
- Evaluate technology investments and modernization initiatives that improve platform reliability, maintainability, scalability, and engineering effectiveness.
- Guide adoption of engineering platforms and practices leveraging technologies such as Azure, GitHub, Jira, Lucidchart, Microsoft Copilot, Claude, and related engineering productivity tools.
Qualifications:
- Degree or equivalent and typically requires 10+ years of relevant experience. Less years required if has relevant Master’s or Doctorate qualifications.
- Education: Bachelor's degree in Computer Science, Engineering, Information Technology, or related discipline.
- Critical Skills: 10+ years of experience in software engineering, solution architecture, enterprise architecture, or related technology disciplines, including 5+ years in a Lead Architect, Principal Architect, Solution Architect, or equivalent technical-leadership role.
- Demonstrated experience owning architecture across multiple applications, products, or Agile engineering teams.
- Experience establishing architectural roadmaps and technical direction within Agile, Scrum, or SAFe delivery environments.
- Experience designing enterprise solutions using Microsoft Azure or a comparable cloud platform, including cloud-native or distributed architectures, APIs, microservices, event-driven systems, and enterprise integrations.
- Experience with architecture governance and documentation,
The last bullet seems cut off: "Experience with architecture governance and documentation," - but that's all the text provided. I'll include it as is.
Now, I'll structure the HTML.
I'll create:
About the role
McKesson intro...
Job Summary...
Responsibilities
Then
for prose 4. Don't repeat job title as heading 5. Don't put Job ID/requisition numbers as headings 6. Preserve ALL substantive information 7. Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) 8. Only include sections with real content 9. No filler/placeholder text 10. Output ONLY HTML fragment Looking at the content: - There's an intro paragraph about McKesson - Job Summary section - Key Responsibilities with multiple sub-sections - Minimum Qualifications with education and critical skills I need to organize this into logical sections. The posting has: 1. About the role / Job Summary (the intro + job summary) 2. Responsibilities (the Key Responsibilities section with multiple sub-areas) 3. Requirements / Qualifications (Minimum Qualifications) Let me structure it: - About the role: combine the McKesson intro and Job Summary - Responsibilities: break down the Key Responsibilities into sub-sections or keep as one big list? The rules say use
- for lists of duties. The responsibilities are quite detailed with multiple sub-categories. I could make each sub-category a separate list or combine. Since they're all responsibilities, I'll create one Responsibilities section with the sub-categories as nested lists or separate lists with headings. But the rules say use
for section headings only. I could use
for sub-sections? The rules only mention
for section headings. I'll keep it simple: one Responsibilities section with all the bullet points, but that's a lot. Better to group by the sub-headings in the original. Actually, looking at the original, the Key Responsibilities has 7 sub-sections: 1. Architectural Runway & Value Stream Leadership 2. AI & Agentic Engineering Leadership 3. Solution Architecture & Technical Design 4. Agile Delivery & Technical Leadership 5. Enterprise Architecture Alignment & Governance 6. Architecture Documentation & Knowledge Management 7. Security, Compliance & Operational Excellence 8. Cloud, Platform & Engineering Excellence That's 8 sub-sections. I could make each a separate
? But the rules say use
for section headings like "Responsibilities". Maybe I should have one "Responsibilities"
and then use
for sub-sections? The rules don't forbid
. But they say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So they expect those main sections. I'll create a Responsibilities section with the sub-sections as nested lists or separate lists with bold labels. Better: Use
for "Responsibilities" and then for each sub-area, use a label followed by
- . That keeps semantic structure.
Similarly for Qualifications: there's Education and Critical Skills (which is a list). I'll make a "Qualifications" section.
No mention of Benefits, Pay, Schedule - so omit those sections.
Now, let's write the HTML.
First, the About the role section: combine the McKesson intro paragraph and the Job Summary paragraph.
Then Responsibilities: list all the bullet points from each sub-section.
Then Qualifications: Education and Critical Skills.
I need to preserve ALL substantive information. So I must include all bullet points.
Let me extract all bullet points:
From Architectural Runway & Value Stream Leadership:
- Plan the architectural runway for an Agile Release Train (ART), proactively defining solution approaches, technical enablers, architecture patterns, dependencies, and future-state designs that enable teams across the Value Stream to deliver effectively at scale.
- Partner with Product Management, Engineering Leadership, and Enterprise Architecture to ensure upcoming features, epics, and initiatives have a clear architectural path prior to implementation.
- Develop and maintain technology and architecture roadmaps that support Value Stream objectives while balancing scalability, technical debt reduction, reliability, security, compliance, and delivery velocity.
- Identify capability gaps, modernization opportunities, architectural risks, and cross-team dependencies before they become delivery impediments.
- Establish architectural direction across multiple teams and applications, ensuring alignment on technology strategy and implementation approaches.
- Ensure teams are never waiting on architecture guidance, standards, patterns, technical decisions, architecture artifacts, or technical enablers required to execute delivery commitments.
From AI & Agentic Engineering Leadership:
- Partner with the CoverMyMeds AI Enablement team to evaluate, adopt, and operationalize AI-assisted software delivery practices across the ART.
- Serve as the primary architecture lead for AI adoption within the Value Stream, driving practical implementation of approved AI capabilities, tools, patterns, and engineering practices.
- Identify opportunities to improve engineering productivity, software quality, documentation, testing, knowledge management, architecture governance, operational support, and delivery effectiveness through AI-enabled workflows and automation.
- Develop adoption roadmaps and implementation plans that accelerate AI-assisted software delivery across engineering teams.
- Partner with Engineering Managers, Technical Leads, and development teams to increase adoption of AI-assisted development practices using platforms such as Microsoft Copilot, Claude, GitHub Copilot, and future enterprise-supported solutions.
- Define and maintain the architectural context, Architecture Decision Records (ADRs), repository standards, architecture artifacts, and knowledge-management practices required to effectively support agentic engineering.
- Drive adoption of architecture-as-code, AI-assisted documentation, automated architecture validation, and agent-enabled engineering workflows.
- Collaborate with the AI Enablement team to evaluate emerging agentic engineering capabilities and determine how they can be safely and effectively operationalized within the Value Stream.
- Serve as a champion for modern engineering practices and help teams evolve how software is designed, built, tested, documented, and supported.
From Solution Architecture & Technical Design:
- Lead the design of scalable, secure, resilient, and maintainable enterprise solutions.
- Create detailed architecture artifacts including system context diagrams, solution architecture diagrams, integration diagrams, deployment topologies, sequence diagrams, data flow diagrams, domain models, reference architectures, and implementation-ready design materials.
- Translate business and product objectives into actionable technical designs that can be executed consistently across multiple delivery teams.
- Evaluate architectural alternatives and recommend solutions based on business, operational, compliance, security, and technical tradeoffs.
- Develop implementation-ready architectural guidance that accelerates delivery and reduces ambiguity.
- Establish architecture patterns that promote reuse, consistency, maintainability, and operational excellence across the ART.
- Create current-state and future-state architecture views used to drive portfolio planning and modernization activities.
From Agile Delivery & Technical Leadership:
- Actively participate in Agile, Scrum, and SAFe planning and delivery activities, providing architectural guidance throughout the delivery lifecycle.
- Partner with Product Managers, Product Owners, Scrum Masters, Engineering Managers, and Technical Leads to ensure architectural priorities and technical enablers are reflected in team backlogs and delivery plans.
- Guide decomposition of large initiatives into implementable capabilities, features, and architectural enablers aligned with Agile delivery practices.
- Mentor engineers and technical leaders, helping elevate architectural maturity and engineering excellence across the ART.
- Influence technical decision-making and technology adoption across teams without direct managerial authority.
- Foster a culture of architectural thinking, engineering excellence, continuous learning, and innovation.
From Enterprise Architecture Alignment & Governance:
- Serve as the primary architecture representative for the ART, preparing, presenting, and defending solution designs, architecture decisions, technology strategies, and exception requests through Architecture Review Board (ARB) governance processes.
- Partner with Enterprise Architecture to operationalize enterprise standards, approved reference architectures, architectural guardrails, and strategic platform direction within the ART.
- Promote and govern adherence to enterprise architecture standards, ensuring solutions align with enterprise technology direction and approved patterns.
- Drive adoption of approved architectural patterns, shared services, platform capabilities, reusable solutions, and strategic technology platforms across teams and applications within the Value Stream.
- Partner effectively with Enterprise Architecture, Security, Platform Engineering, Compliance, Infrastructure, Cloud Operations, Developer Experience, AI Enablement, and other shared service organizations.
- Advocate for Value Stream needs while leveraging enterprise platforms, shared services, and reusable capabilities whenever possible.
- Track and communicate architectural risks, technical debt, modernization opportunities, major technology decisions, and cross-team dependencies.
- Maintain visibility into enterprise and platform dependencies that could impact delivery outcomes across the ART.
From Architecture Documentation & Knowledge Management:
- Own the architecture repository for the ART and application portfolio.
- Accountable for maintaining the architectural context, Architecture Decision Records (ADRs), architecture artifacts, and solution documentation for all applications and platforms within the ART.
- Establish and maintain architectural context including system boundaries, integrations, dependencies, data flows, technology selections, technical constraints, and historical decision records.
- Create and maintain current-state and future-state architecture documentation for applications and platforms owned within the Value Stream.
- Maintain architecture diagrams including system context diagrams, integration diagrams, deployment topologies, application interaction diagrams, domain models, sequence diagrams, and solution blueprints.
- Ensure architecture documentation remains current, accurate, discoverable, and accessible to engineers, architects, leadership, and stakeholders.
- Establish documentation standards and review processes that institutionalize architecture knowledge and reduce dependency on individual contributors.
- Maintain architectural knowledge in a manner that enables both engineers and AI-assisted tools to effectively understand and operate within the application portfolio.
From Security, Compliance & Operational Excellence:
- Ensure solutions adhere to enterprise security, privacy, audit, regulatory, and compliance requirements.
- Design architectures that support appropriate handling of Protected Health Information (PHI), Personally Identifiable Information (PII), and other sensitive data assets.
- Incorporate requirements associated with HIPAA, HITRUST, SOC, SOX, and related compliance frameworks into architectural designs and technology decisions.
- Partner with Security, Risk, Compliance, and Enterprise Architecture teams to proactively identify and mitigate architectural risks.
- Ensure security, resiliency, observability, and compliance requirements are incorporated into architectural runway planning and solution design activities.
- Promote secure-by-design and compliance-by-design practices throughout the software development lifecycle.
From Cloud, Platform & Engineering Excellence:
- Design and implement cloud-native architectures utilizing Azure and modern platform services.
- Promote CoverMyMeds standards for platforms, APIs, integrations, distributed systems, platform services, observability, resiliency, scalability, security, and operational excellence.
- Collaborate with Security, Platform Engineering, Enterprise Architecture, and Operations teams to align solutions with organizational standards.
- Evaluate technology investments and modernization initiatives that improve platform reliability, maintainability, scalability, and engineering effectiveness.
- Guide adoption of engineering platforms and practices leveraging technologies such as Azure, GitHub, Jira, Lucidchart, Microsoft Copilot, Claude, and related engineering productivity tools.
Qualifications:
- Degree or equivalent and typically requires 10+ years of relevant experience. Less years required if has relevant Master’s or Doctorate qualifications.
- Education: Bachelor's degree in Computer Science, Engineering, Information Technology, or related discipline.
- Critical Skills: 10+ years of experience in software engineering, solution architecture, enterprise architecture, or related technology disciplines, including 5+ years in a Lead Architect, Principal Architect, Solution Architect, or equivalent technical-leadership role.
- Demonstrated experience owning architecture across multiple applications, products, or Agile engineering teams.
- Experience establishing architectural roadmaps and technical direction within Agile, Scrum, or SAFe delivery environments.
- Experience designing enterprise solutions using Microsoft Azure or a comparable cloud platform, including cloud-native or distributed architectures, APIs, microservices, event-driven systems, and enterprise integrations.
- Experience with architecture governance and documentation,
The last bullet seems cut off: "Experience with architecture governance and documentation," - but that's all the text provided. I'll include it as is.
Now, I'll structure the HTML.
I'll create:
About the role
McKesson intro...
Job Summary...
Responsibilities
Then