Software Engineer, GPU Infrastructure
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we must not repeat the job title as a heading. We need to map content to appropriate headings.
We need to decide which sections are present: About Fluidstack (company description) could be "About the role"? Actually "About the role" is typical heading for role description. But we have "About Fluidstack" which is company overview. Could map to "About the role"? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings if appropriate. We should not invent sections without content. We have content for: About Fluidstack (company mission), How We Operate (culture/values), The Production Engineering Team (team description/examples), Role Scope (responsibilities), What We're Looking For (requirements/qualifications/skills), Salary & Benefits (compensation and benefits). Also there is a compensation range at end.
We need to output only HTML fragment, no /. Use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not include boilerplate like EEO, application instructions, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should omit the EEO paragraph, the confirmation email instructions, etc. Also we should not include "Compensation Range: $208K - $269K" maybe as part of Pay section. The Salary & Benefits section already mentions competitive total compensation package, retirement, health, dental, vision, generous PTO, equity. We can also include the compensation range as part of Pay.
We need to decide headings: Could use "About the role" for About Fluidstack? Might be better to use "About the company" but not in list. The instruction says use those headings as examples, not strictly limited to them? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when applicable. For company description maybe "About the role" is not accurate but could be used for role overview. However we have a separate "Role Scope" which is responsibilities. So maybe we use "About the role" for the company mission and how we operate? Hmm.
Better: Use headings that match content: "About the role" could encompass the company description and how we operate? But we also have "Responsibilities" for role scope. "Requirements" or "Qualifications" for what we're looking for. "Skills" maybe for specific skills. "Benefits" for benefits. "Pay" for compensation range. "Schedule" maybe not present.
We need to avoid filler headings. So we should only include sections where we have real specific content.
Let's map:
- About the role: Could include "About Fluidstack" and "How We Operate" (mission, culture). That's substantive.
- Responsibilities: Role Scope (own compute fleet health, build metrics pipelines, etc.)
- Requirements: What We're Looking For (list of traits). Could also include "Qualifications" but we can combine.
- Skills: Maybe list specific technical skills: Go or Python, LLM APIs, MCP, agentic frameworks, Claude Code, Cursor, etc., plus bonus items.
- Benefits: Salary & Benefits (health, dental, vision, PTO, retirement, equity). Also maybe mention competitive total compensation.
- Pay: Compensation range $208K - $269K.
We should not include Schedule as not present.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like "Be a barrel. Full autonomy..." etc. That's part of How We Operate. We'll include that as prose under About the role.
We need to turn lists into - . For example, the bullet points under "How We Operate" are actually sentences separated by periods? The text: "Be a barrel. Full autonomy. Own things end to end, take on scope without being asked, no permission required to operate outside your core role.Insane urgency. We drive everything forward as fast as possible.Reason from first principles. Challenge every assumption. Zero analogy thinking, no egos, the best idea wins.Love of the game. The frontier of AI is the most interesting problem of our time. We put in long hours at high intensity to push the frontier forward.Build something that actually matters. If you're going to spend your time, spend it on something that matters to the world."
That's a series of statements separated by periods. We could treat each sentence as a list item? The instruction says use
- for any list of duties/requirements/benefits. This is a list of cultural values. Could be considered a list. We'll convert each sentence to
- . However we need to preserve the content exactly. Might be okay.
Similarly, under "The Production Engineering Team Examples of key exciting problems the team is working on" there are several bullet-like sentences separated by colons? Actually it's a paragraph with semicolons? Let's extract:
"Build the repair pipeline that keeps pace with a fleet of 10s to 100s of GWs: at our scale, a GPU failure isn't a ticket. It's a throughput problem. We're building the automation that takes a chip from fault detection through triage, RMA, and return to service without human intervention.Qualify every new GPU generation inside a 6-month build window: our platform covers burn-in, performance baselining, and NPI execution. It has to define "production-ready" before a site goes live, not after. New hardware gets certified at speeds unheard of in the industry.Migrate live compute at construction speed: we're converting clusters across production sites simultaneously, bringing new sites online, and making Kubernetes-orchestrated bare metal sustainable at the pace we're building – multiple GW annually.See and own the entire fleet in real time, at any scale: build the observability and orchestration layer that makes hyperscale AI compute actually operable. Debug, tune, and performance-test infrastructure that grows by another site every few months."
We could split each sentence after colon? Might be messy. Perhaps better to keep as prose
because it's not a clear list. The instruction says use
- for any list of duties/requirements/benefits. This is a list of examples; could be considered a list. But the sentences are long and contain internal punctuation. We could still make each example a
- . Let's do that.
Similarly, under Role Scope: list of responsibilities separated by periods: "Own compute fleet health end to end. Build the metrics pipelines, alerting, and unified health view that tell you the true state of every GPU in production — across Kubernetes-orchestrated workloads and bare metal, at scale.Turn deployment/repair into a pipeline, not a procedure. Build and own the automation that takes a compute failure from detection through triage, parts management, and return to service. No one-off scripts, no heroics.Design and expand the GPU qualification platform. Burn-in, performance baselining, and NPI execution for every new GPU generation. You define what "good" looks like before hardware goes into production.Own Redfish and BMC tooling. Firmware-level telemetry, log collection at fleet scale, and the low-level access layer that repair automation and health tooling depend on.Own end-to-end reliability, scalability, and operation of the compute fleet at-scale. Fluidstack is building one of the largest GPU fleets in the world and that can only be accomplished with aggressive automation, tooling, and incident discipline."
We can split each sentence into
- .
What We're Looking For: list of traits separated by periods: "You treat toil as a bug. Manual steps in a repair workflow are a backlog item, not a job description.You have an instinct for hardware. You're comfortable reasoning about failure modes at the firmware and silicon level, not just the software stack above it.You move toward ambiguity, not away from it. You walk into the fog, build the map, and explain it to everyone else.You learn at a steep slope. You reach real competence in an unfamiliar domain fast. We value this over existing expertise.You carry a pager without flinching. You run the incident, write the postmortem, fix the systemic cause, and move on.You're fluent with AI tooling. LLM APIs, MCP servers, and agentic frameworks, and you drive Claude Code, Cursor, or similar every day.You've shipped production automation that other teams depend on, and you're comfortable in any language using AI coding tools.Bonus: Hardware lifecycle management and RMA automation. BMC/Redfish or IPMI tooling. GPU qualification or burn-in frameworks. Workflow and orchestration engines (Temporal, Cadence). Metrics and alerting pipelines (Prometheus, Grafana). Go or Python..."
We can split each sentence into
- . Bonus items also list.
Salary & Benefits: "Competitive total compensation package (salary + equity).Retirement or pension plan, in line with local norms.Health, dental, and vision insurance.Generous PTO policy, in line with local norms. Total compensation may also include equity in the form of restricted stock units. We are committed to pay equity and transparency."
We can split into
- .
Pay: "Compensation Range: $208K - $269K". Could be a
.
Now we need to ensure we don't include boilerplate: EEO paragraph, confirmation email instructions, etc. Also we should not include "Fluidstack is an Equal Employment Opportunity Employer..." etc. Also not include "You will receive a confirmation email..." etc.
Also we should not duplicate lines.
Now produce HTML fragment:
About the role
... maybe combine About Fluidstack and How We Operate into prose? But we decided to make list for How We Operate. About Fluidstack is paragraph.
Thus:
About the role
About Fluidstack We exist to make humanity more free. For most of human history, you farmed or you starved. Technology gave people more time for the things they wanted to do, instead of things they had to do. Powerful AI will be the biggest lever for human choice we've ever built - but only if models are aligned with what humanity actually wants. There are groups building AI who don't share these goals. Whoever deploys frontier compute infrastructure fastest will decide whether AI expands human freedom or shrinks it. We're singularly focused on delivering 10 to 100s of GWs of compute faster than anyone else, rethinking every layer of the stack. We acquire power, design and build data centers, and operate them - with teams spanning hardware and software. Speed and scale are our key differentiators. Come be a part of building civilization-scale infrastructure for AI. We hire people who care deeply about this problem space. If that is you, please apply!
Then How We Operate as list:
How We Operate
- Be a barrel.
- Full autonomy.
- Own things end to end, take on scope without being asked, no permission required to operate outside your core role.
- Insane urgency.
- We drive everything forward as fast as possible.
- Reason from first principles.
- Challenge every assumption.
- Zero analogy thinking, no egos, the best idea wins.
- Love
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not include boilerplate like EEO, application instructions, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should omit the EEO paragraph, the confirmation email instructions, etc. Also we should not include "Compensation Range: $208K - $269K" maybe as part of Pay section. The Salary & Benefits section already mentions competitive total compensation package, retirement, health, dental, vision, generous PTO, equity. We can also include the compensation range as part of Pay.
We need to decide headings: Could use "About the role" for About Fluidstack? Might be better to use "About the company" but not in list. The instruction says use those headings as examples, not strictly limited to them? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when applicable. For company description maybe "About the role" is not accurate but could be used for role overview. However we have a separate "Role Scope" which is responsibilities. So maybe we use "About the role" for the company mission and how we operate? Hmm.
Better: Use headings that match content: "About the role" could encompass the company description and how we operate? But we also have "Responsibilities" for role scope. "Requirements" or "Qualifications" for what we're looking for. "Skills" maybe for specific skills. "Benefits" for benefits. "Pay" for compensation range. "Schedule" maybe not present.
We need to avoid filler headings. So we should only include sections where we have real specific content.
Let's map:
- About the role: Could include "About Fluidstack" and "How We Operate" (mission, culture). That's substantive.
- Responsibilities: Role Scope (own compute fleet health, build metrics pipelines, etc.)
- Requirements: What We're Looking For (list of traits). Could also include "Qualifications" but we can combine.
- Skills: Maybe list specific technical skills: Go or Python, LLM APIs, MCP, agentic frameworks, Claude Code, Cursor, etc., plus bonus items.
- Benefits: Salary & Benefits (health, dental, vision, PTO, retirement, equity). Also maybe mention competitive total compensation.
- Pay: Compensation range $208K - $269K.
We should not include Schedule as not present.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like "Be a barrel. Full autonomy..." etc. That's part of How We Operate. We'll include that as prose under About the role.
We need to turn lists into - . For example, the bullet points under "How We Operate" are actually sentences separated by periods? The text: "Be a barrel. Full autonomy. Own things end to end, take on scope without being asked, no permission required to operate outside your core role.Insane urgency. We drive everything forward as fast as possible.Reason from first principles. Challenge every assumption. Zero analogy thinking, no egos, the best idea wins.Love of the game. The frontier of AI is the most interesting problem of our time. We put in long hours at high intensity to push the frontier forward.Build something that actually matters. If you're going to spend your time, spend it on something that matters to the world."
That's a series of statements separated by periods. We could treat each sentence as a list item? The instruction says use
- for any list of duties/requirements/benefits. This is a list of cultural values. Could be considered a list. We'll convert each sentence to
- . However we need to preserve the content exactly. Might be okay.
Similarly, under "The Production Engineering Team Examples of key exciting problems the team is working on" there are several bullet-like sentences separated by colons? Actually it's a paragraph with semicolons? Let's extract:
"Build the repair pipeline that keeps pace with a fleet of 10s to 100s of GWs: at our scale, a GPU failure isn't a ticket. It's a throughput problem. We're building the automation that takes a chip from fault detection through triage, RMA, and return to service without human intervention.Qualify every new GPU generation inside a 6-month build window: our platform covers burn-in, performance baselining, and NPI execution. It has to define "production-ready" before a site goes live, not after. New hardware gets certified at speeds unheard of in the industry.Migrate live compute at construction speed: we're converting clusters across production sites simultaneously, bringing new sites online, and making Kubernetes-orchestrated bare metal sustainable at the pace we're building – multiple GW annually.See and own the entire fleet in real time, at any scale: build the observability and orchestration layer that makes hyperscale AI compute actually operable. Debug, tune, and performance-test infrastructure that grows by another site every few months."
We could split each sentence after colon? Might be messy. Perhaps better to keep as prose
because it's not a clear list. The instruction says use
- for any list of duties/requirements/benefits. This is a list of examples; could be considered a list. But the sentences are long and contain internal punctuation. We could still make each example a
- . Let's do that.
Similarly, under Role Scope: list of responsibilities separated by periods: "Own compute fleet health end to end. Build the metrics pipelines, alerting, and unified health view that tell you the true state of every GPU in production — across Kubernetes-orchestrated workloads and bare metal, at scale.Turn deployment/repair into a pipeline, not a procedure. Build and own the automation that takes a compute failure from detection through triage, parts management, and return to service. No one-off scripts, no heroics.Design and expand the GPU qualification platform. Burn-in, performance baselining, and NPI execution for every new GPU generation. You define what "good" looks like before hardware goes into production.Own Redfish and BMC tooling. Firmware-level telemetry, log collection at fleet scale, and the low-level access layer that repair automation and health tooling depend on.Own end-to-end reliability, scalability, and operation of the compute fleet at-scale. Fluidstack is building one of the largest GPU fleets in the world and that can only be accomplished with aggressive automation, tooling, and incident discipline."
We can split each sentence into
- .
What We're Looking For: list of traits separated by periods: "You treat toil as a bug. Manual steps in a repair workflow are a backlog item, not a job description.You have an instinct for hardware. You're comfortable reasoning about failure modes at the firmware and silicon level, not just the software stack above it.You move toward ambiguity, not away from it. You walk into the fog, build the map, and explain it to everyone else.You learn at a steep slope. You reach real competence in an unfamiliar domain fast. We value this over existing expertise.You carry a pager without flinching. You run the incident, write the postmortem, fix the systemic cause, and move on.You're fluent with AI tooling. LLM APIs, MCP servers, and agentic frameworks, and you drive Claude Code, Cursor, or similar every day.You've shipped production automation that other teams depend on, and you're comfortable in any language using AI coding tools.Bonus: Hardware lifecycle management and RMA automation. BMC/Redfish or IPMI tooling. GPU qualification or burn-in frameworks. Workflow and orchestration engines (Temporal, Cadence). Metrics and alerting pipelines (Prometheus, Grafana). Go or Python..."
We can split each sentence into
- . Bonus items also list.
Salary & Benefits: "Competitive total compensation package (salary + equity).Retirement or pension plan, in line with local norms.Health, dental, and vision insurance.Generous PTO policy, in line with local norms. Total compensation may also include equity in the form of restricted stock units. We are committed to pay equity and transparency."
We can split into
- .
Pay: "Compensation Range: $208K - $269K". Could be a
.
Now we need to ensure we don't include boilerplate: EEO paragraph, confirmation email instructions, etc. Also we should not include "Fluidstack is an Equal Employment Opportunity Employer..." etc. Also not include "You will receive a confirmation email..." etc.
Also we should not duplicate lines.
Now produce HTML fragment:
About the role
... maybe combine About Fluidstack and How We Operate into prose? But we decided to make list for How We Operate. About Fluidstack is paragraph.
Thus:
About the role
About Fluidstack We exist to make humanity more free. For most of human history, you farmed or you starved. Technology gave people more time for the things they wanted to do, instead of things they had to do. Powerful AI will be the biggest lever for human choice we've ever built - but only if models are aligned with what humanity actually wants. There are groups building AI who don't share these goals. Whoever deploys frontier compute infrastructure fastest will decide whether AI expands human freedom or shrinks it. We're singularly focused on delivering 10 to 100s of GWs of compute faster than anyone else, rethinking every layer of the stack. We acquire power, design and build data centers, and operate them - with teams spanning hardware and software. Speed and scale are our key differentiators. Come be a part of building civilization-scale infrastructure for AI. We hire people who care deeply about this problem space. If that is you, please apply!
Then How We Operate as list:
How We Operate
- Be a barrel.
- Full autonomy.
- Own things end to end, take on scope without being asked, no permission required to operate outside your core role.
- Insane urgency.
- We drive everything forward as fast as possible.
- Reason from first principles.
- Challenge every assumption.
- Zero analogy thinking, no egos, the best idea wins.
- Love
for prose. We must not include boilerplate like EEO, application instructions, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should omit the EEO paragraph, the confirmation email instructions, etc. Also we should not include "Compensation Range: $208K - $269K" maybe as part of Pay section. The Salary & Benefits section already mentions competitive total compensation package, retirement, health, dental, vision, generous PTO, equity. We can also include the compensation range as part of Pay. We need to decide headings: Could use "About the role" for About Fluidstack? Might be better to use "About the company" but not in list. The instruction says use those headings as examples, not strictly limited to them? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when applicable. For company description maybe "About the role" is not accurate but could be used for role overview. However we have a separate "Role Scope" which is responsibilities. So maybe we use "About the role" for the company mission and how we operate? Hmm.
Better: Use headings that match content: "About the role" could encompass the company description and how we operate? But we also have "Responsibilities" for role scope. "Requirements" or "Qualifications" for what we're looking for. "Skills" maybe for specific skills. "Benefits" for benefits. "Pay" for compensation range. "Schedule" maybe not present.
We need to avoid filler headings. So we should only include sections where we have real specific content.
Let's map:
- About the role: Could include "About Fluidstack" and "How We Operate" (mission, culture). That's substantive.
- Responsibilities: Role Scope (own compute fleet health, build metrics pipelines, etc.)
- Requirements: What We're Looking For (list of traits). Could also include "Qualifications" but we can combine.
- Skills: Maybe list specific technical skills: Go or Python, LLM APIs, MCP, agentic frameworks, Claude Code, Cursor, etc., plus bonus items.
- Benefits: Salary & Benefits (health, dental, vision, PTO, retirement, equity). Also maybe mention competitive total compensation.
- Pay: Compensation range $208K - $269K.
We should not include Schedule as not present.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like "Be a barrel. Full autonomy..." etc. That's part of How We Operate. We'll include that as prose under About the role.
We need to turn lists into - . For example, the bullet points under "How We Operate" are actually sentences separated by periods? The text: "Be a barrel. Full autonomy. Own things end to end, take on scope without being asked, no permission required to operate outside your core role.Insane urgency. We drive everything forward as fast as possible.Reason from first principles. Challenge every assumption. Zero analogy thinking, no egos, the best idea wins.Love of the game. The frontier of AI is the most interesting problem of our time. We put in long hours at high intensity to push the frontier forward.Build something that actually matters. If you're going to spend your time, spend it on something that matters to the world."
That's a series of statements separated by periods. We could treat each sentence as a list item? The instruction says use
- for any list of duties/requirements/benefits. This is a list of cultural values. Could be considered a list. We'll convert each sentence to
- . However we need to preserve the content exactly. Might be okay.
Similarly, under "The Production Engineering Team Examples of key exciting problems the team is working on" there are several bullet-like sentences separated by colons? Actually it's a paragraph with semicolons? Let's extract:
"Build the repair pipeline that keeps pace with a fleet of 10s to 100s of GWs: at our scale, a GPU failure isn't a ticket. It's a throughput problem. We're building the automation that takes a chip from fault detection through triage, RMA, and return to service without human intervention.Qualify every new GPU generation inside a 6-month build window: our platform covers burn-in, performance baselining, and NPI execution. It has to define "production-ready" before a site goes live, not after. New hardware gets certified at speeds unheard of in the industry.Migrate live compute at construction speed: we're converting clusters across production sites simultaneously, bringing new sites online, and making Kubernetes-orchestrated bare metal sustainable at the pace we're building – multiple GW annually.See and own the entire fleet in real time, at any scale: build the observability and orchestration layer that makes hyperscale AI compute actually operable. Debug, tune, and performance-test infrastructure that grows by another site every few months."
We could split each sentence after colon? Might be messy. Perhaps better to keep as prose
because it's not a clear list. The instruction says use
- for any list of duties/requirements/benefits. This is a list of examples; could be considered a list. But the sentences are long and contain internal punctuation. We could still make each example a
- . Let's do that.
Similarly, under Role Scope: list of responsibilities separated by periods: "Own compute fleet health end to end. Build the metrics pipelines, alerting, and unified health view that tell you the true state of every GPU in production — across Kubernetes-orchestrated workloads and bare metal, at scale.Turn deployment/repair into a pipeline, not a procedure. Build and own the automation that takes a compute failure from detection through triage, parts management, and return to service. No one-off scripts, no heroics.Design and expand the GPU qualification platform. Burn-in, performance baselining, and NPI execution for every new GPU generation. You define what "good" looks like before hardware goes into production.Own Redfish and BMC tooling. Firmware-level telemetry, log collection at fleet scale, and the low-level access layer that repair automation and health tooling depend on.Own end-to-end reliability, scalability, and operation of the compute fleet at-scale. Fluidstack is building one of the largest GPU fleets in the world and that can only be accomplished with aggressive automation, tooling, and incident discipline."
We can split each sentence into
- .
What We're Looking For: list of traits separated by periods: "You treat toil as a bug. Manual steps in a repair workflow are a backlog item, not a job description.You have an instinct for hardware. You're comfortable reasoning about failure modes at the firmware and silicon level, not just the software stack above it.You move toward ambiguity, not away from it. You walk into the fog, build the map, and explain it to everyone else.You learn at a steep slope. You reach real competence in an unfamiliar domain fast. We value this over existing expertise.You carry a pager without flinching. You run the incident, write the postmortem, fix the systemic cause, and move on.You're fluent with AI tooling. LLM APIs, MCP servers, and agentic frameworks, and you drive Claude Code, Cursor, or similar every day.You've shipped production automation that other teams depend on, and you're comfortable in any language using AI coding tools.Bonus: Hardware lifecycle management and RMA automation. BMC/Redfish or IPMI tooling. GPU qualification or burn-in frameworks. Workflow and orchestration engines (Temporal, Cadence). Metrics and alerting pipelines (Prometheus, Grafana). Go or Python..."
We can split each sentence into
- . Bonus items also list.
Salary & Benefits: "Competitive total compensation package (salary + equity).Retirement or pension plan, in line with local norms.Health, dental, and vision insurance.Generous PTO policy, in line with local norms. Total compensation may also include equity in the form of restricted stock units. We are committed to pay equity and transparency."
We can split into
- .
Pay: "Compensation Range: $208K - $269K". Could be a
.
Now we need to ensure we don't include boilerplate: EEO paragraph, confirmation email instructions, etc. Also we should not include "Fluidstack is an Equal Employment Opportunity Employer..." etc. Also not include "You will receive a confirmation email..." etc.
Also we should not duplicate lines.
Now produce HTML fragment:
About the role
... maybe combine About Fluidstack and How We Operate into prose? But we decided to make list for How We Operate. About Fluidstack is paragraph.
Thus:
About the role
About Fluidstack We exist to make humanity more free. For most of human history, you farmed or you starved. Technology gave people more time for the things they wanted to do, instead of things they had to do. Powerful AI will be the biggest lever for human choice we've ever built - but only if models are aligned with what humanity actually wants. There are groups building AI who don't share these goals. Whoever deploys frontier compute infrastructure fastest will decide whether AI expands human freedom or shrinks it. We're singularly focused on delivering 10 to 100s of GWs of compute faster than anyone else, rethinking every layer of the stack. We acquire power, design and build data centers, and operate them - with teams spanning hardware and software. Speed and scale are our key differentiators. Come be a part of building civilization-scale infrastructure for AI. We hire people who care deeply about this problem space. If that is you, please apply!
Then How We Operate as list:
How We Operate
- Be a barrel.
- Full autonomy.
- Own things end to end, take on scope without being asked, no permission required to operate outside your core role.
- Insane urgency.
- We drive everything forward as fast as possible.
- Reason from first principles.
- Challenge every assumption.
- Zero analogy thinking, no egos, the best idea wins.
- Love
- for any list of duties/requirements/benefits. This is a list of cultural values. Could be considered a list. We'll convert each sentence to
- . However we need to preserve the content exactly. Might be okay.
Similarly, under "The Production Engineering Team Examples of key exciting problems the team is working on" there are several bullet-like sentences separated by colons? Actually it's a paragraph with semicolons? Let's extract:
"Build the repair pipeline that keeps pace with a fleet of 10s to 100s of GWs: at our scale, a GPU failure isn't a ticket. It's a throughput problem. We're building the automation that takes a chip from fault detection through triage, RMA, and return to service without human intervention.Qualify every new GPU generation inside a 6-month build window: our platform covers burn-in, performance baselining, and NPI execution. It has to define "production-ready" before a site goes live, not after. New hardware gets certified at speeds unheard of in the industry.Migrate live compute at construction speed: we're converting clusters across production sites simultaneously, bringing new sites online, and making Kubernetes-orchestrated bare metal sustainable at the pace we're building – multiple GW annually.See and own the entire fleet in real time, at any scale: build the observability and orchestration layer that makes hyperscale AI compute actually operable. Debug, tune, and performance-test infrastructure that grows by another site every few months."
We could split each sentence after colon? Might be messy. Perhaps better to keep as prose
because it's not a clear list. The instruction says use
- for any list of duties/requirements/benefits. This is a list of examples; could be considered a list. But the sentences are long and contain internal punctuation. We could still make each example a
- . Let's do that. Similarly, under Role Scope: list of responsibilities separated by periods: "Own compute fleet health end to end. Build the metrics pipelines, alerting, and unified health view that tell you the true state of every GPU in production — across Kubernetes-orchestrated workloads and bare metal, at scale.Turn deployment/repair into a pipeline, not a procedure. Build and own the automation that takes a compute failure from detection through triage, parts management, and return to service. No one-off scripts, no heroics.Design and expand the GPU qualification platform. Burn-in, performance baselining, and NPI execution for every new GPU generation. You define what "good" looks like before hardware goes into production.Own Redfish and BMC tooling. Firmware-level telemetry, log collection at fleet scale, and the low-level access layer that repair automation and health tooling depend on.Own end-to-end reliability, scalability, and operation of the compute fleet at-scale. Fluidstack is building one of the largest GPU fleets in the world and that can only be accomplished with aggressive automation, tooling, and incident discipline." We can split each sentence into
- . What We're Looking For: list of traits separated by periods: "You treat toil as a bug. Manual steps in a repair workflow are a backlog item, not a job description.You have an instinct for hardware. You're comfortable reasoning about failure modes at the firmware and silicon level, not just the software stack above it.You move toward ambiguity, not away from it. You walk into the fog, build the map, and explain it to everyone else.You learn at a steep slope. You reach real competence in an unfamiliar domain fast. We value this over existing expertise.You carry a pager without flinching. You run the incident, write the postmortem, fix the systemic cause, and move on.You're fluent with AI tooling. LLM APIs, MCP servers, and agentic frameworks, and you drive Claude Code, Cursor, or similar every day.You've shipped production automation that other teams depend on, and you're comfortable in any language using AI coding tools.Bonus: Hardware lifecycle management and RMA automation. BMC/Redfish or IPMI tooling. GPU qualification or burn-in frameworks. Workflow and orchestration engines (Temporal, Cadence). Metrics and alerting pipelines (Prometheus, Grafana). Go or Python..." We can split each sentence into
- . Bonus items also list. Salary & Benefits: "Competitive total compensation package (salary + equity).Retirement or pension plan, in line with local norms.Health, dental, and vision insurance.Generous PTO policy, in line with local norms. Total compensation may also include equity in the form of restricted stock units. We are committed to pay equity and transparency." We can split into
- .
Pay: "Compensation Range: $208K - $269K". Could be a
. Now we need to ensure we don't include boilerplate: EEO paragraph, confirmation email instructions, etc. Also we should not include "Fluidstack is an Equal Employment Opportunity Employer..." etc. Also not include "You will receive a confirmation email..." etc. Also we should not duplicate lines. Now produce HTML fragment:
About the role
... maybe combine About Fluidstack and How We Operate into prose? But we decided to make list for How We Operate. About Fluidstack is paragraph. Thus:
About the role
About Fluidstack We exist to make humanity more free. For most of human history, you farmed or you starved. Technology gave people more time for the things they wanted to do, instead of things they had to do. Powerful AI will be the biggest lever for human choice we've ever built - but only if models are aligned with what humanity actually wants. There are groups building AI who don't share these goals. Whoever deploys frontier compute infrastructure fastest will decide whether AI expands human freedom or shrinks it. We're singularly focused on delivering 10 to 100s of GWs of compute faster than anyone else, rethinking every layer of the stack. We acquire power, design and build data centers, and operate them - with teams spanning hardware and software. Speed and scale are our key differentiators. Come be a part of building civilization-scale infrastructure for AI. We hire people who care deeply about this problem space. If that is you, please apply!
Then How We Operate as list:How We Operate
- Be a barrel.
- Full autonomy.
- Own things end to end, take on scope without being asked, no permission required to operate outside your core role.
- Insane urgency.
- We drive everything forward as fast as possible.
- Reason from first principles.
- Challenge every assumption.
- Zero analogy thinking, no egos, the best idea wins.
- Love