Software Engineer, AI Automation
Fluidstack · San Francisco, CA · 3 wk ago
On-siteInformation Technology$224k–$300k/yrContract
We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Fluidstack, How We Operate, The Decision Team, Role Scope, What We're Looking For, Benefits, Compensation Range. Also maybe "Compensation Range" is pay. Use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading (none given). Do NOT put Job ID / requisition numbers as headings (none). Remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, etc. Also remove navigation/cookie/legal. So we need to keep substantive info.
We need to decide which sections to include: About the role? The posting has "About Fluidstack" (company description). Could be considered "About the role"? But the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map sections accordingly. The posting includes:
- About Fluidstack (company mission) -> could be "About the role"? Actually "About the role" is typical heading for role description. But we have "About Fluidstack". Might be better to use "About the role" heading and put the Fluidstack description there? However instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can use those headings if they match content. We have content that fits "About the role" (description of company and mission). Could also have "How We Operate" maybe as "Responsibilities"? Not exactly. "The Decision Team" maybe as "Responsibilities"? Actually "Role Scope" is responsibilities. "What We're Looking For" is qualifications/requirements/skills. "Benefits" is benefits. "Compensation Range" is pay.
We should not create sections with filler. So we need to include sections only if there is real specific content.
Thus we can have:
About the role
with paragraph(s) about Fluidstack mission and maybe How We Operate? Actually How We Operate describes culture/operating principles; could be part of role description.
But we also have "Role Scope" which is a list of responsibilities (building hiring machine, cash view, capital pipeline, parsing contracts, embed forward-deployed). That's definitely responsibilities.
We have "What We're Looking For" which is a list of qualifications/skills.
We have "Benefits" list.
We have "Compensation Range" (pay).
We might also include "How We Operate" as a separate section maybe "Culture" but not in list; but we could incorporate into About the role or Responsibilities? Probably better to have a section "How we operate" as a heading? Not in the examples but we could still use for any section heading; the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use for section headings (e.g. those). Likely they expect us to use those standard headings where applicable. So we should map content to those headings.
Thus:
- About the role: include Fluidstack mission and maybe How We Operate? Could be separate but we can combine.
- Responsibilities: Role Scope bullet points.
- Requirements / Qualifications / Skills: What We're Looking For bullet points (some are requirements, some skills). Could split into Requirements and Skills but we can combine into one section "Requirements" or "Qualifications". The instruction says prefer a few substantive sections over many thin ones. So maybe one section "Qualifications" covering all.
- Benefits: list.
- Pay: compensation range.
We should not include Schedule (none). Also we should not include sections like "Responsibilities" if we don't have? We do have Role Scope.
Now we need to preserve all substantive information, not invent or summarize away detail. So we need to keep the bullet points exactly as given (or close). We must not omit details.
Let's extract content.
About Fluidstack paragraph:
"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!"
How We Operate paragraph:
"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 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."
The Decision Team paragraph:
"The Decision Team Examples of key problems the team is working on Automate the delivery of gigawatts. Every process that takes AI infrastructure from land to live compute becomes software: schedules, decisions, and todos generated from a live knowledge graph instead of chased by hand.Forward-deploy beside the experts. Product teams sit with quality managers, sourcing leads, and deployment engineers on factory floors and sites, and turn their judgment into systems that reach every unit.Deliver every supercomputer faster than the last. Dozens of concurrent projects feed one graph, so every lesson learned at one site becomes a preventive check at all of them."
Role Scope paragraph (multiple bullet-like sentences):
"Role Scope Build the hiring machine as software. Hiring is the company's biggest bottleneck. Every role, seat, and interview loop already lives in one graph, and you take it the rest of the way: the recruiting system synced both directions, interviewer supply and load visible to every hiring manager, and onboarding generated the moment an offer is signed, so day one starts with the job instead of the checklist.Build the cash view the company runs on: today no system derives near term spend, so finance forecasts by hand and misses what construction already committed. You turn purchase orders, contract terms, and build milestones into an order schedule, a cash demand curve by month, and a payment schedule that recompute as procurement and construction move.Build one capital pipeline from approved budget to released capital to spent dollar, gated on build milestones the delivery system already verifies, with the proof chain behind every financing drawdown assembled automatically, so releasing nine figures takes a day of judgment and funding follows construction within days.Parse every MSA, change order, and side letter into obligations, prices, deadlines, penalties, and SLAs, so a delivery lead gets what we owe a customer at a site with the clause attached, a change order arrives with its legal and finance checks done, and the corpus of executed deals prices the next negotiation.Embed forward-deployed with finance, treasury, accounting, legal, and people teams through a close, a drawdown, a negotiation, and a hiring loop, and turn their approvals, contract terms, screens, and reconciliations into structured data and generated work, including a continuous close where capitalization and depreciation post as events the moment they happen."
What We're Looking For bullet list (looks like sentences separated by periods but we can treat as list items):
"You've shipped production code in Go, Python, or TypeScript, and you pick up whatever language the problem demands.
You've built real features on LLM APIs (OpenAI, Anthropic, or open-weight models), MCP servers, and agentic frameworks.
You work daily with AI coding tools like Claude Code and Cursor, and you get agents doing useful work autonomously alongside you.
You identify problems, design the solution, and ship it without waiting for direction or approval.
You've moved fast under deadline while leaving foundations that other engineers extended after you moved on.
You've earned credibility with experts outside engineering: finance leads, lawyers, recruiters, or auditors, and driven adoption of your software inside their real deadlines, like a working close calendar or an offer that has to go out today.
Your product taste shows in what you've shipped: a controller, a recruiter, or a lawyer calls your interface obvious, and the workflow matches how their work actually happens.
Bonus: ERP and fixed asset accounting. FP&A, cash forecasting, and capital planning. Structured finance or treasury operations. Contract lifecycle systems. ATS and HRIS integrations (Ashby, Greenhouse, Rippling, Workday). LLM extraction over legal and financial documents."
Benefits list:
"Benefits Competitive total compensation package (cash + equity)Health, dental, and vision insuranceRetirement planGenerous PTO policy"
Compensation Range: "Compensation Range: $224K - $300K"
We need to remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, confirmation email etc. Also remove "We are committed to pay equity and transparency." That's maybe okay but it's boilerplate? It's about pay equity; could be considered boilerplate but it's a statement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "We are committed to pay equity and transparency." is not exactly EEO but could be considered legal boilerplate. Safer to remove.
Also remove "Fluidstack is an Equal Employment Opportunity Employer..." etc.
Also remove "You will receive a confirmation email..." etc.
Now we need to output HTML fragment only.
Structure:
About the role
... (combined About Fluidstack + How We Operate + The Decision Team? maybe we split? But we need to preserve all substantive info; we could put them in separate paragraphs under same heading.)
Better to keep them as separate paragraphs under About the role.
Then:
Responsibilities
- ... each bullet from Role Scope
Then:
Qualifications
- ... each bullet from What We're Looking For
Then:
Benefits
- Competitive total compensation package (cash + equity)
- Health, dental, and vision insurance
- Retirement plan
- Generous PTO policy
Then:
Pay
$224K - $300K
We should not include Schedule.
Check that we didn't miss any substantive info: The Decision Team examples maybe could be considered part of responsibilities? But we already have Role Scope which is the main responsibilities. The Decision Team describes examples of key problems the team is working on; could be considered part of responsibilities or context. To preserve all substantive info, we should include it somewhere. Could add a paragraph under About the role or maybe under Responsibilities as additional context. Since we have Responsibilities section already, we could add a paragraph before the list describing the Decision Team examples. That would preserve info.
Thus under Responsibilities heading, we can have a describing the Decision Team examples, then
for Role Scope.
Similarly, About the
for prose. Do NOT repeat job title as heading (none given). Do NOT put Job ID / requisition numbers as headings (none). Remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, etc. Also remove navigation/cookie/legal. So we need to keep substantive info. We need to decide which sections to include: About the role? The posting has "About Fluidstack" (company description). Could be considered "About the role"? But the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map sections accordingly. The posting includes:
- About Fluidstack (company mission) -> could be "About the role"? Actually "About the role" is typical heading for role description. But we have "About Fluidstack". Might be better to use "About the role" heading and put the Fluidstack description there? However instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can use those headings if they match content. We have content that fits "About the role" (description of company and mission). Could also have "How We Operate" maybe as "Responsibilities"? Not exactly. "The Decision Team" maybe as "Responsibilities"? Actually "Role Scope" is responsibilities. "What We're Looking For" is qualifications/requirements/skills. "Benefits" is benefits. "Compensation Range" is pay.
We should not create sections with filler. So we need to include sections only if there is real specific content.
Thus we can have:
About the role
with paragraph(s) about Fluidstack mission and maybe How We Operate? Actually How We Operate describes culture/operating principles; could be part of role description.
But we also have "Role Scope" which is a list of responsibilities (building hiring machine, cash view, capital pipeline, parsing contracts, embed forward-deployed). That's definitely responsibilities.
We have "What We're Looking For" which is a list of qualifications/skills.
We have "Benefits" list.
We have "Compensation Range" (pay).
We might also include "How We Operate" as a separate section maybe "Culture" but not in list; but we could incorporate into About the role or Responsibilities? Probably better to have a section "How we operate" as a heading? Not in the examples but we could still use for any section heading; the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use for section headings (e.g. those). Likely they expect us to use those standard headings where applicable. So we should map content to those headings.
Thus:
- About the role: include Fluidstack mission and maybe How We Operate? Could be separate but we can combine.
- Responsibilities: Role Scope bullet points.
- Requirements / Qualifications / Skills: What We're Looking For bullet points (some are requirements, some skills). Could split into Requirements and Skills but we can combine into one section "Requirements" or "Qualifications". The instruction says prefer a few substantive sections over many thin ones. So maybe one section "Qualifications" covering all.
- Benefits: list.
- Pay: compensation range.
We should not include Schedule (none). Also we should not include sections like "Responsibilities" if we don't have? We do have Role Scope.
Now we need to preserve all substantive information, not invent or summarize away detail. So we need to keep the bullet points exactly as given (or close). We must not omit details.
Let's extract content.
About Fluidstack paragraph:
"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!"
How We Operate paragraph:
"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 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."
The Decision Team paragraph:
"The Decision Team Examples of key problems the team is working on Automate the delivery of gigawatts. Every process that takes AI infrastructure from land to live compute becomes software: schedules, decisions, and todos generated from a live knowledge graph instead of chased by hand.Forward-deploy beside the experts. Product teams sit with quality managers, sourcing leads, and deployment engineers on factory floors and sites, and turn their judgment into systems that reach every unit.Deliver every supercomputer faster than the last. Dozens of concurrent projects feed one graph, so every lesson learned at one site becomes a preventive check at all of them."
Role Scope paragraph (multiple bullet-like sentences):
"Role Scope Build the hiring machine as software. Hiring is the company's biggest bottleneck. Every role, seat, and interview loop already lives in one graph, and you take it the rest of the way: the recruiting system synced both directions, interviewer supply and load visible to every hiring manager, and onboarding generated the moment an offer is signed, so day one starts with the job instead of the checklist.Build the cash view the company runs on: today no system derives near term spend, so finance forecasts by hand and misses what construction already committed. You turn purchase orders, contract terms, and build milestones into an order schedule, a cash demand curve by month, and a payment schedule that recompute as procurement and construction move.Build one capital pipeline from approved budget to released capital to spent dollar, gated on build milestones the delivery system already verifies, with the proof chain behind every financing drawdown assembled automatically, so releasing nine figures takes a day of judgment and funding follows construction within days.Parse every MSA, change order, and side letter into obligations, prices, deadlines, penalties, and SLAs, so a delivery lead gets what we owe a customer at a site with the clause attached, a change order arrives with its legal and finance checks done, and the corpus of executed deals prices the next negotiation.Embed forward-deployed with finance, treasury, accounting, legal, and people teams through a close, a drawdown, a negotiation, and a hiring loop, and turn their approvals, contract terms, screens, and reconciliations into structured data and generated work, including a continuous close where capitalization and depreciation post as events the moment they happen."
What We're Looking For bullet list (looks like sentences separated by periods but we can treat as list items):
"You've shipped production code in Go, Python, or TypeScript, and you pick up whatever language the problem demands.
You've built real features on LLM APIs (OpenAI, Anthropic, or open-weight models), MCP servers, and agentic frameworks.
You work daily with AI coding tools like Claude Code and Cursor, and you get agents doing useful work autonomously alongside you.
You identify problems, design the solution, and ship it without waiting for direction or approval.
You've moved fast under deadline while leaving foundations that other engineers extended after you moved on.
You've earned credibility with experts outside engineering: finance leads, lawyers, recruiters, or auditors, and driven adoption of your software inside their real deadlines, like a working close calendar or an offer that has to go out today.
Your product taste shows in what you've shipped: a controller, a recruiter, or a lawyer calls your interface obvious, and the workflow matches how their work actually happens.
Bonus: ERP and fixed asset accounting. FP&A, cash forecasting, and capital planning. Structured finance or treasury operations. Contract lifecycle systems. ATS and HRIS integrations (Ashby, Greenhouse, Rippling, Workday). LLM extraction over legal and financial documents."
Benefits list:
"Benefits Competitive total compensation package (cash + equity)Health, dental, and vision insuranceRetirement planGenerous PTO policy"
Compensation Range: "Compensation Range: $224K - $300K"
We need to remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, confirmation email etc. Also remove "We are committed to pay equity and transparency." That's maybe okay but it's boilerplate? It's about pay equity; could be considered boilerplate but it's a statement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "We are committed to pay equity and transparency." is not exactly EEO but could be considered legal boilerplate. Safer to remove.
Also remove "Fluidstack is an Equal Employment Opportunity Employer..." etc.
Also remove "You will receive a confirmation email..." etc.
Now we need to output HTML fragment only.
Structure:
About the role
About the role
with paragraph(s) about Fluidstack mission and maybe How We Operate? Actually How We Operate describes culture/operating principles; could be part of role description. But we also have "Role Scope" which is a list of responsibilities (building hiring machine, cash view, capital pipeline, parsing contracts, embed forward-deployed). That's definitely responsibilities. We have "What We're Looking For" which is a list of qualifications/skills. We have "Benefits" list. We have "Compensation Range" (pay). We might also include "How We Operate" as a separate section maybe "Culture" but not in list; but we could incorporate into About the role or Responsibilities? Probably better to have a section "How we operate" as a heading? Not in the examples but we could still use for any section heading; the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use for section headings (e.g. those). Likely they expect us to use those standard headings where applicable. So we should map content to those headings.
Thus:
- About the role: include Fluidstack mission and maybe How We Operate? Could be separate but we can combine.
- Responsibilities: Role Scope bullet points.
- Requirements / Qualifications / Skills: What We're Looking For bullet points (some are requirements, some skills). Could split into Requirements and Skills but we can combine into one section "Requirements" or "Qualifications". The instruction says prefer a few substantive sections over many thin ones. So maybe one section "Qualifications" covering all.
- Benefits: list.
- Pay: compensation range.
We should not include Schedule (none). Also we should not include sections like "Responsibilities" if we don't have? We do have Role Scope.
Now we need to preserve all substantive information, not invent or summarize away detail. So we need to keep the bullet points exactly as given (or close). We must not omit details.
Let's extract content.
About Fluidstack paragraph:
"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!"
How We Operate paragraph:
"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 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."
The Decision Team paragraph:
"The Decision Team Examples of key problems the team is working on Automate the delivery of gigawatts. Every process that takes AI infrastructure from land to live compute becomes software: schedules, decisions, and todos generated from a live knowledge graph instead of chased by hand.Forward-deploy beside the experts. Product teams sit with quality managers, sourcing leads, and deployment engineers on factory floors and sites, and turn their judgment into systems that reach every unit.Deliver every supercomputer faster than the last. Dozens of concurrent projects feed one graph, so every lesson learned at one site becomes a preventive check at all of them."
Role Scope paragraph (multiple bullet-like sentences):
"Role Scope Build the hiring machine as software. Hiring is the company's biggest bottleneck. Every role, seat, and interview loop already lives in one graph, and you take it the rest of the way: the recruiting system synced both directions, interviewer supply and load visible to every hiring manager, and onboarding generated the moment an offer is signed, so day one starts with the job instead of the checklist.Build the cash view the company runs on: today no system derives near term spend, so finance forecasts by hand and misses what construction already committed. You turn purchase orders, contract terms, and build milestones into an order schedule, a cash demand curve by month, and a payment schedule that recompute as procurement and construction move.Build one capital pipeline from approved budget to released capital to spent dollar, gated on build milestones the delivery system already verifies, with the proof chain behind every financing drawdown assembled automatically, so releasing nine figures takes a day of judgment and funding follows construction within days.Parse every MSA, change order, and side letter into obligations, prices, deadlines, penalties, and SLAs, so a delivery lead gets what we owe a customer at a site with the clause attached, a change order arrives with its legal and finance checks done, and the corpus of executed deals prices the next negotiation.Embed forward-deployed with finance, treasury, accounting, legal, and people teams through a close, a drawdown, a negotiation, and a hiring loop, and turn their approvals, contract terms, screens, and reconciliations into structured data and generated work, including a continuous close where capitalization and depreciation post as events the moment they happen."
What We're Looking For bullet list (looks like sentences separated by periods but we can treat as list items):
"You've shipped production code in Go, Python, or TypeScript, and you pick up whatever language the problem demands.
You've built real features on LLM APIs (OpenAI, Anthropic, or open-weight models), MCP servers, and agentic frameworks.
You work daily with AI coding tools like Claude Code and Cursor, and you get agents doing useful work autonomously alongside you.
You identify problems, design the solution, and ship it without waiting for direction or approval.
You've moved fast under deadline while leaving foundations that other engineers extended after you moved on.
You've earned credibility with experts outside engineering: finance leads, lawyers, recruiters, or auditors, and driven adoption of your software inside their real deadlines, like a working close calendar or an offer that has to go out today.
Your product taste shows in what you've shipped: a controller, a recruiter, or a lawyer calls your interface obvious, and the workflow matches how their work actually happens.
Bonus: ERP and fixed asset accounting. FP&A, cash forecasting, and capital planning. Structured finance or treasury operations. Contract lifecycle systems. ATS and HRIS integrations (Ashby, Greenhouse, Rippling, Workday). LLM extraction over legal and financial documents."
Benefits list:
"Benefits Competitive total compensation package (cash + equity)Health, dental, and vision insuranceRetirement planGenerous PTO policy"
Compensation Range: "Compensation Range: $224K - $300K"
We need to remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, confirmation email etc. Also remove "We are committed to pay equity and transparency." That's maybe okay but it's boilerplate? It's about pay equity; could be considered boilerplate but it's a statement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "We are committed to pay equity and transparency." is not exactly EEO but could be considered legal boilerplate. Safer to remove.
Also remove "Fluidstack is an Equal Employment Opportunity Employer..." etc.
Also remove "You will receive a confirmation email..." etc.
Now we need to output HTML fragment only.
Structure:
About the role
for section headings (e.g. those). Likely they expect us to use those standard headings where applicable. So we should map content to those headings.
Thus:
- About the role: include Fluidstack mission and maybe How We Operate? Could be separate but we can combine.
- Responsibilities: Role Scope bullet points.
- Requirements / Qualifications / Skills: What We're Looking For bullet points (some are requirements, some skills). Could split into Requirements and Skills but we can combine into one section "Requirements" or "Qualifications". The instruction says prefer a few substantive sections over many thin ones. So maybe one section "Qualifications" covering all.
- Benefits: list.
- Pay: compensation range.
We should not include Schedule (none). Also we should not include sections like "Responsibilities" if we don't have? We do have Role Scope.
Now we need to preserve all substantive information, not invent or summarize away detail. So we need to keep the bullet points exactly as given (or close). We must not omit details.
Let's extract content.
About Fluidstack paragraph:
"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!"
How We Operate paragraph:
"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 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."
The Decision Team paragraph:
"The Decision Team Examples of key problems the team is working on Automate the delivery of gigawatts. Every process that takes AI infrastructure from land to live compute becomes software: schedules, decisions, and todos generated from a live knowledge graph instead of chased by hand.Forward-deploy beside the experts. Product teams sit with quality managers, sourcing leads, and deployment engineers on factory floors and sites, and turn their judgment into systems that reach every unit.Deliver every supercomputer faster than the last. Dozens of concurrent projects feed one graph, so every lesson learned at one site becomes a preventive check at all of them."
Role Scope paragraph (multiple bullet-like sentences):
"Role Scope Build the hiring machine as software. Hiring is the company's biggest bottleneck. Every role, seat, and interview loop already lives in one graph, and you take it the rest of the way: the recruiting system synced both directions, interviewer supply and load visible to every hiring manager, and onboarding generated the moment an offer is signed, so day one starts with the job instead of the checklist.Build the cash view the company runs on: today no system derives near term spend, so finance forecasts by hand and misses what construction already committed. You turn purchase orders, contract terms, and build milestones into an order schedule, a cash demand curve by month, and a payment schedule that recompute as procurement and construction move.Build one capital pipeline from approved budget to released capital to spent dollar, gated on build milestones the delivery system already verifies, with the proof chain behind every financing drawdown assembled automatically, so releasing nine figures takes a day of judgment and funding follows construction within days.Parse every MSA, change order, and side letter into obligations, prices, deadlines, penalties, and SLAs, so a delivery lead gets what we owe a customer at a site with the clause attached, a change order arrives with its legal and finance checks done, and the corpus of executed deals prices the next negotiation.Embed forward-deployed with finance, treasury, accounting, legal, and people teams through a close, a drawdown, a negotiation, and a hiring loop, and turn their approvals, contract terms, screens, and reconciliations into structured data and generated work, including a continuous close where capitalization and depreciation post as events the moment they happen."
What We're Looking For bullet list (looks like sentences separated by periods but we can treat as list items):
"You've shipped production code in Go, Python, or TypeScript, and you pick up whatever language the problem demands.
You've built real features on LLM APIs (OpenAI, Anthropic, or open-weight models), MCP servers, and agentic frameworks.
You work daily with AI coding tools like Claude Code and Cursor, and you get agents doing useful work autonomously alongside you.
You identify problems, design the solution, and ship it without waiting for direction or approval.
You've moved fast under deadline while leaving foundations that other engineers extended after you moved on.
You've earned credibility with experts outside engineering: finance leads, lawyers, recruiters, or auditors, and driven adoption of your software inside their real deadlines, like a working close calendar or an offer that has to go out today.
Your product taste shows in what you've shipped: a controller, a recruiter, or a lawyer calls your interface obvious, and the workflow matches how their work actually happens.
Bonus: ERP and fixed asset accounting. FP&A, cash forecasting, and capital planning. Structured finance or treasury operations. Contract lifecycle systems. ATS and HRIS integrations (Ashby, Greenhouse, Rippling, Workday). LLM extraction over legal and financial documents."
Benefits list:
"Benefits Competitive total compensation package (cash + equity)Health, dental, and vision insuranceRetirement planGenerous PTO policy"
Compensation Range: "Compensation Range: $224K - $300K"
We need to remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, confirmation email etc. Also remove "We are committed to pay equity and transparency." That's maybe okay but it's boilerplate? It's about pay equity; could be considered boilerplate but it's a statement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "We are committed to pay equity and transparency." is not exactly EEO but could be considered legal boilerplate. Safer to remove.
Also remove "Fluidstack is an Equal Employment Opportunity Employer..." etc.
Also remove "You will receive a confirmation email..." etc.
Now we need to output HTML fragment only.
Structure:
About the role
... (combined About Fluidstack + How We Operate + The Decision Team? maybe we split? But we need to preserve all substantive info; we could put them in separate paragraphs under same heading.) Better to keep them as separate paragraphs under About the role. Then:
Responsibilities
- ... each bullet from Role Scope
Qualifications
- ... each bullet from What We're Looking For
Benefits
- Competitive total compensation package (cash + equity)
- Health, dental, and vision insurance
- Retirement plan
- Generous PTO policy
Pay
$224K - $300K
We should not include Schedule. Check that we didn't miss any substantive info: The Decision Team examples maybe could be considered part of responsibilities? But we already have Role Scope which is the main responsibilities. The Decision Team describes examples of key problems the team is working on; could be considered part of responsibilities or context. To preserve all substantive info, we should include it somewhere. Could add a paragraph under About the role or maybe under Responsibilities as additional context. Since we have Responsibilities section already, we could add a paragraph before the list describing the Decision Team examples. That would preserve info. Thus under Responsibilities heading, we can have adescribing the Decision Team examples, then
- for Role Scope.
Similarly, About the