Green Card Chief Architect Jobs
Chief Architect roles qualify for EB-2 and EB-3 green card sponsorship through PERM labor certification, where your employer documents that no qualified U.S. worker is available for the position. Architecture firms, real estate developers, and large construction companies regularly sponsor foreign-trained architects, making direct employer outreach a practical path to permanent residency.
Find Green Card Chief Architect JobsOverview
Showing 5 of 19+ Chief Architect jobs
See all Chief Architect Jobs
Sign up for free to unlock all listings, filter by visa type, and get alerts for new Chief Architect roles.
Get Access To All JobsINTRODUCTION
The Chief Architect for HealthShare is accountable for the architectural direction of the HealthShare platform and its evolution toward a more adoptable, upgradeable, and operationally efficient product. This role works across Development and Product Management to ensure architectural decisions support the product roadmap, improve execution across teams, and reduce the cost and complexity of deploying, upgrading, and operating HealthShare. This role owns the long-term technical shape of the platform, including service boundaries, deployment architecture, tenancy model, operational model, interoperability architecture, and the standards needed to move HealthShare toward a more productized and manageable service platform. It is expected that key architectural directions will include multi-tenant-capable design, cloud-deployable services, and stronger operational manageability. This role reports to the Director of Development, HealthCare Solutions.
Primary Accountability
- Define and maintain the target architecture for HealthShare.
- Drive architectural evolution from deployment-specific patterns toward reusable platform services.
- Ensure architectural investments materially reduce the cost and complexity of adoption, upgrade, and operation.
- Guide HealthShare services toward multi-tenant-capable, cloud-deployable, and operationally manageable designs where those approaches improve product scalability and lifecycle efficiency.
- Align architecture with Product Management goals and roadmap priorities.
- Establish and enforce architectural standards across teams.
- Mentor senior engineers and architects and raise the quality of technical decision-making across the organization.
Key Responsibilities
- Set the architectural direction for HealthShare platform capabilities, shared services, and major subsystem investments.
- Define platform architecture in ways that reduce implementation friction, simplify deployment, and improve upgrade consistency across customer environments.
- Lead architecture for multi-tenancy, including tenant isolation, configuration strategy, security boundaries, data partitioning, and operational controls, where it supports lower-cost delivery and operation.
- Define architectural requirements for cloud deployment, including portability, automation, resilience, observability, upgradeability, and lifecycle management.
- Drive improvements in manageability, including provisioning, deployment consistency, monitoring, telemetry, support diagnostics, and fault isolation.
- Partner with Product Management to ensure architectural investments support product goals and avoid short-term decisions that increase downstream adoption, upgrade, or support cost.
- Guide technical strategy for healthcare interoperability capabilities, including data exchange, transformation, normalization, orchestration, and standards alignment.
- Review major technical designs and steer teams toward consistent platform patterns and reusable solutions.
- Identify and drive reduction of technical debt that limits scalability, manageability, delivery speed, upgradeability, or product consistency.
- Influence roadmap sequencing where architectural prerequisites or technical constraints materially affect delivery, operational efficiency, or customer lifecycle cost.
- Build alignment across teams when technical tradeoffs span product, architecture, delivery, support, and operational concerns.
Required Experience
- Deep experience with InterSystems HealthShare architecture and engineering.
- Strong understanding of InterSystems IRIS and HealthShare platform patterns relevant to service design, interoperability, deployment, and lifecycle management.
- Proven experience designing enterprise healthcare systems with substantial interoperability requirements.
- Strong understanding of HL7 v2, FHIR, CDA/C-CDA, and related healthcare integration patterns.
- Experience evolving existing platforms toward architectures that improve product adoption, simplify upgrades, and reduce operating burden.
- Experience defining or guiding architecture for multi-tenant and operationally scalable systems.
- Demonstrated ability to influence across teams and functions at a senior technical level.
- Strong judgment in balancing architectural rigor with delivery realities and product economics.
Expected Outcomes
- HealthShare has a clearer and more consistent architectural direction across teams.
- Platform investments better support long-term product strategy rather than isolated implementation needs.
- The cost and complexity of adopting HealthShare are reduced through more standardized, reusable, and manageable platform patterns.
- Upgrades become more predictable and less expensive because architecture reduces environment-specific variation and operational friction.
- Services become easier to deploy, observe, operate, and support.
- The platform moves materially closer to scalable service models, including multi-tenant and cloud deployment approaches where appropriate.
- Teams make more consistent design decisions with less rework and fewer architecture-driven delivery issues.
Leadership Expectations
- Operates as the senior technical authority for HealthShare architecture.
- Provides clear architectural guidance, not just review feedback.
- Brings product, engineering, platform, and lifecycle cost concerns into a single technical direction.
- Raises standards through direct involvement, mentoring, and disciplined decision-making.
- Focuses on durable platform outcomes that improve product economics over time.
We are an equal-opportunity employer and do not discriminate because of race, color, religion, sex, national origin, ancestry, marital status, veteran status, age, disability, sexual orientation or gender identity or expression or any other legally protected category. InterSystems is an E-Verify Employer in the United States.
InterSystems is providing a current good faith estimate of the anticipated base salary range for this position depending on a variety of factors including experience, education, skills, and performance. Other compensation may include a discretionary annual variable target incentive. The company also provides generous employee benefits including:
- Medical, vision, and dental insurance
- Short-term and long-term disability, and life insurance
- 401(k) Profit Sharing Contribution
- Paid Time Off and Holidays
- Parental Leave
- Tuition reimbursement
The estimated base compensation range for this role is: $145,000—$190,000 USD
About InterSystems
InterSystems, a creative data technology provider, delivers a unified foundation for next-generation applications for healthcare, finance, manufacturing, and supply chain customers in more than 80 countries. Our data platforms solve interoperability, speed, and scalability problems for large organizations around the globe to unlock the power of data and allow people to perceive data in imaginative ways. Established in 1978, InterSystems is committed to excellence through its 24×7 support for customers and partners around the world. Privately held and headquartered in Boston, Massachusetts, InterSystems has 38 offices in 28 countries worldwide. For more information, please visit InterSystems.com.
INTRODUCTION
The Chief Architect for HealthShare is accountable for the architectural direction of the HealthShare platform and its evolution toward a more adoptable, upgradeable, and operationally efficient product. This role works across Development and Product Management to ensure architectural decisions support the product roadmap, improve execution across teams, and reduce the cost and complexity of deploying, upgrading, and operating HealthShare. This role owns the long-term technical shape of the platform, including service boundaries, deployment architecture, tenancy model, operational model, interoperability architecture, and the standards needed to move HealthShare toward a more productized and manageable service platform. It is expected that key architectural directions will include multi-tenant-capable design, cloud-deployable services, and stronger operational manageability. This role reports to the Director of Development, HealthCare Solutions.
Primary Accountability
- Define and maintain the target architecture for HealthShare.
- Drive architectural evolution from deployment-specific patterns toward reusable platform services.
- Ensure architectural investments materially reduce the cost and complexity of adoption, upgrade, and operation.
- Guide HealthShare services toward multi-tenant-capable, cloud-deployable, and operationally manageable designs where those approaches improve product scalability and lifecycle efficiency.
- Align architecture with Product Management goals and roadmap priorities.
- Establish and enforce architectural standards across teams.
- Mentor senior engineers and architects and raise the quality of technical decision-making across the organization.
Key Responsibilities
- Set the architectural direction for HealthShare platform capabilities, shared services, and major subsystem investments.
- Define platform architecture in ways that reduce implementation friction, simplify deployment, and improve upgrade consistency across customer environments.
- Lead architecture for multi-tenancy, including tenant isolation, configuration strategy, security boundaries, data partitioning, and operational controls, where it supports lower-cost delivery and operation.
- Define architectural requirements for cloud deployment, including portability, automation, resilience, observability, upgradeability, and lifecycle management.
- Drive improvements in manageability, including provisioning, deployment consistency, monitoring, telemetry, support diagnostics, and fault isolation.
- Partner with Product Management to ensure architectural investments support product goals and avoid short-term decisions that increase downstream adoption, upgrade, or support cost.
- Guide technical strategy for healthcare interoperability capabilities, including data exchange, transformation, normalization, orchestration, and standards alignment.
- Review major technical designs and steer teams toward consistent platform patterns and reusable solutions.
- Identify and drive reduction of technical debt that limits scalability, manageability, delivery speed, upgradeability, or product consistency.
- Influence roadmap sequencing where architectural prerequisites or technical constraints materially affect delivery, operational efficiency, or customer lifecycle cost.
- Build alignment across teams when technical tradeoffs span product, architecture, delivery, support, and operational concerns.
Required Experience
- Deep experience with InterSystems HealthShare architecture and engineering.
- Strong understanding of InterSystems IRIS and HealthShare platform patterns relevant to service design, interoperability, deployment, and lifecycle management.
- Proven experience designing enterprise healthcare systems with substantial interoperability requirements.
- Strong understanding of HL7 v2, FHIR, CDA/C-CDA, and related healthcare integration patterns.
- Experience evolving existing platforms toward architectures that improve product adoption, simplify upgrades, and reduce operating burden.
- Experience defining or guiding architecture for multi-tenant and operationally scalable systems.
- Demonstrated ability to influence across teams and functions at a senior technical level.
- Strong judgment in balancing architectural rigor with delivery realities and product economics.
Expected Outcomes
- HealthShare has a clearer and more consistent architectural direction across teams.
- Platform investments better support long-term product strategy rather than isolated implementation needs.
- The cost and complexity of adopting HealthShare are reduced through more standardized, reusable, and manageable platform patterns.
- Upgrades become more predictable and less expensive because architecture reduces environment-specific variation and operational friction.
- Services become easier to deploy, observe, operate, and support.
- The platform moves materially closer to scalable service models, including multi-tenant and cloud deployment approaches where appropriate.
- Teams make more consistent design decisions with less rework and fewer architecture-driven delivery issues.
Leadership Expectations
- Operates as the senior technical authority for HealthShare architecture.
- Provides clear architectural guidance, not just review feedback.
- Brings product, engineering, platform, and lifecycle cost concerns into a single technical direction.
- Raises standards through direct involvement, mentoring, and disciplined decision-making.
- Focuses on durable platform outcomes that improve product economics over time.
We are an equal-opportunity employer and do not discriminate because of race, color, religion, sex, national origin, ancestry, marital status, veteran status, age, disability, sexual orientation or gender identity or expression or any other legally protected category. InterSystems is an E-Verify Employer in the United States.
InterSystems is providing a current good faith estimate of the anticipated base salary range for this position depending on a variety of factors including experience, education, skills, and performance. Other compensation may include a discretionary annual variable target incentive. The company also provides generous employee benefits including:
- Medical, vision, and dental insurance
- Short-term and long-term disability, and life insurance
- 401(k) Profit Sharing Contribution
- Paid Time Off and Holidays
- Parental Leave
- Tuition reimbursement
The estimated base compensation range for this role is: $145,000—$190,000 USD
About InterSystems
InterSystems, a creative data technology provider, delivers a unified foundation for next-generation applications for healthcare, finance, manufacturing, and supply chain customers in more than 80 countries. Our data platforms solve interoperability, speed, and scalability problems for large organizations around the globe to unlock the power of data and allow people to perceive data in imaginative ways. Established in 1978, InterSystems is committed to excellence through its 24×7 support for customers and partners around the world. Privately held and headquartered in Boston, Massachusetts, InterSystems has 38 offices in 28 countries worldwide. For more information, please visit InterSystems.com.
See all Green Card Chief Architect Jobs
Sign up for free to unlock all listings, filter by visa type, and get alerts for new Green Card Chief Architect Jobs.
Get Access To All JobsTips for Finding Green Card Sponsorship in Chief Architect
Align your credentials before applying
PERM requires your employer to list a specific degree and field in the job posting. Make sure your architecture degree and any licensure credentials match the role's stated requirements exactly, since discrepancies can stall the labor certification audit.
Target firms with active PERM history
Use the OFLC Wage Search to identify architecture and design firms that have filed PERM applications in your specialty. Employers with existing PERM infrastructure move faster and face fewer internal approvals before sponsoring a new candidate.
Understand EB-2 versus EB-3 for your credentials
If your role requires a master's degree or you hold a bachelor's plus five years of progressive experience, you may qualify for EB-2, which can mean shorter priority date waits for some nationalities. Confirm your classification with your employer before PERM is filed.
Find green card sponsoring employers on Migrate Mate
Search Chief Architect roles on Migrate Mate to filter specifically for employers offering employment-based green card sponsorship. The platform surfaces PERM-filing history so you can prioritize outreach to companies that have sponsored architects before.
Negotiate sponsorship terms before accepting an offer
Ask whether the employer covers PERM filing and I-140 legal fees, or passes costs to you. USCIS does not require employers to pay attorney fees, so this is a negotiable point that significantly affects your out-of-pocket costs during the multi-year process.
Request concurrent filing when your priority date is current
Once your I-140 is approved and a visa number is available, ask your employer to file the I-485 adjustment of status concurrently. This lets you obtain work authorization and travel permission while USCIS adjudicates permanent residency, reducing employment gaps.
Green Card Chief Architect: Frequently Asked Questions
Does a Chief Architect role qualify for EB-2 or EB-3 sponsorship?
Chief Architect positions typically qualify for both. EB-3 covers roles requiring at least a bachelor's degree in architecture or a related field. EB-2 applies when the position requires an advanced degree, or when you hold a bachelor's plus at least five years of progressive post-degree experience. Your employer's job requirements and your credentials together determine which category USCIS reviews your I-140 petition under.
How does green card sponsorship differ from H-1B for a Chief Architect?
H-1B visa is temporary status that must be renewed every three years and is subject to an annual lottery cap for most applicants. PERM-based green card sponsorship has no annual cap at the EB-3 level for most nationalities, leads to permanent residency rather than temporary authorization, and gives you portability rights after 180 days of I-485 adjudication. The trade-off is time: the PERM and I-140 process typically takes one to three years before an immigrant visa number becomes available.
What does the PERM labor certification process involve for architecture roles?
PERM requires your employer to run a mandatory recruitment campaign, including print and online job postings, to document that no qualified U.S. worker applied for the Chief Architect position. DOL reviews the application and, if approved, your employer files the I-140 immigrant petition with USCIS. Architecture roles with highly specific licensure requirements, such as state licensure in a particular jurisdiction, can support a narrower recruitment definition, which sometimes strengthens the PERM application.
How can I find architecture firms that sponsor green cards?
OFLC Wage Search lets you search DOL's public PERM disclosure data by occupation and employer, so you can identify firms that have filed labor certifications for architecture roles before. Migrate Mate also filters Chief Architect job listings by employers with documented green card sponsorship history, saving you the step of manually cross-referencing disclosure files with open positions.
Can I change employers during the green card process without losing my place?
Yes, under AC21 portability rules, you can change to a same or similar occupation after your I-485 has been pending for at least 180 days and your I-140 has been approved. For Chief Architects, a move to a senior design or principal role at another firm generally qualifies as same or similar. Your new employer doesn't restart PERM, but they should confirm portability in writing before you resign.