Green Card Senior IT Architect Jobs
Senior IT Architect roles qualify for EB-2 and EB-3 green card sponsorship through PERM labor certification, which requires employers to document that no qualified U.S. worker is available before filing your I-140 petition. Architecture roles map cleanly to specialty occupation criteria, making sponsorship a realistic path for credentialed foreign professionals in enterprise infrastructure, cloud, and systems design.
Find Green Card Senior IT Architect JobsOverview
Showing 5 of 146+ Senior IT Architect jobs
See all 146+ Senior IT Architect Jobs
Sign up for free to unlock all listings, filter by visa type, and get alerts for new Senior IT Architect roles.
Get Access To All JobsINTRODUCTION
McKesson is an impact-driven, Fortune 10 company that touches virtually every aspect of healthcare. We are known for delivering insights, products, and services that make quality care more accessible and affordable. Here, we focus on the health, happiness, and well-being of you and those we serve – we care.
What you do at McKesson matters. We foster a culture where you can grow, make an impact, and are empowered to bring new ideas. Together, we thrive as we shape the future of health for patients, our communities, and our people. If you want to be part of tomorrow’s health today, we want to hear from you.
ROLE SUMMARY
Ontada is an oncology data science and technology business dedicated to transforming the fight against cancer. We specialize in real-world data and evidence generation that accelerates life science research, clinical technologies that support community providers with precise care, and provider engagement channels that enable education and insights.
We are hiring an IT Architect to define and drive cloud-native integration architecture across Ontada products and partner ecosystems. This role owns solution and platform architecture for API-led connectivity, event-driven integration, and secure data exchange—ensuring our systems are scalable, reliable, observable, and straightforward to evolve. Familiarity with healthcare interoperability standards (HL7/FHIR, including SMART on FHIR) is a plus for certain partner pathways, but the primary focus is strong enterprise-architecture fundamentals applied to modern cloud-native integration models.
Success in this role is measured by the clarity and adoption of your reference architectures and standards, the reliability and scalability of the integration ecosystem you enable, and your ability to influence decisions across multiple initiatives while mentoring and elevating engineering teams. Familiarity with AI/ML and NLP capabilities used in products (e.g., LLM-enabled workflows, retrieval patterns, evaluation, and governance) is a plus as Ontada expands intelligent experiences, but is not the core requirement.
TECHNICAL ENVIRONMENT
Cloud-Native Integration: API-led connectivity, event-driven architecture, pub/sub, schema management, idempotency, retries, backpressure
APIs: RESTful services, OpenAPI/Swagger, API gateways, versioning and contract-first design
Messaging: Kafka (or equivalent), queues/streams, event schema design
Platform Patterns: Microservices, containerization (Docker), service discovery, configuration management; service mesh (where applicable)
Data & Performance: Oracle and relational databases; Redis (caching); Elasticsearch; analytics/pipelines (e.g., Databricks)
Interoperability (nice to have): HL7v2, FHIR (R4+), SMART on FHIR, OAuth2/OIDC, C-CDA
Observability: Logging, metrics, distributed tracing (e.g., Dynatrace)
Cloud & Platforms: Azure, AWS, GCP, Cloud Foundry
Engineering Practices: CI/CD, automated testing, code reviews, architecture documentation
KEY RESPONSIBILITIES
Architecture Leadership & Strategy
- Drive architecture for interoperability and integration capabilities across systems, services, and product offerings.
- Partner with Product Owners, Sales, Business Analysts, Quality Assurance, and Project Management to translate functional and non-functional requirements into target architectures and delivery plans.
- Define architecture standards, reference implementations, and guardrails for APIs, integration patterns, security, and operational readiness.
- Evaluate solution options and drive alignment across stakeholders; communicate tradeoffs, risks, and recommendations to technical and non-technical audiences.
- Provide technical guidance to coach, motivate, and develop engineers and architects.
Cloud-Native Integration Architecture
- Define and govern integration reference architectures across APIs, events, and asynchronous workflows (request/response, pub/sub, choreography vs. orchestration).
- Establish platform patterns and guardrails for API gateways, service-to-service communication, schema/version management, and contract testing.
- Design for resiliency and performance using proven patterns (timeouts, retries, circuit breakers, bulkheads, idempotency, caching) and align to SLOs/SLAs.
- Guide event-driven integration (e.g., Kafka or equivalent) with well-defined event schemas, lifecycle management, and operational controls.
- Collaborate with security and platform teams to ensure secure-by-default integration approaches (OAuth2/OIDC, least privilege, secrets management, threat modeling).
Healthcare Interoperability (Optional) & Partner Integrations
- When applicable, drive design for healthcare data exchange leveraging HL7v2 and/or FHIR (R4+), including SMART on FHIR, to enable integrations with EMRs and partner systems.
- Partner with domain SMEs and external stakeholders to define interoperability expectations (security, conformance, and onboarding) and ensure integrations are scalable and supportable.
- Define API contracts, versioning strategy, and error taxonomy to enable predictable integrations for internal and external consumers.
- Partner with engineering teams to implement and evolve reusable integration components, adapters, and accelerators that reduce time-to-integrate.
Operational Excellence & Production Ownership
- Collaborate with engineering in release, sprint, and project planning to ensure delivery commitments are tracked and met across the SDLC.
- Demonstrate strong architectural ownership in production operations to address customer needs for support, issue analysis, enhancements, and corrective actions.
- Evolve software systems, infrastructure, and architecture to support growth, SLAs, availability, and continued operation.
- Drive operational readiness practices including observability, runbooks, incident response, and post-incident improvements.
- Resolve technical problems, issues, and escalations across delivery teams and project activities.
AI Enablement (Preferred)
- Partner with product and engineering teams to identify and deliver AI-enabled capabilities, from discovery and design through deployment, monitoring, and continuous improvement.
- Guide architecture patterns for integrating model services into cloud-native systems (APIs, events, data pipelines) with appropriate security, privacy, and compliance controls.
- Promote MLOps/LLMOps practices (versioning, CI/CD, automated testing, observability, rollback) and responsible AI governance.
- Collaborate on evaluation approaches to ensure AI features are reliable and safe for production use.
MINIMUM REQUIREMENT
Degree or equivalent and typically requires 7+ years of relevant experience.
Education
Bachelor’s degree in computer science, Software Engineering, Information Systems, or equivalent practical experience.
CRITICAL SKILLS
- 7+ years of software engineering experience, including 4+ years in architecture (solution, platform, or enterprise) with ownership across multiple systems.
- Strong enterprise integration architecture skills across REST APIs, event-driven messaging, and secure data exchange patterns.
- Strong technical fundamentals in cloud-native architecture (microservices, containers, resiliency patterns, observability) on Azure, AWS, or GCP.
- Experience designing and operating large-scale, multi-tenant services with reliability, scalability, and security best practices.
- Ability to drive cross-functional technical decisions, mentor engineers/architects, and communicate clearly through documentation and design reviews.
- Strong communication and stakeholder-management skills, with a track record of influencing cross-team decisions through documentation and design reviews.
- Nice to have: familiarity with HL7/FHIR and/or willingness to learn quickly as needed for partner integrations.
PREFERRED SKILLS
- Optional/nice to have: hands-on experience with FHIR (profiles, implementation guides, SMART on FHIR) and/or HL7v2, including conformance and integration testing.
- Experience integrating with multiple EMRs and partner ecosystems; familiarity with common healthcare workflows and data exchange constraints.
- Hands-on experience with microservices frameworks (e.g., Spring or equivalent) and API management practices.
- Experience with messaging and integration platforms (Kafka, service bus/queues, stream processing) and caching technologies (e.g., Redis).
- Experience with platform engineering patterns such as service mesh, policy-as-code, and automated architecture validation in CI/CD.
- Experience with observability platforms (e.g., Dynatrace) and production operations best practices.
- AI/ML product delivery experience (LLM-enabled workflows, evaluation, and responsible AI governance).
- Experience with Elasticsearch and/or analytics platforms (e.g., Databricks).
WHAT SUCCESS LOOKS LIKE
At 6 Months
- You have established and socialized a target-state cloud-native integration architecture, with clear standards for APIs, events, resiliency, and security.
- You have delivered at least one end-to-end initiative (design through production) for a key integration capability (e.g., event streaming, API modernization, partner onboarding accelerator).
- Teams are adopting your reference patterns and documentation with reduced integration friction and faster delivery.
- You are actively supporting production operations through improved observability, incident learnings, and reliability improvements.
At 12 Months
- You own and continuously improve the integration architecture across multiple products and partner pathways, with measurable gains in reliability, scalability, and onboarding speed.
- You have matured governance for integration assets (API standards, event schemas, implementation guides where applicable, and conformance testing) and created a repeatable delivery playbook across the SDLC.
- You are a trusted technical leader influencing roadmaps, investment decisions, and cross-team alignment.
- You have helped teams incorporate intelligent capabilities responsibly (where applicable) through clear evaluation, monitoring, and risk controls.
We are proud to offer a competitive compensation package at McKesson as part of our Total Rewards. This is determined by several factors, including performance, experience and skills, equity, regular job market evaluations, and geographical markets. The pay range shown below is aligned with McKesson's pay philosophy, and pay will always be compliant with any applicable regulations. In addition to base pay, other compensation, such as an annual bonus or long-term incentive opportunities may be offered. For more information regarding benefits at McKesson, please click here.
Our Base Pay Range for this position
$133,100 - $221,900
McKesson has become aware of online recruiting-related scams in which individuals who are not affiliated with or authorized by McKesson are using McKesson’s (or affiliated entities, like CoverMyMeds or RxCrossroads) name in fraudulent emails, job postings or social media messages. In light of these scams, please bear the following in mind:
McKesson Talent Advisors will never solicit money or credit card information in connection with a McKesson job application.
McKesson Talent Advisors do not communicate with candidates via online chatrooms or using email accounts such as Gmail or Hotmail. Note that McKesson does rely on a virtual assistant (Gia) for certain recruiting-related communications with candidates.
McKesson job postings are posted on our career site: careers.mckesson.com.
McKesson is an Equal Opportunity Employer
McKesson provides equal employment opportunities to applicants and employees, without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, protected veteran status, disability, age, genetic information, or any other legally protected category. For additional information on McKesson’s full Equal Employment Opportunity policies, visit our Equal Employment Opportunity page.
McKesson is committed to being an Equal Employment Opportunity Employer and offers opportunities to all job seekers including job seekers with disabilities. If you need a reasonable accommodation to assist with your job search or application for employment, please contact us by sending an email to (United States) Disability_Accommodation@McKesson.com or (Canada) Accessibility@mckesson.ca. Resumes or CVs submitted to this email box will not be accepted.
Join us at McKesson!
INTRODUCTION
McKesson is an impact-driven, Fortune 10 company that touches virtually every aspect of healthcare. We are known for delivering insights, products, and services that make quality care more accessible and affordable. Here, we focus on the health, happiness, and well-being of you and those we serve – we care.
What you do at McKesson matters. We foster a culture where you can grow, make an impact, and are empowered to bring new ideas. Together, we thrive as we shape the future of health for patients, our communities, and our people. If you want to be part of tomorrow’s health today, we want to hear from you.
ROLE SUMMARY
Ontada is an oncology data science and technology business dedicated to transforming the fight against cancer. We specialize in real-world data and evidence generation that accelerates life science research, clinical technologies that support community providers with precise care, and provider engagement channels that enable education and insights.
We are hiring an IT Architect to define and drive cloud-native integration architecture across Ontada products and partner ecosystems. This role owns solution and platform architecture for API-led connectivity, event-driven integration, and secure data exchange—ensuring our systems are scalable, reliable, observable, and straightforward to evolve. Familiarity with healthcare interoperability standards (HL7/FHIR, including SMART on FHIR) is a plus for certain partner pathways, but the primary focus is strong enterprise-architecture fundamentals applied to modern cloud-native integration models.
Success in this role is measured by the clarity and adoption of your reference architectures and standards, the reliability and scalability of the integration ecosystem you enable, and your ability to influence decisions across multiple initiatives while mentoring and elevating engineering teams. Familiarity with AI/ML and NLP capabilities used in products (e.g., LLM-enabled workflows, retrieval patterns, evaluation, and governance) is a plus as Ontada expands intelligent experiences, but is not the core requirement.
TECHNICAL ENVIRONMENT
Cloud-Native Integration: API-led connectivity, event-driven architecture, pub/sub, schema management, idempotency, retries, backpressure
APIs: RESTful services, OpenAPI/Swagger, API gateways, versioning and contract-first design
Messaging: Kafka (or equivalent), queues/streams, event schema design
Platform Patterns: Microservices, containerization (Docker), service discovery, configuration management; service mesh (where applicable)
Data & Performance: Oracle and relational databases; Redis (caching); Elasticsearch; analytics/pipelines (e.g., Databricks)
Interoperability (nice to have): HL7v2, FHIR (R4+), SMART on FHIR, OAuth2/OIDC, C-CDA
Observability: Logging, metrics, distributed tracing (e.g., Dynatrace)
Cloud & Platforms: Azure, AWS, GCP, Cloud Foundry
Engineering Practices: CI/CD, automated testing, code reviews, architecture documentation
KEY RESPONSIBILITIES
Architecture Leadership & Strategy
- Drive architecture for interoperability and integration capabilities across systems, services, and product offerings.
- Partner with Product Owners, Sales, Business Analysts, Quality Assurance, and Project Management to translate functional and non-functional requirements into target architectures and delivery plans.
- Define architecture standards, reference implementations, and guardrails for APIs, integration patterns, security, and operational readiness.
- Evaluate solution options and drive alignment across stakeholders; communicate tradeoffs, risks, and recommendations to technical and non-technical audiences.
- Provide technical guidance to coach, motivate, and develop engineers and architects.
Cloud-Native Integration Architecture
- Define and govern integration reference architectures across APIs, events, and asynchronous workflows (request/response, pub/sub, choreography vs. orchestration).
- Establish platform patterns and guardrails for API gateways, service-to-service communication, schema/version management, and contract testing.
- Design for resiliency and performance using proven patterns (timeouts, retries, circuit breakers, bulkheads, idempotency, caching) and align to SLOs/SLAs.
- Guide event-driven integration (e.g., Kafka or equivalent) with well-defined event schemas, lifecycle management, and operational controls.
- Collaborate with security and platform teams to ensure secure-by-default integration approaches (OAuth2/OIDC, least privilege, secrets management, threat modeling).
Healthcare Interoperability (Optional) & Partner Integrations
- When applicable, drive design for healthcare data exchange leveraging HL7v2 and/or FHIR (R4+), including SMART on FHIR, to enable integrations with EMRs and partner systems.
- Partner with domain SMEs and external stakeholders to define interoperability expectations (security, conformance, and onboarding) and ensure integrations are scalable and supportable.
- Define API contracts, versioning strategy, and error taxonomy to enable predictable integrations for internal and external consumers.
- Partner with engineering teams to implement and evolve reusable integration components, adapters, and accelerators that reduce time-to-integrate.
Operational Excellence & Production Ownership
- Collaborate with engineering in release, sprint, and project planning to ensure delivery commitments are tracked and met across the SDLC.
- Demonstrate strong architectural ownership in production operations to address customer needs for support, issue analysis, enhancements, and corrective actions.
- Evolve software systems, infrastructure, and architecture to support growth, SLAs, availability, and continued operation.
- Drive operational readiness practices including observability, runbooks, incident response, and post-incident improvements.
- Resolve technical problems, issues, and escalations across delivery teams and project activities.
AI Enablement (Preferred)
- Partner with product and engineering teams to identify and deliver AI-enabled capabilities, from discovery and design through deployment, monitoring, and continuous improvement.
- Guide architecture patterns for integrating model services into cloud-native systems (APIs, events, data pipelines) with appropriate security, privacy, and compliance controls.
- Promote MLOps/LLMOps practices (versioning, CI/CD, automated testing, observability, rollback) and responsible AI governance.
- Collaborate on evaluation approaches to ensure AI features are reliable and safe for production use.
MINIMUM REQUIREMENT
Degree or equivalent and typically requires 7+ years of relevant experience.
Education
Bachelor’s degree in computer science, Software Engineering, Information Systems, or equivalent practical experience.
CRITICAL SKILLS
- 7+ years of software engineering experience, including 4+ years in architecture (solution, platform, or enterprise) with ownership across multiple systems.
- Strong enterprise integration architecture skills across REST APIs, event-driven messaging, and secure data exchange patterns.
- Strong technical fundamentals in cloud-native architecture (microservices, containers, resiliency patterns, observability) on Azure, AWS, or GCP.
- Experience designing and operating large-scale, multi-tenant services with reliability, scalability, and security best practices.
- Ability to drive cross-functional technical decisions, mentor engineers/architects, and communicate clearly through documentation and design reviews.
- Strong communication and stakeholder-management skills, with a track record of influencing cross-team decisions through documentation and design reviews.
- Nice to have: familiarity with HL7/FHIR and/or willingness to learn quickly as needed for partner integrations.
PREFERRED SKILLS
- Optional/nice to have: hands-on experience with FHIR (profiles, implementation guides, SMART on FHIR) and/or HL7v2, including conformance and integration testing.
- Experience integrating with multiple EMRs and partner ecosystems; familiarity with common healthcare workflows and data exchange constraints.
- Hands-on experience with microservices frameworks (e.g., Spring or equivalent) and API management practices.
- Experience with messaging and integration platforms (Kafka, service bus/queues, stream processing) and caching technologies (e.g., Redis).
- Experience with platform engineering patterns such as service mesh, policy-as-code, and automated architecture validation in CI/CD.
- Experience with observability platforms (e.g., Dynatrace) and production operations best practices.
- AI/ML product delivery experience (LLM-enabled workflows, evaluation, and responsible AI governance).
- Experience with Elasticsearch and/or analytics platforms (e.g., Databricks).
WHAT SUCCESS LOOKS LIKE
At 6 Months
- You have established and socialized a target-state cloud-native integration architecture, with clear standards for APIs, events, resiliency, and security.
- You have delivered at least one end-to-end initiative (design through production) for a key integration capability (e.g., event streaming, API modernization, partner onboarding accelerator).
- Teams are adopting your reference patterns and documentation with reduced integration friction and faster delivery.
- You are actively supporting production operations through improved observability, incident learnings, and reliability improvements.
At 12 Months
- You own and continuously improve the integration architecture across multiple products and partner pathways, with measurable gains in reliability, scalability, and onboarding speed.
- You have matured governance for integration assets (API standards, event schemas, implementation guides where applicable, and conformance testing) and created a repeatable delivery playbook across the SDLC.
- You are a trusted technical leader influencing roadmaps, investment decisions, and cross-team alignment.
- You have helped teams incorporate intelligent capabilities responsibly (where applicable) through clear evaluation, monitoring, and risk controls.
We are proud to offer a competitive compensation package at McKesson as part of our Total Rewards. This is determined by several factors, including performance, experience and skills, equity, regular job market evaluations, and geographical markets. The pay range shown below is aligned with McKesson's pay philosophy, and pay will always be compliant with any applicable regulations. In addition to base pay, other compensation, such as an annual bonus or long-term incentive opportunities may be offered. For more information regarding benefits at McKesson, please click here.
Our Base Pay Range for this position
$133,100 - $221,900
McKesson has become aware of online recruiting-related scams in which individuals who are not affiliated with or authorized by McKesson are using McKesson’s (or affiliated entities, like CoverMyMeds or RxCrossroads) name in fraudulent emails, job postings or social media messages. In light of these scams, please bear the following in mind:
McKesson Talent Advisors will never solicit money or credit card information in connection with a McKesson job application.
McKesson Talent Advisors do not communicate with candidates via online chatrooms or using email accounts such as Gmail or Hotmail. Note that McKesson does rely on a virtual assistant (Gia) for certain recruiting-related communications with candidates.
McKesson job postings are posted on our career site: careers.mckesson.com.
McKesson is an Equal Opportunity Employer
McKesson provides equal employment opportunities to applicants and employees, without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, protected veteran status, disability, age, genetic information, or any other legally protected category. For additional information on McKesson’s full Equal Employment Opportunity policies, visit our Equal Employment Opportunity page.
McKesson is committed to being an Equal Employment Opportunity Employer and offers opportunities to all job seekers including job seekers with disabilities. If you need a reasonable accommodation to assist with your job search or application for employment, please contact us by sending an email to (United States) Disability_Accommodation@McKesson.com or (Canada) Accessibility@mckesson.ca. Resumes or CVs submitted to this email box will not be accepted.
Join us at McKesson!
See all 146+ Green Card Senior IT Architect Jobs
Sign up for free to unlock all listings, filter by visa type, and get alerts for new Green Card Senior IT Architect Jobs.
Get Access To All JobsTips for Finding Green Card Sponsorship in Senior IT Architect
Translate your architecture credentials for PERM
PERM requires your degree and job duties to align precisely. If your title is 'Solutions Architect' or 'Enterprise Architect' abroad, document how your experience maps to the DOL's job requirements for the posted position before your employer files.
Use O*NET to anchor your specialty occupation case
The O*NET profile for IT Architects shows that a bachelor's degree in computer science or a related field is standard entry. Employers and attorneys cite this profile directly when establishing specialty occupation for your I-140, so review it yourself before negotiations.
Target employers with active PERM filing history
Not every company that hires IT Architects sponsors green cards. Filter your search to employers who have filed PERM applications in your target role category. Migrate Mate surfaces this filing history by employer and job title, so you don't need to parse raw OFLC disclosure files yourself.
Verify the prevailing wage tier before accepting an offer
Your employer must pay at least the DOL prevailing wage for your role and location. Look up the wage level using the OFLC Wage Search before signing an offer. Accepting a Level I or II wage when your duties are Level III or IV can delay or derail your PERM filing.
Understand how your nationality affects your EB-2 vs EB-3 choice
If you're from India or China, EB-2 and EB-3 priority date backlogs can mean decades of waiting. For many nationals in this situation, EB-3 downgrading or concurrent filing strategies can meaningfully shorten the path to a green card, depending on your current visa status.
Time your I-140 filing to protect your priority date
Your priority date locks in when USCIS receives your I-140, not when PERM is approved. If your employer changes law firms or restructures during the process, confirm in writing that your approved PERM will be used promptly so you don't lose months of queue position.
Green Card Senior IT Architect: Frequently Asked Questions
Does a Senior IT Architect role qualify for EB-2 or EB-3 sponsorship?
Senior IT Architect positions typically qualify for both EB-2 and EB-3 depending on the specific requirements the employer sets for the role. EB-2 applies when the position requires a master's degree or equivalent, while EB-3 applies for roles requiring a bachelor's degree with experience. The employer's job description and minimum requirements drive which category USCIS will accept, so the framing matters as much as your actual credentials.
How does green card sponsorship differ from H-1B sponsorship for IT Architects?
H-1B visa sponsorship is temporary, capped annually, and subject to a lottery. Green card sponsorship through PERM and I-140 is permanent, has no annual lottery, and ties your immigration status to a specific employer only until you reach the 180-day portability threshold under AC21. EB-3 has no numerical cap concerns for most nationalities outside India and China, and the process leads to lawful permanent residency rather than a renewable temporary status.
How long does the PERM and I-140 process typically take for Senior IT Architects?
PERM labor certification currently takes roughly 12 to 18 months at the DOL when filed through normal channels, though audit-triggered cases can run longer. Once PERM is approved, USCIS adjudicates the I-140 within 6 to 12 months on standard processing, or faster with premium processing. Your total timeline from PERM filing to I-140 approval commonly runs 18 to 30 months before adjustment of status can begin, depending on your priority date and nationality.
What should I look for in an employer to improve my green card sponsorship odds?
Look for employers with a documented PERM filing history in IT or architecture roles, not just a general willingness to sponsor. Companies that have filed successfully in the past have in-house or retained immigration counsel and understand the PERM advertising and prevailing wage requirements. Use Migrate Mate to filter Senior IT Architect roles by employers with active green card sponsorship history, so you're targeting companies that have completed this process before rather than those encountering it for the first time.
Can I switch employers after my I-140 is approved without losing my place in the green card queue?
Yes, under AC21 portability rules, you can change employers after your I-140 has been approved and your adjustment of status application has been pending for at least 180 days, provided the new role is in the same or a similar occupational classification. For Senior IT Architects, moving between companies in enterprise infrastructure, cloud architecture, or systems design generally satisfies the same or similar requirement. USCIS evaluates this on a case-by-case basis, so document the overlap between your old and new roles carefully.