Principal Software Architect Jobs in USA with Visa Sponsorship
Principal Software Architect roles rank among the most H-1B visa-sponsored positions in the U.S. tech industry, qualifying as specialty occupations under USCIS guidelines. Employers filing an LCA must meet prevailing wage requirements, and your architecture-level credentials directly affect which wage tier applies to your offer.
Find Principal Software Architect JobsOverview
Showing 5 of 66+ Principal Software Architect jobs
See all 66+ 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 66+ 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 JobsTips for Finding Principal Software Architect Jobs
Align your credentials to specialty occupation standards
USCIS requires a direct relationship between your degree field and the architect role. A computer science or software engineering degree maps cleanly, but an unrelated degree needs documented equivalency through a credential evaluation before your employer files.
Check prevailing wage tiers before accepting offers
Principal architect roles almost always land at DOL wage Level III or IV. Run your job title and work location through the OFLC Wage Search so you can verify your offer clears the LCA threshold before the employer certifies it.
Target companies with active LCA filing history
Use Migrate Mate to find employers who have filed verified LCAs for senior architecture roles. This filters out companies that say they sponsor but have no documented track record, saving you weeks of back-and-forth.
Understand how cap-exempt employers change your timeline
Universities, nonprofit research institutions, and certain government contractors are H-1B cap-exempt. For a Principal Architect role, this means no annual lottery wait and filing possible at any point in the year, not just October starts.
Secure a written description of your architectural responsibilities
Vague job descriptions are the most common reason RFEs are issued for architect-level H-1B petitions. Get a detailed offer letter specifying system design ownership, cross-functional technical leadership, and the degree requirement before your employer submits Form I-129.
Frequently Asked Questions
Does a Principal Software Architect role qualify as a specialty occupation for H-1B purposes?
Yes. Principal Software Architect is consistently recognized by USCIS as a specialty occupation because the role requires at minimum a bachelor's degree in computer science, software engineering, or a directly related field. The architectural scope of the role, covering system design, technical strategy, and cross-team engineering leadership, reinforces the specialty occupation argument. Employers with vague job descriptions have faced RFEs, so the offer letter needs to be specific about those duties.
Which visas are realistic for a Principal Software Architect seeking U.S. sponsorship?
H-1B is the most common path, covering most nationalities through the annual cap and lottery. Australian citizens can pursue the E-3 visa, which has a separate cap that has never been exhausted and requires no lottery. Chilean and Singaporean nationals may qualify for the H-1B1 visa. All three require employer-filed LCAs and a qualifying specialty occupation, which Principal Architect roles satisfy. O*NET classifies this occupation at the highest job zone, supporting the degree requirement across all three visa types.
How do I find employers who actively sponsor Principal Software Architect roles?
Migrate Mate lists employers with verified LCA sponsorship history for senior engineering and architecture roles, so you can focus your search on companies with a documented track record rather than relying on job posts that mention sponsorship without evidence.
Does my degree field matter if I have 15 or more years of experience?
Yes, it still matters for H-1B, E-3, and H-1B1 visa purposes. USCIS requires a direct relationship between the degree field and the role, not just a degree plus experience. If your degree is in an unrelated field, your employer will need to demonstrate equivalency through a credential evaluation or by documenting progressive responsibility that substitutes for the missing coursework. Experience alone does not replace field alignment under the specialty occupation standard.
What is the LCA process for a Principal Software Architect, and how long does it take?
The employer files the LCA with DOL before submitting the H-1B, E-3, or H-1B1 visa petition. DOL certifies most LCAs within seven business days when filed through the FLAG system. The LCA must specify the work location, the prevailing wage level, and the job title. For a Principal Architect, the wage level is almost always Level III or IV, which you can verify in advance using the OFLC Wage Search. The LCA must be certified before the visa petition or consular application can proceed.
What is the prevailing wage requirement for sponsored Principal Software Architect jobs?
U.S. employers sponsoring a visa must pay at least the prevailing wage, which is what workers in the same role, area, and experience level typically earn. The Department of Labor sets this rate to make sure companies aren't hiring foreign workers simply because they'd accept lower pay than a U.S. worker. It varies by job title, location, and experience. You can look up current prevailing wage rates for any occupation and location using the OFLC Wage Search page.