Access: -
Session: -
Mokka System One

System One <> Mokka

Prepared for:Zac Shaw, VP
Date:April 2026
Max Krasnykh
Max Krasnykh
CEO & Founder, Mokka
Zac, good chatting this morning. I pulled together everything we covered, with extra depth on the candidate integrity and AI pre-screen pieces since those map most directly to the IT fraud patterns and federal clearance filtering you described.

Feel free to share this with the recruiting leads before any follow-up call — the sections are built to be skimmed.

Your challenges

Candidate fraud in IT roles

Interview impersonation on remote positions — one person screens, a different person shows up on day one. Missing profile photos used as an improvised fraud heuristic.

Inbound volume burying recruiters

Hundreds of applicants per role, most unfit. Recruiters lose time on the wrong people instead of building relationships with the right ones.

Manual LinkedIn × resume cross-checking

Recruiters hand-verifying profiles against LinkedIn, tab-switching to figure out what unfamiliar companies on a resume actually do. Labor-intensive, doesn't scale with applicant volume.

Federal clearance filtering

Clearance-gated roles attract applicants who don't hold the required level. Another manual screening pass stacked on top of the fraud and fit checks.

Change management with a tenured team

Experienced recruiters with long-established workflows. Adoption of AI tooling has to be earned, not imposed — the rollout matters as much as the product.

Mapped to your challenges

Candidate integrity analytics

Every application is cross-checked against LinkedIn and third-party sources automatically, with IP and metadata signals flagged (e.g., candidate claims India, IP resolves to Russia). Integrity flags are a filterable facet, so recruiters triage the pile in one pass instead of verifying profiles by hand.

Note: Mokka doesn't run government-grade ID verification. If live identity proofing becomes the priority, we integrate with Persona or Clear — we've scoped that layer for other customers.

AI pre-screen interview at the top of funnel

Every applicant gets a structured check-in conversation — voice or chat, your choice — that probes the claims on their resume and collects the data a recruiter would gather on a first call. Answer integrity is scored: generic mirror-the-question answers and claimed experience absent from the resume get flagged. By the time a human recruiter engages, they're engaging a qualified candidate, not triaging a pile.

Standardized, enriched candidate profiles

Every resume is normalized and enriched. Companies on the resume are expanded with what they do, industry, size — no more switching tabs to figure out whether a listed employer is real. Fit is scored across explicit requirements plus industry, growth stage, and culture signals.

Natural-language screening for clearance and fit

Requirements — including clearance level, location, tech stack, or anything specific to a federal req — are pulled automatically from the Bullhorn job and editable in plain English. Knockouts run on submission; job-hopper flags and other patterns fire on autopilot. No rules engine to maintain.

Embedded recruitment engineer for rollout

Enterprise deployments ship with a paired recruitment engineer as a near-permanent member of the team — not a CSM, an operator who works with your recruiters on screening criteria, interview plans, and the change-management gradient with your most tenured folks. The tool lands because someone owns the landing.

Your stack

Mokka sits at the top of your funnel and syncs bidirectionally with Bullhorn. Sourcing, AI pre-screen, and candidate integrity happen in Mokka; everything flows back into Bullhorn for the rest of the recruiter workflow. Requirements and job data are pulled from Bullhorn on day one — no duplicate job entry, no parallel system for recruiters to maintain.

If the team is also evaluating Woo for database freshness, Mokka complements rather than competes: Mokka owns top-of-funnel screening and passive outreach, Woo focuses on keeping existing records current. Both can live alongside Bullhorn.

Getting started

Step 1

Follow-up with your recruiting leads

Walk through the IT and federal use cases with the broader team. We tailor the session to your specific workflows and surface one live req to anchor the trial.

Step 2

Sandbox trial on one live req

Point Mokka at one active IT role — ideally a clearance-gated federal one — for a two-week pilot. Measure integrity flag precision and recruiter time saved on profile verification.

Step 3

Rollout

Full deployment on IT first, with embedded recruitment engineer owning the change-management gradient for your tenured recruiters. Expand to other verticals as it lands.

Ready to take the next step?

Schedule a follow-up or share this room with your team.

Schedule call