Sponsorship verdict
Sponsorship possible
One solid signal, not two. Worth applying, and worth asking about sponsorship early.
-
✓
Employer is on a government sponsor recordThe US Department of Labor certified 2 H-1B/E-3 labor condition applications for this employer between Oct 2025 and Jun 2026 (latest Jun 2026) — the step every H-1B hire needs first.
-
?
The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
-
?
No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area.
-
✓
Confirmed live todayWhen a source last listed this job as open.
Details and sources
- Employer is on a government sponsor record
- The US Department of Labor certified 2 H-1B/E-3 labor condition applications for this employer between Oct 2025 and Jun 2026 (latest Jun 2026) — the step every H-1B hire needs first. Source: LCA disclosure data (US Department of Labor (OFLC)).
- No salary bar for this route
- H-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.
US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).
A verdict summarises public evidence. It is not legal advice and never a guarantee: the employer and the immigration authority decide. Sign in to factor in where you can already work.
About the role
About the role
We are seeking a Senior Solutions Architect with deep security expertise to join the Voyager team in the Mirantis Office of the CTO. You will own the security solutioning of k0rdent AI, our platform for building and operating GPU clouds and AI factories, from metal to model.
You will define how k0rdent AI environments are secured end to end: the hardware and firmware they boot from, the hosts, virtual machines and Kubernetes clusters they run, the networks and storage they share, the secrets and certificates that hold them together, and the AI models and applications they serve. You will turn that design into published reference architectures, working code and proofs of concept that run on real hardware with our customers and partners.
As part of the Office of the CTO, research is a core part of the job. You will explore threats, designs and technologies before customers ask for them, prototype ideas that may not ship, and challenge established practice when a better approach exists. Your work will shape where k0rdent AI goes next, not only how it is deployed today.
This role combines research with hands-on, outward-facing work. You will split your time between exploring new designs, writing architecture, building and validating it in the lab, and explaining it to engineers, security teams, executives and conference audiences. You will work with Solutions Architects, Partner Management and Engineering colleagues across many countries and time zones.
Key Responsibilities
Reference architecture
• Design and publish security reference architectures and solution designs for k0rdent AI, covering single-tenant private AI clouds, multi-tenant GPU clouds and hybrid deployments that span public cloud and on-premises infrastructure.
• Define a defence-in-depth model across the stack, from hardware root of trust and firmware to hosts, virtual machines, Kubernetes, networks, storage, models and applications.
• Define tenant isolation boundaries and their guarantees, and document where each boundary is strong, where it is weak, and what it costs to strengthen.
• Map designs to the controls and frameworks customers must meet, and document trade-offs (risk, cost, performance, operability) with defensible reasoning a customer can follow.
Platform and infrastructure security
• Bare-metal and host security: secure and measured boot, TPM-based attestation, BMC and Redfish hardening, firmware integrity, and hardened Linux hosts.
• Virtual machine security: hypervisor and KubeVirt hardening, VM isolation, and the security implications of PCI passthrough and SR-IOV for GPUs and NICs.
• Kubernetes security: RBAC, Pod Security Standards, admission control and policy-as-code, runtime security, and secure multi-cluster and multi-tenant operation.
• Secrets management: secret stores, KMS and HSM integration, envelope encryption, secret delivery to workloads, and rotation.
• Certificates and PKI: internal certificate authorities, automated issuance and rotation, mTLS between services, and workload identity.
• Network security: segmentation and zero-trust designs, Kubernetes network policy, tenant isolation on front-end and GPU fabrics, and DPU-based security enforcement.
• Storage security: encryption at rest and in transit, key management, and tenant isolation on shared block, file and object storage used for training data and model weights.
• Public cloud security: secure landing zones, identity and access management, and network controls on major public clouds, and how they extend to hybrid deployments.
AI model and application security
• Define how Transformer-based models are protected through their lifecycle: provenance and signing of model weights, integrity of training and fine-tuning data, and secure model registries.
Apply on company site ↗