Senior Software Engineer – BMaaS & Datacenter Networking
Mirantis · United States · 1 mo ago
RemoteRemoteDistributionFull-time
We need to output HTML fragment with sections: About the role? Actually we have sections: About the Team, Role Overview, Core Responsibilities, Qualifications (Technical Qualifications, Universal Requirements, Educational & Experience Baseline), Additional Information (benefits). Also maybe "About the role" not present; we have "About the Team". Use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting and extract content.
Let's extract sections:
- About the Team: paragraph(s) describing team.
- Role Overview: paragraph(s) describing role.
- Core Responsibilities: list of bullet points (Control Plane Development, Architecture & API Design, Network Integration, Observability & Diagnostics, Quality & Engineering Excellence). Each bullet may have sub-bullets? The posting lists each with colon then description. We'll treat each as
- with description.
- Qualifications: This includes Technical Qualifications (list of sub-items), Universal Requirements (list), Educational & Experience Baseline (list). Could combine under Qualifications heading with subheadings? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications
and inside we can have maybe subheadings? But they didn't say we cannot use other headings; but they said use for section headings (list). Probably we should stick to those headings only. Could we have nested ? Not specified. Safer to just have one Qualifications section and put all qualification content as lists under it, maybe with
introducing subcategories? But we need to preserve all substantive info; we can include paragraphs describing each subcategory.
We could do:
Qualifications
Technical Qualifications
... etc.
But using is okay; not prohibited. The instruction only about headings and lists. Using for emphasis is fine.
Similarly for Universal Requirements and Educational & Experience Baseline.
- Additional Information: benefits etc. This could be under Benefits
(since they mention benefits). The posting includes "What does Mirantis offer you?" with bullet-like sentences separated by semicolons. We'll convert to - .
Also maybe we could have a section "About the Team" as heading? Not in the list but we can still use
About the Team
because they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. is examples, not exclusive. So we can use About the Team.
Similarly Role Overview could be under Role Overview
(maybe they'd expect About the role). But we can use Role Overview.
Core Responsibilities -> Responsibilities
.
Qualifications -> Qualifications
.
Benefits -> Benefits
.
We should not include Pay or Schedule as not present.
Now extract content.
About the Team paragraph:
"Mirantis, an IREN company, is the Kubernetes-native AI infrastructure company, enabling organizations to build and operate scalable, secure, and sovereign infrastructure for modern AI, machine learning, and data-intensive applications. By combining open source innovation with deep expertise in Kubernetes orchestration, Mirantis empowers platform engineering teams to deliver composable, production-ready developer platforms across any environment—on-premises, in the cloud, at the edge, or in sovereign data centers. As enterprises navigate the growing complexity of AI-driven workloads, Mirantis delivers the automation, GPU orchestration, and policy-driven control needed to manage infrastructure with confidence and agility. Committed to open standards and freedom from lock-in, Mirantis ensures that customers retain full control of their infrastructure strategy."
That's the intro before Job Description. Actually that's company description; but it's part of About the Team? The posting says "About the Team" then paragraph: "Our engineering team builds next-generation, cloud-native bare-metal orchestration platforms for AI neo-cloud environments. We operate on a T-shaped engineering model: while each engineer brings deep expertise in a primary domain, every team member maintains practical fluency across neighboring systems. This shared foundation enables rigorous design reviews, effective cross-domain code reviews, and dependable on-call coverage. Our development is fundamentally based on open-source projects, and contributing to them is a major part of our work. We develop primary control plane software in Rust and Go, leverage Kubernetes operators, and foster an OpenTelemetry-first operational culture."
Thus we have two paragraphs: company overview (maybe not part of About the Team) but we can include it as part of About the Team? The instruction: preserve ALL substantive information. So we should include both. Could treat first paragraph as part of About the Team (company description) then second paragraph as team specifics. We'll combine them under About the Team heading.
Role Overview paragraph:
"We are seeking a Senior Software Engineer who combines strong software architecture principles with deep technical domain expertise in Datacenter Networking and DPU architectures. Fitting into our T-shaped engineering model, you will drive the development of control planes powering high-density, high-throughput infrastructure for AI training and inference workloads. Familiarity with automated bare-metal provisioning and lifecycle management is a strong asset."
Core Responsibilities bullets:
- Control Plane Development: Design, build, and maintain production-grade control plane microservices, custom Kubernetes operators, and robust reconciliation engines in Rust and Go.
- Architecture & API Design: Author clear Functional (FR) and Non-Functional Requirements (NFR), architectural specs, system sequence diagrams, and clean gRPC/Protobuf and REST API schemas.
- Network Integration: Develop custom integration modules and integrations for modern network operating systems (SONiC, NVUE, Cumulus) and DPU hardware platforms.
- Observability & Diagnostics: Instrument services end-to-end using OpenTelemetry (OTel) traces and metrics, performing systematic root-cause analysis across polyglot distributed systems.
- Quality & Engineering Excellence: Participate in rigorous, review-gated pull request workflows across Rust, Go, and SQL codebases while ensuring high test coverage via mock-driven testing.
Qualifications:
Technical Qualifications list:
- Language Proficiency: Primary mastery of Rust (Tokio async runtime, Tonic, Axum, sqlx) and strong proficiency in Go.
- Data & APIs: Advanced SQL / PostgreSQL fluency, gRPC/Protobuf contract design, and schema evolution.
- Concurrency & Reliability: Strong background in async concurrency models, lock-free patterns, distributed state handling, and mock-driven testing discipline.
- Datacenter Protocols & OS: Expertise in BGP, MP-BGP, EVPN, VXLAN, L3VNI, route targets, and route server design. Hands-on experience with SONiC, Cumulus Linux, and NVUE (featuring a first-class NVUE client).
- DPU & Fabric Ecosystem: Deep knowledge of NVIDIA DOCA, Host-Based Networking (HBN), BlueField DPU architectures, and the DPF (DOCA Platform Framework) operator model (BFB, DPUSet, DPUNode CRDs).
- High-Performance Interconnects: Understanding of InfiniBand fabrics, NVLink / NMX-M partitioning, and RoCEv2.
- Linux Kernel Networking: Advanced grasp of Linux netlink, network namespaces, routing tables, and internal DHCP/DNS service implementations (the project ships its own services).
- Cloud & Kubernetes Networking: Familiarity with CNI plugins (Calico, Cilium). OVS and DPDK experience is a plus.
- Provisioning & Boot Infrastructure: Expertise in PXE/iPXE, UEFI, Secure Boot, measured boot, and TPM attestation.
- Hardware Management: Proficiency in Redfish, IPMI, and BMC abstractions across heterogeneous hardware platforms (Dell, Lenovo, NVIDIA reference hardware).
- Linux Systems Internals: In-depth knowledge of boot chains, systemd, initramfs, BIOS configuration matrices.
- Identity & Security: Practical experience with PKI, X.509 certificates, TLS, SPIFFE/SVID, Vault, KMS, Keycloak (OAuth2/JWT), and RBAC.
- Virtualization: Experience with KubeVirt / KVM.
- Kubernetes Control Planes: Experience writing custom controllers/operators using kube-rs or controller-runtime with CRD-driven reconciliation loop patterns.
Universal Requirements:
- Testing Discipline: Commitment to test-driven design, writing highly testable code with mock interfaces for external hardware and network dependencies.
- Collaborative Architecture: Proven track record of writing crisp architectural specs and engaging in constructive, cross-functional design reviews.
Educational & Experience Baseline:
- Bachelor’s or Master’s degree in Computer Science, Computer Engineering, or equivalent practical experience.
- 5+ years of software engineering experience in cloud-native platforms, systems programming, networking, or infrastructure automation.
- Demonstrated participation or maintainership in open-source systems projects is a plus.
Additional Information (Benefits):
"What does Mirantis offer you? Work with an established Silicon Valley leader in the cloud infrastructure industry;Work with exceptionally passionate, talented and engaging colleagues, helping Fortune 500 and Global 2000 customers implement next-generation cloud technologies;Be a part of cutting-edge, open-source innovation;Thrive in the high-energy environment of a young company where openness, collaboration, risk-taking, and continuous growth are valued;Professional development and training;Attend conferences and working groups;Company outings, happy hours, hackathons, and tech talks;Receive a competitive compensation package with a strong benefits plan. We are a Leader for Container Management in G2 (#2 after AWS)!"
We need to split by semicolons into list items.
Let's list:
- Work with an established Silicon Valley leader in the cloud infrastructure industry
- Work with exceptionally passionate, talented and engaging colleagues, helping Fortune 500 and Global 2000 customers implement next-generation cloud technologies
- Be a part of cutting-edge, open-source innovation
- Thrive in the high-energy environment of a young company where openness, collaboration, risk-taking, and continuous growth are valued
- Professional development and training
- Attend conferences and working groups
- Company outings, happy hours, hackathons, and tech talks
- Receive a competitive compensation package with a strong benefits plan
- We are a Leader for Container Management in G2 (#2 after AWS)
Now produce HTML.
We'll wrap each section in heading then content.
For lists, use - .
For prose, use
.
We need to avoid repeating job title; we aren't.
We must not include any boilerplate like cookie/navigation/legal/EEO etc. Not present.
Now craft final HTML.
Let's produce:
About the Team
Mirantis, an IREN company, is the Kubernetes-native AI infrastructure company, enabling organizations to build and operate scalable, secure, and sovereign infrastructure for modern AI, machine learning, and data-intensive applications. By combining open source innovation with deep expertise in Kubernetes orchestration, Mirantis empowers platform engineering teams to deliver composable, production-ready developer platforms across any environment—on-premises, in the cloud, at the edge, or in sovereign data centers. As enterprises navigate the growing complexity of AI-driven workloads, Mirantis delivers the automation, GPU orchestration, and policy-driven control needed to manage infrastructure with confidence and agility. Committed to open standards and freedom from lock-in, Mirantis ensures that customers retain full control of their infrastructure strategy.
Our engineering team builds next-generation, cloud-native bare-metal orchestration platforms for AI neo-cloud environments. We operate on a T-shaped engineering model: while each engineer brings deep expertise in a primary domain, every team member maintains practical
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting and extract content. Let's extract sections: - About the Team: paragraph(s) describing team. - Role Overview: paragraph(s) describing role. - Core Responsibilities: list of bullet points (Control Plane Development, Architecture & API Design, Network Integration, Observability & Diagnostics, Quality & Engineering Excellence). Each bullet may have sub-bullets? The posting lists each with colon then description. We'll treat each as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications
and inside we can have maybe subheadings? But they didn't say we cannot use other headings; but they said use for section headings (list). Probably we should stick to those headings only. Could we have nested ? Not specified. Safer to just have one Qualifications section and put all qualification content as lists under it, maybe with
? Not specified. Safer to just have one Qualifications section and put all qualification content as lists under it, maybe with
introducing subcategories? But we need to preserve all substantive info; we can include paragraphs describing each subcategory. We could do:
Qualifications
Technical Qualifications
- ... etc.
But using is okay; not prohibited. The instruction only about headings and lists. Using for emphasis is fine.
Similarly for Universal Requirements and Educational & Experience Baseline.
- Additional Information: benefits etc. This could be under
- .
Also maybe we could have a section "About the Team" as heading? Not in the list but we can still use
About the Team
because they said usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. is examples, not exclusive. So we can use About the Team. Similarly Role Overview could be under
Role Overview
(maybe they'd expect About the role). But we can use Role Overview. Core Responsibilities ->Responsibilities
. Qualifications ->Qualifications
. Benefits ->Benefits
. We should not include Pay or Schedule as not present. Now extract content. About the Team paragraph: "Mirantis, an IREN company, is the Kubernetes-native AI infrastructure company, enabling organizations to build and operate scalable, secure, and sovereign infrastructure for modern AI, machine learning, and data-intensive applications. By combining open source innovation with deep expertise in Kubernetes orchestration, Mirantis empowers platform engineering teams to deliver composable, production-ready developer platforms across any environment—on-premises, in the cloud, at the edge, or in sovereign data centers. As enterprises navigate the growing complexity of AI-driven workloads, Mirantis delivers the automation, GPU orchestration, and policy-driven control needed to manage infrastructure with confidence and agility. Committed to open standards and freedom from lock-in, Mirantis ensures that customers retain full control of their infrastructure strategy." That's the intro before Job Description. Actually that's company description; but it's part of About the Team? The posting says "About the Team" then paragraph: "Our engineering team builds next-generation, cloud-native bare-metal orchestration platforms for AI neo-cloud environments. We operate on a T-shaped engineering model: while each engineer brings deep expertise in a primary domain, every team member maintains practical fluency across neighboring systems. This shared foundation enables rigorous design reviews, effective cross-domain code reviews, and dependable on-call coverage. Our development is fundamentally based on open-source projects, and contributing to them is a major part of our work. We develop primary control plane software in Rust and Go, leverage Kubernetes operators, and foster an OpenTelemetry-first operational culture." Thus we have two paragraphs: company overview (maybe not part of About the Team) but we can include it as part of About the Team? The instruction: preserve ALL substantive information. So we should include both. Could treat first paragraph as part of About the Team (company description) then second paragraph as team specifics. We'll combine them under About the Team heading. Role Overview paragraph: "We are seeking a Senior Software Engineer who combines strong software architecture principles with deep technical domain expertise in Datacenter Networking and DPU architectures. Fitting into our T-shaped engineering model, you will drive the development of control planes powering high-density, high-throughput infrastructure for AI training and inference workloads. Familiarity with automated bare-metal provisioning and lifecycle management is a strong asset." Core Responsibilities bullets: - Control Plane Development: Design, build, and maintain production-grade control plane microservices, custom Kubernetes operators, and robust reconciliation engines in Rust and Go. - Architecture & API Design: Author clear Functional (FR) and Non-Functional Requirements (NFR), architectural specs, system sequence diagrams, and clean gRPC/Protobuf and REST API schemas. - Network Integration: Develop custom integration modules and integrations for modern network operating systems (SONiC, NVUE, Cumulus) and DPU hardware platforms. - Observability & Diagnostics: Instrument services end-to-end using OpenTelemetry (OTel) traces and metrics, performing systematic root-cause analysis across polyglot distributed systems. - Quality & Engineering Excellence: Participate in rigorous, review-gated pull request workflows across Rust, Go, and SQL codebases while ensuring high test coverage via mock-driven testing. Qualifications: Technical Qualifications list: - Language Proficiency: Primary mastery of Rust (Tokio async runtime, Tonic, Axum, sqlx) and strong proficiency in Go. - Data & APIs: Advanced SQL / PostgreSQL fluency, gRPC/Protobuf contract design, and schema evolution. - Concurrency & Reliability: Strong background in async concurrency models, lock-free patterns, distributed state handling, and mock-driven testing discipline. - Datacenter Protocols & OS: Expertise in BGP, MP-BGP, EVPN, VXLAN, L3VNI, route targets, and route server design. Hands-on experience with SONiC, Cumulus Linux, and NVUE (featuring a first-class NVUE client). - DPU & Fabric Ecosystem: Deep knowledge of NVIDIA DOCA, Host-Based Networking (HBN), BlueField DPU architectures, and the DPF (DOCA Platform Framework) operator model (BFB, DPUSet, DPUNode CRDs). - High-Performance Interconnects: Understanding of InfiniBand fabrics, NVLink / NMX-M partitioning, and RoCEv2. - Linux Kernel Networking: Advanced grasp of Linux netlink, network namespaces, routing tables, and internal DHCP/DNS service implementations (the project ships its own services). - Cloud & Kubernetes Networking: Familiarity with CNI plugins (Calico, Cilium). OVS and DPDK experience is a plus. - Provisioning & Boot Infrastructure: Expertise in PXE/iPXE, UEFI, Secure Boot, measured boot, and TPM attestation. - Hardware Management: Proficiency in Redfish, IPMI, and BMC abstractions across heterogeneous hardware platforms (Dell, Lenovo, NVIDIA reference hardware). - Linux Systems Internals: In-depth knowledge of boot chains, systemd, initramfs, BIOS configuration matrices. - Identity & Security: Practical experience with PKI, X.509 certificates, TLS, SPIFFE/SVID, Vault, KMS, Keycloak (OAuth2/JWT), and RBAC. - Virtualization: Experience with KubeVirt / KVM. - Kubernetes Control Planes: Experience writing custom controllers/operators using kube-rs or controller-runtime with CRD-driven reconciliation loop patterns. Universal Requirements: - Testing Discipline: Commitment to test-driven design, writing highly testable code with mock interfaces for external hardware and network dependencies. - Collaborative Architecture: Proven track record of writing crisp architectural specs and engaging in constructive, cross-functional design reviews. Educational & Experience Baseline: - Bachelor’s or Master’s degree in Computer Science, Computer Engineering, or equivalent practical experience. - 5+ years of software engineering experience in cloud-native platforms, systems programming, networking, or infrastructure automation. - Demonstrated participation or maintainership in open-source systems projects is a plus. Additional Information (Benefits): "What does Mirantis offer you? Work with an established Silicon Valley leader in the cloud infrastructure industry;Work with exceptionally passionate, talented and engaging colleagues, helping Fortune 500 and Global 2000 customers implement next-generation cloud technologies;Be a part of cutting-edge, open-source innovation;Thrive in the high-energy environment of a young company where openness, collaboration, risk-taking, and continuous growth are valued;Professional development and training;Attend conferences and working groups;Company outings, happy hours, hackathons, and tech talks;Receive a competitive compensation package with a strong benefits plan. We are a Leader for Container Management in G2 (#2 after AWS)!" We need to split by semicolons into list items. Let's list: - Work with an established Silicon Valley leader in the cloud infrastructure industry - Work with exceptionally passionate, talented and engaging colleagues, helping Fortune 500 and Global 2000 customers implement next-generation cloud technologies - Be a part of cutting-edge, open-source innovation - Thrive in the high-energy environment of a young company where openness, collaboration, risk-taking, and continuous growth are valued - Professional development and training - Attend conferences and working groups - Company outings, happy hours, hackathons, and tech talks - Receive a competitive compensation package with a strong benefits plan - We are a Leader for Container Management in G2 (#2 after AWS) Now produce HTML. We'll wrap each section inheading then content. For lists, use
- .
For prose, use
. We need to avoid repeating job title; we aren't. We must not include any boilerplate like cookie/navigation/legal/EEO etc. Not present. Now craft final HTML. Let's produce:
About the Team
Mirantis, an IREN company, is the Kubernetes-native AI infrastructure company, enabling organizations to build and operate scalable, secure, and sovereign infrastructure for modern AI, machine learning, and data-intensive applications. By combining open source innovation with deep expertise in Kubernetes orchestration, Mirantis empowers platform engineering teams to deliver composable, production-ready developer platforms across any environment—on-premises, in the cloud, at the edge, or in sovereign data centers. As enterprises navigate the growing complexity of AI-driven workloads, Mirantis delivers the automation, GPU orchestration, and policy-driven control needed to manage infrastructure with confidence and agility. Committed to open standards and freedom from lock-in, Mirantis ensures that customers retain full control of their infrastructure strategy.
Our engineering team builds next-generation, cloud-native bare-metal orchestration platforms for AI neo-cloud environments. We operate on a T-shaped engineering model: while each engineer brings deep expertise in a primary domain, every team member maintains practical
- .
For prose, use