Green Card Principal Software Architect Jobs
Principal Software Architect jobs with green card sponsorship require employers to complete PERM labor certification with the Department of Labor, file an I-140 petition with USCIS, and demonstrate that no qualified U.S. worker was displaced. EB-2 applies to advanced-degree candidates; EB-3 covers professionals with a bachelor's degree, though per-country backlogs affect nationals from high-demand countries.
Find Green Card Principal Software Architect JobsOverview
Showing 5 of 59+ Principal Software Architect jobs
See all 59+ Principal Software Architect Jobs
Sign up for free to unlock all listings, filter by visa type, and get alerts for new Principal Software Architect roles.
Get Access To All JobsINTRODUCTION
Senseonics is looking for a Sr Principal Software Architect, Mobile, to define and build the next generation of our mobile platform for the Eversense continuous glucose monitoring (CGM) system. Our mobile apps are the primary interface between patients, their implanted sensor and smart transmitter, and our cloud. They are safety-relevant, regulated medical device software running on thousands of iOS and Android phone models, plus watches and widgets. This is a hands-on technical leadership role. You will set next-generation mobile architecture across product lines and lead cross-team design discussions with firmware, cloud, systems, quality, regulatory, and external development partners. You will also stay close to the code, building reference implementations of key components and leading by example in code and design reviews. You will help the mobile team use AI assisted engineering to move faster without compromising the rigor medical device software requires. The role spans our current commercial platform (Eversense 365, US and OUS) and our next-generation sensor and system programs, from feasibility and prototypes through pivotal studies, regulatory submission, and post-market maintenance.
Duties and Responsibilities:
Architecture and Technical Leadership
- Define the target architecture for the next generation of Senseonics mobile apps, including a shared device-communication layer, data persistence and sync, cloud integration, and a modular structure that supports multiple sensor generations and product lines from a common foundation.
- Own the architecture of the mobile-to-device boundary: BLE communication with transmitters and sensors, pairing and bonding, connection reliability, background execution, and reconnection behavior across iOS and Android OS versions and phone manufacturers.
- Lead cross-functional and cross-team architecture forums with embedded/firmware, cloud/backend, systems engineering, human factors, quality, regulatory, and clinical teams. Align interfaces, protocols, and data contracts across system boundaries.
- Provide technical direction to internal teams and external development partners. Review and approve designs, set coding and architectural standards, and make sure partner-delivered software meets Senseonics’ quality and maintainability bar.
- Drive the mobile architecture for new-product programs from feasibility through pivotal and commercial release: rapid prototypes, test-system apps, and data-collection tools for feasibility and clinical/animal studies, evolving into production-grade design.
- Establish a security-by-design architecture aligned with FDA premarket cybersecurity expectations. That includes threat modeling, secure device communication, secure storage, authentication and identity integration, SBOM and third-party dependency management, and remediation strategy for static analysis and adversarial testing findings.
- Define the strategy for observability and diagnostics: structured and parseable logs, telemetry, diagnostic data upload, and field-issue triage tooling that shortens investigation of field and complaint issues.
- Lead technical debt strategy and modernization. Assess annual platform changes (WWDC and Google I/O), toolchain and compiler upgrades, deprecations, and new form factors such as foldables, wearables, and widgets. Present prioritized, risk-ranked recommendations.
- Author and own architecture documentation for regulated development: software architecture and design specifications, interface specifications, risk analysis inputs, and change impact assessments, consistent with IEC 62304 and ISO 14971.
- Articulate tradeoffs among safety, reliability, cost, schedule, technical necessity, and competitive trends to engineering and business leadership, and give clear recommendations.
- Mentor senior and staff engineers, raise the technical bar of the mobile organization, and help assess technical candidates during hiring.
Hands-On Development
- Design and write production code in critical areas such as the BLE communication stack, orchestration and data layers, security, and diagnostics.
- Build proof-of-concept and reference implementations to validate architectural direction, de-risk new technologies, and establish patterns teams can adopt.
- Lead deep technical investigations of complex field issues, especially connectivity, background behavior, and device- or OS-specific defects, from root cause through fix and verification.
- Take part in code reviews, design reviews, and verification activities. Champion unit, integration, and automated testing, including CI/CD pipeline improvements.
AI-Accelerated Engineering
- Lead practical adoption of AI across the mobile development lifecycle. Use coding agents and AI assistants for implementation, refactoring, and platform migrations. Use AI-assisted code review and adversarial review, test generation, log and field-issue analysis, and requirements and change-impact analysis.
- Build and share reusable workflows, prompts, agent rules, and tooling that measurably speed up the team on both platforms.
- Coach engineers on using AI effectively, and set pragmatic guardrails: human review of AI-generated code, protection of proprietary and patient data, and verification standards appropriate for regulated software.
- Evaluate new AI developer tools and recommend which ones to adopt based on demonstrated impact on throughput and quality.
KNOWLEDGE, SKILLS, ABILITIES AND REQUIREMENTS
Required:
- BS in Computer Science, Computer Engineering, Electrical Engineering, or equivalent.
- 10+ years of professional software development experience, including 6+ years building native mobile applications.
- Deep expertise in at least one native mobile platform: iOS (Swift, Objective-C) or Android (Kotlin, Java). Must be able to read, review, and reason about architecture on both platforms.
- Significant hands-on experience with Bluetooth, preferably Bluetooth Low Energy: GATT design, pairing and bonding, connection management, throughput and latency tuning, background operation, and handling the differences across iOS CoreBluetooth and Android BLE stacks and phone manufacturers.
- Proven track record as the technical owner who defined and delivered the architecture of at least one shipped, complex mobile product, including modular design, layering, data persistence and synchronization, offline-first behavior, and cloud/REST API integration.
- Experience integrating mobile software with embedded devices or hardware peripherals, including working directly with firmware teams on protocols and interface definitions.
- Strong communicator who can lead cross-team technical discussions, write clear design documentation, and influence without direct authority, including with external partners.
- Self-directed, with sound judgment on balancing architectural vision with delivery commitments.
Desirable:
- Demonstrated use of AI-assisted development (coding agents, AI code review, AI-driven testing or debugging) to accelerate a team, not just individual productivity.
- Hands-on depth on both iOS and Android.
- NFC experience (Core NFC, Android NFC).
- Experience developing software for Class II or Class III medical devices (SiMD or SaMD). Familiarity with IEC 62304, ISO 14971, IEC 62366, and FDA design controls.
- Mobile cybersecurity experience: threat modeling, secure BLE communication, mobile app security testing (static, dynamic, adversarial), SBOM, and FDA premarket cybersecurity guidance.
- Experience with cross-platform or shared-code strategies (for example Kotlin Multiplatform, shared C/C++ libraries) and the tradeoffs versus fully native implementations.
- Experience with Apple Watch / Wear OS companion apps, home-screen widgets, and foldable-device support.
- Experience with mobile observability: structured logging, telemetry, crash analytics, and remote diagnostic data collection.
- Experience in health, CGM, insulin delivery, or other connected-health ecosystems, including third-party data integrations.
- MS in Computer Science, Software Engineering, or a related field.
LOCATION
This role is remote, with hybrid preferred at our Germantown, MD or Minneapolis, MN offices.
INTRODUCTION
Senseonics is looking for a Sr Principal Software Architect, Mobile, to define and build the next generation of our mobile platform for the Eversense continuous glucose monitoring (CGM) system. Our mobile apps are the primary interface between patients, their implanted sensor and smart transmitter, and our cloud. They are safety-relevant, regulated medical device software running on thousands of iOS and Android phone models, plus watches and widgets. This is a hands-on technical leadership role. You will set next-generation mobile architecture across product lines and lead cross-team design discussions with firmware, cloud, systems, quality, regulatory, and external development partners. You will also stay close to the code, building reference implementations of key components and leading by example in code and design reviews. You will help the mobile team use AI assisted engineering to move faster without compromising the rigor medical device software requires. The role spans our current commercial platform (Eversense 365, US and OUS) and our next-generation sensor and system programs, from feasibility and prototypes through pivotal studies, regulatory submission, and post-market maintenance.
Duties and Responsibilities:
Architecture and Technical Leadership
- Define the target architecture for the next generation of Senseonics mobile apps, including a shared device-communication layer, data persistence and sync, cloud integration, and a modular structure that supports multiple sensor generations and product lines from a common foundation.
- Own the architecture of the mobile-to-device boundary: BLE communication with transmitters and sensors, pairing and bonding, connection reliability, background execution, and reconnection behavior across iOS and Android OS versions and phone manufacturers.
- Lead cross-functional and cross-team architecture forums with embedded/firmware, cloud/backend, systems engineering, human factors, quality, regulatory, and clinical teams. Align interfaces, protocols, and data contracts across system boundaries.
- Provide technical direction to internal teams and external development partners. Review and approve designs, set coding and architectural standards, and make sure partner-delivered software meets Senseonics’ quality and maintainability bar.
- Drive the mobile architecture for new-product programs from feasibility through pivotal and commercial release: rapid prototypes, test-system apps, and data-collection tools for feasibility and clinical/animal studies, evolving into production-grade design.
- Establish a security-by-design architecture aligned with FDA premarket cybersecurity expectations. That includes threat modeling, secure device communication, secure storage, authentication and identity integration, SBOM and third-party dependency management, and remediation strategy for static analysis and adversarial testing findings.
- Define the strategy for observability and diagnostics: structured and parseable logs, telemetry, diagnostic data upload, and field-issue triage tooling that shortens investigation of field and complaint issues.
- Lead technical debt strategy and modernization. Assess annual platform changes (WWDC and Google I/O), toolchain and compiler upgrades, deprecations, and new form factors such as foldables, wearables, and widgets. Present prioritized, risk-ranked recommendations.
- Author and own architecture documentation for regulated development: software architecture and design specifications, interface specifications, risk analysis inputs, and change impact assessments, consistent with IEC 62304 and ISO 14971.
- Articulate tradeoffs among safety, reliability, cost, schedule, technical necessity, and competitive trends to engineering and business leadership, and give clear recommendations.
- Mentor senior and staff engineers, raise the technical bar of the mobile organization, and help assess technical candidates during hiring.
Hands-On Development
- Design and write production code in critical areas such as the BLE communication stack, orchestration and data layers, security, and diagnostics.
- Build proof-of-concept and reference implementations to validate architectural direction, de-risk new technologies, and establish patterns teams can adopt.
- Lead deep technical investigations of complex field issues, especially connectivity, background behavior, and device- or OS-specific defects, from root cause through fix and verification.
- Take part in code reviews, design reviews, and verification activities. Champion unit, integration, and automated testing, including CI/CD pipeline improvements.
AI-Accelerated Engineering
- Lead practical adoption of AI across the mobile development lifecycle. Use coding agents and AI assistants for implementation, refactoring, and platform migrations. Use AI-assisted code review and adversarial review, test generation, log and field-issue analysis, and requirements and change-impact analysis.
- Build and share reusable workflows, prompts, agent rules, and tooling that measurably speed up the team on both platforms.
- Coach engineers on using AI effectively, and set pragmatic guardrails: human review of AI-generated code, protection of proprietary and patient data, and verification standards appropriate for regulated software.
- Evaluate new AI developer tools and recommend which ones to adopt based on demonstrated impact on throughput and quality.
KNOWLEDGE, SKILLS, ABILITIES AND REQUIREMENTS
Required:
- BS in Computer Science, Computer Engineering, Electrical Engineering, or equivalent.
- 10+ years of professional software development experience, including 6+ years building native mobile applications.
- Deep expertise in at least one native mobile platform: iOS (Swift, Objective-C) or Android (Kotlin, Java). Must be able to read, review, and reason about architecture on both platforms.
- Significant hands-on experience with Bluetooth, preferably Bluetooth Low Energy: GATT design, pairing and bonding, connection management, throughput and latency tuning, background operation, and handling the differences across iOS CoreBluetooth and Android BLE stacks and phone manufacturers.
- Proven track record as the technical owner who defined and delivered the architecture of at least one shipped, complex mobile product, including modular design, layering, data persistence and synchronization, offline-first behavior, and cloud/REST API integration.
- Experience integrating mobile software with embedded devices or hardware peripherals, including working directly with firmware teams on protocols and interface definitions.
- Strong communicator who can lead cross-team technical discussions, write clear design documentation, and influence without direct authority, including with external partners.
- Self-directed, with sound judgment on balancing architectural vision with delivery commitments.
Desirable:
- Demonstrated use of AI-assisted development (coding agents, AI code review, AI-driven testing or debugging) to accelerate a team, not just individual productivity.
- Hands-on depth on both iOS and Android.
- NFC experience (Core NFC, Android NFC).
- Experience developing software for Class II or Class III medical devices (SiMD or SaMD). Familiarity with IEC 62304, ISO 14971, IEC 62366, and FDA design controls.
- Mobile cybersecurity experience: threat modeling, secure BLE communication, mobile app security testing (static, dynamic, adversarial), SBOM, and FDA premarket cybersecurity guidance.
- Experience with cross-platform or shared-code strategies (for example Kotlin Multiplatform, shared C/C++ libraries) and the tradeoffs versus fully native implementations.
- Experience with Apple Watch / Wear OS companion apps, home-screen widgets, and foldable-device support.
- Experience with mobile observability: structured logging, telemetry, crash analytics, and remote diagnostic data collection.
- Experience in health, CGM, insulin delivery, or other connected-health ecosystems, including third-party data integrations.
- MS in Computer Science, Software Engineering, or a related field.
LOCATION
This role is remote, with hybrid preferred at our Germantown, MD or Minneapolis, MN offices.
See all 59+ Green Card Principal Software Architect Jobs
Sign up for free to unlock all listings, filter by visa type, and get alerts for new Green Card Principal Software Architect Jobs.
Get Access To All JobsTips for Finding Green Card Sponsorship in Principal Software Architect
Document your architecture leadership credentials early
Gather evidence of system design ownership, patents, published technical standards, and cross-team leadership before PERM begins. Employers need to justify the role's requirements, and your credentials directly shape how the job description is drafted for the prevailing wage determination.
Use the OFLC Wage Search to benchmark your offer
Look up the prevailing wage for your SOC code and work location before negotiating salary. PERM requires your offered wage to meet or exceed the DOL-determined prevailing wage, and a shortfall discovered after filing restarts the entire process.
Find sponsors through Migrate Mate before applying
Search Migrate Mate to identify employers with verified green card sponsorship history for software architecture roles. Targeting companies already familiar with the PERM process reduces the risk of an employer backing out midway through a multi-year sponsorship commitment.
Verify your degree maps to EB-2 requirements
EB-2 requires a U.S. master's degree or foreign equivalent, or a bachelor's plus five years of progressive experience. If your credentials fall into the experience-based path, get a formal credentials evaluation completed before your employer files the PERM application with DOL.
Ask employers about their PERM recruitment audit trail
PERM requires employers to run a full recruitment test before filing, and DOL audits a portion of applications. Confirm your prospective employer has conducted genuine recruitment and retained all documentation, since audit responses require evidence of active recruitment steps.
Track your priority date against the Visa Bulletin
Once your I-140 is approved, your priority date determines when you can file for adjustment of status. Nationals from India and China face significant backlogs in the EB-2 and EB-3 categories, so monitor the USCIS Visa Bulletin monthly to know your projected filing window.
Green Card Principal Software Architect: Frequently Asked Questions
How does green card sponsorship differ from H-1B sponsorship for Principal Software Architects?
Green card sponsorship leads to lawful permanent residence rather than a temporary work authorization period. The employer must complete PERM labor certification with the Department of Labor, proving no qualified U.S. worker was available, before filing an I-140 with USCIS. H-1B visa involves an LCA and a fixed status period with lottery risk; EB-2 and EB-3 green card paths involve no lottery but do have per-country numerical limits and potential priority date backlogs.
What PERM steps should a Principal Software Architect expect their employer to complete?
Your employer first requests a prevailing wage determination from DOL, then conducts a mandatory recruitment campaign including job postings, internal notices, and potentially Sunday newspaper ads. After recruitment closes, the employer files the ETA Form 9089 with DOL. The entire PERM process typically takes several months before the I-140 petition can be filed with USCIS.
How can I find Principal Software Architect roles where employers already sponsor green cards?
Migrate Mate lists employers with verified green card sponsorship history, letting you target companies already experienced with the PERM process for technical roles. This matters because sponsoring a Principal Software Architect through PERM is a multi-year commitment, and employers unfamiliar with the process often withdraw before completion.
Can I change employers after my green card process has started?
AC21 job portability lets you change to a same or similar occupation once your I-485 adjustment of status application has been pending for 180 days or more, without losing your place in the queue. Separately, an approved I-140 petition's priority date can be carried over to a new employer's I-140 filing, protecting the time you've already accumulated in the backlog.
Does a Principal Software Architect role qualify for EB-2 or EB-3?
Most Principal Software Architect positions qualify for EB-2 because the role typically requires a master's degree or a bachelor's degree combined with at least five years of progressive experience in software architecture or engineering. If the employer defines the position as requiring only a bachelor's degree and two or more years of experience, EB-3 may apply instead, though EB-2 is more common at this seniority level.