Member of Technical Staff - Bare Metal & Fleet Provisioning
for section headings, - for lists,
for prose.
We need to extract content.
Let's parse posting:
"Own Your Intelligence Prime Intellect is building the open superintelligence stack: the infrastructure frontier AI labs build internally, made available to every ambitious AI team. Our platform, Lab, unifies compute, environments, evaluations, secure sandboxes, high-performance training, and deployment into one full-stack system for post-training at frontier scale - from SFT and RL to tool use, agent workflows, and continuously improving production models. We are building open frontier AI: open-source models trained end to end for long-horizon tasks like autonomous research, and the full-stack platform our own research team uses to build them. The next generation of AI companies, enterprises, and research teams do not just need more GPUs. They need the ability to turn their own workflows, tools, data, and feedback loops into superintelligence they own. Prime Intellect has raised $150M in total funding from Founders Fund, Radical Ventures, NVIDIA, and exceptional AI, infrastructure, and enterprise operators — including Andrej Karpathy, Dwarkesh Patel, and leaders and founders from Ramp, Perplexity, Harvey, Mercor, Zapier, Datadog, Cognition, OpenAI, Thinking Machines, Together AI, SemiAnalysis, LangChain, Browserbase, Cloudflare, Sierra, Databricks, Airbnb, OpenRouter, Standard Intelligence, Fleet, Core Auto, and more. We are looking for people who want to build at the intersection of frontier research, real infrastructure, and go-to-market for a category that does not fully exist yet."
That's about the company and mission; could be "About the role"? Actually "Role Impact" section follows.
"Role Impact You'll build the systems that turn bare-metal GPU servers into reliable, production-ready compute. Own the machine lifecycle from discovery and provisioning through validation, upgrades, repair, and secure reuse, reducing manual work as our fleet grows."
That's about role impact; we can put under About the role.
"Core Technical Responsibilities Build automated discovery, network boot, OS imaging, and configuration workflows for GPU serversAutomate BIOS, BMC, NIC, GPU driver, and firmware configuration with staged rollouts and safe recovery pathsDevelop hardware inventory and lifecycle services that track machine identity, configuration, health, and readinessCreate acceptance tests and burn-in workflows for GPUs, memory, storage, and interconnects before capacity enters productionIntegrate provisioning and health checks with SLURM, Kubernetes, and compute allocation systemsBuild observability, quarantine, repair, and re-provisioning workflows; partner with datacenter teams to resolve hardware failuresImplement secure credential handling, tenant isolation, and data sanitization across the server lifecycle"
We need to split into list items.
"Technical Requirements Required Experience 3+ years of experience operating Linux servers or building bare-metal infrastructure automation in productionHands-on experience with PXE/iPXE, DHCP, image provisioning, and out-of-band management such as Redfish or IPMIStrong software engineering and debugging skills in Python, Go, or a comparable language, plus BashExperience designing reliable automation that handles partial failures, retries, and configuration driftAbility to own operational incidents and collaborate across hardware, networking, and platform teams"
"Infrastructure Skills Linux boot, systemd, kernel and driver troubleshooting, and OS image managementInfrastructure automation with tools such as Ansible and TerraformGPU server diagnostics, PCIe topology, BMC telemetry, and firmware compatibilityNetwork fundamentals including addressing, VLANs, DNS, and management networksMetrics, logs, alerting, and auditable configuration management"
"Nice to Have Experience with large NVIDIA GPU fleets, DGX/HGX platforms, or heterogeneous server vendorsExperience with MAAS, Ironic, Tinkerbell, or similar provisioning systemsKubernetes or SLURM node lifecycle integrationsHardware qualification, automated burn-in, and fleet health scoringContributions to open-source infrastructure tooling"
"Growth Opportunity You'll work directly with customers pushing the boundaries of AI, from startups training foundation models to enterprises deploying massive inference infrastructure. You'll collaborate with our world-class engineering team while having direct impact on systems powering the next generation of AI breakthroughs. We value expertise and customer obsession - if you're passionate about building reliable, high-performance GPU infrastructure and have a track record of successful large-scale deployments, we want to talk to you."
"Compensation Cash compensation range of $150,000–$300,000 plus equity incentives."
We need to output sections: About the role (maybe combine Role Impact and maybe some intro?), Responsibilities, Requirements, Skills, Pay. Possibly also include Nice to Have as part of Requirements? But we can keep as part of Requirements or separate? The instruction: Use sections only when posting has real specific content. Nice to Have is specific content; but we don't have a heading for Nice to Have in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Nice to Have could be folded into Requirements or Skills. Probably include under Requirements as a sublist? But we must not invent headings. Could add a
inside Requirements that mentions nice-to-have. Or we could create a separate section "Qualifications" for nice-to-have? But Qualifications is allowed heading. However the posting does not have a explicit "Qualifications" section; but we could treat Nice to Have as qualifications. But we must not create a section unless posting has real specific content for it. The posting does have Nice to Have content; we could map that to Qualifications heading. That seems acceptable: we have a Qualifications section with the nice-to-have items. Meanwhile Requirements section contains required experience.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay.
We must not include Benefits or Schedule.
Now we need to format.
We'll produce:
About the role
... (role impact paragraph)
Responsibilities
- Build automated discovery, network boot, OS imaging, and configuration workflows for GPU servers
- Automate BIOS, BMC, NIC, GPU driver, and firmware configuration with staged rollouts and safe recovery paths
- Develop hardware inventory and lifecycle services that track machine identity, configuration, health, and readiness
- Create acceptance tests and burn-in workflows for GPUs, memory, storage, and interconnects before capacity enters production
- Integrate provisioning and health checks with SLURM, Kubernetes, and compute allocation systems
- Build observability, quarantine, repair, and re-provisioning workflows; partner with datacenter teams to resolve hardware failures
- Implement secure credential handling, tenant isolation, and data sanitization across the server lifecycle
Requirements
- 3+ years of experience operating Linux servers or building bare-metal infrastructure automation in production
- Hands-on experience with PXE/iPXE, DHCP, image provisioning, and out-of-band management such as Redfish or IPMI
- Strong software engineering and debugging skills in Python, Go, or a comparable language, plus Bash
- Experience designing reliable automation that handles partial failures, retries, and configuration drift
- Ability to own operational incidents and collaborate across hardware, networking, and platform teams
Qualifications
- Experience with large NVIDIA GPU fleets, DGX/HGX platforms, or heterogeneous server vendors
- Experience with MAAS, Ironic, Tinkerbell, or similar provisioning systems
- Kubernetes or SLURM node lifecycle integrations
- Hardware qualification, automated burn-in, and fleet health scoring
- Contributions to open-source infrastructure tooling
Skills
- Linux boot, systemd, kernel and driver troubleshooting, and OS image management
- Infrastructure automation with tools such as Ansible and Terraform
- GPU server diagnostics, PCIe topology, BMC telemetry, and firmware compatibility
- Network fundamentals including addressing, VLANs, DNS, and management networks
- Metrics, logs, alerting, and auditable configuration management
Pay
Cash compensation range of $150,000–$300,000 plus equity incentives.
We need to ensure no extra fluff. Also we need to include the About the role paragraph: combine role impact and maybe the introductory company description? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." The About the role section should contain the role impact description. The initial company description could be considered "About the company" but not required. We could include it as part of About the role paragraph to preserve all substantive info. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the company overview as part of About the role? It's not about the role but about the company. However we have no other section for company info. Could we put it in About the role as a preamble? That would preserve it. The role impact paragraph is separate; we could combine both into one
or two
s. Probably better to have two
s under About the role: first the company overview, then the role impact. That preserves all.
Thus About the role: two paragraphs.
Let's craft:
Own Your Intelligence Prime Intellect is building the open superintelligence stack: the infrastructure frontier AI labs build internally, made available to every ambitious AI team. Our platform, Lab, unifies compute, environments, evaluations, secure sandboxes, high-performance training, and deployment into one full-stack system for post-training at frontier scale - from SFT and RL to tool use, agent workflows, and continuously improving production models. We are building open frontier AI: open-source models trained end to end for long-horizon tasks like autonomous research, and the full-stack platform our own research team uses to build them. The next generation of AI companies, enterprises, and research teams do not just need more GPUs. They need the ability to turn their own workflows, tools, data, and feedback loops into superintelligence they own. Prime Intellect has raised $150M in total funding from Founders Fund, Radical Ventures, NVIDIA, and exceptional AI, infrastructure, and enterprise operators — including Andrej Karpathy, Dwarkesh Patel, and leaders and founders from Ramp, Perplexity, Harvey, Mercor, Zapier, Datadog, Cognition, OpenAI, Thinking Machines, Together AI, SemiAnalysis, LangChain, Browserbase, Cloudflare, Sierra, Databricks, Airbnb, OpenRouter, Standard Intelligence
for prose. We need to extract content. Let's parse posting: "Own Your Intelligence Prime Intellect is building the open superintelligence stack: the infrastructure frontier AI labs build internally, made available to every ambitious AI team. Our platform, Lab, unifies compute, environments, evaluations, secure sandboxes, high-performance training, and deployment into one full-stack system for post-training at frontier scale - from SFT and RL to tool use, agent workflows, and continuously improving production models. We are building open frontier AI: open-source models trained end to end for long-horizon tasks like autonomous research, and the full-stack platform our own research team uses to build them. The next generation of AI companies, enterprises, and research teams do not just need more GPUs. They need the ability to turn their own workflows, tools, data, and feedback loops into superintelligence they own. Prime Intellect has raised $150M in total funding from Founders Fund, Radical Ventures, NVIDIA, and exceptional AI, infrastructure, and enterprise operators — including Andrej Karpathy, Dwarkesh Patel, and leaders and founders from Ramp, Perplexity, Harvey, Mercor, Zapier, Datadog, Cognition, OpenAI, Thinking Machines, Together AI, SemiAnalysis, LangChain, Browserbase, Cloudflare, Sierra, Databricks, Airbnb, OpenRouter, Standard Intelligence, Fleet, Core Auto, and more. We are looking for people who want to build at the intersection of frontier research, real infrastructure, and go-to-market for a category that does not fully exist yet." That's about the company and mission; could be "About the role"? Actually "Role Impact" section follows. "Role Impact You'll build the systems that turn bare-metal GPU servers into reliable, production-ready compute. Own the machine lifecycle from discovery and provisioning through validation, upgrades, repair, and secure reuse, reducing manual work as our fleet grows." That's about role impact; we can put under About the role. "Core Technical Responsibilities Build automated discovery, network boot, OS imaging, and configuration workflows for GPU serversAutomate BIOS, BMC, NIC, GPU driver, and firmware configuration with staged rollouts and safe recovery pathsDevelop hardware inventory and lifecycle services that track machine identity, configuration, health, and readinessCreate acceptance tests and burn-in workflows for GPUs, memory, storage, and interconnects before capacity enters productionIntegrate provisioning and health checks with SLURM, Kubernetes, and compute allocation systemsBuild observability, quarantine, repair, and re-provisioning workflows; partner with datacenter teams to resolve hardware failuresImplement secure credential handling, tenant isolation, and data sanitization across the server lifecycle" We need to split into list items. "Technical Requirements Required Experience 3+ years of experience operating Linux servers or building bare-metal infrastructure automation in productionHands-on experience with PXE/iPXE, DHCP, image provisioning, and out-of-band management such as Redfish or IPMIStrong software engineering and debugging skills in Python, Go, or a comparable language, plus BashExperience designing reliable automation that handles partial failures, retries, and configuration driftAbility to own operational incidents and collaborate across hardware, networking, and platform teams" "Infrastructure Skills Linux boot, systemd, kernel and driver troubleshooting, and OS image managementInfrastructure automation with tools such as Ansible and TerraformGPU server diagnostics, PCIe topology, BMC telemetry, and firmware compatibilityNetwork fundamentals including addressing, VLANs, DNS, and management networksMetrics, logs, alerting, and auditable configuration management" "Nice to Have Experience with large NVIDIA GPU fleets, DGX/HGX platforms, or heterogeneous server vendorsExperience with MAAS, Ironic, Tinkerbell, or similar provisioning systemsKubernetes or SLURM node lifecycle integrationsHardware qualification, automated burn-in, and fleet health scoringContributions to open-source infrastructure tooling" "Growth Opportunity You'll work directly with customers pushing the boundaries of AI, from startups training foundation models to enterprises deploying massive inference infrastructure. You'll collaborate with our world-class engineering team while having direct impact on systems powering the next generation of AI breakthroughs. We value expertise and customer obsession - if you're passionate about building reliable, high-performance GPU infrastructure and have a track record of successful large-scale deployments, we want to talk to you." "Compensation Cash compensation range of $150,000–$300,000 plus equity incentives." We need to output sections: About the role (maybe combine Role Impact and maybe some intro?), Responsibilities, Requirements, Skills, Pay. Possibly also include Nice to Have as part of Requirements? But we can keep as part of Requirements or separate? The instruction: Use sections only when posting has real specific content. Nice to Have is specific content; but we don't have a heading for Nice to Have in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Nice to Have could be folded into Requirements or Skills. Probably include under Requirements as a sublist? But we must not invent headings. Could add a
inside Requirements that mentions nice-to-have. Or we could create a separate section "Qualifications" for nice-to-have? But Qualifications is allowed heading. However the posting does not have a explicit "Qualifications" section; but we could treat Nice to Have as qualifications. But we must not create a section unless posting has real specific content for it. The posting does have Nice to Have content; we could map that to Qualifications heading. That seems acceptable: we have a Qualifications section with the nice-to-have items. Meanwhile Requirements section contains required experience. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. We must not include Benefits or Schedule. Now we need to format. We'll produce:
About the role
... (role impact paragraph)
Responsibilities
- Build automated discovery, network boot, OS imaging, and configuration workflows for GPU servers
- Automate BIOS, BMC, NIC, GPU driver, and firmware configuration with staged rollouts and safe recovery paths
- Develop hardware inventory and lifecycle services that track machine identity, configuration, health, and readiness
- Create acceptance tests and burn-in workflows for GPUs, memory, storage, and interconnects before capacity enters production
- Integrate provisioning and health checks with SLURM, Kubernetes, and compute allocation systems
- Build observability, quarantine, repair, and re-provisioning workflows; partner with datacenter teams to resolve hardware failures
- Implement secure credential handling, tenant isolation, and data sanitization across the server lifecycle
Requirements
- 3+ years of experience operating Linux servers or building bare-metal infrastructure automation in production
- Hands-on experience with PXE/iPXE, DHCP, image provisioning, and out-of-band management such as Redfish or IPMI
- Strong software engineering and debugging skills in Python, Go, or a comparable language, plus Bash
- Experience designing reliable automation that handles partial failures, retries, and configuration drift
- Ability to own operational incidents and collaborate across hardware, networking, and platform teams
Qualifications
- Experience with large NVIDIA GPU fleets, DGX/HGX platforms, or heterogeneous server vendors
- Experience with MAAS, Ironic, Tinkerbell, or similar provisioning systems
- Kubernetes or SLURM node lifecycle integrations
- Hardware qualification, automated burn-in, and fleet health scoring
- Contributions to open-source infrastructure tooling
Skills
- Linux boot, systemd, kernel and driver troubleshooting, and OS image management
- Infrastructure automation with tools such as Ansible and Terraform
- GPU server diagnostics, PCIe topology, BMC telemetry, and firmware compatibility
- Network fundamentals including addressing, VLANs, DNS, and management networks
- Metrics, logs, alerting, and auditable configuration management
Pay
Cash compensation range of $150,000–$300,000 plus equity incentives.
We need to ensure no extra fluff. Also we need to include the About the role paragraph: combine role impact and maybe the introductory company description? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." The About the role section should contain the role impact description. The initial company description could be considered "About the company" but not required. We could include it as part of About the role paragraph to preserve all substantive info. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the company overview as part of About the role? It's not about the role but about the company. However we have no other section for company info. Could we put it in About the role as a preamble? That would preserve it. The role impact paragraph is separate; we could combine both into one
or two
s. Probably better to have two
s under About the role: first the company overview, then the role impact. That preserves all. Thus About the role: two paragraphs. Let's craft:
Own Your Intelligence Prime Intellect is building the open superintelligence stack: the infrastructure frontier AI labs build internally, made available to every ambitious AI team. Our platform, Lab, unifies compute, environments, evaluations, secure sandboxes, high-performance training, and deployment into one full-stack system for post-training at frontier scale - from SFT and RL to tool use, agent workflows, and continuously improving production models. We are building open frontier AI: open-source models trained end to end for long-horizon tasks like autonomous research, and the full-stack platform our own research team uses to build them. The next generation of AI companies, enterprises, and research teams do not just need more GPUs. They need the ability to turn their own workflows, tools, data, and feedback loops into superintelligence they own. Prime Intellect has raised $150M in total funding from Founders Fund, Radical Ventures, NVIDIA, and exceptional AI, infrastructure, and enterprise operators — including Andrej Karpathy, Dwarkesh Patel, and leaders and founders from Ramp, Perplexity, Harvey, Mercor, Zapier, Datadog, Cognition, OpenAI, Thinking Machines, Together AI, SemiAnalysis, LangChain, Browserbase, Cloudflare, Sierra, Databricks, Airbnb, OpenRouter, Standard Intelligence