AI Operations Lead

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. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Must not include filler like "commensurate with experience". Must not create sections unless posting has real specific content. We need to parse the posting. First part: About Karbon (company description) – not needed as a section? Could be part of About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include those that have real specific content. We need to extract content for each. Let's read posting: - About Karbon (company overview). Not needed as a section but could be part of About the role? The "About The Role" heading appears later. - About The Role: includes Build the Tooling, Own Governance and Visibility, Train Teams and Set the Standard, Measure and Report the Return. That's responsibilities. - About You! (requirements/qualifications/skills). Contains bullet-like paragraphs. - What Success Looks Like! (maybe could be part of responsibilities or expectations, but not a standard section; we could treat as part of Responsibilities or maybe as "What Success Looks Like" not in list; we should not create a section unless matches one of allowed headings. So we could incorporate into Responsibilities or maybe omit? But we must preserve ALL substantive information; we cannot drop it. So we need to embed that info somewhere appropriate, maybe under Responsibilities or a separate section like "Expectations". But only allowed headings are those listed. We could put it under Responsibilities as part of the role description. Or we could create a section "What Success Looks Like" but that's not allowed per instruction (they gave examples but said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings; we should not create other headings. So we must fit that content into one of those sections. - Why Work at Karbon? (benefits). That maps to Benefits. - Compensation range: Pay. - Schedule? Not mentioned explicitly; maybe remote/hybrid? Not given. So we should not create Schedule section if no specific content. - Requirements: maybe from About You! includes required experience: shipped production software, Python/TypeScript, SQL, REST APIs, built something on LLM, worked with non-technical teams, etc. That's requirements. - Qualifications: maybe similar; but we could split: Requirements = mandatory, Qualifications = preferred? The posting includes "Bonus Points" which could be Qualifications. So we can have Requirements (mandatory) and Qualifications (bonus/preferred). Skills maybe also separate but could be covered. We need to avoid filler like "commensurate with experience". Not present. We must not include boilerplate like EEO etc. The posting includes diversity statement at end; that's boilerplate EEO; we must remove it. Also the scam warning about email domain; that's also boilerplate; remove. Also the note about agency referrals; remove. We must preserve all substantive information: company description maybe not needed but could be part of About the role? The instruction says 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. The company description is not a heading; we could include it as a paragraph before sections? The instruction says output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid extra paragraphs outside sections. But they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. So we can have prose paragraphs outside sections? Probably better to wrap everything in sections; but we can have an introductory paragraph about the company under About the role? Actually About the role section should describe the role. The company overview could be placed in a short

  before the first heading or as part of About the role? The instruction says "About the role" heading for section headings. So we could have

  About the role

  and then include the company overview as part of that section's prose? Might be okay. But we must not repeat the job title; we don't have it. Let's extract content: **About the role** (the role description): - 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. Karbon runs its own MCP server. You extend it into a routing proxy that sits between Claude and every internal data source teams need. Authentication via Okta. RBAC enforcement by department. Request logging for spend attribution and audit. Once the gateway is approved by Security, new connectors plug into a config entry instead of triggering a full review each time. That is your first thirty days. - After that: CS gets a renewal risk signal. Sales gets a proposal draft automation. Implementation gets a SOW generator with scope-creep flags. Support gets a ticket triage router. Prototype fast. Harden what people use. Delete what they ignore. Hand every tool to an owner in the team that uses it. You build it. They run it. - Own Governance and Visibility: Manage the Claude access and provisioning workflow — seat requests, model and tool access, connector approvals — and the Slack workflows that support it. Run the connector security review pipeline in partnership with Security. Own the spend dashboard across all AI tools, not just Claude. Cursor, Codex, Linear AI, and anything else the org is running sit alongside Claude in one view. Department leaders see their own number weekly without asking you to pull it. Bad trends surface before they become invoice surprises. Extend that visibility into an ROI framework: adoption rate, hours saved, cost per seat, project-level impact. Partner with Finance on budget accountability. Run the AI champions program. Fourteen department champions, organized into pods, own peer enablement and skill submissions within their teams. You run the cadences, maintain the hub pages, and hold champions accountable for engagement. When people leave Karbon, their projects and skills do not leave with them. You own the offboarding flow that captures and reassigns that work. Build and maintain the AI wiki — per-department documentation of tools, active use cases, and skills in use. Keep it current as tools evolve. - Train Teams and Set the Standard: Work with each department lead to agree how their team uses AI, then hold that standard. Run practical training. Short, specific, and repeatable. Teach people the efficient way to get the same answer. Most cost problems are habit problems. After month one, you know what each team's workflows look like because you built them. That makes you a better trainer than anyone who has not. Build and maintain a shared library of prompts, skills, and patterns so knowledge stays when a person leaves. Own the pipeline that moves skills from intake through review to the shared library — and automate the parts of it that should not require a human. - Measure and Report the Return: Define the small set of metrics that show whether AI is working: cost, adoption, delivery, and quality. Build the data pipelines behind those metrics. Expect the source data to be messy. Publish a regular report to the executive team. Same format every time. Bad news included. Delete any metric that has not changed a decision in a quarter. **About You! (Requirements/Qualifications/Skills)**: - 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. **What Success Looks Like!** (could be part of Responsibilities or maybe a separate section but we can incorporate into Responsibilities as expected outcomes). We'll embed under Responsibilities maybe as a subsection. **Why Work at Karbon? (Benefits)**: - 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 **Pay**: - The estimated base salary range for this role is: $180,000 USD - $190,000 USD - Also note: base salary is one component of total compensation package, which may include target bonus, competitive equity grant, generous benefits. But we should not include filler like "not typical for a candidate to be hired at or near the top". That's maybe filler but still substantive? It's commentary; we could keep it as it's part of compensation description. However instruction: "Do NOT repeat the job title as a heading ... fold minor metadata into a short

  or drop it." This is not metadata; it's compensation description. We can keep it but avoid fluff like "While we believe competitive compensation is a critical aspect...". That's maybe boilerplate; we should remove boilerplate. The paragraph about compensation includes some fluff; we need to keep substantive info: the range, that base salary is one component, may include target bonus, equity grant, benefits. The rest about mission etc is fluff; we can drop. **Schedule**: Not mentioned; we should not create Schedule section. Now we need to output HTML fragment with sections. We'll have:

  About the role

  ... (company overview maybe?) Actually we could include company overview as a short paragraph before the responsibilities list. But the instruction says use

  for prose. We'll put company overview in a

  under About the role? Or we could have a separate

  before the heading? Probably better to include it under About the role as part of the role description. We'll structure:

  About the role

  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