AI Operations Lead

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting content. First, there is an "About Karbon" paragraph describing company. That's not a required 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. We need to include sections only when posting has real specific content. The posting includes: - About Karbon (company description). Could be considered "About the role"? Actually "About the role" is separate. There's "About The Role" heading in the posting. So we should have a section with heading

About the role

containing the content under that heading. - Then there are sub-sections within About The Role: Build the Tooling, Own Governance and Visibility, Train Teams and Set the Standard, Measure and Report the Return. Those could be considered responsibilities. So we could put them under Responsibilities as

• ... maybe each bullet. - Then "About You!" is qualifications/requirements. Could be Requirements or Qualifications. We'll map to Requirements. - Then "What Success Looks Like!" maybe could be considered something like "Goals" but not in list; we could treat as part of Responsibilities or maybe as a separate section like "Success Metrics"? Not in allowed headings. Probably we incorporate into Responsibilities. - Then "Why Work at Karbon?" includes benefits. So we can have Benefits section. - Pay: there is salary range: $180,000 USD - $190,000 USD. So we need Pay section. - Schedule: not mentioned. So we omit Schedule. - Skills: maybe we can extract from About You! but we could put under Skills or Requirements. The instruction: Use headings for Skills, Benefits, Pay, Schedule. We could have Skills section listing relevant skills: Python/TypeScript, SQL, REST APIs, LLM experience, etc. But we need to ensure we don't invent. The posting mentions: "You shipped production software in the last two years, as the person writing the code. Python or TypeScript, SQL, and REST APIs. You built something real on top of a large language model.... You worked directly with non-technical teams... You can build a number out of messy data and defend it to a CFO. You have run a cross-functional program...". Those are qualifications/experience. Could be placed under Requirements or Qualifications. We could have both Requirements and Qualifications but we need to avoid thin sections. Perhaps combine into one Requirements section. But we have to follow instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exhaustive. So we can choose which to include. We need to preserve all substantive information. So we need to include company description? Possibly under a brief intro paragraph before sections. Not required to be a heading. Could be a

  before sections. We must not include boilerplate like EEO, legal, scam warning, navigation, cookie, duplicated lines, application instructions. So we need to strip those. Let's extract substantive content: Company description (About Karbon) - keep. About The Role - keep with subpoints. About You! (requirements/qualifications) - keep. What Success Looks Like! - keep as maybe part of Responsibilities or separate "Success Metrics"? Could be its own heading but not in list; maybe we can treat as "Goals" but not allowed. Safer to incorporate into Responsibilities or maybe a separate section "Success Metrics" but that might be considered thin. However it's substantive; we could add a heading

  Success Metrics

  but not in the allowed list; instruction says use those headings for sections, but not that we cannot use other headings? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could still use other headings if needed, but better to stick to those. We could treat Success Metrics as part of Responsibilities. Why Work at Karbon? - benefits. Pay - salary range. We also have note about compensation range statement; we need to include that as part of Pay. We need to remove: "As we hire across various locations within the USA we are required by law to include a reasonable estimate of the compensation range for this role...." That's part of Pay description; we keep it. Also remove: "Please be aware that Karbon will only contact you via email from our domain, karbonhq.com...." That's maybe application instruction / scam warning; remove. Also remove: "Karbon embraces diversity and inclusion..." EEO boilerplate; remove. Also remove: "At this time, we request that agency referrals are not submitted for this position...." That's application instruction; remove. Also remove: "Thank you!" maybe not needed. Now construct HTML. We'll start with a

  for company description. Then

  About the role

  with content: maybe a

  summarizing the role? The posting has a paragraph after "About The Role": "Build the Tooling Ship internal automations..." Actually the heading "About The Role" then content: "Build the Tooling Ship internal automations and agents that remove repeated manual work across Sales, CS, Implementation, Support, and Operations. Connect AI to the systems we already run, through APIs and MCP servers.The first build is the data gateway...." So we can put that as a

  then maybe a

  for the bullet points? But the content already includes bullet-like sentences separated by periods. We could break into
  • for each distinct responsibility: Build the Tooling, Own Governance and Visibility, Train Teams and Set the Standard, Measure and Report the Return. Each of those has sub-details. Better: Under About the role, we can have a
    with each major responsibility as
    • containing subpoints maybe as
      inside. But instruction: Use
      • for any list of duties/requirements/benefits. So we should treat the responsibilities as a list. Thus:

        About the role

        • Build the Tooling: Ship internal automations and agents that remove repeated manual work across Sales, CS, Implementation, Support, and Operations. Connect AI to the systems we already run, through APIs and MCP servers. The first build is the data gateway... (details). After that: CS gets a renewal risk signal... etc.
        • Own Governance and Visibility: Manage the Claude access and provisioning workflow... (details).
        • Train Teams and Set the Standard: Work with each department lead... (details).
        • Measure and Report the Return: Define the small set of metrics... (details).
        We need to preserve all specifics; we must not lose details. So we need to include the details inside each
      • . Could be multiple sentences; that's fine. Then

        Requirements

        (or Qualifications). We'll use Requirements. We need to list the qualifications from About You! as a list. Content: - You shipped production software in the last two years, as the person writing the code. Python or TypeScript, SQL, and REST APIs. - You built something real on top of a large language model. Not a demo. Something with users, error handling, and a cost you had to control. - You worked directly with non-technical teams as the technical person in the room. Forward deployed engineer, solutions engineer, GTM engineer, internal tools engineer, or similar. You know what a CS renewal motion looks like and what implementation scoping feels like. You do not need to have worked in those roles. You need to have built something those teams actually used. - You can build a number out of messy data and defend it to a CFO. - You have run a cross-functional program where the participants did not report to you — a champion network, an ambassador program, an adoption initiative. You know how to create accountability without authority. - You write clearly, and you can say no to work that will not pay off. - Bonus Points: Accounting, professional services, or B2B software market experience. Familiarity with MCP server development, Claude API, or agent frameworks. Experience with Okta or similar identity providers. We'll put these as
        • items. Then

          Benefits

          from Why Work at Karbon?: - Gain global experience across Australia, New Zealand, UK, and Canada - Strong benefits package including: - Flexible Time Off with an encouraged 4 weeks use per year - Company paid medical for you and eligible spouse/partner and dependents - Paid dental and vision and eligible spouse/partner and dependents - 401(k) with company matching - Flexible Spending Account - Up to 8 weeks paid parental leave - Work-from-home stipend - Work with (and learn from) an experienced, high-performing team - A collaborative, team-oriented culture that embraces diversity, invests in development and provides consistent feedback - Be part of a fast-growing company that firmly believes in promoting high performers from within We need to keep as list. Then

          Pay

          : - The estimated base salary range for this role is: $180,000 USD - $190,000 USD - Also include the explanatory paragraph about compensation range being broad, etc. We'll keep that as a

          maybe. We should not include Schedule. Now we need to ensure we didn't miss any substantive info like "You will report into the CEO and work across every department." That's part of About the role? Actually appears earlier: "You will report into the CEO and work across every department. You will have the access and sponsorship to make changes stick." That is under About Karbon? Actually after "About Karbon" paragraph, there is a paragraph: "The next phase is scale. We need one person whose entire job is extending what we have built, measuring what it returns, and adding the next layer of capability. Not a strategy deck. A working system, the governance that makes it trustworthy, and the numbers that prove it. You will report into the CEO and work across every department. You will have the access and sponsorship to make changes stick." This is part of the role description; we should include it maybe in About the role intro paragraph. Thus we need to incorporate that into About the role section maybe as a

          before the list. Let's restructure: After company description

          , we have

          About the role

          with a

          containing: "You will report into the CEO and work across every department. You will have the access and sponsorship to make changes stick. The next phase is scale. We need one person whose entire job is extending what we have built, measuring what it returns, and adding the next layer of capability. Not a strategy deck. A working system, the governance that makes it trustworthy, and the numbers that prove it." Then the

          list of responsibilities. Now we need to ensure we didn't duplicate content. Let's craft final HTML. We must output only HTML fragment, no /, no markdown. Let's write:

          Karbon is the global leader in AI-powered practice management software for accounting firms. We provide an award-winning cloud platform that helps tens of thousands of accounting professionals work more efficiently and collaboratively every day. With customers in 40 countries, we have