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 that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must not create sections with filler like "commensurate with experience". Must include Pay and Benefits only if posting actually states them. The posting includes salary range: "The estimated base salary range for this role is: : $180,000 USD - $190,000 USD". So we can include Pay section with that. Benefits: there is a "Why Work at Karbon?" section listing benefits: Strong benefits package including: Flexible Time Off..., Company paid medical..., Paid dental and vision..., 401(k) with company matching, Flexible Spending Account, Up to 8 weeks paid parental leave, Work-from-home stipend, etc. So we can include Benefits section. Schedule: Not mentioned. So omit. Qualifications: The posting has "About You!" which lists requirements: shipped production software, Python/TypeScript, SQL, REST APIs, built something real on top of LLM, worked with non-technical teams, can build a number out of messy data, run cross-functional program, write clearly, can say no, bonus points etc. That's qualifications/requirements. We can put under Requirements or Qualifications. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have "About The Role" section describing responsibilities: Build the Tooling, Own Governance and Visibility, Train Teams and Set the Standard, Measure and Report the Return. That's responsibilities. So we can have

About the role

maybe but they said About the role heading is allowed. However they also said do NOT repeat the job title as a heading (the page already shows it). So we can have About the role as a heading describing the role overview. Then we can have Responsibilities heading with bullet list of duties. Or we could combine. But they want sections only when posting has real specific content. We have content for About the role (the paragraph about Karbon and the role). Actually the first part "About Karbon" is company overview, not role. Then "About The Role" is a heading in the source. So we can output

About the role

with the paragraph(s) describing the role: "Build the Tooling Ship internal automations..." etc. That is substantive. Then we can have

Responsibilities

with a list of duties: Build the Tooling (list sub-items), Own Governance and Visibility (list), Train Teams and Set the Standard (list), Measure and Report the Return (list). Could also combine but better to separate. Then

Requirements

or

Qualifications

with the "About You!" bullet points. Could split into Requirements (must-haves) and Qualifications (bonus). But we can just have one section Requirements containing all. Then

Benefits

with list from Why Work at Karbon. Then

Pay

with salary range. We must not include Schedule. We must not include filler like "commensurate with experience". Not present. We must remove boilerplate: The sections about diversity, EEO, scam warning, agency referrals, contact email, etc. Also remove "Please be aware that Karbon will only contact you via email..." etc. Also remove "As we hire across various locations..." paragraph about compensation range? Actually we need to keep the salary range but we can discard the surrounding explanatory text about it being broad etc. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the salary range info, but we can discard the fluff around it? The fluff is not substantive? It's explanatory but maybe considered boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The paragraph about compensation range being broad etc is not exactly boilerplate but could be considered fluff. However the salary range itself is substantive. We could keep just the range sentence. The rest is fluff; we can drop it. Also remove "Why Work at Karbon?" heading? We'll convert to Benefits section. We must output only HTML fragment, no markdown fences. Let's craft. Structure:

About the role

... paragraph(s) describing role overview ...

Responsibilities

• 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.

Requirements

• 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.

Benefits

• 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

We must ensure no extra headings like About Karbon etc. We included About the role paragraph summarizing the role overview. Should we include the initial "About Karbon" company description? That's not about the role; it's company overview. Could be considered 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 can have About the role heading that includes both company and role? But they said do NOT repeat the job title as a heading (the page already shows it). The About Karbon section is not a heading; we could include it as a paragraph under About the role. However the About Karbon paragraph is generic company info; maybe we should keep it as it's substantive about the company. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the About Karbon description as part of About the role section. Let's include it as a paragraph(s) under About the role before the responsibilities list. Thus About the role section will have two paragraphs: first about Karbon company, second about the role responsibilities overview (maybe summarizing). But we already have responsibilities list separate. To avoid duplication, we could put the company overview under About the role, and then responsibilities list under Responsibilities heading. That seems fine. Let's craft About the role paragraph:

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 grown into a globally distributed team across the US, Australia, New Zealand, Canada, the United Kingdom, and the Philippines. We