Founding BizOps, US

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invented or summarized away detail. Remove boilerplate: mission, legal note, EEO, etc. Also remove duplicated lines, navigation, cookie, etc. Must not include sections like "About the role" if not present? The posting includes sections: "Our Mission", "What We're Looking For", "What Can You Expect?" with subparts, "About You", "A Few Things To Note". We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content for each. First, identify the role: US GM Arie’s commercial and executional partner. The description: "You’ll be our US GM Arie’s commercial and executional partner, working closely with our CCO’s CoS Liat, to own problems that don’t yet have a natural home: growing our GTM team without lowering the bar, leveraging our VC and angel network to build a community, ramping new hires fast, and deciding which markets we build next." This is about the role. Responsibilities: The bullet list under "What Can You Expect?" includes building US Growth engine, scaling & hiring, AI enablement & ramp, strategic projects & market expansion. Those are responsibilities. Requirements: The "About You" section lists experience 3-5 years in high-calibre fast-paced environment, consulting, banking, VC, or building inside an AI startup, etc. Also attributes: relentless data-driven problem solver, proven operator across messy cross-functional work streams, outstanding communicator, scrappy entrepreneurial, comfortable in mess, nice to have exposure to US/Canadian markets or network. Qualifications: Might overlap with requirements; but we can treat "About You" as qualifications/requirements. However we need separate sections if content distinct. Could put "Requirements" for experience and "Qualifications" for skills/attributes. But we must not invent. Let's see: The posting includes "About You" with bullet-like sentences. Could split: Requirements: 3-5 years experience in high-calibre fast-paced environment - consulting, banking, VC, or building inside an AI startup. Bonus points if you've founded one yourself. Nice to have: exposure to both US and Canadian markets, or an existing network in either. Qualifications/Skills: A relentless, data-driven problem solver... proven operator across messy cross-functional work streams... outstanding communicator... scrappy, entrepreneurial, allergic to playbooks... comfortable in the mess. We could combine into Skills section. Benefits: The posting mentions "We offer competitive geo-localised benefits, and you can check out our UK Benefits Package here and our US Benefits Package here." That's a statement about benefits but not specific details. According to rules, we should not create Benefits section unless posting actually states them (specific). It says they offer competitive geo-localised benefits and links. That's somewhat specific? It mentions they have benefits packages. Might be enough to include a Benefits section with that statement. However we must avoid filler like "competitive geo-localised benefits" is not placeholder like "varies". It's actual statement. So we can include Benefits section with that sentence. Pay: No mention of salary or pay. So we should NOT include Pay section. Schedule: The posting mentions "We work Tuesdays, Wednesdays & Thursdays in-person at our offices." That's schedule info. So we can include Schedule section with that sentence. Now we need to output HTML with

for each section heading, and

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as in posting, but we can format as lists. We must not repeat job title. Must not include Job ID etc. We must remove boilerplate: mission, legal note, EEO, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "Find out more about the team and life at Omnea here." etc. Also remove "A Few Things To Note" maybe we keep benefits and schedule from there but discard other notes like AI note-takers, legal note, etc. We need to ensure we keep all substantive info from the posting that is relevant to role: The mission paragraph maybe not needed as it's not about role specifics? It's about company mission. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Mission might be considered boilerplate? It's not strictly required to preserve; but we need to preserve ALL substantive information. Does mission count as substantive? It's about company, not role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say we must keep mission; but we could keep it if it's substantive. However they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Mission is not those. But they also said "Prefer a few substantive sections over many thin ones." Might be okay to include mission as a paragraph before sections? But they said use headings for sections; we could include a

  for mission before headings. However they said "Do NOT repeat the job title as a heading (the page already shows it)". They didn't forbid other headings besides the listed ones. But they gave list of headings to use for sections. Likely they expect only those headings if content exists. Mission could be placed as a

  before any heading, but not as a heading. However they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections. It doesn't forbid other headings, but to be safe we can just output those sections that have content, and any other prose can be in

  without heading. Thus we could output:

  Our Mission At Omnea, we’re reinventing how enterprise businesses operate, starting with the most painful parts: procurement – where a single purchase can drag on for months, trigger 50+ emails, and pull in Finance, Legal, Security, and IT just to get something approved. We’ve raised $75M from Khosla Ventures, Insight Partners, and Accel to change that. Our AI-native platform connects every person, step, and system so buying is fast, safe, and efficient – one place to request, automated approvals and renewals, real-time supplier risk, and complete spend visibility. The opportunity is massive. Every enterprise on the planet has this problem and nobody has solved it. We’ve 10x’d ARR to double-digit millions in 18 months and are trusted by global enterprises like Spotify, MongoDB, Monzo, and Albertsons. We’re now the 4th fastest growing startup in Europe & the Sunday Times' #1 Best Medium Sized Tech Company To Work for. Our team previously scaled Tessian (cybersecurity tech, backed by Sequoia, Balderton, Accel, acquired post-Series C), and our team includes ex-founders operators who’ve grown unicorns, shipped world-class products, and executed at the highest levels. You’ll work alongside leaders like Ben, Abs, Sabrina, and Rebe. Find out more about the team and life at Omnea here.

  But that includes "Find out more about the team and life at Omnea here." which is maybe a link; but it's okay. Then we need About the role section: maybe we can put a

  About the role

  and then a

  with the description: "You’ll be our US GM Arie’s commercial and executional partner, working closely with our CCO’s CoS Liat, to own problems that don’t yet have a natural home: growing our GTM team without lowering the bar, leveraging our VC and angel network to build a community, ramping new hires fast, and deciding which markets we build next." Then Responsibilities:

  Responsibilities

  then a
  with each bullet from "What Can You Expect?" subparts. We need to preserve all substantive information; we should not summarize away detail. So we need to keep each bullet's text exactly as in posting. Let's extract the bullet points: Under "What Can You Expect?": - Scaling & Hiring (core focus during first 6-12 months) - You'll build the machine that helps us identify the top 1% of talent and close them - diagnosing the funnel, running the experiments, and owning the number to 3x our sales headcount - You'll build and own our comp benchmarking model — the difference between losing candidates to banking and consulting, and actually landing them - You'll rebuild our people process from the ground up, sitting in on interviews to diagnose exactly where signal breaks down and building the rubric that gets our bar genuinely aligned - You'll shape how Omnea shows up in the US market — through podcasts, events, our VC network — so the best people in New York already know who we are before we ever reach out - AI, Enablement & Ramp - You'll own the ramping target — building the onboarding that turns a hire into a top performer in weeks, not months - You'll build the collateral, tooling, and process that shortens time-to-ramp and becomes the playbook other teams end up borrowing - You’ll figure out ways to automate the process end to end so the team can scale efficiently - Strategic Projects & Market Expansion - You'll oversee strategic decision like where we expand to next in North America — working with our CFO and RevOps team to make the case with real data, not guesswork - You'll build the reporting that gives GTM leadership a clear, unfiltered view of what's actually working, shaping how we operate over the next 12 months We need to keep the headings (Scaling & Hiring, AI, Enablement & Ramp, Strategic Projects & Market Expansion) maybe as part of the list items? They are subheadings within responsibilities. We could keep them as
  • with bold? But we cannot add formatting beyond HTML; we could keep them as plain text within
  • . That's fine. Thus each bullet becomes a
  • . Ensure we preserve punctuation. Now Requirements:

    Requirements

    then a

    or

    ? The requirement is a sentence: "3-5 years of experience in a high-calibre, fast-paced environment - consulting, banking, VC, or building inside an AI startup. Bonus points if you've founded one yourself. Nice to have: exposure to both the US and Canadian markets, or an existing network in either." We could make a
    with each bullet as
    • . But the instruction: Use
      • for any list of duties/requirements/benefits. So we should treat requirements as a list. So we can split into items: - 3-5 years of experience in a high-calibre, fast-paced environment - consulting, banking, VC, or building inside an AI startup. - Bonus points if you've founded one yourself. - Nice to have: exposure to both the US and Canadian markets, or an existing network in either. Now Qualifications/Skills: The "About You" bullet-like sentences after that: "A relentless, data-driven problem solver. You build models, stress-test it against reality, and change your mind fast when the evidence tells you to. A proven operator across messy, cross-functional work streams - you get people who don't report to you to move, and make it look easy. An outstanding communicator who builds trust fast, whether you're in the room with GTM, RevOps, or the leadership team. Scrappy