Senior Manager of FP&A

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. We have sections: About Fluidstack (company description) - not required as heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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. So we need to include sections only if posting has real specific content. We have "About The Role" heading present. That is a section heading: we can output

About the role

then content. We have "What You’ll Do" which is responsibilities. So we can have

Responsibilities

with list. We have "Basic Qualifications" and "Preferred Qualifications". Those could be under Requirements or Qualifications. The instruction: Use headings like Requirements, Qualifications, Skills. We need to decide. Probably combine basic and preferred qualifications under Requirements or Qualifications. Since they are qualifications, we can put under

Qualifications

and list both basic and preferred as items? But we need to preserve all substantive info. Could separate Basic and Preferred as subheadings? Not allowed; only those headings. Could put both under Qualifications with

• items, maybe differentiate with text. We have "Salary & Benefits" section with details: Competitive total compensation package (salary + equity). Retirement or pension plan, health, dental, vision insurance, generous PTO, equity RSUs, pay equity statement. Also compensation range: $196K - $240K. So we can have

  Pay

  with the range and maybe mention equity. Benefits: we can have

  Benefits

  with list. Schedule: not mentioned. So omit. Skills: not explicitly listed; maybe we could infer from qualifications but better not to create unless explicit. So omit Skills. We also have "How We Operate" describing culture; could be part of About the role? Not needed. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We must not include boilerplate like EEO, legal, application instructions, cookie/navigation, etc. So we need to drop the EEO paragraph, the confirmation email instructions, etc. We also need to drop duplicated lines like "We are committed to pay equity and transparency." appears twice; we should keep only once? The instruction: remove duplicated lines. So we keep one instance. We need to keep the compensation range. We need to keep the "About Fluidstack" description? It's not under the specified headings but it's substantive info about company. Should we include it? The instruction says to reformat a job posting into clean, well-structured semantic HTML. Use headings for sections. It didn't say we must drop company description; we could include it as a

  before sections or under a heading like "About Fluidstack"? But the allowed headings list does not include "About Fluidstack". However we could still include a

  paragraph before sections, as it's not a heading. The instruction: 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 those for those sections. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include other headings if we want, but better to stick to allowed ones. However the company description is substantive; we could put it under a

  before the sections, not as a heading. That seems acceptable. Thus output:

  About Fluidstack ...

  Then

  About the role

  with paragraph(s) from "About The Role". Then

  Responsibilities

  with
  • items from "What You’ll Do". Then

    Qualifications

    with maybe two sublists? Could separate Basic and Preferred as
    • but we need to preserve distinction. Could include a

      Basic Qualifications:

      then
      ..., then

      Preferred Qualifications:

      then
      ... That's okay. Then

      Benefits

      with
      • items from Salary & Benefits (excluding pay range). Then

        Pay

        with

        Compensation range: $196K - $240K.

        plus maybe mention competitive total compensation package (salary + equity). Could combine. We must not repeat "We are committed to pay equity and transparency." more than once. Include once maybe under Benefits or Pay? Could include as a

        under Benefits. We must drop the duplicated line. We must drop the EEO paragraph, application instructions, confirmation email instructions. We must drop the "How We Operate" maybe? It's substantive but not under headings; could include as a

        before sections? But it's about culture; maybe we can include as a

        under About the role? But it's separate. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that content somewhere. Could add a

        Culture

        but not in allowed list. However we could include as a

        before sections, maybe after About Fluidstack. The instruction didn't forbid other headings, but said use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we cannot use other headings; it's just examples. Safer to include as a

        paragraph. Thus we will have:

        About Fluidstack ...

        How We Operate ...

        About the role

        ... etc. Check for any other substantive info: "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!" That's a call to action; maybe we can drop as it's application instruction? It's not exactly instruction but encouraging to apply. Might be considered boilerplate? Probably safe to drop as it's not substantive detail about role. The instruction: remove application instructions. This line is a call to apply; could be considered application instruction. Safer to drop. Now we need to ensure we don't include any navigation/legal/EEO etc. Let's extract the exact text. 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!" We may drop the last sentence "Come be a part..." and "We hire people..." and "If that is you, please apply!" as they are fluff/call to action. But they are substantive? They describe mission and hiring criteria. Might be okay to keep but could be considered boilerplate. I'd keep the core mission description up to "Speed and scale are our key differentiators." The rest is more fluff. However instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep all of it unless it's clearly boilerplate/navigation/legal/EEO/etc. The call to apply is not boilerplate but it's not substantive detail about the role; still it's part of posting. I'd keep it but maybe it's okay. But we already have a call to apply later; maybe we can keep it as part of About Fluidstack. 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." We need to preserve that. About The Role paragraph: "About The Role As Senior Manager of FP&A at Fluidstack, you will be a cornerstone of our Finance leadership team, owning the financial planning, analysis, and decision-support infrastructure that powers one of the fastest-moving companies in AI. You will lead the full FP&A function — from annual planning and budgeting to long-range financial modeling, scenario analysis, and board-level reporting — all while building processes from the ground up. This is a high-impact, high-ownership role for someone who thrives in ambiguity, moves with urgency, and understands that great FP&A is as much about influencing decisions as it is about accuracy. You will partner deeply with Engineering, Operations, Sales, and Finance to translate business strategy into financial clarity, and you will be instrumental in preparing Fluidstack for the next phase of its growth." What You’ll Do bullet list: - Own Fluidstack’s annual operating plan, quarterly forecasting cycles, and long-range financial model across all business units and geographies. - Build and lead a world-class FP&A team, establishing the infrastructure, cadence, and culture of financial rigor the business needs to scale. - Partner with executive leadership team to develop and pressure-test strategic financial scenarios, capital allocation decisions, and growth investments. - Drive board and investor reporting — translating complex operational data into clear, compelling financial narratives. - Embed FP&A as a true business partner across Engineering, Operations, Sales, and Finance — owning the P&L bridge and variance analysis end-to-end. - Lead IPO readiness efforts from an FP&A perspective, including development of public-company-grade financial reporting processes and controls. - Own the build-out of FP&A systems and tooling, including integration with ERP platforms (NetSuite) and data infrastructure. - Develop KPI frameworks and financial performance dashboards that give leadership real-time visibility into business health. Basic Qualifications list: - 10+ years of progressive FP&A experience, including prior experience in a senior leadership role. - Proven track record building and leading FP&A functions at high-growth technology, infrastructure, or pre-IPO companies. - Deep expertise in financial modeling, budgeting, forecasting, and long-range planning in complex, multi-entity environments. - Experience partnering directly with C-suite and board-level stakeholders on financial strategy and reporting. - Strong command of ERP systems; NetSuite proficiency required. - Demonstrated ability to hire, develop, and lead high-performing finance teams. - Exceptional communication skills — you can distill complex financial data into clear insights for both technical and non-technical audiences. - Bachelor’s degree in Finance, Accounting, Economics, or a related field; CPA or CFA preferred. Preferred Qualifications list: - Experience at a data center, infrastructure, AI/ML, or