Skip to main content
§ Product

HR Operations AI

An AI layer over the People-Ops workflows — resume screening with bias-audit, interview scheduling, draft generation for employee communications, onboarding workflow automation. Integrates with the existing ATS and HRIS.

Engagement
6–10 week build · ongoing operation
Built for
Heads of People · TA leads · People ops
§ Problem

People ops accumulates routine work — resume screening for the high-volume reqs, interview scheduling across calendars, employee communications drafted from templates, onboarding workflows that should be automated and aren't.

What this is

A People-Ops augmentation engagement. Four components:

  • Resume screening. Per-req screening model with bias audit. Produces ranked list for the hiring manager.
  • Interview scheduling. Cross-calendar coordination, panel-building, candidate-side flexibility.
  • Communications drafting. Routine employee comms drafted from templates and trained patterns. Sensitive comms surfaced for human authoring.
  • Onboarding automation. Workflow orchestration across the systems involved (IT provisioning, payroll setup, document collection, training enrollment).

How it's built

LightGBM with monotonic constraints for the screening layer (interpretability matters for bias defense). Calendar-integration for scheduling. LLM layer for drafting. Workflow orchestration (Temporal-class for the complex onboarding pipelines) integrated with the HRIS and ATS.

What you get

  • The screening pipeline with bias-audit documentation.
  • The interview-scheduling layer.
  • The communications-draft system with review workflow.
  • The onboarding workflow automation.
  • Quarterly bias-audit refresh and model retraining.
§ How we engage

Engagement is shape, not list.

Length and price are functions of the data and the destination. The shape below is the typical engagement.

Length
6–10 week build · ongoing operation

Scoped during the discovery call against the actual data and the operation it integrates with.

Lead
Bogdan

Principal engineer. Architecture and most code ships through one keyboard.

Cadence
Async, weekly

Written updates between, calls when the decision needs the room.

Bar
Production

Async correctness, capacity under burst, observability at every boundary.

§ Questions

What buyers ask about this one.

  • How do you handle bias in resume screening?

    Carefully and explicitly. The screening model is audited for bias against the standard protected-class proxy variables. Demographic correlations get surfaced and pruned. The screening produces a ranked list with confidence; the hiring manager makes the decision. We document the bias-audit methodology per engagement.

  • What about candidate experience?

    Configurable. Some businesses prefer fully-automated scheduling and standard responses; others prefer all candidate-facing communications human-reviewed. The engagement scopes the candidate-facing posture during discovery.

  • What HRIS systems do you integrate with?

    Workday, BambooHR, Rippling, Gusto, Justworks, plus custom platforms via standard API. The ATS layer (Greenhouse, Lever, Ashby) integrates separately.

  • Does it draft performance reviews or other sensitive communications?

    It can draft routine ones (offer letters, onboarding emails, policy reminders, anniversary notes). For sensitive communications (performance feedback, terminations, escalation responses), the engine surfaces the structure but the People-team writes the substance. We're explicit about where the line is.

  • Pricing?

    Scoped to employee count, hiring volume, and integration depth. Discovery call covers all three.

§ The next step

If the deliverable matches the gap, the next step is one call.

We'll scope length and price against your data and the operation it integrates with. No retainer, no fishing.

Bogdan and team · async-first · OP—2026