Head of Operations

We need to produce HTML fragment with sections: About the role? The posting includes "Who We Are", "The Role", "Who We're Looking For", "Location", "Life at Prior Labs", "Our Commitments". We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can also use other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings if applicable. However we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we map content to those standard headings where appropriate. The posting doesn't have explicit responsibilities list but we can extract responsibilities from "The Role". Could map to "About the role" maybe. Also "Who We're Looking For" could be "Requirements" or "Qualifications". "Location" could be separate but not in list; maybe we can omit if not specified? The instruction: "IMPORTANT: 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 sections for which we have content. The allowed headings list is just examples; we can use other headings if needed? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Probably they want us to use those headings where applicable; but we could also use other headings like "Who We Are", "Life at Prior Labs", "Our Commitments". However they didn't list those as examples; but they didn't forbid. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; but we could also use other headings if needed? Safer to map content to those headings: About the role (summary), Responsibilities (duties), Requirements/Qualifications (skills/experience), Benefits, Pay, Schedule. The posting does not mention Pay, Benefits, Schedule explicitly. So we should not create those sections. We can create About the role, Responsibilities, Requirements, Qualifications maybe combined. Also maybe "Location" could be omitted or placed in a paragraph under About the role? But they said do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Location is not minor metadata? It's location info; could be included in a paragraph under About the role or as its own section? Not in the list; but we could include as a paragraph under About the role. We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all details from the posting, but we can format them into sections. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is "Our Commitments" which includes EEO statement; that is boilerplate? It's an equal opportunities statement. According to instruction, remove EEO/equal-opportunity boilerplate. So we should remove the "Our Commitments" paragraph entirely. Also "Life at Prior Labs" maybe not boilerplate; keep. We need to output only HTML fragment, no /, no markdown fences. Let's extract content: Who We Are: paragraph about foundation models, TabPFN, team, SAP acquisition, etc. The Role: description of Head of Operations responsibilities. Who We're Looking For: bullet-like list of essential qualifications and plus. Location: Ideally located at hubs in New York or Berlin; remote/hybrid possible. Life at Prior Labs: description of work environment, offices, offsites. We need to avoid duplication. We'll create sections:

About the role

maybe includes Who We Are and The Role? Actually About the role could be summary of role and company. But we have separate Who We Are (company description). Could put that under About the role? Or we could have separate section "Who we are"? Not in list but maybe okay. However 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 to be safe we could map Who We Are to About the role? But About the role is supposed to be about the role, not company. However we could still include company info under About the role as context. Might be okay. Alternatively we could have sections: About the role (company + role), Responsibilities (duties), Requirements (essential qualifications), Qualifications (maybe plus), Skills (maybe not needed). But we need to avoid thin sections. Let's think: The posting has a lot of prose; we can break into logical sections: - About the company (Who We Are) maybe as a paragraph under About the role? Or we could have a section "About the company" but not in list; risk. Better to follow the instruction: Use headings from the list only when we have real content. So we need to decide which of those headings we have content for. We have content for: - About the role: we can describe the role and maybe company context. - Responsibilities: we can list duties from The Role. - Requirements: essential qualifications from Who We're Looking For. - Qualifications: maybe the "A big plus" items. - Skills: maybe not explicitly listed; we could omit. - Benefits, Pay, Schedule: not present, so omit. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities we should make a list. For Requirements also list. For Qualifications also list. We need to preserve all substantive information; we must not lose details. So we need to convert the prose into list items while preserving meaning. Let's extract responsibilities from The Role paragraph: "The Head of Operations reports to Sauraj (Co-CEO, GTM and Operations) and take ownership of operational excellence company-wide. As Finance, Legal, People, IT and InfoSec, and Compliance grow into their own functions, this person partners with each lead on the operational side of their work and holds the whole together as one system. They lead the operations team and grow it into one fit for a company many times our current size. Builds the operating engine for growth and scale. Owns how the company runs operationally and designs the processes that hold up as headcount, revenue, and complexity grow fast. Everything breaks at each new stage of growth; this person sees it coming and rebuilds ahead of the curve so operations never becomes the ceiling on how fast we can move. Drives operational excellence across every function. Accountable for the operational side of finance, people, legal, and the wider back office, with IT, InfoSec, and compliance covered through the relevant leads. You will set the standard and makes sure nothing important falls between functions. Brings order to ambiguity. Takes the most complex, cross-functional problems and drives them to resolution bringing all the right stakeholder to the table, motivating and inspiring them to come together and deliver the project for everyone’s benefit. Is a decision partner. Frames trade-offs, surfaces risk early, and turns decisions into action, so the leadership team works from reliable data and sound judgment. Builds and inspires the operations team. Hires, develops, and leads an operations team people want to be part of, and sets a standard of execution that raises the bar for everyone who works with them." We can break into bullet points each sentence or clause. Similarly Requirements (Essential): - High-growth experience above all: operated inside a company through rapid scaling, seen what breaks at each stage, built processes and structures that scaled through it. - Global operating experience: run operations across multiple countries and regions, comfortable holding a company together across time zones and jurisdictions, not just in a single market. - Broad operations ownership: driven operational excellence across two or more of finance, people, legal, and business operations as a senior generalist, partnering with specialist leads rather than owning their decisions. - A leader operators want to follow: builds and develops strong teams and is the kind of person other excellent operators want to come and work with. - A big plus: Experience in the data, developer tools, or AI market, and comfort working credibly with a technical, research-led team; has built an operations function that grew with a company from startup into real scale. - What makes someone thrive here: Energized by building the systems that unlock the next stage of growth, not by maintaining the status quo; Radical ownership: runs at the most difficult problems and resolves them rather than passing them up; Practical and pragmatic: builds processes that scale without bloat, using as much structure as the moment needs; Calm and decisive under ambiguity and competing priorities, and sets that standard for the team. We could treat the "What makes someone thrive here" as part of Requirements or Qualifications; but we can include as part of Requirements. Location: "Ideally this person will be located at one of our hubs in New York or Berlin. In exceptional circumstances, we will be able to consider remote/hybrid applications." This is location info; we could include as a paragraph under About the role or maybe a separate section but not in list; we could just include as a paragraph after About the role. Life at Prior Labs: description; we could include as a paragraph under About the role or separate section "Life at Prior Labs". Not in list but we could include as a paragraph. We must not include boilerplate like Our Commitments. Now produce HTML:

  About the role

  [company description + role summary + location + life at prior labs?]

  But we need to avoid too much mixing; maybe better to separate: About the role (role summary), Life at Prior Labs (as its own paragraph), Location (as paragraph). However the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but to be safe we could keep only those headings and put other info in paragraphs under those sections. Thus we can put company description, location, life at prior labs all under About the role as paragraphs. Then Responsibilities as

  • ... Requirements as
    • ... Qualifications as
      • ... (for big plus and thriving attributes). We must ensure we don't lose any detail. Let's craft About the role paragraph: We need to include Who We Are description: "Foundation models transformed text and images. Structured data - the largest and most consequential data format in the world - stayed untouched, until now. What LLMs did for language, we're doing for tables. We pioneered tabular foundation models: TabPFN v2 was a Nature cover story, has passed 3.5M+ downloads and 7,500+ GitHub stars, and runs in production from detecting lung disease with Oxford Cancer Analytics to preventing train failures with Hitachi. The hardest problems - millions of rows, real-time inference, entirely new modalities - are still open, and no one else is working on them at this level. We're a small, highly selective team of 40+ with backgrounds from Google, DeepMind, Meta, Apple, Amazon, Jane Street, and CERN, led by Frank Hutter, Noah Hollmann, and Sauraj Gambhir, and advised by Bernhard Schölkopf and Turing Award winner Yann LeCun. In July 2026, less than 18 months after our €9M pre-seed, we joined SAP as an independent frontier AI lab - same team, mission,