Staff Operations AI Engineer
Checkr, Inc. · Denver, CO · 1 mo ago
$150k–$176k/yrFull-time
We need to output HTML fragment with sections: About the role (but note "About The Role" heading). Use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info.
We need sections only when posting has real specific content. We have:
- About Checkr (company description) maybe not needed? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must include About Checkr, but we can include if it's substantive. However they gave examples of headings; we can include other headings if appropriate? Probably we should stick to those headings if content matches. The posting includes "About Checkr" which is company overview; could be considered "About the role"? No, that's separate. Might be okay to include as a section with heading About Checkr
. But they didn't list that as example; but they said "e.g." not exclusive. Safer to include only those headings that have content: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (the "About The Role" paragraph). Responsibilities: "What You’ll Do" with bullet-like paragraphs. Requirements: "What You Bring" includes Required Experience etc. Qualifications maybe overlapping; but we can treat Required Experience as Requirements, and "Nice-to-Have Experience" as Qualifications or Skills. Skills: maybe list specific skills. Benefits: "What We Offer". Pay: salary ranges. Schedule: "Individuals are expected to work from the office 3+ days a week." plus hub locations etc. That's schedule info.
We must not include filler like "commensurate with experience". Not present.
We need to remove duplicated lines, boilerplate like Equal Employment Opportunities, Applicant Privacy Policy, etc. Also remove "Pay Transparency Disclosure" maybe keep as part of Pay? It's about pay transparency; we can keep the salary ranges but discard the explanatory text? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the pay transparency disclosure text as it's substantive? It explains how ranges are determined. Might be considered substantive. However they said to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Pay transparency disclosure is not exactly that; it's about compensation philosophy. Might keep.
We also need to remove duplicated lines. There's some duplication: "On-target Earnings OR Base Salary range (Denver, CO) $150,000—$176,000 USD" and similar for Nashville. Keep both.
Now structure:
About the role
We're looking for a Staff Operations AI Engineer who will architect, build, and refine the intelligent systems that power Checkr’s AI-driven operations. In this role, you'll be the technical expert responsible for designing the integrations, workflows, and data structures that enable AI Agents and automation to operate reliably at scale. You’ll work across system integration, workflow orchestration, application logic, data transformation, AI guardrails, and multi-platform automation—translating leadership’s strategic direction into high-quality technical execution. You’ll own complex, high-impact projects end-to-end, serve as a technical authority across teams, and develop robust systems that materially improve operational efficiency and AI performance.
Then Responsibilities: maybe heading Responsibilities
with - items from "What You’ll Do". The text includes several paragraphs each starting with a bold heading? Actually it's:
"What You’ll Do
AI Agent Integration & Automation Architecture
Design and own the integration architecture that enables AI Agents to operate safely and reliably across Checkr systems and third-party platforms.
Build production-grade API integrations with secure authentication flows, webhook and event-driven patterns, and robust automation workflows that coordinate actions across tools like Zendesk, Salesforce, and internal services.
Ensure AI-driven operations are resilient through strong error handling, retries, observability, and fallback mechanisms.
Proactively identify integration gaps, system bottlenecks, and failure modes, and lead the technical solutions that improve reliability and scale.
Systems Engineering & Data Foundations
Build and maintain the technical foundations that power AI-driven workflows, including structured data pipelines, normalized schemas, and predictable JSON inputs for LLMs.
Establish engineering standards for workflow design, code quality, and system observability.
Communicate architecture clearly through documentation and diagrams, and serve as a technical authority across teams to ensure consistent, high-quality execution.
AI Quality, Safety & Guardrails
Implement guardrails, validation rules, and safety checks that ensure AI Agents act responsibly and accurately in production.
Evaluate model output quality and continuously refine prompts, transformations, and logic to improve consistency, reliability, and trust in AI-driven decisions."
We can turn each bullet into
- . Might group under subheadings? But we only need
- . Could just list each sentence as
- . Might be long but okay.
Then Requirements: heading
Requirements
with - from "What You Bring Required Experience". List each bullet.
Then Qualifications: maybe from "Nice-to-Have Experience". Use
Qualifications
with list.
Skills: maybe we can extract specific skills: JavaScript, Python, SQL, Snowflake, OAuth, webhooks, etc. Could be under Skills heading.
Benefits: heading Benefits
with list from "What We Offer".
Pay: heading Pay
with paragraphs for each location range plus pay transparency disclosure.
Schedule: heading Schedule
with paragraph about in-office expectation 3+ days a week, hub locations, relocation stipend, in-office perks.
We must not repeat job title as heading. Not include Job ID.
We must not include boilerplate like Equal Employment Opportunities, Applicant Privacy Policy, Legitimate Checkr emails, etc. Remove those.
Now produce HTML fragment.
Let's craft.
Check for duplication: The "About Checkr" paragraph at start is company overview; we might omit because not in list of headings. Could include as a separate section but not required. Safer to omit to keep to specified headings. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we can stick to those.
Thus we will not include About Checkr.
Now produce.
Let's write the HTML.
Be careful to escape any special characters? Not needed.
We'll output:
About the role
...
Responsibilities
- Design and own the integration architecture that enables AI Agents to operate safely and reliably across Checkr systems and third-party platforms.
- Build production-grade API integrations with secure authentication flows, webhook and event-driven patterns, and robust automation workflows that coordinate actions across tools like Zendesk, Salesforce, and internal services.
- Ensure AI-driven operations are resilient through strong error handling, retries, observability, and fallback mechanisms.
- Proactively identify integration gaps, system bottlenecks, and failure modes, and lead the technical solutions that improve reliability and scale.
- Build and maintain the technical foundations that power AI-driven workflows, including structured data pipelines, normalized schemas, and predictable JSON inputs for LLMs.
- Establish engineering standards for workflow design, code quality, and system observability.
- Communicate architecture clearly through documentation and diagrams, and serve as a technical authority across teams to ensure consistent, high-quality execution.
- Implement guardrails, validation rules, and safety checks that ensure AI Agents act responsibly and accurately in production.
- Evaluate model output quality and continuously refine prompts, transformations, and logic to improve consistency, reliability, and trust in AI-driven decisions.
Requirements
- 5-7+ years in automation platforms, integration architecture, or AI-enabled operations
- Deep expertise in API design, OAuth/token-based authentication, webhooks, and event-driven systems
- Proven experience building reliable automation workflows with observability, retries, and failure handling
- Strong JavaScript and Python expertise for backend logic, scripting, and internal tooling
- Solid SQL experience for data transformation, validation, and operational analytics (Snowflake a plus)
- Advanced comfort with JSON, schemas, and data normalization for LLM and automation use cases
- Hands-on experience running LLM-powered agents or automations in production, including guardrails and output validation, with proven experience in prompt engineering frameworks
- Familiarity with integrating with CRM and support systems (e.g., Salesforce, Zendesk)
- An A-player mindset with a strong bias for action: you raise the bar, move with urgency, stay resilient through ambiguity, and take ownership to deliver meaningful outcomes
Qualifications
- Direct experience with Tray.io / Make / Zapier / UiPath
- Programming experience in Python
- Snowflake specifically (vs strong SQL generally)
- Salesforce or Zendesk integrations
- Front-end UI widgets / embeds
- Prior work in operations technology specifically (vs platform, infra, or product engineering)
Skills
- API design
- OAuth/token-based authentication
- Webhooks
- Event-driven systems
- JavaScript
- Python
- SQL (Snowflake a plus)
- JSON, schemas, data normalization
- LLM-powered agents, guardrails, output validation, prompt engineering
- CRM and support system integration (Salesforce, Zendesk)
- Workflow observability, retries, failure handling
- Technical documentation and diagramming
Benefits
- Fast-paced and collaborative environment
- Learning and development allowance
- Competitive cash and equity compensation, and opportunity for advancement
- 100% medical, dental, and vision coverage
- Up to $25K reimbursement for fertility, adoption, and parental planning services
- Flexible PTO policy
- Monthly wellness stipend
- In-office perks: lunch five times a week, commuter stipend, abundance of snacks and beverages
- Relocation stipend may be available for those willing to relocate to a Checkr hub location
Pay
On-target Earnings OR Base Salary range (Denver, CO) $150,000—$176,000 USD
On-target Earnings OR Base Salary range (Nashville, TN) $136,000—$159,980 USD
We use geographic cost of labor as an input to develop ranges for our roles and as such, each location where we hire may have a different range. If this role is remote, we have listed the top to the bottom of the possible range, but we will specify the target range for an
for prose. Do NOT repeat job title as heading. Do NOT include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. We need sections only when posting has real specific content. We have: - About Checkr (company description) maybe not needed? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must include About Checkr, but we can include if it's substantive. However they gave examples of headings; we can include other headings if appropriate? Probably we should stick to those headings if content matches. The posting includes "About Checkr" which is company overview; could be considered "About the role"? No, that's separate. Might be okay to include as a section with heading About Checkr
. But they didn't list that as example; but they said "e.g." not exclusive. Safer to include only those headings that have content: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (the "About The Role" paragraph). Responsibilities: "What You’ll Do" with bullet-like paragraphs. Requirements: "What You Bring" includes Required Experience etc. Qualifications maybe overlapping; but we can treat Required Experience as Requirements, and "Nice-to-Have Experience" as Qualifications or Skills. Skills: maybe list specific skills. Benefits: "What We Offer". Pay: salary ranges. Schedule: "Individuals are expected to work from the office 3+ days a week." plus hub locations etc. That's schedule info.
We must not include filler like "commensurate with experience". Not present.
We need to remove duplicated lines, boilerplate like Equal Employment Opportunities, Applicant Privacy Policy, etc. Also remove "Pay Transparency Disclosure" maybe keep as part of Pay? It's about pay transparency; we can keep the salary ranges but discard the explanatory text? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the pay transparency disclosure text as it's substantive? It explains how ranges are determined. Might be considered substantive. However they said to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Pay transparency disclosure is not exactly that; it's about compensation philosophy. Might keep.
We also need to remove duplicated lines. There's some duplication: "On-target Earnings OR Base Salary range (Denver, CO) $150,000—$176,000 USD" and similar for Nashville. Keep both.
Now structure:
About the role
We're looking for a Staff Operations AI Engineer who will architect, build, and refine the intelligent systems that power Checkr’s AI-driven operations. In this role, you'll be the technical expert responsible for designing the integrations, workflows, and data structures that enable AI Agents and automation to operate reliably at scale. You’ll work across system integration, workflow orchestration, application logic, data transformation, AI guardrails, and multi-platform automation—translating leadership’s strategic direction into high-quality technical execution. You’ll own complex, high-impact projects end-to-end, serve as a technical authority across teams, and develop robust systems that materially improve operational efficiency and AI performance.
Then Responsibilities: maybe headingResponsibilities
with- items from "What You’ll Do". The text includes several paragraphs each starting with a bold heading? Actually it's: "What You’ll Do AI Agent Integration & Automation Architecture Design and own the integration architecture that enables AI Agents to operate safely and reliably across Checkr systems and third-party platforms. Build production-grade API integrations with secure authentication flows, webhook and event-driven patterns, and robust automation workflows that coordinate actions across tools like Zendesk, Salesforce, and internal services. Ensure AI-driven operations are resilient through strong error handling, retries, observability, and fallback mechanisms. Proactively identify integration gaps, system bottlenecks, and failure modes, and lead the technical solutions that improve reliability and scale. Systems Engineering & Data Foundations Build and maintain the technical foundations that power AI-driven workflows, including structured data pipelines, normalized schemas, and predictable JSON inputs for LLMs. Establish engineering standards for workflow design, code quality, and system observability. Communicate architecture clearly through documentation and diagrams, and serve as a technical authority across teams to ensure consistent, high-quality execution. AI Quality, Safety & Guardrails Implement guardrails, validation rules, and safety checks that ensure AI Agents act responsibly and accurately in production. Evaluate model output quality and continuously refine prompts, transformations, and logic to improve consistency, reliability, and trust in AI-driven decisions." We can turn each bullet into
- . Might group under subheadings? But we only need
- . Could just list each sentence as
- . Might be long but okay.
Then Requirements: heading
Requirements
with- from "What You Bring Required Experience". List each bullet.
Then Qualifications: maybe from "Nice-to-Have Experience". Use
Qualifications
with list. Skills: maybe we can extract specific skills: JavaScript, Python, SQL, Snowflake, OAuth, webhooks, etc. Could be under Skills heading. Benefits: headingBenefits
with list from "What We Offer". Pay: headingPay
with paragraphs for each location range plus pay transparency disclosure. Schedule: headingSchedule
with paragraph about in-office expectation 3+ days a week, hub locations, relocation stipend, in-office perks. We must not repeat job title as heading. Not include Job ID. We must not include boilerplate like Equal Employment Opportunities, Applicant Privacy Policy, Legitimate Checkr emails, etc. Remove those. Now produce HTML fragment. Let's craft. Check for duplication: The "About Checkr" paragraph at start is company overview; we might omit because not in list of headings. Could include as a separate section but not required. Safer to omit to keep to specified headings. The instruction: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we can stick to those. Thus we will not include About Checkr. Now produce. Let's write the HTML. Be careful to escape any special characters? Not needed. We'll output:
About the role
...
Responsibilities
- Design and own the integration architecture that enables AI Agents to operate safely and reliably across Checkr systems and third-party platforms.
- Build production-grade API integrations with secure authentication flows, webhook and event-driven patterns, and robust automation workflows that coordinate actions across tools like Zendesk, Salesforce, and internal services.
- Ensure AI-driven operations are resilient through strong error handling, retries, observability, and fallback mechanisms.
- Proactively identify integration gaps, system bottlenecks, and failure modes, and lead the technical solutions that improve reliability and scale.
- Build and maintain the technical foundations that power AI-driven workflows, including structured data pipelines, normalized schemas, and predictable JSON inputs for LLMs.
- Establish engineering standards for workflow design, code quality, and system observability.
- Communicate architecture clearly through documentation and diagrams, and serve as a technical authority across teams to ensure consistent, high-quality execution.
- Implement guardrails, validation rules, and safety checks that ensure AI Agents act responsibly and accurately in production.
- Evaluate model output quality and continuously refine prompts, transformations, and logic to improve consistency, reliability, and trust in AI-driven decisions.
Requirements
- 5-7+ years in automation platforms, integration architecture, or AI-enabled operations
- Deep expertise in API design, OAuth/token-based authentication, webhooks, and event-driven systems
- Proven experience building reliable automation workflows with observability, retries, and failure handling
- Strong JavaScript and Python expertise for backend logic, scripting, and internal tooling
- Solid SQL experience for data transformation, validation, and operational analytics (Snowflake a plus)
- Advanced comfort with JSON, schemas, and data normalization for LLM and automation use cases
- Hands-on experience running LLM-powered agents or automations in production, including guardrails and output validation, with proven experience in prompt engineering frameworks
- Familiarity with integrating with CRM and support systems (e.g., Salesforce, Zendesk)
- An A-player mindset with a strong bias for action: you raise the bar, move with urgency, stay resilient through ambiguity, and take ownership to deliver meaningful outcomes
Qualifications
- Direct experience with Tray.io / Make / Zapier / UiPath
- Programming experience in Python
- Snowflake specifically (vs strong SQL generally)
- Salesforce or Zendesk integrations
- Front-end UI widgets / embeds
- Prior work in operations technology specifically (vs platform, infra, or product engineering)
Skills
- API design
- OAuth/token-based authentication
- Webhooks
- Event-driven systems
- JavaScript
- Python
- SQL (Snowflake a plus)
- JSON, schemas, data normalization
- LLM-powered agents, guardrails, output validation, prompt engineering
- CRM and support system integration (Salesforce, Zendesk)
- Workflow observability, retries, failure handling
- Technical documentation and diagramming
Benefits
- Fast-paced and collaborative environment
- Learning and development allowance
- Competitive cash and equity compensation, and opportunity for advancement
- 100% medical, dental, and vision coverage
- Up to $25K reimbursement for fertility, adoption, and parental planning services
- Flexible PTO policy
- Monthly wellness stipend
- In-office perks: lunch five times a week, commuter stipend, abundance of snacks and beverages
- Relocation stipend may be available for those willing to relocate to a Checkr hub location
Pay
On-target Earnings OR Base Salary range (Denver, CO) $150,000—$176,000 USD
On-target Earnings OR Base Salary range (Nashville, TN) $136,000—$159,980 USD
We use geographic cost of labor as an input to develop ranges for our roles and as such, each location where we hire may have a different range. If this role is remote, we have listed the top to the bottom of the possible range, but we will specify the target range for an
- from "What You Bring Required Experience". List each bullet.
Then Qualifications: maybe from "Nice-to-Have Experience". Use