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 networking expertise to join the Voyager team in the Mirantis Office of the CTO. You will own the network solutioning of k0rdent AI, our platform for building and operating GPU clouds and AI factories, from metal to model.
You will design how large GPU clusters are interconnected, how tenants are isolated, and how workloads reach the network from containers, virtual machines and bare metal nodes. 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 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, 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 network reference architectures and solution designs for k0rdent AI, covering data center topologies from a single rack to multi-thousand-GPU clusters.
• Define compute (east-west) fabrics on InfiniBand and on RoCEv2 Ethernet, including rail-optimised and fat-tree / Clos designs, oversubscription and failure-domain choices.
• Define front-end, storage and management networks, and how they connect to customer data centers, public clouds and hybrid environments.
• Specify multi-tenant isolation across the stack: InfiniBand partitions (PKeys), VRFs and EVPN-VXLAN on Ethernet, and Kubernetes-level network policy.
• Document scale limits and trade-offs (cost, performance, operability, vendor lock-in) with defensible reasoning a customer can follow.
Host and platform networking
• Define how Linux hosts expose NICs, DPUs and SuperNICs to workloads: PCI passthrough, SR-IOV virtual functions, IOMMU groups, NUMA and GPU-NIC affinity.
• Design Kubernetes networking for AI workloads: primary and secondary CNIs, Multus, SR-IOV and RDMA device plugins, NVIDIA Network Operator, and Dynamic Resource Allocation (DRA).
• Design networking for virtual machines on KubeVirt, including passthrough and SR-IOV for GPU and RDMA traffic.
Research and exploration
• Track and evaluate emerging technologies and standards in AI networking, such as Ultra Ethernet (UEC), SuperNIC and DPU offloads, scale-up and scale-across fabrics, and Kubernetes DRA network drivers.
• Prototype alternative designs in the lab, including ones customers have not yet asked for, and measure them against current practice.
• Challenge established or customer-preferred designs when evidence points to a better option, and make the case with data.
• Publish findings as internal research notes and design proposals and, where appropriate, as external papers, blog posts or talks.
Code and proofs of concept
• Build and run proofs of concept with customers and partners, on Mirantis lab hardware and on customer sites, and report results against agreed success criteria.
• Write automation and tooling (Python, Go, Bash, Ansible, Helm, Kubernetes manifests, Terraform) that makes the reference architectures reproducible.
• Run validation and benchmarking of fabrics and host configurations (e.g. NCCL tests, perftest, ib_write_bw) and turn findings into design guidance.
Customers, partners and community
• Act
Apply on company site ↗