Zita — LLM-powered AI recruitment platform with the bias audit built in

AI Recruiting Platform · Resume Parsing · Semantic Matching · Bias-Aware Ranking · AI Interview Questions · Applicant Tracking

Sense7ai engineered the AI layer powering Zita's recruitment and applicant tracking platform. Eight engines: resume parsing, LLM-based semantic candidate-job matching with feature-level Match Analysis, bias-aware ranking, AI-generated job descriptions and interview questions, candidate profile intelligence, pipeline analytics, and a public REST API.

Built for recruitment teams, agencies, and hiring managers who need to move from 'lots of applications' to 'the right candidate' — without losing fairness, explainability, or speed.

At a glance

A Sense7ai ProductLive · production
Zita
AI recruiting platform with applicant tracking (zita.ai) — Product engineering on the AI feature surface
AI engines delivered
Resume parsingSemantic matchingBias-aware rankingAI JD generatorAI interview question generatorCandidate profile intelligenceAnalytics & ReportingAPI Suite
Stack
TypeScript (React)Python (Django, scikit-learn, sentence-transformers)MySQLOn-premise private cloud (Zita)
Privacy controls in scope05
On-premise private cloud
Automated-decision transparency
Bias audit hooks
Eval-suite release gating
Encryption + RBAC
Constraints

The challenges

Recruitment software lives in tension. Recruiters need to move faster than the volume of applications allows; candidates expect to be treated as more than rows in a database; hiring managers need a decision they can defend; and the whole system has to operate without amplifying the biases that human-only hiring already carries. Most applicant tracking systems solve one of these problems and quietly degrade the others. Zita was built to solve them together — which raised the engineering bar substantially.

CONSTRAINT-01Non-negotiable
REQ

Parsing has to be reliable, not just clever.

NOTE

Resume parsing that gets the easy resumes right and the unusual ones wrong is worse than no parsing at all — it teaches recruiters to distrust the system on exactly the candidates who most need fair evaluation.

CONSTRAINT-02Non-negotiable
REQ

Matching has to be semantic, not keyword.

NOTE

Hiring is full of synonyms, near-equivalents, and adjacent experience. A model that scores 'Python developer' and 'backend engineer with Python' as different candidates fails the job.

CONSTRAINT-03Non-negotiable
REQ

Bias has to be addressed in the pipeline, not in a disclaimer.

NOTE

Saying 'we use AI fairly' doesn't make a system fair. Fairness has to be testable, traceable, and observable at the decision point — and the audit has to be conductable by recruiting leadership, not just engineering.

Audience

Who this is for

VerticalsIn-house Talent Acquisition · Staffing & Recruiting Agencies · RPO Providers · High-volume Hiring.

WorkflowsResume parsing · Candidate sourcing · Semantic matching · JD writing · Interview prep · Bias audit · Pipeline reporting.

RolesRecruiters · Talent Acquisition Leaders · Hiring Managers · HR Operations · DEI Officers · Recruitment Engineering.

FitTeams hiring at volume who need explainable AI in the candidate evaluation pipeline — and treat bias, fairness, and data subject rights as engineering requirements, not press releases.

The platform

Eight AI engines, all live — seven in the platform, one as a REST API.

Engineered into Zita's recruitment and applicant tracking surface — usable standalone inside Zita, or embeddable into any operator's existing ATS via the public REST API.

Resume Parsing Engine

Live

Structured extraction of contact, experience, education, skills, certifications, and project history from PDF, Word, and image-based résumés. Built to handle non-standard formats, cross-region templates, and the long tail of formatting choices candidates actually use. Output is a typed, structured profile downstream systems can rely on.

See it on zita.ai →
PDFWordImage OCR

AI Job Description Generator

Live

Generates role-specific job descriptions from a brief, with field-level controls — must-have skills, nice-to-haves, seniority, working style. Designed so a recruiter can publish a credible job post in minutes without losing the company's voice or compliance-relevant language.

See it on zita.ai →
Role-specificField-level controls

Semantic Candidate–Job Matching

Live

Candidate-to-role matching that combines LLM-based ranking with vector embeddings, scoring each candidate against the parsed requirements of the job — skill, experience, and qualification dimensions weighted independently. Returns a relevance score plus detailed Match Analysis explaining which dimensions matched and which did not.

See it on zita.ai →
LLM rankingVector embeddingsMatch Analysis

Bias-Aware Ranking

Live

A scoring layer that holds the relevance assessment separate from protected-attribute proxies. Runtime audit hooks expose the features influencing each score so fairness reviews can be conducted by recruiting leadership, not just engineering.

See it on zita.ai →
Fairness audit hooks

AI Interview Question Generator

Live

Role-specific question generation across three categories — General Proficiency (suitability and culture fit), Behavioural Analysis (problem-solving and soft skills), and Technical Acumen (specific technical skills for the role). Questions are tailored to the candidate's parsed profile and the role's posted requirements; complexity is adjusted to candidate seniority.

See it on zita.ai →
GeneralBehaviouralTechnical

Candidate Profile Intelligence

Live

A consolidated candidate view that surfaces parsed profile data, match analysis, interview history, scoring, and messaging in a single workspace. Designed for the recruiter who is hiring twenty roles at once and needs context per candidate without context-switching.

See it on zita.ai →
Unified workspace

Analytics & Reporting

Live

Real-time hiring pipeline metrics — pipeline velocity, source effectiveness, conversion by stage, time-to-hire — surfaced through customisable reports for recruiting leadership.

See it on zita.ai →
Pipeline velocityTime-to-hire

API Suite

Live

Every engine above, exposed as a permissioned REST API. Operators wire Zita's intelligence directly into the ATS, HRIS, or recruiting workflow they already run — without adopting Zita's full UI surface. Single-call endpoints with structured JSON I/O; multipart upload for binary inputs (résumés, JDs).

View API docs →
Resume ParserJD ParserJD GenerationAI Matching AnalysisComparative AnalysisAI Interview Question GenerationProfile Summary
Operating principles

Engineering invariants

Properties that hold across every AI engine, every release, and every customer — what the platform commits to, regardless of feature roadmap.

Reliability

Parsing reliability before parsing cleverness.

Tested
Parser output instrumented against a held-out test set covering non-standard layouts, language variants, and image-based resumes.
Shipped
Extraction-logic improvements ship only after the test set passes.
Commitment
The parser does not get the unusual resumes wrong — those are the candidates fairness depends on.
Explainability

Explainable matching, not black-box scoring.

Embedded
Vector embeddings score each candidate against parsed job requirements with skill / experience / qualification weighted independently.
Explained
Every score carries feature-level Match Analysis — readable by a recruiter without engineering escort.
Commitment
A hiring manager can answer 'why this score?' without an engineer in the room.
Fairness

Bias and fairness as a first-class engineering concern.

Separated
Relevance assessment held separate from protected-attribute proxies; runtime audit hooks expose feature influence per score.
Reviewed
Audit-hook surface designed for recruiting leadership and DEI officers, not just engineering dashboards.
Commitment
Fairness is observable at the decision point. The audit is not a press release.
Gating

Eval-suite gating on every AI feature.

Gated
Every AI engine ships behind an evaluation harness — regression, fairness, and adversarial-input behaviour.
Released
CI/CD blocks the release if any gate fails. Zero AI features ship without passing all three.
Commitment
The eval suite is the line between merge and production — not a milestone before launch.
Engagement model

How we worked

TeamFull Stack and Platform Engineers maintain the runtime and pipeline surfaces. Dev / Cloud / MLOps Engineers manage the CI/CD pipeline. QA Engineers manage overall QC and assurance. ML Engineers build, train, and test ML/DL models, embeddings, fairness, and accuracy. Annotators gather and label all training, testing, and validating data — the Source of Truth (SoT) the platform's behaviour is measured against.

StackTypeScript (React) for workbench surfaces. Python (Django, scikit-learn, sentence-transformers, embedding models) for AI engines and the application backend. MySQL for data. Deployed in Zita's on-premise private cloud — Sense7ai designed and configured the platform-level security controls (encryption at rest, TLS, RBAC); Zita operates the underlying infrastructure.

Privacy controls built into the platform

  • Deployment model — On-premise private cloud in Zita's environment. Candidate data does not leave Zita's controlled infrastructure.
  • Encryption + access control — AES-256 at rest, TLS 1.2+ in transit. Role-based access with audit logs on every read of candidate PII.
  • Data subject rights — Access, erasure, and portability workflows for the candidate; consent capture with revocation hooks that propagate to active processing.
  • Automated-decision transparency — Every relevance score carries feature-level Match Analysis explaining which dimensions matched, which did not, and why.
  • Bias / fairness audit — Runtime audit hooks expose feature influence per score; pre-deployment fairness assessments + adversarial-input tests gate every release.
How Zita compares

Zita vs. AI in the recruiting market

Compared against Eightfold AI, Greenhouse, Manatal, and Workable — by the criteria a recruitment buyer who cares about explainability and bias evaluates. Read as: what's native to the platform, what's partial or requires an add-on, and what isn't there at all.

CriterionZitaEightfold AIGreenhouseManatalWorkable
Explainable AI scoring — feature-level reason per matchFullPartialPartialPartialPartial
Bias / fairness audit hooks accessible to recruiting leadership (not only engineering)FullPartialPartialNot nativePartial
Eval-suite gating on every release — regression, fairness, adversarialFullPartialNot nativeNot nativeNot native
Resume parsing for non-standard formats + image-based résumés (OCR)FullFullPartialFullFull
Semantic candidate-job matching with dimension-level weights (skill / experience / qualification)FullFullPartialPartialPartial
AI job description generator with field-level controls (must-have, nice-to-have, seniority)FullPartialPartialFullFull
AI interview question generator across General / Behavioural / TechnicalFullPartialNot nativePartialPartial
Candidate Profile Intelligence — match analysis surfaced in a unified workspaceFullFullPartialPartialPartial
Data subject rights workflows built-in (access · erasure · portability · consent)FullPartialFullPartialFull
Automated-decision transparency — feature-level explanation for every relevance scoreFullPartialNot nativeNot nativePartial
On-premise private-cloud deployment — candidate data never leaves the operator's controlled infrastructureFullNot nativeNot nativeNot nativeNot native
Every AI engine exposed as a public REST API for embedding into an existing ATS / HRISFullPartialPartialPartialPartial
Full
Native and available out of the box.
Partial
Limited scope, in preview, or via add-on.
Not native
Not part of the stated platform capability.

Comparison is the authors' interpretation based on publicly available product documentation as of June 2026. For independent, vendor-neutral context, see G2's recruiting software category and Gartner's research on artificial intelligence. Vendor capabilities evolve quickly — verify directly with each vendor for current scope.

Outcomes

Eight AI engines live in Zita. 50% faster resume evaluation. Enterprise-grade AI-based ATS.

Program status · Zita · Live in productionAudited · risk-scaled · evidence-bound
50%
Faster resume evaluation
vs. manual baseline
100%
Decisions audit-readable
Match Analysis on every score
8
AI engines live in production
all under eval-suite gating; all API-addressable
0
Production regressions
through release gates to date

Time-to-hire deltas, source-effectiveness lift, fairness-test pass rates, and customer-attributed numbers are available under NDA and require Zita's written authorisation for publication.

Frequently asked questions

How does Zita's semantic candidate–job matching work?
Vector embeddings of the candidate's parsed profile are scored against the parsed requirements of the job, with skill, experience, and qualification dimensions weighted independently. Every relevance score carries feature-level Match Analysis explaining which dimensions matched and which did not — readable by a recruiter without engineering escort.
How does Zita address bias in AI-assisted hiring?
Bias and fairness are treated as engineering concerns, not disclaimers. The scoring layer holds the relevance assessment separate from protected-attribute proxies. Runtime audit hooks expose the features influencing each score so fairness reviews can be conducted by recruiting leadership, not just engineering. Pre-deployment fairness assessments + adversarial-input tests gate every release.
Can Zita be embedded into my existing ATS, or is it a standalone platform?
Both. Zita runs standalone as a full AI recruiting platform with applicant tracking — or every AI engine can be embedded into an operator's existing ATS / HRIS via Zita's public REST API. The seven AI engines (resume parser, JD parser / generator, AI matching analysis, comparative analysis, AI interview question generation, profile summary) plus pipeline analytics are individually addressable as API endpoints, so an operator can adopt the full Zita surface or selectively wire one or two engines into a system of record they already run.
What résumé formats does Zita's parser support?
PDF, Word, and image-based résumés (OCR). The parser is built to handle non-standard formats, cross-region templates, and the long tail of formatting choices candidates actually use. Output is a typed, structured profile that downstream systems can rely on.
How does Zita handle candidate data privacy?
Zita is deployed in Zita's on-premise private cloud — candidate data does not leave Zita's controlled infrastructure. On top of that hosting posture, the platform ships with engineering controls the operator configures for jurisdiction-specific privacy posture: data-subject access / erasure / portability workflows, configurable retention windows, consent capture + revocation hooks, encryption at rest (AES-256) and in transit (TLS 1.2+), role-based access, audit logs, and automated-decision transparency via Match Analysis explanations.
Where do Zita's LLM inferences run — does candidate data leave the operator's environment?
No. The LLM ranking layer runs on models hosted within Zita's on-premise private cloud. Candidate data — résumés, parsed profiles, match analysis, interview question generation context — is not transmitted to external LLM providers for inference. This is what the on-premise deployment posture is actually for: keeping the most sensitive PII (the candidate's full profile) inside the operator's controlled infrastructure across every engine, including the LLM-based ones.
What stops Zita's AI features from shipping with regressions?
Every AI engine ships behind an evaluation harness that gates each release on regression performance, fairness criteria, and adversarial-input behaviour. CI/CD blocks the release if any of the three gates fail — no AI feature ships to production without passing all three.
Is Zita compatible with the EU AI Act for high-risk AI in HR?
Recruitment AI falls under the EU AI Act's 'high-risk' classification. Zita ships the engineering controls operators configure for EU AI Act compliance: automated-decision transparency via per-candidate Match Analysis explanations (Art. 14 human oversight + Art. 13 transparency), runtime bias / fairness audit hooks accessible to recruiting leadership (Art. 10 data governance), and eval-suite gating on regression / fairness / adversarial behaviour (Art. 9 risk management). Operators retain responsibility for the formal compliance posture — risk management documentation, post-market monitoring, conformity assessment — for their jurisdiction-specific deployment.
What's Zita's pricing and engagement model?
Zita's commercials are quoted per operator engagement — variables include deployment footprint (on-premise infrastructure scale), the set of AI engines under contract, and API call volume across the engine surface. Engagements are governed by a written master services agreement; typical timeline from first contact to a written proposal is five to seven business days following a scoping call.

Put Zita's AI engines to work in your recruiting stack.

Use Zita standalone as a full AI recruiting platform, or embed individual engines — resume parsing, semantic matching, AI interview question generation, candidate profile intelligence — into an existing ATS via Zita's API. Qualified inquiries: same-day or next-business-day response. Scoping calls within five business days.

Schedule a scoping callVisit zita.ai →