# MinMaxHR: full content for LLMs
> Complete plain-text content of every MinMaxHR resource. Index: https://minmaxhr.com/llms.txt
# Recruiting inside an AI assistant: CandidRanker's MCP integration
URL: https://minmaxhr.com/resources/ai-assistant-recruiting
Category: Workflow reference
Published: 2026-07-09 · Updated: 2026-08-11
The newest recruiting surface is not a dashboard. It is a conversation. CandidRanker ships a Model Context Protocol (MCP) server, so AI assistants like Claude can list your jobs, rank candidates, and pull shortlists on request, with access scoped to one workspace you approve.
CandidRanker's MCP server lets AI assistants like Claude work with your recruiting data conversationally (list jobs, rank candidates, generate shortlists) under OAuth, scoped to a single approved workspace.
## What MCP is, in recruiting terms
MCP, Model Context Protocol, is the open standard that lets AI assistants use external tools safely. CandidRanker exposes its recruiting operations as MCP tools: list jobs, list candidates, rank candidates, and more. Connect it once, and your assistant can answer 'who are the top five for the Bengaluru backend role?' with live data.
## What a recruiter can ask
- List the open jobs in my workspace.
- Rank the candidates for this role.
- Who are the strongest matches, and why?
- Summarize this candidate's fit for the hiring manager.
- Which roles have decisions pending this week?
Each of these maps to a tool on CandidRanker's MCP server, scoped by OAuth to a single workspace.
## How the connection works
In Claude, add CandidRanker as a custom connector using its MCP server URL. Authorization runs over OAuth: you log in to CandidRanker, pick one workspace on the consent screen, and approve the scopes. The token is bound to that workspace and those scopes: switching workspaces means reconnecting, by design.
No API keys are pasted into the assistant. Access is pure OAuth with per-tool controls: most actions start disabled, and the recruiter enables exactly the tools the assistant may use. The same setup works on Claude's mobile apps.
## Why conversational access changes the workflow
Dashboards are where recruiters go; assistants are where work already happens. When the ranking layer is reachable from a conversation, the gap between a hiring manager's question and a data-backed answer drops to seconds: no login, no export, no screenshot.
It works because CandidRanker's governance travels with it: the assistant inherits the same isolation, logging, and no-auto-reject rules as the app.
## The governance model underneath
Conversational access inherits CandidRanker's governance, it does not bypass it. Rankings stay deterministic and explainable. Workspace data stays isolated. Decisions stay with named recruiters. The assistant reads and reasons, but the shortlist remains a human call, logged like every other.
## Beyond MCP: the REST API
For teams wiring CandidRanker into internal tools rather than assistants, the same operations are available over a full REST API with per-workspace API keys. MCP and the API are two doors into the same governed system: data hosted in-region, malware scanning on uploads by default (a workspace setting can disable it, and those files are marked unscanned), per-workspace controls.
## Frequently asked questions
Q: Can I use Claude for recruiting and candidate screening?
A: Yes, by connecting a recruiting system that speaks MCP. CandidRanker by MinMaxHR ships an MCP server, so Claude can list your jobs, rank candidates against a role, and summarize matches, using live workspace data under OAuth-scoped access.
Q: What is an MCP server in recruiting software?
A: MCP (Model Context Protocol) is the open standard for connecting AI assistants to external tools. A recruiting MCP server like CandidRanker's exposes operations (list jobs, list candidates, rank candidates) that an assistant can call on the recruiter's behalf.
Q: How do I connect CandidRanker to Claude?
A: In Claude's settings, add a custom connector with CandidRanker's MCP server URL, then authorize via OAuth: log in, pick one workspace on the consent screen, and approve. The connector then appears in Claude's tools menu. The same flow works on Claude mobile.
Q: Is it safe to let an AI assistant access candidate data?
A: The safeguards matter: CandidRanker uses pure OAuth (no pasted API keys), binds each token to a single approved workspace, starts with most actions disabled until the recruiter enables them, and keeps workspace data fully isolated.
Q: Can the AI assistant reject candidates?
A: No. The assistant reads rankings and reasoning; hiring decisions stay with named recruiters and are logged as such. CandidRanker never auto-rejects, regardless of which surface (dashboard, API, or assistant) is asking.
Q: What can Claude actually do once connected to CandidRanker?
A: The MCP server exposes around 14 tools, including list_jobs, list_candidates, and rank_candidates. Practically: pull the ranked shortlist for a role, ask why a candidate ranked where they did, and get a plain-English fit summary for a hiring manager.
Q: Does the MCP integration cost extra or need engineering work?
A: Connecting is a settings-level task, not an engineering project: paste the MCP URL, authorize with OAuth, enable the tools you want. Custom connectors require a paid Claude plan (Pro, Max, Team, or Enterprise).
Q: What is the difference between the REST API and the MCP server?
A: Same governed operations, two doors. The REST API with per-workspace API keys suits internal tools and integrations; the MCP server suits AI assistants with OAuth consent per workspace. Both inherit the same isolation, logging, and security controls.
Q: Which AI assistants work with CandidRanker?
A: Any assistant that supports remote MCP connectors: Claude (web, desktop, and mobile) today, and the standard is being adopted across the AI ecosystem. The server self-registers via Dynamic Client Registration and uses PKCE.
Q: Why would a hiring team want recruiting data in an AI assistant?
A: Speed of answers. 'Who should I talk to first for this role and why?' becomes a ten-second conversation instead of a login, a filter, and an export, while the ranking, reasoning, and decision governance stay exactly as auditable as in the dashboard.
---
# AI recruitment tools in 2026: what actually helps a hiring team
URL: https://minmaxhr.com/resources/ai-recruitment-tools
Category: Buyer guide
Published: 2026-07-09 · Updated: 2026-08-11
Every recruiting tool now claims AI. The useful question is narrower: which parts of your hiring workflow does AI actually improve, and which tools do it in a way your team can defend? This guide maps the categories and the questions that matter.
The AI recruitment tools worth buying in 2026 automate evaluation work (parsing, ranking, explaining) while leaving hiring decisions with named recruiters.
## The AI recruiting stack, mapped
AI shows up in five places in a hiring workflow: sourcing (finding candidates), screening (reading resumes), ranking (evaluating fit), shortlisting (deciding who to talk to), and analytics (measuring the funnel). Most teams buy sourcing first and regret not fixing evaluation, the step where hours actually go.
MinMaxHR's CandidRanker sits in the evaluation layer of this map: ranking and shortlisting, next to your ATS, not in place of it.
## Where AI helps most: the evaluation step
Sourcing tools add more resumes to the pile. Evaluation tools shrink the pile intelligently. If your recruiters spend evenings reading applications, the highest-return AI purchase is a ranking and shortlisting layer: what MinMaxHR calls a Hiring Decision System, sitting next to the ATS.
## What good AI evaluation looks like
- Ranks against the specific role, not a generic profile.
- Explains every score in recruiter-visible terms.
- Deterministic: same inputs, same score, every run.
- Parses any format: PDF, Word, scanned image, photo.
- Never auto-rejects; the recruiter decides.
- Logs every decision to a named recruiter.
That list is effectively CandidRanker's spec: deterministic scores, visible reasoning, human decisions, logged outcomes.
## CandidRanker: the evaluation layer in practice
CandidRanker, MinMaxHR's flagship tool, ranks every resume against the job description across eight dimensions: skills, experience, tools, education, title, certifications, projects, and semantic fit. Batch upload runs at roughly 100 resumes a minute. One click writes a plain-English match explanation for the hiring manager.
Skill evaluation weights depth and recency, not keyword counts. Employment gaps surface as interview talking points, never penalties. And nothing is auto-rejected: the recruiter owns every shortlist decision, with the full trail logged.
## The analytics layer: numbers leadership asks for
Every shortlist, select, and reject in CandidRanker feeds funnel analytics automatically: decisions per week, time-to-decision, time-to-fill, and pipeline health. Recruiter productivity and bottlenecks become visible without anyone building a spreadsheet.
## AI assistants as a recruiting surface
The newest category: using an AI assistant like Claude as the interface to your recruiting data. CandidRanker ships a full REST API and an MCP (Model Context Protocol) server, so a recruiter can ask an AI assistant to list open jobs, rank candidates, or pull a shortlist: conversationally, with workspace-scoped OAuth access.
## Governance: the question that filters the market
Regulators and internal audit teams are catching up with AI hiring. Tools that auto-reject or cannot explain their scores create liability under GDPR, India's DPDP Act, and emerging AI hiring rules. Explainable, recruiter-governed, fully-logged evaluation is the pattern that survives review.
It is the question CandidRanker is built to answer well: named-recruiter decisions, an append-only audit log, and no automated rejections.
## How to run a two-week evaluation
- Pick one live role with 100+ applications.
- Run your normal manual screen in parallel with the tool.
- Compare shortlists: overlap, misses, and time spent.
- Ask the tool to explain its top and bottom rankings.
- Check the decision log an auditor would see.
CandidRanker's ₹0 free plan (100 resumes, 10 job descriptions) is sized for exactly this kind of trial.
## Frequently asked questions
Q: What are AI recruitment tools?
A: AI recruitment tools apply machine intelligence to hiring workflow steps: sourcing candidates, parsing and screening resumes, ranking candidates against roles, building shortlists, and measuring the hiring funnel. The highest-return category for most teams is evaluation, ranking and shortlisting.
Q: What is the best AI recruitment tool for screening and shortlisting?
A: Look for explainable, deterministic ranking against the specific role. CandidRanker by MinMaxHR scores candidates across eight dimensions with visible per-dimension evidence, processes about 100 resumes a minute, and never auto-rejects. The recruiter keeps every decision.
Q: Do AI recruitment tools replace recruiters?
A: No, well-designed ones move recruiter time from resume scanning to judgment. CandidRanker automates parsing, ranking, and explanation, but every shortlist decision belongs to a named recruiter and is logged that way.
Q: Are AI hiring tools legally risky?
A: Black-box scoring and automated rejection are the risky patterns under GDPR, India's DPDP Act, and emerging AI hiring regulations. Explainable scores, human decisions, and a preserved audit trail are the mitigations, and the features to insist on when buying.
Q: What is an AI resume ranker?
A: An AI resume ranker scores each resume against a job description and returns a prioritized list. CandidRanker's ranking is deterministic and breaks down across eight dimensions, so recruiters see exactly why each candidate ranked where they did.
Q: Can AI recruitment tools work inside Claude or other AI assistants?
A: Yes: CandidRanker ships an MCP (Model Context Protocol) server, so AI assistants like Claude can list jobs, rank candidates, and pull shortlists conversationally. Access is OAuth-scoped to one workspace with recruiter-approved permissions.
Q: What should a small hiring team buy first?
A: Fix evaluation before sourcing. A ranking and shortlisting layer next to your existing ATS collapses screening time immediately and improves shortlist quality, without replacing systems or retraining the team.
Q: How do AI tools measure recruiting performance?
A: CandidRanker logs every decision and turns the log into funnel analytics automatically: decisions per week, time-to-decision, time-to-fill, and pipeline health per role. Leadership sees the numbers without a spreadsheet.
Q: Do AI recruitment tools integrate with an existing ATS?
A: The good ones sit alongside it. The ATS keeps postings, stages, and records; the evaluation layer adds ranking and reasoning. MinMaxHR positions CandidRanker as a Hiring Decision System next to the ATS, not a replacement.
Q: How is candidate data protected in AI recruiting tools?
A: Ask three questions: where is data hosted, who can see it, and what is scanned. CandidRanker hosts data in-region, isolates every workspace, scans uploads for malware by default (a workspace can disable scanning, and those files are marked unscanned), and scopes access per team member with owner-level controls.
Q: How much do AI recruitment tools cost compared to manual screening?
A: Price the recruiter hours: manually screening 300 applications consumes days per role. Ranking that pile takes minutes of machine time. For teams filling many roles, evaluation tooling typically pays for itself on the first few positions.
---
# AI resume screening: what works, what fails, and what to use instead
URL: https://minmaxhr.com/resources/ai-resume-screening
Category: Workflow reference
Published: 2026-07-02 · Updated: 2026-08-11
AI resume screening tools have moved fast, and the reporting on their failures has moved faster. The useful question is not whether to use AI in screening but where AI helps and where it quietly damages your hiring.
AI resume screening works as a prioritisation tool but fails as a decision tool; safe use keeps the recruiter as the shortlist decision-maker and preserves per-criterion reasoning for audit.
## What AI resume screening actually does
An AI resume screener parses resumes into structured fields, compares those fields to a role definition, and outputs a score or rank. Some tools stop there. Others apply a threshold and auto-reject everything below it, which is where most of the documented failures cluster.
CandidRanker is the explainable version of this category: eight visible scoring dimensions instead of a single opaque number.
## Why the bias and bug problem is real
NPR's 2025 investigation found widespread bias and pattern-matching bugs across commercial AI screening tools. The root cause is the training-data shape: models learn the patterns of past hires, including the patterns of past hiring biases. Strong candidates whose resumes don't fit those patterns get silently filtered out before any recruiter sees them.
It is why CandidRanker never auto-rejects and shows its per-dimension reasoning, failures stay visible and correctable instead of silent.
## Where AI screening genuinely helps
Prioritisation, not rejection. When AI ranks 300 candidates against shared role criteria and surfaces the strongest 30 first with visible reasoning, the recruiter starts from a useful foundation. The recruiter still reviews the full pile, but in a sensible order, and no one is filtered out by the model.
This is the slice CandidRanker automates: parsing and ranking at roughly 100 resumes a minute, with humans making every decision.
## The governance bar HR leaders should hold
Three non-negotiables: recruiters make the final shortlist decision, per-criterion reasoning is visible to recruiters and hiring managers, and evaluation history is preserved for audit. Tools that fail any of these create the conditions for both bad hires and regulatory exposure.
CandidRanker was designed to clear this bar by default: determinism, plain-English explanations, named decisions, audit log.
## How MinMaxHR approaches the same problem
MinMaxHR ranks candidates against recruiter-authored role criteria, shows the reasoning for each score, and keeps recruiters as the shortlist decision-maker. No candidate is auto-rejected. Every evaluation is attributable and reviewable. The goal is to remove the screening drag without removing the recruiter from the decision.
## Frequently asked questions
Q: What is AI resume screening?
A: AI resume screening uses machine-learning models to parse and score resumes against a role. It typically ranks candidates and, in some tools, auto-rejects ones below a threshold.
Q: Is AI resume screening accurate?
A: Accuracy depends entirely on the training data and the role. Independent reporting, including NPR's 2025 investigation, has documented widespread bias and bugs in commercial AI screening tools. Accuracy claims should be evaluated per-role, not in aggregate.
Q: Is AI resume screening legal?
A: It is legal in most jurisdictions but increasingly regulated. New York City's Local Law 144, the EU AI Act, and India's DPDP all set expectations around human review, bias audits, and candidate transparency. Tools that auto-reject without recruiter review carry the most exposure.
Q: What are the main risks of AI resume screening?
A: Three: silent bias against under-represented candidates, strong candidates rejected because their resumes don't match training patterns, and shortlists hiring managers cannot defend because the model's reasoning is opaque.
Q: How can AI resume screening be used safely?
A: Use it to prioritise, not to reject. Keep the recruiter as the decision-maker, make the per-criterion reasoning visible, and preserve evaluation history for audit. This is the human-in-loop pattern MinMaxHR is built around.
Q: How does MinMaxHR's approach differ from typical AI resume screening?
A: MinMaxHR ranks candidates against recruiter-authored role criteria and shows the reasoning for each score. Recruiters always make the shortlist decision, no candidate is auto-rejected, and every evaluation is auditable.
Q: Does AI resume screening replace recruiters?
A: It should not. Tools that position AI as a replacement for recruiters tend to produce the worst hiring outcomes and the highest legal exposure. AI should remove screening drag, not decision accountability.
Q: What should HR leaders ask vendors about AI resume screening?
A: Ask: who makes the final shortlist decision, can recruiters see per-criterion reasoning, is any candidate auto-rejected, is evaluation history preserved for audit, and has the model been bias-audited for the role types you hire.
---
# ATS quality scoring and structured hiring readiness
URL: https://minmaxhr.com/resources/ats-quality-scoring
Category: Workflow reference
Published: 2026-07-02 · Updated: 2026-08-11
ATS quality scoring measures how ready your hiring inputs are before ranking begins. JD clarity, criteria coverage, and screening consistency, each made visible as a score. Weak inputs make weak shortlists even with a strong recruiter team; scoring the input layer is how shortlist reliability stops being a guessing game.
ATS quality scoring workflows help recruiters evaluate job description clarity, screening consistency, and structured hiring readiness.
## Why ATS workflows quietly underperform
Most ATS deployments do their job. They organise candidate records and track pipeline stage. What they typically do not do is evaluate whether the inputs feeding those records are strong enough to produce reliable shortlists. Weak inputs silently degrade everything downstream.
CandidRanker's separate ATS quality score (0–100) exists precisely to make this visible before ranking begins.
## The cost of weak job descriptions
A vague or mis-scoped JD widens the funnel in the wrong direction. Candidates self-select badly, recruiters spend more time screening, and shortlists carry more noise than they should. The hiring manager often only realises the JD was the problem after several shortlist rounds.
This is why CandidRanker scores JD readiness before it ranks a single resume. A weak JD caps every match score built on it.
## Why screening inconsistency damages shortlist quality
When screening rules drift between recruiters or between hiring rounds, the same role can produce very different candidate pools. The shortlist looks like a recruiter quality issue, but the root cause is in the screening layer itself.
CandidRanker removes that variance by scoring every resume against the same criteria with the same weights, deterministically.
## Missing or unclear evaluation criteria
Many roles enter the recruiter workflow without explicit criteria. Recruiters then infer criteria from the JD, the hiring manager's comments, and past hires. ATS quality scoring makes the missing criteria visible so the team can fix the inputs before evaluating candidates.
In CandidRanker, criteria live on the job description itself, so every recruiter ranks against the same definition of the role.
## How ATS quality scoring works
MinMaxHR scores the data quality and structure inside the customer's ATS: structural completeness, criteria coverage, and JD-to-record alignment. Recruiters see those signals at the start of every ranking workflow.
## Evaluation readiness, in operational terms
A role is evaluation-ready when the JD is clear, the criteria are defined, the weights are agreed, and the ATS records carry the structure the ranking needs. ATS quality scoring turns 'evaluation readiness' from a vague feeling into a visible signal.
MinMaxHR treats readiness as a number: CandidRanker's ATS quality score tells you whether the inputs can support a reliable ranking.
## Recruiter screening visibility
Recruiters see which roles are strong inputs, which need JD work, and which ATS records carry enough signal to trust. That visibility removes a lot of guesswork from the start of the shortlist workflow.
CandidRanker's audit log gives TA leads exactly this view, who screened what, against which criteria, and when.
## Why this makes ranking reliable
Candidate ranking is only as reliable as the inputs. Strong inputs (clear JD, defined criteria, structured ATS data) produce defensible rankings and shortlists hiring managers can review without re-litigating the basics.
It is the reason CandidRanker's match scores are comparable across recruiters and across weeks: same inputs, same score.
## Operational outcomes
- Weak JDs and missing criteria are caught before they degrade shortlists.
- Recruiters know which inputs to trust before they spend time on ranking.
- Shortlist reliability improves without changing the ATS itself.
- Hiring managers see better first slates because the inputs were cleaner.
Teams running this on the MinMaxHR platform see it as a same-day path from resume pile to defensible shortlist.
## Frequently asked questions
Q: What is ATS quality scoring, in plain terms?
A: ATS quality scoring evaluates whether the data and structure inside the Applicant Tracking System are strong enough to produce reliable shortlists. It surfaces weak job descriptions, missing criteria, and inconsistent screening before they affect hiring outcomes.
Q: Why do strong recruiter teams still produce inconsistent shortlists?
A: Often the recruiter workflow is fine and the inputs are the problem. Weak JDs, missing role criteria, and inconsistent screening rules inside the ATS produce noisy shortlists no matter how careful the recruiter is.
Q: How does poor JD quality affect hiring outcomes?
A: A weak or mis-scoped JD degrades every downstream candidate match. Recruiters work harder, shortlists are noisier, and hiring managers push back more often. All because the role itself was unclear at the start.
Q: What does JD quality analysis actually check?
A: It checks how well the JD maps to the role being hired and to the criteria recruiters intend to rank against: role clarity, criteria coverage, and whether the JD will produce a meaningful candidate match downstream.
Q: How does ATS quality scoring change the recruiter workflow?
A: Recruiters see input-quality signals at the start of every ranking workflow. They know which JDs are strong, which roles are missing criteria, and which ATS records to trust, before they spend time on shortlist work.
Q: Does ATS quality scoring replace existing ATS reports?
A: No. It adds an evaluation-readiness view that ATS reporting typically does not provide. MinMaxHR uses ATS data as input and adds a quality layer on top, without replacing the ATS itself.
Q: What does 'structured hiring readiness' mean?
A: Structured hiring readiness is the degree to which a role is set up to produce a consistent, defensible shortlist: clear JD, defined criteria, agreed weights, recruiter and hiring manager aligned. Scoring it makes the gaps visible early.
Q: How is screening consistency measured?
A: Screening consistency reflects whether candidates for the same role are evaluated against the same criteria. ATS quality scoring surfaces where screening rules are missing, inconsistent, or contradicting the JD.
Q: How does input quality affect explainable ranking?
A: Ranking is only as defensible as the inputs. If a JD is vague, the ranking reasoning becomes vague too. ATS quality scoring keeps the inputs strong so the ranking and shortlist remain explainable to hiring managers and leadership.
Q: Where does ATS quality scoring fit in the overall hiring workflow?
A: It runs alongside structured hiring and candidate ranking. Quality signals appear before the ranking step, the ranking uses recruiter-defined criteria, and the shortlist record preserves the inputs and reasoning together.
---
# Audit-ready hiring workflows and recruiter accountability
URL: https://minmaxhr.com/resources/audit-ready-hiring
Category: Workflow reference
Published: 2026-07-02 · Updated: 2026-08-11
Enterprise hiring is reviewed long after the decision is made: by HR, by leadership, sometimes by auditors. Audit-ready hiring workflows make that review possible without slowing recruiters down.
Audit-ready hiring workflows help organizations maintain recruiter-visible evaluation records, structured shortlist reasoning, and accountable hiring workflows.
## Why governance matters in hiring
Hiring decisions are reviewed long after they are made: when a hire underperforms, when a role is challenged, when leadership asks why one shortlist was preferred over another. Without a structured record, the answers are reconstructed from memory, which neither HR nor leadership find satisfactory.
This is the design brief MinMaxHR builds against: hiring decisions that can be reviewed later without archaeology.
## Recruiter accountability as a workflow property
Every shortlist action is attributable to a named recruiter and a defined criteria set. Accountability is not a separate step or a periodic review. It is a property of how the workflow records itself as recruiters work.
CandidRanker enforces it structurally. Every shortlist decision requires a named recruiter and a reason before it saves.
## Explainable evaluation throughout the workflow
Each candidate ranking carries recruiter-visible reasoning tied to the role criteria. The shortlist record preserves that reasoning, which means later reviewers see exactly what the recruiter saw at the time of the decision.
In CandidRanker, that means eight visible scoring dimensions per candidate, not a single unexplained number.
## Human-reviewed hiring decisions
MinMaxHR prioritises and explains; recruiters always make the shortlist decision. There are no automated rejections, and every decision is attributable to a person rather than to a model.
## What the audit trail captures
- Role criteria, weights, and any mid-hiring revisions.
- Candidate rankings and the reasoning per criterion.
- Shortlist decisions and the recruiter who made them.
- Access history at the role and workspace level.
CandidRanker's audit log records all of it automatically: criteria, rankings, reasons, decisions, timestamps.
## Role-based access and tenant isolation
Recruiters, hiring managers, and administrators see only the data their role requires. Each customer's hiring data is isolated inside their own workspace and never crosses between tenants. Both properties reduce incidental exposure and support enterprise procurement expectations.
On the MinMaxHR platform, this is the workspace model: data scoped to the people who need it, isolated per tenant.
## Policy-aligned candidate evaluation
Organisational hiring policy is encoded into the role criteria themselves. That makes policy alignment a property of every evaluation, not a separate compliance exercise applied after the fact.
CandidRanker implements this by encoding policy into the role criteria every candidate is scored against.
## DPDP-aligned hiring workflows
Organisations operating under DPDP-aligned data governance models increasingly require recruiter-visible hiring workflows, structured evaluation records, and accountable shortlist processes. MinMaxHR fits those expectations into the day-to-day recruiter workflow.
## Procurement-safe hiring infrastructure
Procurement teams ask the same questions every time: who can see what, how decisions are made, how decisions are recorded, and how the workflow holds up under review. An audit-ready workflow turns those answers into evidence drawn directly from the system.
It is why CandidRanker's answers to a security questionnaire (data residency in asia-south1 (Mumbai), tenant isolation, named-recruiter logging) are workflow facts, not promises.
## Operational outcomes
- Hiring decisions remain reviewable months and years later.
- Recruiter accountability is recorded automatically as part of the workflow.
- Procurement and policy reviews become straightforward to support.
- Leadership trust in the hiring pipeline strengthens over time.
These are the outcomes CandidRanker is built to make routine rather than exceptional.
## Frequently asked questions
Q: What does 'audit-ready hiring' actually mean for HR leadership?
A: It means every shortlist decision can be reviewed later with the original role criteria, the ranking, and the recruiter reasoning intact. Leadership and HR can answer 'why was this candidate hired' without reconstructing the process from memory.
Q: Why does recruiter accountability matter at the enterprise level?
A: Enterprise hiring touches policy, fairness, and procurement expectations. When every shortlist action is attributable to a named recruiter and a defined criteria set, the team can answer questions from HR, legal, and leadership without ambiguity.
Q: What is preserved in an audit-ready workflow?
A: The role criteria, the weights, the ranking, the recruiter reasoning, the shortlist decision, and the access history. Together those form a reviewable record of how the hiring decision was made.
Q: Does MinMaxHR make automated hiring decisions?
A: No. Every shortlist decision is recruiter-made. MinMaxHR prioritises and explains; recruiters decide. There are no automated rejections at any point in the workflow.
Q: What is role-based access in this context?
A: Recruiters, hiring managers, and administrators see only the hiring data their role requires. Role-based access keeps candidate information scoped to the people who actually need it and removes incidental exposure.
Q: What does tenant isolation provide for enterprise customers?
A: Each customer's hiring data is isolated from every other tenant. Candidate records, role criteria, rankings, and shortlist decisions stay inside the customer's workspace and never cross between tenants.
Q: How are DPDP-aligned hiring workflows different from generic data practices?
A: Organisations operating under DPDP-aligned governance models increasingly require recruiter-visible hiring workflows, structured evaluation records, and accountable shortlist processes. MinMaxHR is designed to fit those expectations into the day-to-day recruiter workflow rather than treat them as a separate compliance project.
Q: How does policy-aligned evaluation work in practice?
A: Organisational hiring policy is encoded into the role criteria themselves. Every candidate is evaluated against those criteria, and the workflow record shows how policy was applied to each shortlist.
Q: What does 'human-in-loop hiring' mean operationally?
A: CandidRanker supports the recruiter; it does not replace them. Recruiters see the ranking and reasoning, can override at any point, and own the shortlist decision. Every decision is attributable to a person, not to a model.
Q: How does audit-readiness help during procurement reviews?
A: Procurement teams want clear answers on data scope, access, recruiter accountability, and decision visibility. An audit-ready workflow turns those answers into evidence drawn directly from CandidRanker's audit log, rather than into promises.
Q: What if a hiring decision is challenged later?
A: The original role criteria, the ranking, the recruiter reasoning, and the shortlist record remain available. Reviewers can see what the recruiter saw at the time of the decision, which makes a structured response possible.
Q: Does audit-readiness add friction to recruiter workflows?
A: No. CandidRanker's audit trail is a byproduct of the structured evaluation workflow, not a separate step recruiters have to maintain. Recruiters do their normal work; the record assembles itself.
Q: How does MinMaxHR support GDPR-aligned hiring workflows?
A: The same governance properties that support DPDP also support GDPR expectations: recruiter-visible processing, role-scoped access, tenant isolation, and a preserved decision trail.
Q: Is MinMaxHR a compliance certification?
A: No. MinMaxHR provides workflow alignment with DPDP and GDPR expectations. Certification is a separate organisational responsibility; MinMaxHR makes the workflow side of that responsibility much easier to demonstrate.
---
# Auditable hiring workflows that record themselves as recruiters work
URL: https://minmaxhr.com/resources/auditable-hiring-workflows
Category: Governance reference
Published: 2026-07-02 · Updated: 2026-08-11
The hardest audit problem in hiring is the missing record. Auditable workflows solve it by recording criteria, reasoning, and decisions as a byproduct of the recruiter's normal work.
Auditable hiring workflows preserve criteria, ranking, recruiter reasoning, and shortlist decisions as a byproduct of the workflow rather than as a separate logging step.
## Why audit records usually go missing
When audit logging is a separate step, recruiters skip it under pressure. When it is a property of the workflow itself, the record cannot be skipped. It assembles as the work happens.
CandidRanker avoids the problem by making the record a side effect of the work, not a separate task.
## What an auditable workflow records
- Role criteria and any mid-hiring revisions.
- Ranking and per-criterion reasoning for every candidate.
- Recruiter overrides and reasoning notes.
- Shortlist decisions and the named recruiter behind each one.
- Access history at the role and workspace level.
This is CandidRanker's audit log, field for field.
## Auditable by construction
The recruiter never types into a logging form. The workflow itself records each criteria definition, ranking, and shortlist action with the recruiter and timestamp attached.
That is how CandidRanker is built: ranking, reasoning, and decisions land in the log as they happen.
## Reviewer-friendly export
The record is designed for HR, leadership, and audit review: recruiter-legible, criteria-anchored, and structured so reviewers see how each decision was made.
CandidRanker exports this as a one-click report a reviewer can read without a product login.
## Operational outcomes
- Audit records exist for every shortlist by default.
- Recruiters carry no extra logging burden.
- Procurement, policy, and compliance review have direct evidence.
- Hiring decisions stay reviewable months and years later.
On the MinMaxHR platform, audit-readiness costs recruiters nothing extra, the log builds itself.
## Frequently asked questions
Q: What makes a hiring workflow auditable?
A: The workflow records criteria, evaluation reasoning, ranking, recruiter overrides, and shortlist decisions as the recruiter works. Auditability is a byproduct of the workflow, not a separate logging step.
Q: How is this different from audit-ready hiring?
A: Audit-ready hiring is the operational outcome. The record is ready for review. Auditable hiring workflows describe the workflow design that produces that outcome.
Q: What is preserved by an auditable workflow?
A: Role criteria and revisions, ranking and per-criterion reasoning, recruiter overrides, shortlist decisions, access history, and the timestamps that hold those together.
Q: Do recruiters have to maintain the audit record?
A: No. The record assembles itself as recruiters work. There is no separate logging step.
Q: Can the audit record be exported?
A: Yes. The structured workflow record is designed for export to HR, leadership, and audit reviewers in a recruiter-legible format.
Q: How does this support DPDP and GDPR posture?
A: Recruiter-visible processing, role-scoped access, tenant isolation, and a preserved decision trail are exactly the workflow properties those frameworks expect.
---
# Best ATS for small business: an honest 2026 comparison
URL: https://minmaxhr.com/resources/best-ats-for-small-business
Category: Buyer guide
Published: 2026-07-02 · Updated: 2026-08-11
Most 'best ATS' lists rank vendors by who paid for the placement. This one ranks them by fit, which ATS makes sense at which hiring volume and team shape, and where a Hiring Decision System belongs alongside whichever ATS the team picks.
The best ATS for a small business depends on hiring volume and team shape; Workable, Recruitee, JazzHR, BambooHR, and Greenhouse cover the main tradeoffs, and MinMaxHR sits next to whichever ATS is chosen as a Hiring Decision System.
## How to read this comparison
Every ATS on this list is competent. The differences that matter at small-business scale are hiring volume, whether sourcing tools are needed, and whether HR and hiring should share one platform. Match those three to a vendor, ignore the rest of the feature lists.
One note on scope: MinMaxHR is not an ATS. CandidRanker sits next to whichever ATS you pick below, handling the ranking and shortlist-decision layer the ATS leaves open.
## Workable
Strong sourcing tools and a clean candidate inbox. Best for teams that run multi-channel job ads and want sourcing and tracking in one place. Pricing scales quickly with seats, so it suits teams of 5–25 recruiters rather than solo ones.
Pairing note: CandidRanker works alongside Workable. Workable runs the pipeline, CandidRanker ranks the applicants in it with explainable scores.
## Recruitee
Designed around hiring-manager involvement. Best for teams where managers screen candidates directly and need a low-friction interface. Reporting is lighter than Workable's; sourcing tooling is lighter than Greenhouse's.
Pairing note: teams on Recruitee use CandidRanker for the evaluation step Recruitee doesn't rank, resume-to-JD scoring with visible reasoning.
## JazzHR
Lower-cost, focused on small teams. Best for companies hiring under 50 roles a year. The interface is dated but the per-seat cost is the lowest in the category. Integrations are narrower than the mid-market options.
Pairing note: JazzHR plus CandidRanker covers both halves. JazzHR for workflow, CandidRanker for deterministic candidate ranking.
## BambooHR
HRIS-first, with an ATS module. Best when the team wants core HR and hiring in one platform and is willing to accept a less-deep ATS in exchange. Strong for companies that have outgrown spreadsheets but not yet split HR and TA into separate functions.
Pairing note: BambooHR's hiring module handles records and stages; CandidRanker adds the explainable ranking layer on top.
## Greenhouse
Structured-hiring ATS with strong interview scorecards. Best for engineering-heavy hiring at scale. Overkill for small teams; under-used unless the company commits to structured-hiring discipline across the org.
Pairing note: even with Greenhouse's structured interviewing, CandidRanker adds pre-interview resume ranking with per-dimension evidence.
## Where MinMaxHR fits
MinMaxHR is not an ATS and does not try to replace one. It is a Hiring Decision System that sits next to whichever ATS the team picks: adding structured candidate ranking, explainable evaluation, and Quality of Hire reporting. The ATS keeps the workflow; MinMaxHR runs the shortlist decision step.
## Frequently asked questions
Q: What is the best ATS for a small business?
A: There is no single best ATS. The right choice depends on hiring volume, whether the team needs sourcing tools, and whether HRIS and ATS should live in one platform. Workable, Recruitee, JazzHR, and BambooHR cover the main tradeoffs for teams under 200 employees.
Q: Do I need an ATS if I hire only a few roles a year?
A: If you hire fewer than 10 roles a year, a shared spreadsheet and email folder usually work better than an ATS. Above that, the cost of lost candidates and inconsistent shortlists usually outweighs the ATS subscription.
Q: How is MinMaxHR different from these ATS platforms?
A: MinMaxHR is not an ATS. It is a Hiring Decision System that complements an ATS: adding structured candidate ranking, explainable evaluation, and Quality of Hire reporting alongside whichever ATS the team uses.
Q: Can I use MinMaxHR with Workable or BambooHR?
A: Yes. MinMaxHR is integration-ready with major ATS platforms including Workable, BambooHR, Bullhorn, Ceipal, and Workday via implementation engagement.
Q: What features matter most when choosing an ATS for a small business?
A: Three: a clean candidate inbox, a simple way to share candidates with hiring managers, and clear reporting on Time to Hire. Everything else is secondary at small-business scale.
Q: How much does an ATS cost for a small business?
A: Pricing typically ranges from $50 to $500 per user per month depending on features and seat count. The best-ats listicles usually compare list price, but real cost depends on implementation time and how often the team will actually log in.
---
# Best resume screening tools in 2026: five approaches, compared honestly
URL: https://minmaxhr.com/resources/best-resume-screening-tools
Category: Buyer guide
Published: 2026-07-09 · Updated: 2026-08-11
The best resume screening tool depends on what breaks first in your process: volume, consistency, or defensibility. This comparison covers the five approaches teams actually use in 2026 (ATS keyword filters, AI sourcing tools, assessment platforms, black-box AI matchers, and explainable ranking systems) and is honest about where each one wins, including where CandidRanker does not.
One-line answer: if your pain is finding candidates, buy a sourcing tool; if it is testing them, buy assessments; if it is reading hundreds of resumes and defending the shortlist, buy explainable ranking.
## Approach 1: your ATS's built-in keyword filters
Every mainstream ATS (Workable, Greenhouse, Zoho Recruit, JazzHR) ships some form of keyword or knockout filtering. It is free with the ATS, instantly available, and fine for hard disqualifiers like work authorization or licensure. Where it fails is ranking: a keyword filter cannot tell six years of daily Kubernetes from a bootcamp mention of it, and it silently drops strong candidates who phrased a skill differently. If your volume is low and your criteria are binary, this is genuinely enough. You do not need to buy anything.
That gap (ranking, not filtering) is exactly where CandidRanker picks up next to your ATS.
## Approach 2: AI sourcing tools
Tools like hireEZ and SeekOut solve the opposite problem: not too many resumes, but too few. They search the open web and talent databases to find candidates who never applied. They are the right buy when your pipeline is empty. They are the wrong buy for screening. They add candidates to the pile; they do not help you rank the pile you already have.
CandidRanker is their complement, not their competitor: sourcing tools fill the pile, CandidRanker ranks it.
## Approach 3: assessment platforms
TestGorilla, HireVue, and similar platforms test candidates directly: skills tests, work samples, structured video. Direct evidence beats resume claims, and for high-stakes roles assessments are worth the friction. The trade-off is exactly that friction: every assessment costs candidate goodwill and drop-off, so you can only assess a shortlist, not an applicant pool of 300. Assessments come after screening; they do not replace it.
The efficient pairing is ranking first, testing second: CandidRanker narrows 300 applicants to a shortlist worth assessing.
## Approach 4: black-box AI matchers
A large class of tools returns a match percentage with no visible reasoning. Some are accurate. The operational problem is not accuracy. It is that a score nobody can explain is a score nobody can defend to a hiring manager, a rejected candidate, or an auditor. Under India's DPDP Act and GDPR-era scrutiny, 'the model said 82%' is not an answer. If you evaluate a matcher, ask one question first: can a recruiter see why the score is what it is?
That question is the one CandidRanker answers on screen: every score decomposes into eight visible dimensions with plain-English evidence.
## Approach 5: explainable ranking, where CandidRanker sits
Explainable ranking systems score every resume against the specific job description and show the reasoning. CandidRanker scores across eight visible dimensions (skills, experience, tools, education, title, certifications, projects, and semantic fit) deterministically: same resume, same JD, same score, every time. It processes roughly 100 resumes a minute with OCR for scanned files, never auto-rejects anyone, and logs every recruiter decision to a named person.
Where it does not win: CandidRanker does not source candidates, does not run skills tests, and does not replace your ATS. It sits next to one. Teams with five applicants per role do not need it. Its fit is teams screening dozens to hundreds of resumes per role who have to defend the shortlist afterwards.
## The comparison in one pass
- ATS keyword filters: free, binary knockouts only; buy nothing if this is enough.
- Sourcing tools (hireEZ, SeekOut), fill an empty pipeline; do not rank an existing one.
- Assessments (TestGorilla, HireVue): strongest evidence, highest candidate friction; use after screening.
- Black-box matchers: fast scores, indefensible reasoning; risky under DPDP/GDPR review.
- Explainable ranking (CandidRanker): ranks the pile you have, shows why, keeps humans deciding; free plan at ₹0 for 100 resumes.
## Frequently asked questions
Q: What is the best resume screening tool in 2026?
A: It depends on the bottleneck. For empty pipelines, a sourcing tool like hireEZ or SeekOut. For testing a shortlist, an assessment platform like TestGorilla. For ranking a large applicant pool with defensible reasoning, an explainable ranking system like CandidRanker (free plan: ₹0 for 100 resumes and 10 job descriptions).
Q: Is my ATS's built-in screening enough?
A: For binary knockout questions (work authorization, required license) and low volume, yes. ATS keyword filters cannot rank candidates by depth of fit and silently drop applicants who phrase skills differently. That is where a dedicated ranking layer earns its keep.
Q: What is wrong with AI matchers that just give a match percentage?
A: Nothing, until someone asks why. A score without visible reasoning cannot be defended to a hiring manager, a rejected candidate, or an auditor, a growing liability under India's DPDP Act and GDPR. Explainable ranking shows the per-dimension evidence behind every score.
Q: Do resume screening tools replace the ATS?
A: No. The ATS manages workflow: postings, stages, records. Screening and ranking tools sit next to the ATS and handle the decision step. CandidRanker is designed explicitly as that companion layer, not an ATS replacement.
Q: How much does resume screening software cost?
A: ATS filters are bundled free. Sourcing tools and assessment platforms typically run per-seat or per-test subscriptions. CandidRanker prices by volume: Free (₹0 (100 resumes), Growth (₹9,999 per 30-day period) 1,000 resumes), Enterprise (custom, unlimited, with REST API and MCP integration). No auto-renewal.
---
# Bulk resume screening: reviewing hundreds of resumes without burning out
URL: https://minmaxhr.com/resources/bulk-resume-screening
Category: Workflow reference
Published: 2026-07-09 · Updated: 2026-08-11
High-volume hiring has a simple arithmetic problem: fifty open roles, hundreds of applications each, and a screening process designed for one resume at a time. Bulk resume screening fixes the arithmetic, without sacrificing the quality of who gets through.
Bulk resume screening batch-processes entire resume folders in the background, roughly 100 resumes a minute, and returns a ranked, explainable list per role the same day.
## The volume problem, stated plainly
When you are filling 50 roles, not 5, throughput is the metric that matters. A recruiter who manually screens six resumes an hour cannot process a 400-application role this week, so screening quality quietly degrades to skimming, and strong candidates get missed for arithmetic reasons, not judgment reasons.
It is the arithmetic CandidRanker's batch pipeline is sized for: roughly 100 resumes a minute, OCR included.
## Batch upload: drag in the folder
In CandidRanker, bulk screening starts with a folder drag. Files upload instantly and parse in the background at roughly 100 resumes a minute while the recruiter keeps working. Navigate away and back. The count badge updates as the batch completes.
## Parsing the real-world mess
Bulk piles are messy piles: two-column PDFs, Word tables, scanned images, photos of paper resumes. CandidRanker's parsing pipeline reads them all, with OCR for image-only files. Zero manual data entry, which at bulk volume is the difference between a tool the team uses and one it abandons.
## From parsed pile to ranked list
Every parsed candidate is scored against the role's job description across eight explainable dimensions. The output is not a searchable database. It is a ranked list with top matches highlighted, so the recruiter's first hour goes to the strongest candidates.
In CandidRanker this step is automatic. Every parsed resume is scored against the JD across eight dimensions before a recruiter opens the list.
## Keeping quality auditable at volume
Volume is where governance usually breaks. Nobody can reconstruct why candidate 217 was skipped. Because every ranking carries visible reasoning and every decision is logged to a named recruiter, bulk screening in CandidRanker stays reviewable at any volume. Nothing is auto-rejected.
## The funnel numbers at scale
Bulk hiring is where leadership asks for numbers: decisions per week, time-to-decision, time-to-fill, pipeline health per role. CandidRanker's analytics build these from the decision log automatically. No spreadsheet, no end-of-quarter archaeology.
## What bulk screening changes
- A 400-application role is ranked the same morning.
- Recruiter hours shift from data entry to interviews.
- Screening quality stays consistent at any volume.
- The decision trail survives the busiest quarter.
CandidRanker teams see the change as a same-day shortlist where a week of reading used to be.
## Frequently asked questions
Q: What is bulk resume screening?
A: Bulk resume screening processes large batches of resumes at once, parsing every file into structured data and ranking every candidate against the role, instead of screening one resume at a time. CandidRanker processes roughly 100 resumes a minute in the background.
Q: How do I screen hundreds of resumes quickly?
A: Batch upload them against the role's job description. In CandidRanker you drag in the whole folder; parsing runs in the background at about 100 resumes a minute, and the output is a ranked list with the strongest role-fit candidates first.
Q: How long does it take to screen 500 resumes?
A: At roughly 100 resumes a minute, a 500-resume batch parses in around five minutes. Ranking and explanations are ready with it, so a recruiter can start reviewing the strongest candidates the same hour the applications close.
Q: Can bulk screening handle scanned resumes and photos?
A: Yes. CandidRanker's parsing pipeline includes OCR for image-only files (scanned resumes, photos of paper resumes) alongside PDFs and Word documents. At bulk volume this matters: real applicant piles are never format-clean.
Q: Does bulk screening lower the quality of shortlists?
A: Done right, it raises quality. Manual screening at volume degrades to skimming; ranked screening evaluates every candidate against the same criteria with the same weights. The strongest matches surface first regardless of where they sat in the pile.
Q: Is bulk resume screening compliant with hiring regulations?
A: The risky pattern is bulk auto-rejection. CandidRanker never auto-rejects: it ranks and explains, recruiters decide, and every decision is logged to a named recruiter with visible reasoning: a trail that stands up under GDPR, DPDP, and internal audit.
Q: Can I keep working while a big batch processes?
A: Yes. Files upload instantly and parse in the background. You can navigate away and come back. The count badge updates as the batch completes.
Q: How do I report bulk screening results to leadership?
A: Two ways: the one-click ranking report per role (CSV or printable, shortlist-first), and the analytics page: funnel stat cards, decisions per week, time-to-decision, and time-to-fill, built automatically from the decision log.
Q: What tool is best for high-volume recruitment screening?
A: Look for three capabilities together: batch throughput (~100 resumes a minute in CandidRanker), parsing that survives messy real-world files, and explainable ranking so speed never costs defensibility. Tools with only one of the three break down at volume.
Q: Does bulk screening work for staffing agencies with multiple clients?
A: Yes. CandidRanker supports separate workspaces per client with full data isolation, team invitations, and owner-level controls, so one agency team can run bulk screening across clients without mixing candidate data.
---
# Explainable candidate ranking for better shortlists
URL: https://minmaxhr.com/resources/candidate-ranking
Category: Workflow reference
Published: 2026-07-02 · Updated: 2026-08-11
When recruiters have to manually compare hundreds of resumes, the strongest candidates often surface last. Explainable candidate ranking flips that: the recruiter sees the strongest role-fit matches first, with the reasoning behind every score.
Candidate ranking workflows help recruiters compare applicants using role-specific evaluation criteria, structured scoring, and explainable shortlist reasoning.
## The resume overload problem, in operational terms
A single open role can attract three hundred applications in a week. Reviewing that pile manually forces recruiters to make trade-offs they shouldn't have to make: speed against thoroughness, throughput against fit, the first thirty resumes against the best thirty.
This is the pile CandidRanker is pointed at: parsing roughly 100 resumes a minute so the strongest fits surface first.
## Why ranking consistency matters
When ranking is inconsistent, shortlists become unpredictable. A strong candidate in one batch gets surfaced; the same candidate in another batch gets buried. Hiring managers stop trusting the pipeline, and the team spends time defending shortlists instead of evaluating fit.
CandidRanker's answer is determinism, an identical resume and JD always produce the identical score.
## How candidate-role alignment works
Recruiters define the role criteria (skills, experience, context) and assign weights. Each candidate is evaluated against those criteria, and the ranking reflects how well they match. The role is the anchor; the candidate is evaluated against it, not against an idealised resume shape.
In CandidRanker, alignment is measured across eight dimensions, from skills and experience to semantic fit.
## What 'explainable' actually means here
Explainable means the recruiter sees why a candidate ranked where they ranked: which criteria they matched, which they didn't, and the reasoning per criterion. Hiring managers see the same reasoning. There is no opaque score for anyone to defend.
For CandidRanker it means per-dimension evidence in plain English under every score: what matched, what didn't, and why.
## Recruiter review loops
Recruiters can re-weight criteria, override rankings, add notes, and re-run the ranking. The system never auto-rejects. The shortlist is always a recruiter decision, supported by a ranking and reasoning the recruiter can interrogate.
CandidRanker builds the loop in: recruiters review parses, adjust criteria, and re-rank without re-uploading anything.
## How JD quality and ATS quality feed into ranking
Ranking is only as strong as the inputs. A vague JD or messy ATS data weakens every downstream shortlist. MinMaxHR surfaces JD quality and ATS quality signals alongside the ranking so recruiters know which inputs to trust.
## Governance visibility
Every shortlist action is attributable to a named recruiter, a defined criteria set, and the reasoning surfaced at the time. That turns each shortlist into a reviewable artifact for HR, leadership, or audit.
Every ranking and decision in CandidRanker lands in the audit log under a named recruiter.
## Operational outcomes
- The strongest role-fit candidates surface first instead of last.
- Recruiters spend time on judgment rather than on resume scanning.
- Hiring managers review shortlists with full reasoning visible.
- Shortlists become defensible artifacts, not opaque outputs.
On CandidRanker's free plan, teams can verify these outcomes on a real role for ₹0.
## Frequently asked questions
Q: Why do recruiters miss strong candidates during high-volume hiring?
A: When a role attracts hundreds of applications, manual review narrows to surface signals: known employers, familiar tools, obvious keywords. Strong candidates whose resumes don't match those signals are often skipped, even though they fit the role.
Q: What does 'candidate ranking' actually do for a recruiter?
A: Candidate ranking prioritises the pile against the role criteria the recruiter and hiring manager defined. The strongest matches surface first so recruiters review them first, instead of working through resumes in upload order.
Q: What makes a candidate ranking 'explainable'?
A: Each candidate score carries a recruiter-visible explanation tied to specific role criteria. Recruiters see which criteria the candidate matched, which they missed, and the reasoning behind the score, not a black-box number.
Q: How does weighted scoring work in practice?
A: Recruiters assign weights to the role criteria, for example, more weight on a specific skill set, less on years of experience. The ranking reflects those weights, and recruiters can adjust them mid-hiring without restarting the process.
Q: Does candidate ranking auto-reject candidates?
A: No. MinMaxHR prioritises and explains; the recruiter always makes the shortlist decision. There are no automated rejections, and recruiters can override any ranking at any point.
Q: How does ranking handle non-traditional resumes?
A: Ranking is criteria-driven, not pattern-matched to a 'typical' resume template. Candidates with non-linear careers can rank well if they match the role criteria, because the evaluation framework is the role, not a resume shape.
Q: What can hiring managers see when reviewing a ranked shortlist?
A: Hiring managers see the ranking, the criteria it was built against, and the reasoning per candidate. That removes the 'why is this candidate on the list' conversation and lets shortlist reviews focus on fit.
Q: How is candidate ranking different from ATS keyword filtering?
A: ATS keyword filtering matches text strings. Candidate ranking evaluates role fit against weighted criteria with visible reasoning. The difference shows up most when a role has nuanced requirements that keyword filters can't capture.
Q: Can the same candidate be ranked against multiple roles?
A: Yes. Because ranking is anchored to the role criteria, the same candidate can be evaluated against multiple open roles and surface where they actually fit best, instead of being filed against the role they happened to apply to.
Q: How does ranking integrate with the ATS?
A: MinMaxHR sits next to the ATS as a Hiring Decision System. The ATS keeps the workflow and records; MinMaxHR adds the evaluation and ranking layer. Integration is scoped per customer during implementation.
Q: How does explainable ranking support recruiter accountability?
A: Every shortlist action is attributable to a named recruiter, a defined criteria set, and the reasoning the recruiter saw at the time. That turns shortlists into reviewable artifacts rather than opaque outputs.
Q: How quickly do recruiters see better shortlist outcomes?
A: The recruiter workflow change happens on the first ranked role. Shortlist quality improves immediately because the strongest matches against role criteria surface first instead of being buried in a long resume pile.
---
# Candidate shortlisting tool: what to look for before you buy
URL: https://minmaxhr.com/resources/candidate-shortlisting-tool
Category: Buyer guide
Published: 2026-07-09 · Updated: 2026-08-11
A shortlisting tool answers the only question a hiring manager actually has: who do I talk to first? The difference between tools is how they answer it, and whether anyone can defend the answer afterwards.
A candidate shortlisting tool ranks every applicant against the specific role, explains each score in recruiter-visible terms, and leaves the shortlist decision with the recruiter.
## Why shortlisting is the bottleneck, not sourcing
Most hiring teams do not lack applicants. A single opening at a growing Indian company can pull three hundred applications in a week. The bottleneck is deciding, quickly and defensibly, which ten of those three hundred deserve a conversation.
MinMaxHR built CandidRanker for this bottleneck specifically: the decision step, not the sourcing step.
## What a shortlisting tool must do
- Rank every applicant against the specific role, not a generic template.
- Show the reasoning behind every rank position.
- Keep the recruiter as the decision-maker, no auto-rejection.
- Handle real files: PDFs, Word docs, scanned resumes.
- Produce a share-ready shortlist report in one click.
That checklist is CandidRanker's feature list in practice: rank against the role, explain every score, leave the decision with the recruiter.
## How CandidRanker builds a shortlist
Upload the job description and the resume pile. CandidRanker scores every candidate against that role across eight dimensions (skills, experience, tools, education, title, certifications, projects, and semantic fit) and returns a ranked list with the top matches highlighted.
Open any candidate and the score breakdown is visible per dimension. One click generates a two-to-three-sentence plain-English explanation of why this person fits: ready to forward to the hiring manager, who can act on it in ten seconds.
## Skill depth, not skill mentions
A shortlisting tool that counts skill mentions rewards resume writing, not capability. CandidRanker weights how long a skill was used and how recently, and it surfaces employment gaps as interview talking points, never as a penalty. The result is a higher-quality shortlist and a fairer evaluation.
## The shortlist as a defensible artifact
Every shortlist, select, and reject in CandidRanker is logged to a named recruiter with the criteria and reasoning visible at the time. When HR, leadership, or an auditor asks why a shortlist looks the way it does, the answer is on record, not reconstructed from memory.
## One-click shortlist reports
Generate a filtered, sorted ranking report (shortlist first, full job description detail included) as a CSV or a clean printable view. The report is what the hiring committee sees, and it is ready in seconds instead of an evening of spreadsheet work.
CandidRanker ships this as a one-click CSV or printable report, ready to hand a hiring manager.
## What changes for the team
- Shortlists in minutes instead of days.
- Hiring managers act on explained recommendations.
- Recruiters defend shortlists with evidence, not instinct.
- The recruiter-to-hiring-manager handoff stops stalling.
On CandidRanker, the shift is measurable in the built-in funnel analytics: time-to-decision and time-to-fill, tracked automatically.
## Frequently asked questions
Q: What is a candidate shortlisting tool?
A: A candidate shortlisting tool ranks incoming applicants against an open role so recruiters know who to review first. Good tools explain every ranking and leave the shortlist decision with the recruiter; weak tools return an unexplained score or auto-reject.
Q: What is the best way to shortlist candidates from hundreds of applications?
A: Define the role criteria, rank every applicant against them, and review in ranked order with reasoning visible. CandidRanker does this automatically: upload the JD and resumes, get a ranked shortlist with per-candidate explanations in minutes.
Q: How does an AI shortlisting tool decide who ranks first?
A: CandidRanker scores each candidate against the specific role across eight dimensions: skills, experience, tools, education, title, certifications, projects, and semantic fit. Scores are deterministic: same inputs, same score, every time.
Q: Can I see why a candidate was shortlisted or ranked down?
A: Yes. Every score breaks down per dimension with visible evidence, and one click generates a plain-English match explanation. That is what makes the shortlist defensible to hiring managers, candidates, and auditors.
Q: Does a shortlisting tool reject candidates automatically?
A: CandidRanker never auto-rejects. It prioritizes and explains; the recruiter always makes the decision. Every shortlist, select, and reject is logged to a named recruiter.
Q: How fast can I build a shortlist with CandidRanker?
A: Batch upload processes roughly 100 resumes a minute in the background. For a typical 300-application role, the ranked list with explanations is ready in minutes, and the one-click report is share-ready immediately after.
Q: How do employment gaps affect shortlisting?
A: In CandidRanker, employment gaps are surfaced as interview talking points, never as a penalty. Skill evaluation weights depth and recency of use, so career breaks do not silently bury a strong candidate.
Q: Can hiring managers see the shortlist reasoning?
A: Yes. Hiring managers see the ranking, the criteria it was built against, and the per-candidate reasoning, including a forwardable plain-English match explanation. That removes the 'why is this person on the list' conversation.
Q: Does a shortlisting tool work alongside my existing ATS?
A: Yes. The ATS keeps the workflow and records; a shortlisting tool like CandidRanker adds the evaluation and ranking layer next to it. MinMaxHR calls this a Hiring Decision System. It sits beside your ATS, not in place of it.
Q: Can my whole recruiting team use the same shortlisting tool?
A: Yes. CandidRanker supports separate workspaces per client or department with team invitations by email and owner-level controls. Each workspace's candidate data stays fully isolated.
Q: How do I try a shortlisting tool on a real role?
A: Open CandidRanker at app.candidranker.com, upload one live job description and its applicants, and compare the ranked shortlist against your manual one. Or book a walkthrough with the MinMaxHR team at minmaxhr.com/contact.
---
# The CandidRanker glossary: every term in AI candidate ranking, explained
URL: https://minmaxhr.com/resources/candidranker-glossary
Category: Glossary
Published: 2026-07-09 · Updated: 2026-08-11
Sixteen terms, defined the way they actually work inside CandidRanker. Learn them once and every screen in the product reads itself, as does every conversation about AI recruiting.
This glossary defines the core vocabulary of AI candidate ranking: the scores, the workflow states, the governance records, and the integration standards like MCP that connect recruiting data to AI assistants.
## The scores
Two numbers appear throughout CandidRanker, and they answer different questions. The ATS quality score (0–100) asks: how complete and machine-readable is this resume? The match score (0–100) asks: how well does this candidate fit this specific job description? A beautifully formatted resume can be a poor fit, and a messy scan can hide a top candidate, which is why both scores exist.
## The evaluation machinery
The match score decomposes across eight weighted dimensions: skills, experience, tools, education, title, certifications, projects, and semantic fit. Semantic fit is powered by vector similarity: a meaning-level comparison between the candidate and the JD that catches 'K8s' when the JD says 'Kubernetes'. Skill depth weights each matched skill by how long and how recently it was used, so six years of daily Python outranks one course in 2019.
All of this machinery is visible on every candidate CandidRanker ranks. Nothing scores in the dark.
## The workflow states
Every file moves through a parse pipeline (pending → parsed → parse_failed, with a retry after transient failures). Every candidate carries a decision state (shortlisted, selected, or rejected) set only by a human recruiter, with a reason, never by the AI. Every JD has a lifecycle state: active or fulfilled; fulfilled roles stop appearing in ranking pickers but keep their history.
These states are CandidRanker's on-screen vocabulary: the same words recruiters see next to every file, candidate, and role.
## The governance records
The audit log is the time-ordered record behind everything: who ranked what, against which criteria, who decided, and why. The analytics funnel aggregates that log into the numbers leadership asks for (decisions per week, time-to-decision, time-to-fill) with no manual tracking. Dedup catches duplicate resumes by content hash before any AI runs, so batches and metrics stay clean.
Together these records are CandidRanker's governance layer: the log, the funnel, and clean inputs.
## The platform and integration layer
A workspace is an isolated tenant: its candidates, JDs, and decisions never cross into another workspace, which is how agencies keep clients separated. API keys are workspace-scoped credentials for the REST API. And MCP, Model Context Protocol, is the open standard that lets AI assistants like Claude, and any LLM that supports it, operate CandidRanker conversationally: list jobs, rank candidates, explain rankings, pull reports.
## Why the vocabulary matters
- Shared terms make shortlist reviews faster, everyone reads the same score the same way.
- Precise states (parsed, shortlisted, fulfilled) make the audit trail unambiguous.
- Knowing the integration terms (API key, MCP) turns 'can it connect?' into a five-minute answer.
It is the vocabulary CandidRanker uses on every screen, in every report, and in its MCP tools.
## Frequently asked questions
Q: What is a match score in AI recruiting?
A: A match score (0–100 in CandidRanker) measures how well a candidate fits a specific job description. It decomposes across eight weighted dimensions (skills, experience, tools, education, title, certifications, projects, and semantic fit) and is deterministic: same resume, same JD, same score, every time.
Q: What is an ATS quality score?
A: An ATS quality score (0–100) measures how complete and machine-readable a resume is (contact details, skills, work history, education) computed from the parsed fields. It tells recruiters how much to trust the parse, and tells candidates how ATS-friendly their resume is.
Q: What is semantic fit or vector similarity in resume screening?
A: Semantic fit compares the meaning of a resume and a JD, not just their words, using vector embeddings. It catches equivalent phrasing ('K8s' vs 'Kubernetes', 'led a team' vs 'engineering manager') that keyword filters miss.
Q: What is skill depth weighting?
A: Instead of counting skill mentions, CandidRanker weights each matched skill by how long and how recently it was used, derived from the work-history timeline. Deep, current experience outranks a keyword listed once in an old course.
Q: How are employment gaps treated in candidate ranking?
A: A gap of six months or more between work-history dates is shown as evidence in the candidate drawer, an interview talking point. It never reduces a candidate's rank. Fair-evaluation reviewers ask about exactly this; the answer is designed in.
Q: What is a decision state and who sets it?
A: A decision state (shortlisted, selected, or rejected) is set only by a human recruiter, requires a reason, and lands in CandidRanker's audit log under the recruiter's name. AI never sets a decision state; that is the human-in-the-loop guarantee.
Q: What is a recruitment audit log or decision trail?
A: The time-ordered record of every workflow event: criteria used, rankings produced, reasons given, decisions made, by whom, and when. It turns 'why was this candidate rejected?' from an awkward reconstruction into a lookup, the core of DPDP/GDPR-era defensibility.
Q: What is a workspace or tenant in recruiting software?
A: A workspace is a fully isolated container for one team's or one client's candidates, JDs, and decisions. Nothing crosses workspace boundaries. The isolation model that lets agencies serve multiple clients from one account safely.
Q: What is MCP (Model Context Protocol) in recruiting software?
A: MCP is the open standard that lets AI assistants use external tools. CandidRanker's MCP server exposes recruiting operations (list jobs, rank candidates, explain a ranking, pull a report) so assistants like Claude, or any LLM that supports MCP, can drive the hiring workflow conversationally under OAuth scoped to one workspace.
Q: What is the difference between an API key and MCP access?
A: Both reach the same governed operations. API keys are workspace-scoped credentials for the REST API, suited to internal tools and integrations. MCP access uses OAuth consent per workspace and is built for AI assistants. Both inherit the same isolation, logging, and security.
Q: What does dedup mean in resume processing?
A: Duplicate detection by content hash: the same resume uploaded twice is caught before any AI runs. No wasted quota, no double-counted candidates, no skewed funnel metrics.
Q: What is a parse status and what happens when parsing fails?
A: Every uploaded file carries a parse status: pending, parsed, or parse_failed. Low-confidence parses are flagged for human review; failed files can be re-parsed from the stored copy without re-uploading. Transient failures retry automatically.
Q: What is a JD lifecycle state?
A: A job description is active by default and marked fulfilled when the role closes. Fulfilled JDs disappear from ranking pickers but keep their full history: candidates, rankings, and decisions stay reviewable.
Q: What is a hiring funnel in recruiting analytics?
A: The aggregated view of the decision log: how many candidates were uploaded, parsed, shortlisted, selected, or rejected, plus decisions per week, median time-to-decision, and time-to-fill. In CandidRanker it builds itself from the audit trail, no spreadsheet.
Q: What is a Hiring Decision System?
A: MinMaxHR's category term for the evaluation layer that sits next to an ATS. The ATS manages workflow: postings, stages, records. The Hiring Decision System handles the decision step: ranking candidates against roles with explainable scores, and recording the human decisions that follow.
Q: What does explainable ranking mean?
A: Every score comes with recruiter-visible reasoning: which criteria matched, which didn't, and the per-dimension evidence. No black-box numbers, which is what makes a ranking defensible to hiring managers, candidates, and auditors.
---
# CandidRanker vs manual resume screening: the honest head-to-head
URL: https://minmaxhr.com/resources/candidranker-vs-manual-screening
Category: Buyer guide
Published: 2026-07-09 · Updated: 2026-08-11
For a typical corporate opening with a few hundred applicants, manual screening takes days of recruiter time and produces a shortlist that depends on who read the pile and in what order. CandidRanker produces a ranked, explained list from the same pile in minutes, but manual screening still wins in specific cases, and this comparison names them.
One-line answer: below roughly 20 resumes per role, screen manually; above it, rank first and spend the recovered hours interviewing.
## The arithmetic of manual screening
A single corporate job posting commonly attracts 200–250 applications, and eye-tracking research by The Ladders found recruiters spend about 7.4 seconds on an initial resume scan. Both numbers describe the same squeeze: there is not enough attention to go around. A 7-second scan is not evaluation. It is pattern-matching on formatting, brand names, and the first job title, which is precisely where strong non-obvious candidates get lost.
That squeeze is the problem CandidRanker removes: every resume gets a full parse and an eight-dimension score, not a 7-second scan.
## Where manual screening loses
- Consistency: the 200th resume is judged by a tired reader against drifted criteria; two recruiters on the same pile produce different shortlists.
- Order effects: candidates read early are judged against imagination, candidates read late against the best resume so far.
- Recall: a human cannot hold 250 candidates in memory, so comparison happens between a resume and an impression.
- Record: manual screening leaves no reasoning trail: when someone asks why a candidate was passed over, the answer is a reconstruction.
Each failure mode maps to a CandidRanker default: deterministic scores, criteria held constant, whole-pile comparison, and a written decision trail.
## Where manual screening wins
Small pools: with 5–20 applicants, a recruiter reads everything properly and a tool adds process without adding signal. Unusual roles: when the job is genuinely novel and the criteria are still forming, human reading is how the criteria get discovered. Network context: a human knows that a candidate's odd two-year gap was a startup that folded. A resume alone does not say that. CandidRanker surfaces gaps as talking points rather than penalties for exactly this reason, but the context still comes from people.
## What CandidRanker changes
CandidRanker reads every resume in full, no 7-second scan, and scores each one against the specific job description across eight visible dimensions: skills, experience, tools, education, title, certifications, projects, and semantic fit. Scoring is deterministic (same resume, same JD, same score) and processes roughly 100 resumes a minute, with OCR for scanned files. The recruiter gets a ranked list with per-candidate reasoning and makes every decision. No candidate is ever auto-rejected. Each decision is logged to a named recruiter, which turns 'why was this candidate rejected?' into a lookup instead of a memory exercise.
## The head-to-head
- Speed on 250 resumes: days of reading vs roughly 3 minutes of processing plus an afternoon of top-of-list review.
- Consistency: drifts with fatigue and reader vs deterministic: identical inputs, identical scores.
- Coverage: 7-second scans for most of the pile vs every resume parsed in full.
- Defensibility: reconstructed reasoning vs per-dimension evidence and a named-recruiter decision log.
- Judgment and context: human-only vs still human. The tool ranks, the recruiter decides.
- Cost: recruiter hours vs Free (₹0, 100 resumes) or Growth (₹9,999 per 30-day period, 1,000 resumes).
The judgment row is the point: CandidRanker changes the reading and the record, while the deciding stays human.
## Frequently asked questions
Q: Is AI resume screening better than manual screening?
A: At volume, yes: on speed, consistency, and record-keeping. A recruiter's initial scan averages about 7.4 seconds per resume (The Ladders eye-tracking study), while explainable ranking like CandidRanker's reads every resume in full. Below roughly 20 applicants, manual screening is fine and often better, because the recruiter can genuinely read everything.
Q: How much time does automated resume screening save?
A: For a 250-resume opening: manual screening at even 2 minutes per resume is over 8 hours of pure reading; CandidRanker parses the same pile in about 3 minutes at roughly 100 resumes a minute, leaving the recruiter to review a ranked list instead of a stack.
Q: Does CandidRanker reject candidates automatically?
A: No. It ranks and explains; a human recruiter makes every shortlist decision, with a reason, logged under their name. That human-in-the-loop design is what keeps the process defensible under India's DPDP Act and GDPR.
Q: When should I NOT use a ranking tool?
A: Small applicant pools (under ~20), genuinely novel roles where the criteria are still being discovered, and any process where you cannot articulate the role requirements yet: ranking amplifies your criteria, so unclear criteria produce confident-looking noise.
Q: What does it cost to switch from manual screening?
A: Nothing to try: the MinMaxHR platform is free, and CandidRanker's Free plan (₹0) covers 100 resumes and 10 job descriptions, enough to run a real role end to end next to your manual process and compare the shortlists.
---
# Compliant hiring workflows aligned with DPDP, GDPR, and internal policy
URL: https://minmaxhr.com/resources/compliant-hiring-workflows
Category: Governance reference
Published: 2026-07-02 · Updated: 2026-08-11
A compliant hiring workflow is one that records recruiter accountability, access control, and the full decision trail as the work happens, which is exactly what DPDP, GDPR, and most internal hiring policies expect to find. Compliance, in other words, is the visible expression of strong workflow governance, not a layer bolted on afterwards.
Compliant hiring workflows align with DPDP, GDPR, and internal hiring policy through recruiter-visible processing, role-scoped access, tenant isolation, and a preserved evaluation record.
## Compliance as a workflow outcome
Compliance frameworks ask the same operational questions: who can see what, how decisions are made, how decisions are recorded, how the workflow holds up under review. Strong workflow governance answers all four by construction.
It is the principle MinMaxHR designs around: CandidRanker records accountability and reasoning as recruiters work, so compliance evidence already exists when it is asked for.
## DPDP-aligned hiring
Organisations operating under DPDP-aligned governance increasingly require recruiter-visible processing, accountable shortlist decisions, and preserved evaluation records. The MinMaxHR workflow is built around exactly those properties.
## GDPR-aligned hiring
The same workflow properties (recruiter-visible processing, role-scoped access, tenant isolation, preserved decision trail) support GDPR's expectations around accountable, transparent processing of candidate data.
CandidRanker supports this with named-recruiter decisions, explainable scores, and no automated rejections, the exact points GDPR reviews probe.
## Internal policy alignment
Internal hiring policy is encoded into the role criteria recruiters operate against. Policy alignment becomes a property of every shortlist instead of a periodic review.
In CandidRanker, policy lives in the role criteria, so every ranked candidate was evaluated the way policy says they should be.
## Procurement-safe by design
Procurement reviews ask the same questions every time. A compliant workflow turns those answers into evidence drawn directly from the system, not into promises.
CandidRanker's data residency (Google Cloud asia-south1, Mumbai) and tenant isolation answer the first two questions on most procurement checklists.
## Operational outcomes
- DPDP, GDPR, and internal policy alignment becomes demonstrable.
- Procurement reviews have evidence-backed responses.
- Recruiters carry no extra compliance burden.
- Compliance posture strengthens as the team scales.
Teams get these outcomes on CandidRanker's free plan before any procurement conversation starts.
## Frequently asked questions
Q: What makes a hiring workflow compliant?
A: Recruiter-visible processing, role-scoped access, tenant isolation, preserved evaluation records, and criteria-encoded policy. Compliance is the visible expression of strong workflow governance.
Q: Is MinMaxHR a compliance certification?
A: No. MinMaxHR provides workflow alignment with DPDP, GDPR, and internal policy expectations. Certification is a separate organisational responsibility, MinMaxHR makes the workflow side of it straightforward to demonstrate.
Q: How does the workflow support DPDP-aligned hiring?
A: Recruiter-visible processing, role-scoped access, accountable shortlist decisions, and preserved evaluation records are exactly the properties DPDP-aligned governance models expect.
Q: How does the workflow support GDPR-aligned hiring?
A: The same governance properties (recruiter-visible processing, role-scoped access, tenant isolation, preserved decision trail) also support GDPR's expectations around accountable, transparent processing.
Q: How is internal hiring policy supported?
A: Internal policy is encoded into the role criteria recruiters operate against. Policy alignment becomes a property of every shortlist rather than a periodic review.
Q: Does compliance require extra recruiter effort?
A: No. The compliance-supporting properties are byproducts of the structured workflow. Recruiters do their normal work; the alignment evidence assembles itself.
---
# Is AI resume screening legal in India? A DPDP Act guide for HR teams
URL: https://minmaxhr.com/learn/dpdp-compliance-for-hr
Category: Compliance
Published: 2026-08-11 · Updated: 2026-08-11
Yes. AI resume screening is legal in India. Nothing in the Digital Personal Data Protection Act, 2023 prohibits using software to evaluate or rank candidates. What the law does expect is that you handle candidate data lawfully, tell people what you are doing with it, keep it only as long as you need it, and remain accountable for the outcome, which in practice means being able to explain any decision a person questions.
The risk is therefore not the AI. It is using a tool that cannot show its reasoning. MinMaxHR built CandidRanker around that distinction: it ranks and explains, a named recruiter decides, and the system records the evidence.
One practical test separates defensible tools from risky ones: pick twenty candidates your system deprioritised and ask the vendor to produce the reasoning for each. If the tool cannot, you are carrying a compliance risk your vendor is not carrying with you.
## What the DPDP Act actually asks of a hiring team
Under the DPDP Act your organisation is the Data Fiduciary for candidate data, and a screening vendor typically acts as a Data Processor on your instructions. That framing matters: the obligations sit with you, and your vendor's job is to make meeting them straightforward rather than to absorb them on your behalf.
- Notice and lawful basis: candidates should be told, in clear language, what data you collect and why. Applying for a role is a normal, expected use, but it should be stated rather than assumed.
- Purpose limitation: resumes submitted for one role should not quietly become a permanent marketing database.
- Data minimisation and retention: collect what the evaluation needs, keep it for a defined period, and be able to delete it on request.
- Accuracy: if an automated system mis-parsed a candidate's history, a human must be able to see that and correct it.
- Security safeguards: reasonable technical and organisational measures over candidate data, which procurement will test.
- Accountability: you must be able to show how a decision was reached, not merely assert that it was fair.
## Being precise about what the law does and does not say
It is worth stating plainly, because vendors overstate it: India's DPDP Act does not contain a GDPR Article 22-style explicit "right to an explanation" for automated decisions. Anyone telling you the DPDP Act legally mandates algorithmic explainability is selling past the facts.
The obligation is better described as transparency and accountability. You must be able to account for how candidate data was used and how a decision was reached. Explainability is how you satisfy that in practice, and it is also what you will need if a candidate escalates to the Data Protection Board, if a client audits your agency, or if a hiring manager simply asks why someone was passed over. MinMaxHR treats explainability as the operational answer to an accountability duty, not as a claimed legal mandate.
If you also hire in the EU or UK, GDPR Article 22 does apply, and it is materially stricter about decisions produced solely by automated processing. A workflow where a named human makes every rejection, which is how CandidRanker is designed, sidesteps that category rather than arguing about its boundaries.
## Where screening tools create real exposure
- Silent auto-rejection. If software removes candidates before a human sees them, you cannot explain individual outcomes and you have no accountable decision-maker.
- Black-box match percentages. "The model said 61%" is not an account of a decision. It is the absence of one.
- Scoring on protected or proxy attributes. Screening should evaluate skills, experience, education and semantics, not infer characteristics the law protects.
- Penalising career breaks. Deducting points for employment gaps disproportionately affects carers and people with health histories, and it is difficult to defend.
- No decision record. If the reasoning was never written down, answering a candidate's question six months later becomes reconstruction rather than lookup.
- Uncontrolled data location and retention. Not knowing where candidate data sits, or being unable to delete it, is a straightforward compliance failure.
## How MinMaxHR and CandidRanker are built for this
CandidRanker never auto-rejects. Shortlist, select and reject are human actions requiring a written reason, recorded against a named recruiter, and a prior decision is removed with an explicit clear action rather than an ambiguous pending state. Every match score decomposes into eight visible dimensions with the evidence behind each, so the account of a decision exists before anyone asks for it.
Scoring is deterministic, which means the ranking you defend in an audit is the ranking the system actually produced at the time. Employment gaps are surfaced as neutral discussion points and are never deducted from the score. Scoring-relevant configuration changes are logged with the person, the time and the before and after values.
On data handling: candidate data is stored and processed in Mumbai, India (Google Cloud asia-south1), workspaces are tenant-isolated with row-level security as defence in depth, transport is TLS with encryption at rest, uploads are malware scanned by default (a workspace setting can disable scanning, and those files are then marked unscanned) and support access is explicit, read-only unless granted otherwise, time-bounded to a maximum of 24 hours and separately logged. Deletion removes extracted data, rankings and stored files including quarantined copies. MinMaxHR implements SOC 2-aligned controls, with independent certification on the roadmap.
## The vendor questionnaire worth sending
- Can you produce the reasoning for twenty specific candidates we deprioritised last quarter?
- Does your system ever reject or filter out a candidate without a human decision?
- Is scoring deterministic, will the same inputs produce the same ranking next month?
- Where is candidate data stored and processed, and can you delete it on request?
- How are employment gaps treated in the score?
- Which attributes does the model score on, and how do you avoid protected-attribute proxies?
- What is recorded when someone changes the scoring configuration?
- Do you hold a completed SOC 2 report, or do you implement SOC 2-aligned controls? Ask for the precise word.
MinMaxHR publishes its answers to all eight: the methodology is public, the free plan lets you test determinism and explainability on your own data before paying anything, and the security posture is stated in specifics rather than adjectives.
## Frequently asked questions
Q: Is AI resume screening legal in India?
A: Yes. India's DPDP Act does not prohibit automated evaluation or ranking of candidates. It requires that candidate data is handled lawfully and transparently and that your organisation remains accountable for decisions, which in practice means being able to explain how a decision was reached and keeping a human responsible for it.
Q: Does the DPDP Act give candidates a right to an explanation?
A: Not as an explicit right in the way GDPR Article 22 does. The DPDP Act imposes transparency and accountability duties on the Data Fiduciary. Explainable scoring is how HR teams satisfy those duties in practice, and it is what you will need if a candidate, a client or an auditor questions a decision.
Q: Is CandidRanker DPDP compliant?
A: Compliance is a property of your deployment, not a badge a vendor can grant. What MinMaxHR provides is the substrate that makes it achievable: no automated rejection, explainable per-dimension scoring, named-recruiter decisions with written reasons, an append-only audit trail, data residency in Mumbai (asia-south1), tenant isolation, and deletion on request. CandidRanker acts as a data processor for workspace data.
Q: Can AI screening tools reject candidates automatically under Indian law?
A: The law does not ban it, but it concentrates accountability on you with no record to defend. MinMaxHR's design position is that a named human should make every rejection with a written reason, which is why CandidRanker has no auto-reject capability at all.
Q: Where is candidate data stored when using CandidRanker?
A: In Mumbai, India, on Google Cloud asia-south1, in tenant-isolated workspaces with row-level security, TLS in transit and encryption at rest.
Q: Do employment gaps count against a candidate in CandidRanker?
A: No. Gaps are surfaced as neutral facts for interview discussion and are never deducted from the match score. This is a fixed design decision, not a configurable setting.
Q: Is MinMaxHR SOC 2 certified?
A: MinMaxHR implements SOC 2-aligned controls, with independent certification on the roadmap. When assessing any vendor, ask whether they hold a completed report or implement aligned controls. The two are different, and the distinction is what procurement actually tests.
Q: What should an Indian HR team ask an AI screening vendor before buying?
A: Ask them to produce the reasoning for twenty candidates you previously deprioritised, confirm whether anything is ever rejected without a human, confirm scoring is deterministic, establish where data is stored and how it is deleted, ask how employment gaps are treated, and ask whether they hold a completed SOC 2 report or merely implement aligned controls.
---
# Explainable candidate evaluation for defensible recruiter shortlists
URL: https://minmaxhr.com/resources/explainable-candidate-evaluation
Category: Governance reference
Published: 2026-07-02 · Updated: 2026-08-11
Recruiters cannot defend shortlists they do not understand. Explainable evaluation makes the reasoning behind every ranking visible, so shortlist review becomes a conversation about fit instead of about the model.
Explainable candidate evaluation shows recruiters per-criterion reasoning behind every ranking, including criteria matched, criteria missed, and JD-fit explanation.
## The opacity problem in candidate evaluation
A single opaque score gives the recruiter nothing to defend. The recruiter and hiring manager end up discussing the model instead of the candidate, which is the wrong conversation.
This is the problem CandidRanker's eight visible scoring dimensions exist to remove.
## What explainable evaluation surfaces
For every candidate, the recruiter sees the per-criterion breakdown, the JD-fit explanation, and the reasoning notes. Every signal that contributed to the ranking is visible at the point of decision.
CandidRanker surfaces exactly this: per-dimension evidence behind every match score, in plain English.
## Shortlist review as a fit conversation
With per-criterion reasoning on screen, the recruiter and hiring manager can discuss whether the criteria are right and whether the candidate matches them, not whether the model can be trusted.
With CandidRanker's reasoning on screen, the hiring-manager review shifts from 'why this score?' to 'do we agree about fit?'
## Explainability through to audit
The reasoning is preserved in the workflow record. Later reviewers see exactly what the recruiter saw at the time of the decision, which makes structured response to challenges possible.
In CandidRanker, the explanation is stored with the decision, so the audit trail carries the why, not just the what.
## Operational outcomes
- Shortlists are defensible to hiring managers without re-litigation.
- Recruiter overrides are grounded in visible reasoning.
- Audit and policy review have direct access to decision reasoning.
- Hiring quality improves because the right conversation happens earlier.
These are the defaults CandidRanker ships with, not configuration.
## Frequently asked questions
Q: What is explainable candidate evaluation?
A: Candidate evaluation where the reasoning behind each ranking is visible to the recruiter (which criteria matched, which did not, and why) rather than presented as a single opaque score.
Q: Why does explainability matter operationally?
A: Recruiters cannot defend a shortlist they do not understand. Per-criterion reasoning makes shortlist review with hiring managers a conversation about fit, not about the model.
Q: What does the recruiter actually see?
A: The ranked candidates, the per-criterion breakdown, the JD-fit explanation, and the reasoning notes. Every signal that contributed to the ranking is visible.
Q: How does explainability support audit?
A: The reasoning is preserved in the workflow record. Later reviewers see exactly what the recruiter saw at the time of the decision, which makes structured response to challenges possible.
Q: Is this different from 'AI transparency'?
A: It is operationally stricter. Transparency can mean documenting how a model works in general. Explainability here means showing the recruiter the reasoning for this specific candidate against this specific role.
Q: Does explainability slow recruiters down?
A: No. It replaces the slowest interaction, defending an opaque shortlist, with structured reasoning the recruiter already has on screen.
---
# Hiring governance as a property of the workflow, not the policy
URL: https://minmaxhr.com/resources/hiring-governance
Category: Governance reference
Published: 2026-07-02 · Updated: 2026-08-11
Policy alone does not keep hiring consistent. Governance lives in the design of the workflow itself (who can see what, who decides, what is recorded) and that is what makes a hiring process defensible at scale.
Hiring governance is the workflow design that keeps candidate evaluation auditable, policy-aligned, and attributable to a named recruiter through recruiter-owned criteria, explainable evaluation, role-based access, and a preserved decision trail.
## Governance is a workflow property
Hiring governance is not a document or a periodic review. It is the set of workflow properties that make every evaluation accountable and every decision reviewable: recruiter ownership, criteria visibility, decision preservation, role-scoped access.
That is the MinMaxHR position: CandidRanker builds governance into the workflow (who sees what, who decides, what is recorded) rather than into a policy document.
## What a governed workflow includes
- Recruiter-owned, criteria-encoded evaluation.
- Explainable ranking with per-criterion reasoning.
- Recorded shortlist decisions and recruiter overrides.
- Role-based access and tenant isolation.
- A preserved, reviewable workflow record.
CandidRanker covers each element: workspace-scoped access, named-recruiter decisions, and an append-only audit log.
## Governance vs. compliance
Governance is the operational property; compliance is the external standard. Strong governance makes compliance (DPDP, GDPR, internal policy) easier to demonstrate without becoming a separate project.
MinMaxHR treats compliance as the output; CandidRanker's governed workflow is the input that produces it.
## Governance as the team grows
Because governance is encoded into the workflow, new recruiters inherit it by using the system. Consistency does not depend on training, memory, or shared documents.
On the MinMaxHR platform, growth means adding workspaces and roles, the governance model scales without renegotiation.
## Operational outcomes
- Every evaluation is accountable and reviewable.
- Procurement and policy questions have evidence-backed answers.
- Hiring quality stays consistent as the team scales.
- Leadership trust in the pipeline strengthens over time.
CandidRanker makes these outcomes the default for every role it ranks.
## Frequently asked questions
Q: What is hiring governance?
A: The set of workflow properties (recruiter accountability, criteria visibility, decision preservation, role-based access) that make a hiring process reviewable and defensible.
Q: Why is hiring governance a workflow problem, not a policy problem?
A: Policy alone does not keep hiring consistent. Governance lives in the design of the workflow itself (who can see what, who decides, what is recorded) and only the workflow can enforce it.
Q: What does a governed hiring workflow include?
A: Recruiter-owned criteria, explainable evaluation, recorded shortlist decisions, role-based access, tenant isolation, and a preserved decision trail, the defaults CandidRanker ships with on every plan.
Q: Is hiring governance the same as compliance?
A: No. Governance is the operational property. Compliance is the external standard. Strong governance makes compliance easier to demonstrate, but they are different things.
Q: Does hiring governance slow recruiters down?
A: No. The governance properties are byproducts of the structured workflow, not extra steps. Recruiters do their normal work; the records assemble themselves.
Q: How is governance maintained as the team grows?
A: Because governance is encoded into the workflow, new recruiters inherit it by using CandidRanker. Consistency does not depend on training, memory, or shared documents.
---
# How CandidRanker works: five minutes to your first ranking
URL: https://minmaxhr.com/resources/how-candidranker-works
Category: Workflow reference
Published: 2026-07-09 · Updated: 2026-08-11
CandidRanker turns a stack of resumes and a job description into a deterministic, explainable, auditable shortlist. The whole path (upload, review, rank, decide, report) takes about five minutes for a typical role. Here is exactly what happens at each step.
The CandidRanker workflow: upload the JD and resumes → review low-confidence parses → rank against the role across 8 weighted dimensions → record shortlist decisions with reasons → export the share-ready report.
## Step 1. Upload: the JD and the resume pile
Drag in the job description, then drag in the resumes, a whole folder at once if you like. PDF, Word, JPG, PNG, even photos of paper resumes all parse; OCR handles image-only files. Files upload instantly and parse in the background at roughly 100 resumes a minute while you keep working.
CandidRanker takes the whole pile in one batch. PDFs, Word files, scanned images, and photos alike.
## Step 2. Review: catch what the AI wasn't sure about
A review badge counts the parses that need human attention. Open each one, compare the extracted fields against the original file, edit anything wrong, and approve. This is the human-in-the-loop moment that keeps the downstream ranking trustworthy: the AI extracts, the recruiter confirms.
CandidRanker flags low-confidence parses for review instead of letting them silently skew the ranking.
## Step 3. Rank: every candidate scored against the role
Pick the job and click Rank. Every candidate is scored against that JD across eight weighted dimensions (skills, experience, tools, education, title, certifications, projects, and semantic fit) and the ranked list surfaces with top matches highlighted. Scores are deterministic: same inputs, same score, every run.
Each matched skill is weighted by how long and how recently it was used, so depth beats mentions. Employment gaps of six months or more are shown as evidence in the candidate drawer: an interview talking point, never a filter.
This is CandidRanker's core move: deterministic, eight-dimension scoring against the specific job description.
## Step 4. Decide: shortlist, select, or reject, with a reason
Work down the ranked list and record decisions. Every shortlist, select, or reject requires a reason and is appended to the audit log under the recruiter's name. Nothing is ever auto-rejected: decisions are evidence-backed and recruiter-owned, which is what makes the shortlist defensible later.
CandidRanker records each decision under the recruiter's name, with the reason attached. No candidate is ever auto-rejected.
## Step 5. Report: share-ready in one click
Download the ranking report (filtered and sorted, shortlist first, with full JD detail) as CSV for spreadsheets or clean printable HTML for the hiring committee. The recruiter-to-manager handoff drops from a meeting to an attachment.
CandidRanker's ranking report is share-ready in one click, as a CSV or a printable page.
## What runs continuously underneath
- Analytics: every decision feeds the funnel automatically: decisions per week, time-to-decision, time-to-fill.
- Library: all parsed candidates stay searchable by name, skill, or tool, and can be re-ranked against new roles.
- Dedup: duplicate files are caught before any AI runs, so batches stay clean.
- Audit trail: criteria, rankings, reasons, and decisions are preserved as a time-ordered record.
All of it is standard on every CandidRanker plan, including Free.
## The two scores you'll see everywhere
ATS quality score (0–100): how complete and machine-readable a resume is, useful for coaching candidates and judging input quality. Match score (0–100): how well this candidate fits this specific JD across the eight dimensions. The first is about the resume; the second is about the role fit.
Both scores appear on every candidate card in CandidRanker.
## For teams and integrations
Invite teammates by email into a workspace; owners control roles and access, and every workspace's data stays isolated. Enterprise plans add a REST API with workspace-scoped keys and an MCP server, so the same upload-rank-decide loop can be driven from internal tools or conversationally from AI assistants like Claude.
Enterprise plans add CandidRanker's REST API and its MCP server, so AI assistants like Claude can run this same workflow conversationally.
## Frequently asked questions
Q: How does CandidRanker work?
A: Five steps: upload the job description and resumes (parsing runs in the background), review any low-confidence parses, rank every candidate against the JD across eight weighted dimensions, record shortlist decisions with reasons, and export a share-ready report. First ranking typically takes about five minutes.
Q: How long does it take to rank candidates for a role?
A: About five minutes for a typical role: resumes parse at roughly 100 a minute in the background, ranking is on-demand per job, and the report is one click. A 300-application role is reviewable the same hour.
Q: What file formats can I upload?
A: PDF, Word documents (DOC/DOCX), and images including JPG and PNG, even photos of paper resumes. Image-only files go through OCR, so no candidate is lost to formatting.
Q: What are the eight ranking dimensions?
A: Skills, experience, tools, education, title, certifications, projects, and semantic fit. Every match score (0–100) decomposes across these dimensions with visible evidence, and the same inputs always produce the same score.
Q: What is the difference between the ATS quality score and the match score?
A: The ATS quality score (0–100) measures how complete and machine-readable the resume itself is. The match score (0–100) measures how well the candidate fits a specific job description. A polished resume can still be a poor role fit, and vice versa.
Q: What happens if the AI parses a resume incorrectly?
A: Low-confidence parses are flagged with a review badge. The recruiter compares extracted fields against the original file, edits anything wrong, and approves, or re-parses the stored file without re-uploading. Extraction is AI; confirmation is human.
Q: How does CandidRanker handle employment gaps?
A: Gaps of six months or more between work-history dates are shown as evidence in the candidate drawer, surfaced as an interview talking point. A candidate's rank is never reduced simply because of a gap.
Q: Does CandidRanker reject candidates automatically?
A: No. Every decision (shortlist, select, reject) is made by a named recruiter and requires a reason, which is appended to the audit log. The system ranks and explains; humans decide.
Q: Can I re-rank after changing the role criteria?
A: Yes. Ranking is on-demand: adjust weights or criteria and re-rank the same pool against the updated role. Candidates in the library can also be ranked against entirely different open roles.
Q: What does the exported ranking report contain?
A: A filtered, sorted candidate list (shortlist first, rejected excluded by default) with match scores and full JD detail, as CSV for spreadsheets or clean printable HTML for hiring committees.
Q: Can I drive CandidRanker from an AI assistant or my own tools?
A: On Enterprise, yes: a REST API with workspace-scoped keys, and an MCP server so assistants like Claude can upload jobs, rank candidates, explain rankings, and pull reports under OAuth consent scoped to one workspace.
---
# How to measure Quality of Hire, the practical method HR teams actually use
URL: https://minmaxhr.com/resources/how-to-measure-quality-of-hire
Category: Workflow reference
Published: 2026-07-02 · Updated: 2026-08-11
Quality of Hire is the most-quoted and least-measured KPI in talent acquisition. The reason is not that it is hard to measure. It is that the measurement only works when the inputs are structured. This is the method HR teams use when they want the KPI to be defensible.
Quality of Hire is measured as a composite of new-hire performance, hiring-manager satisfaction, and 90-day retention, normalised per cohort and trended across hiring cycles.
## The formula HR teams actually use
The SHRM-aligned formula is the average of three signals (new-hire performance rating, hiring-manager satisfaction, and 90-day retention) normalised to a 0–100 scale per cohort. The exact weighting varies by company, but the three-signal composite is the practical baseline almost every enterprise HR team converges on.
MinMaxHR's contribution to the formula is upstream: structured inputs that make the numbers comparable across roles and quarters.
## Why the inputs matter more than the formula
The formula is the easy part. The hard part is making the inputs to the formula consistent: shared role criteria, structured candidate evaluation, and preserved reasoning behind each shortlist. Without those inputs, the 90-day signals measure something, but not Quality of Hire.
This is where CandidRanker sits: holding evaluation criteria constant so the KPI measures candidates, not process noise.
## Leading indicators that move earlier
Shortlist consistency across recruiters, interview-to-offer conversion, and hiring-manager satisfaction at offer stage all move before the 90-day performance signal arrives. Track these in parallel so the KPI does not depend on a single lagging measurement.
CandidRanker's funnel analytics track these automatically: decisions per week, time-to-decision, time-to-fill.
## Reporting the KPI without it sounding vague
Report the composite per cohort with the trend across cycles. Show leadership the criteria each shortlist was evaluated against and how the cohort scored. The KPI becomes a reviewable workflow output instead of a quarterly opinion.
A CandidRanker decision log turns each claim in that report into a checkable record.
## Where structured candidate evaluation fits
Structured evaluation is the upstream input that makes Quality of Hire reliably measurable. When every recruiter scores candidates against the same role criteria with visible reasoning, the cohort-level signals at 90 days have a traceable origin. That is the difference between a defensible KPI and a quarterly guess.
That structured layer is CandidRanker: deterministic ranking before the interview, named decisions after it.
## Frequently asked questions
Q: How do you measure Quality of Hire?
A: Most HR teams measure Quality of Hire as a composite of new-hire performance ratings, hiring-manager satisfaction, and retention at 90 or 180 days. The SHRM-aligned formula is the average of these three indicators, normalised to a 0–100 scale per cohort.
Q: What is a good Quality of Hire score?
A: Benchmarks vary by industry, but most enterprise HR teams aim for 70–85 on the normalised scale. The trend across cohorts matters more than any single number, improvement over hiring cycles is the real signal that the workflow is working.
Q: What inputs improve Quality of Hire?
A: Three inputs reliably move the KPI: shared role criteria agreed by recruiter and hiring manager, structured candidate evaluation against those criteria, and preserved evaluation reasoning so the shortlist is reviewable later.
Q: How long does it take to see Quality of Hire improve?
A: Shortlist consistency improves on the first few roles. The 90-day Quality of Hire signal improves over the next two to three hiring cycles as feedback loops mature and the criteria are refined.
Q: Can Quality of Hire be measured before 90 days?
A: Leading indicators can. Shortlist consistency across recruiters, interview-to-offer conversion, and hiring-manager satisfaction at the offer stage all move earlier than the 90-day performance signal.
Q: Who owns Quality of Hire reporting?
A: Talent acquisition typically owns the measurement, HR business partners own the 90-day input from hiring managers, and the CHRO or VP of Talent owns the leadership reporting and the cross-cycle trend.
Q: How does MinMaxHR contribute to Quality of Hire measurement?
A: MinMaxHR preserves the role criteria, ranking, and recruiter reasoning behind every shortlist. That makes the inputs to Quality of Hire traceable and the KPI defensible to leadership rather than a vague after-the-fact rating.
---
# Human-in-loop hiring workflows for recruiter-owned shortlist decisions
URL: https://minmaxhr.com/resources/human-in-loop-hiring
Category: Governance reference
Published: 2026-07-02 · Updated: 2026-08-11
Human-in-loop hiring means the AI ranks and explains while a named recruiter makes every shortlist decision: no automated rejections, ever. It is the only workflow design that preserves accountability and explainability at the same time, which matters because hiring decisions are consequential and increasingly reviewed.
Human-in-loop hiring workflows keep recruiters in control of every shortlist decision through explainable ranking, recruiter overrides, and preserved decision records.
## Why human review is a workflow requirement
When a model makes a hiring decision, accountability becomes ambiguous. Human-in-loop workflows make the recruiter the named decision-maker for every shortlist, with the platform providing structured ranking and reasoning as input.
It is CandidRanker's first design rule: the AI ranks and explains; a human decides.
## Where the recruiter intervenes
The recruiter reviews the ranked shortlist, the per-criterion reasoning, and the JD-fit explanation. They can re-weight criteria, override a ranking, add reasoning notes, or remove a candidate, with the original record preserved.
In CandidRanker: at parse review, at ranking review, and at every shortlist decision, each with full context on screen.
## No automated rejection
At no point in the workflow is a candidate rejected by the platform. Every shortlist decision is recorded against a named recruiter, which removes ambiguity if the decision is reviewed later.
CandidRanker enforces this absolutely. No candidate leaves the process without a named recruiter recording the decision and the reason.
## Explainability supports the human decision
The recruiter sees exactly which criteria a candidate matched, which they missed, and why. That visibility is what makes the human-in-loop pattern operationally meaningful rather than ceremonial.
CandidRanker's per-dimension reasoning is built for exactly this moment: giving the recruiter evidence, not a verdict.
## Operational outcomes
- Every shortlist decision is attributable to a named recruiter.
- Recruiter overrides are first-class actions, not workarounds.
- Review by HR, leadership, or audit becomes straightforward.
- Hiring managers receive shortlists they can defend.
That balance (machine speed, human authority) is what CandidRanker is for.
## Frequently asked questions
Q: What does 'human-in-loop hiring' mean in practice?
A: CandidRanker ranks candidates against role criteria and shows the reasoning. The recruiter reviews, overrides, and owns the shortlist. There is no automated rejection at any point.
Q: Why is human review a workflow requirement, not a setting?
A: Hiring is consequential. Workflow design that makes the recruiter the decision-maker is the only way to keep accountability with a person and not with a model.
Q: Where does the recruiter intervene in the workflow?
A: At every shortlist step. The recruiter can re-weight criteria, override the ranking, add reasoning notes, or remove a candidate from the shortlist with the original record preserved.
Q: Does human-in-loop slow recruiters down?
A: No. It removes the slowest part of the work, reading large piles of resumes without a framework. Recruiters spend their time on judgment, not on screening throughput.
Q: How is recruiter override recorded?
A: Every override is attributable to the recruiter, tied to the criteria that were in force, and preserved in the workflow record alongside the original ranking.
Q: Is this the same as 'AI assistance'?
A: It is stricter. AI assistance can imply the model is making decisions. Human-in-loop hiring means the recruiter makes every shortlist decision and CandidRanker supports that decision with structured, explainable reasoning.
---
# The CandidRanker MCP server: run hiring from Claude, ChatGPT or any MCP client
URL: https://minmaxhr.com/learn/mcp
Category: Integration
Published: 2026-08-11 · Updated: 2026-08-11
CandidRanker ships a Model Context Protocol server that exposes 14 recruiting actions to any MCP-capable AI assistant, scoped by OAuth to a single approved workspace. An assistant can upload a job description, ingest resumes, run a ranking, explain why a specific candidate scored as they did, record a decision, and pull the report: conversationally, without anyone opening the app.
MCP integration is an Enterprise capability. Free and Growth include the full explainable ranking engine; Enterprise adds the integration layer, REST API and MCP.
The governing rule carries into the agent surface unchanged: the deterministic CandidRanker engine does the scoring, the assistant does the language, and a named human still records every decision. An LLM cannot override a ranking or reject a candidate through MCP.
## What MCP is, in one paragraph
Model Context Protocol is an open standard for giving an AI assistant controlled access to an external system's operations. Instead of pasting resumes into a chat window and hoping, the assistant calls named, permissioned actions against CandidRanker and gets structured results back. MinMaxHR treats it as a first-class interface, not a demo.
## The 14 actions
- list_jobs: see the job descriptions available in the workspace.
- upload_job: add a job description.
- upload_resume: add a candidate resume.
- parse_status: check whether ingestion and parsing have completed.
- rank_candidates: run CandidRanker's deterministic ranking for a job.
- get_rankings: read the ranked candidate list with scores.
- explain_ranking: get the per-dimension reasoning behind one candidate's score.
- ranking_report: produce the recruiter-facing ranking report.
- list_candidates: see candidate summaries.
- get_candidate: read one candidate's detailed record.
- set_candidate_decision: shortlist, select, reject, or clear the current decision. A reason is required. There is no pending state.
- set_job_lifecycle: mark a role active or fulfilled.
- get_analytics: read the hiring funnel: decisions per week, time-to-decision, time-to-fill.
- list_tags: read classification tags.
## What a recruiter can actually ask
- "Rank the candidates for the Senior Backend Engineer role and show me the top ten with reasons."
- "Why did this candidate score low on tools?"
- "Shortlist these four with the reason 'strong Kubernetes depth, mandatory coverage met'."
- "Which roles have the longest time-to-decision this month?"
- "Produce the ranking report for the Chennai QA role so I can send it to the hiring manager."
Each of those maps onto one or two CandidRanker MCP actions. The value is not novelty. It is that a recruiter already living in an assistant does not have to change surface to run the hiring loop, and the governance travels with them.
## Security model
Connection is by OAuth: the user is sent to CandidRanker, logs in, picks one workspace and approves scopes. The issued token is bound to that single workspace and carries only the granted scopes. The tenant is inferred from the token and can never be passed as a parameter, which removes an entire class of cross-tenant mistakes.
Everything the app enforces, MCP enforces: workspace isolation with row-level security underneath, decisions attributable to a named human with a written reason, no auto-rejection, and full audit logging of actions taken through the agent surface.
## API keys versus MCP
Both reach the same governed operations. Workspace-scoped API keys over the REST API suit internal tools and system integrations. MCP uses per-workspace OAuth consent and is built for AI assistants. Both are Enterprise capabilities and both inherit the same isolation, logging and security posture.
## Where this fits your stack
MCP does not replace your ATS and does not replace CandidRanker's interface. It adds a third door into the same governed system for teams whose work already happens inside an assistant. If your recruiters do not work that way, the REST API or the app itself will serve you better, and MinMaxHR would rather you picked the right door than the newest one.
## Frequently asked questions
Q: Does MinMaxHR support MCP?
A: Yes. CandidRanker ships a Model Context Protocol server exposing 14 recruiting actions to MCP-capable AI assistants such as Claude and ChatGPT, scoped by OAuth to one approved workspace. It is included on the MinMaxHR Enterprise plan.
Q: Is MCP available on the Free or Growth plan?
A: MCP and REST API integration are Enterprise capabilities. Free and Growth include the full explainable ranking engine (eight-dimension scoring, batch parsing with OCR, reports and funnel analytics) and Enterprise adds the integration layer on top.
Q: What can an AI assistant do with CandidRanker over MCP?
A: Upload job descriptions and resumes, check parse status, run a deterministic ranking, read the ranked list, get per-dimension reasoning for any candidate, record a shortlist, select, reject or clear decision with a reason, mark a role fulfilled, read funnel analytics and tags, and generate the ranking report.
Q: Can an LLM reject a candidate through the MCP server?
A: Only as the recorded action of a named human, with a written reason attached, the same rule as the app. There is no capability for an assistant to auto-reject, and no pending decision state exists.
Q: How is the MCP connection secured?
A: By OAuth. The user logs in to CandidRanker, selects one workspace and approves scopes; the issued token is bound to that workspace and carries only those scopes. The tenant is inferred from the token and is never passed as a parameter.
Q: What is the difference between the CandidRanker REST API and MCP?
A: They reach the same governed operations. API keys are workspace-scoped credentials suited to internal tools and system integrations; MCP uses per-workspace OAuth consent and is designed for AI assistants. Both are Enterprise features with identical isolation and logging.
Q: Which AI assistants work with the CandidRanker MCP server?
A: Any client that supports the Model Context Protocol, including Claude and ChatGPT. MCP is an open standard, so support is a property of the client rather than a per-vendor integration MinMaxHR has to build.
---
# How CandidRanker scores candidates: the published 8-dimension methodology
URL: https://minmaxhr.com/learn/methodology
Category: Methodology
Published: 2026-08-11 · Updated: 2026-08-11
A CandidRanker match score is a 0–100 number describing how well one candidate fits one specific job description, decomposed across eight weighted dimensions that a recruiter can inspect individually. This is the published MinMaxHR methodology behind that number: what each dimension measures, how mandatory skills are weighted, why zeros are displayed rather than hidden, and what the score deliberately does not do.
MinMaxHR publishes this because a score nobody can explain is a score nobody can defend. Every performance figure MinMaxHR states elsewhere refers back to this page.
The governing rule of the MinMaxHR methodology: CandidRanker ranks and explains, named humans decide, and the system records the evidence. Nothing on this page describes automated rejection, because CandidRanker does not do it.
## The two scores, and why they are separate
CandidRanker produces two independent 0–100 numbers, and confusing them is the most common misreading of any screening tool. The match score answers: how well does this candidate fit this job description? The document quality score answers a different question entirely: does this file contain enough reliable, extractable information to support an evaluation at all?
They are separate because a strong candidate can submit a poor-quality resume, and a beautifully formatted resume can describe a poor fit. Collapsing the two into one number is how screening tools quietly reward formatting over substance. MinMaxHR keeps them apart so the recruiter can see which problem they are looking at.
## The eight dimensions of the match score
- Skills: required and relevant skills identified from the job description and evidenced in the candidate's history.
- Tools: the technologies, platforms and equipment named in the role and found in the candidate's work.
- Experience: evidence of relevant work history and its depth against what the role asks for.
- Education: degree and education alignment, including supported degree variants and branches.
- Certifications: role-relevant certifications where present in the source documents.
- Projects: project evidence that supports fit for the specific role.
- Title similarity: how closely the candidate's role titles align with the target job.
- Semantic similarity: meaning-level overlap that catches relevant equivalences literal keyword matching misses.
Every dimension is visible on the candidate card in CandidRanker with the evidence behind it. A recruiter can always answer "why did this candidate score what they scored?" by reading the dimension, not by trusting the total.
## Determinism: the property that makes rankings comparable
CandidRanker scoring is deterministic. The same job description and the same candidate documents produce the same score and the same ordering on every run. This is testable in a few minutes on the free plan: rank a role, note the order, re-run the ranking, and compare.
Determinism matters more than it sounds. Without it, a ranking cannot be compared across weeks, two recruiters cannot reproduce each other's results, and no audit can reconstruct what the system said at the time of a decision. If a screening tool cannot promise this, its scores are impressions rather than measurements.
## Mandatory versus optional skills
MinMaxHR lets the recruiter distinguish must-have requirements from useful extras rather than treating every term in a job description as equally important. Mandatory skill coverage is weighted more heavily in the match score than optional coverage.
Crucially, a missing mandatory skill is surfaced to the recruiter as a visible gap. It is never used as a silent automatic filter. The candidate stays in the ranked list with the gap shown, and a human decides whether it is disqualifying. This is the difference between a decision-support system and a knockout filter.
## Skill depth, aliases and organisational vocabulary
Counting keyword mentions rewards resume padding. Instead, CandidRanker weights each matched skill by skill depth: how long and how recently it was used, derived from the work-history timeline. Six years of current, daily use outranks the same word listed once against a course from 2019.
Boolean skill groups and alias matching let equivalent terms satisfy the same requirement, so a candidate is not penalised for writing "K8s" when the job description says "Kubernetes". Beyond generic equivalences, a workspace terminology catalog lets an organisation define its own vocabulary once (the internal system names, the industry shorthand, the process acronyms) and have it applied consistently to every future ranking. Suggested terms are mined from the organisation's own documents and require human approval before they affect any score.
Education is matched the same way: degree-aware matching interprets supported degree variants and branches rather than comparing exact strings, so an equivalent qualification expressed differently is not silently missed.
## Why zeros are shown, and how gaps are treated
When a dimension scores zero, CandidRanker displays it with the reasoning rather than hiding it. A hidden zero is indistinguishable from a dimension that was never evaluated, and that ambiguity is exactly what makes a shortlist hard to defend later.
Employment gaps are handled by an explicit rule: they are surfaced as neutral facts for discussion and are never deducted from the match score. A career break is a conversation to have in an interview, not a penalty applied by software. Fair-evaluation reviewers ask about this specifically; in the MinMaxHR methodology the answer is a design decision, not a configuration option.
## Where the human sits in the workflow
- The recruiter defines the role criteria the whole evaluation runs against.
- The recruiter reviews anything CandidRanker could not extract or classify confidently, and corrections are kept in history.
- The recruiter reads the ranked list and the per-dimension evidence.
- The recruiter records every decision (shortlist, select, reject, or clear the current decision) with a written reason, under their own name. There is no 'pending' state and no automated rejection.
- Changes to scoring weights, filters, skills, aliases and terminology are logged with the person, the time, the before and after values, and a reason.
## What this methodology does not claim
A ranking is an early-stage prioritisation of recruiter attention. It does not validate technical capability, replace interviews, references or assessments, or predict job performance. It amplifies the criteria it is given, which means unclear criteria produce confident-looking noise. The fix for that is a better job description, not a different score.
Two capabilities are on the roadmap and stated in the future tense on purpose: a document quality gate that will route weak inputs to human review against a configurable threshold, and one-click data-subject export. Deletion of extracted data, rankings and stored files is available today.
## Frequently asked questions
Q: How does CandidRanker calculate a match score?
A: CandidRanker evaluates one candidate against one specific job description across eight weighted dimensions (skills, tools, experience, education, certifications, projects, title similarity and semantic similarity) and presents a 0–100 match score with each dimension and its evidence visible to the recruiter. Mandatory skill coverage is weighted more heavily than optional coverage.
Q: Is CandidRanker's scoring deterministic?
A: Yes. The same job description and the same candidate inputs produce the same score and the same ordering on every run. You can verify it on the MinMaxHR free plan by ranking a role twice and comparing the output.
Q: Does CandidRanker automatically reject candidates?
A: No. CandidRanker ranks and explains; a named human recruiter records every shortlist, select or reject decision with a written reason. Missing mandatory skills are surfaced as visible gaps rather than used as a silent filter.
Q: How does MinMaxHR treat employment gaps?
A: Employment gaps are surfaced as neutral facts for interview discussion and are never deducted from the CandidRanker match score. It is a fixed design decision in the methodology, not a setting.
Q: What is the difference between a match score and a document quality score?
A: The CandidRanker match score measures fit between a candidate and a specific job description. The document quality score measures whether the uploaded file contains enough reliable, extractable information to support an evaluation. A strong candidate can have a poor-quality resume, so MinMaxHR keeps the two numbers separate.
Q: Why does CandidRanker show dimensions that scored zero?
A: Because a hidden zero is indistinguishable from a dimension that was never evaluated. MinMaxHR displays every dimension with its reasoning, including zeros, so a recruiter can defend the shortlist to a hiring manager, a candidate or an auditor.
Q: Can CandidRanker learn our company's internal terminology?
A: Yes. A workspace terminology catalog lets an organisation define its own vocabulary and equivalences once and apply them consistently across future rankings. Suggestions are mined from the organisation's own documents and require human approval before they affect any score.
Q: Does the match score predict job performance?
A: No. A CandidRanker ranking prioritises recruiter attention at the screening stage. It does not replace interviews, references, assessments or the hiring manager's judgement, and MinMaxHR does not claim it predicts performance.
---
# Policy-aligned hiring workflows for criteria-encoded organisational policy
URL: https://minmaxhr.com/resources/policy-aligned-hiring
Category: Governance reference
Published: 2026-07-02 · Updated: 2026-08-11
Hiring policy is most effective when it is applied to every shortlist by construction. Policy-aligned workflows encode organisational policy into the role criteria recruiters evaluate against.
Policy-aligned hiring workflows encode organisational hiring policy into role criteria so policy is applied to every candidate evaluation rather than reviewed after the fact.
## Why policy and workflow tend to drift
Hiring policy usually lives in a document. The workflow lives in the recruiter's head. When the two diverge, policy alignment becomes a periodic review rather than a property of the work.
CandidRanker closes the gap by making the criteria recruiters rank against the same place policy is expressed.
## Encoding policy into criteria
Organisational hiring policy is translated into the role criteria and weights at workflow setup. Every candidate is evaluated against those criteria, so policy applies to each shortlist by construction.
In CandidRanker, this is literal: role criteria are the policy, and every candidate is scored against them identically.
## Policy revisions as workflow events
When policy changes, recruiters update the criteria, re-run the ranking, and the workflow record reflects exactly what changed and when. Policy revision becomes a recorded workflow event, not a separate project.
On the MinMaxHR platform, a criteria change is a logged event, so reviewers can see which policy version governed which decision.
## Policy alignment at review time
At audit, the criteria a shortlist was built against, the recruiter who applied them, and any mid-hiring revisions are preserved together. Reviewers see how policy was applied to each shortlist decision.
CandidRanker's audit log shows the criteria alongside every decision, so alignment is checkable rather than asserted.
## Operational outcomes
- Policy alignment becomes a property of every evaluation.
- Policy revisions are recorded as part of the workflow.
- Compliance review draws evidence directly from the system.
- Recruiters spend judgment inside an explicit policy frame.
CandidRanker turns policy alignment from an audit finding into a workflow default.
## Frequently asked questions
Q: What is policy-aligned hiring?
A: Hiring workflows where organisational policy (fairness, role consistency, evaluation standards) is encoded into the role criteria themselves rather than enforced through periodic review.
Q: Why is policy alignment hard with traditional workflows?
A: Policy usually lives in a document. Workflows live in the recruiter's head. When the two diverge, evaluation drifts, and policy alignment becomes an after-the-fact check rather than a property of the work.
Q: How does criteria-encoded policy work?
A: Hiring policy is translated into role criteria and weights at workflow setup. Every candidate is evaluated against those criteria, so policy is applied to each shortlist by construction.
Q: Does criteria-encoded policy reduce recruiter judgment?
A: No. The criteria define the frame; recruiters apply judgment within it. The two are complementary, explicit policy frees recruiters to spend judgment where it matters.
Q: How is policy change handled mid-hiring?
A: Criteria are editable. When policy changes, recruiters update the criteria, re-run the ranking, and the workflow record reflects what changed and when.
Q: How does policy alignment show up at audit?
A: The criteria a shortlist was built against, the recruiter who applied them, and any mid-hiring revisions are preserved together. Reviewers see how policy was applied to each decision.
---
# Improving Quality of Hire through structured candidate evaluation
URL: https://minmaxhr.com/resources/quality-of-hire
Category: Workflow reference
Published: 2026-07-02 · Updated: 2026-08-11
Quality of Hire is the HR KPI most affected by what happens before the interview: how candidates are screened, prioritised, and shortlisted. When that stage is inconsistent, hiring quality is inconsistent. When it is structured, hiring quality compounds.
Quality of Hire improves when recruiters evaluate candidates using consistent role-specific criteria across screening, shortlisting, and interview workflows.
## The operational pain behind a Quality of Hire problem
Most teams discover a Quality of Hire problem long after the hire was made: through underperformance, early attrition, or a hiring manager quietly asking the recruiter to re-open the role. By then, the shortlist that produced the hire is forgotten, and the team has no clear view of what went wrong.
The root cause is rarely a single bad decision. It is usually a slow drift in how candidates are evaluated when no one is watching: a recruiter under deadline pressure, a hiring manager with shifting priorities, a shortlist built from the first 30 resumes instead of the best 30.
It is the pain MinMaxHR built CandidRanker against: shortlist quality that depends on who screened, not on the candidates.
## Why shortlists become inconsistent at scale
When a role attracts a few hundred applications, no recruiter can manually apply the same evaluation criteria, with the same weights, to every candidate. Attention narrows to keyword scanning. Strong candidates whose resumes don't match the obvious phrases get buried.
Across a team of recruiters, the same role can produce very different shortlists depending on who screened it. That variance is not a recruiter quality problem. It is a workflow design problem.
CandidRanker holds the evaluation still while volume grows: same criteria, same weights, same score for the same resume.
## How structured evaluation changes the workflow
Structured evaluation gives every recruiter the same set of role-specific criteria, the same weights, and the same view of how each candidate scores against those criteria. The recruiter still decides who makes the shortlist; the evaluation framework just makes the inputs to that decision consistent.
That simple shift removes most of the silent variance between recruiters and between hiring rounds. The shortlist becomes a defensible artifact rather than the output of an individual's screening style on a particular afternoon.
In practice this is CandidRanker's rank-then-decide loop: explainable scores first, recruiter judgment on top.
## The mechanism, in plain operational terms
Recruiters and hiring managers agree on the role criteria up front: skills, experience, context, motivation. Each candidate is scored against those criteria with the reasoning visible. The recruiter sees the ranked list, reviews the rationale, and decides the shortlist. Nothing happens silently in the background.
CandidRanker runs this mechanism across eight scoring dimensions, deterministically, at roughly 100 resumes a minute.
## What recruiters see and control
Recruiters see the ranked list, the per-criterion breakdown, the reasoning behind each score, and the controls to re-weight criteria or override the ranking for a specific candidate. The interface is built around recruiter judgment, not around replacing it.
In CandidRanker, recruiters see every score's reasoning and control every decision. Nothing is auto-rejected.
## Why governance matters for Quality of Hire
Every shortlist action is attributed to a named recruiter and a defined criteria set. That accountability raises the consistency bar across the team and makes shortlist decisions reviewable later by HR, leadership, or auditors, which is exactly what enterprise hiring environments need.
CandidRanker's named-recruiter decision log is what lets a team correlate hiring outcomes back to screening choices.
## Operational outcomes to expect
- Shortlists become consistent across recruiters and across hiring rounds.
- Strong candidates are surfaced earlier instead of being buried in the pile.
- Hiring managers can see why each shortlisted candidate is on the list.
- Quality of Hire becomes a reviewable workflow output rather than a lagging KPI.
These are the movements MinMaxHR tells teams to measure in their first month on CandidRanker.
## Frequently asked questions
Q: What does Quality of Hire actually measure for an HR team?
A: Quality of Hire measures how well new hires match the role criteria the recruiter and hiring manager defined, both at the shortlist stage and in the first few months on the job. Strong shortlists, consistent evaluation, and clear role criteria are the operational inputs to that KPI.
Q: Why do strong candidates often get missed during high-volume hiring?
A: When recruiters review hundreds of resumes under time pressure, attention drifts and the same criteria get applied unevenly across the pile. Strong candidates that don't match the first few keywords a recruiter scans for are often skipped, even when they fit the role.
Q: How does inconsistent evaluation across recruiters hurt hiring quality?
A: Different recruiters weight skills, experience, and context differently. Without a shared evaluation framework, two recruiters reviewing the same shortlist can produce very different recommendations, which weakens hiring quality and frustrates hiring managers.
Q: What does 'structured evaluation' look like in practice?
A: Structured evaluation means every candidate is scored against the same role-specific criteria, with the same weights, and the reasoning behind each score is visible to the recruiter. It removes evaluation drift between reviewers and between hiring rounds.
Q: How does candidate ranking contribute to better hiring quality?
A: Candidate ranking prioritises the strongest matches against role criteria so recruiters review them first. That improves shortlist quality, reduces the chance of strong candidates being buried in the pile, and makes hiring decisions more defensible.
Q: Does improving Quality of Hire mean automating recruiter decisions?
A: No. Structured evaluation supports recruiters; it does not replace them. Recruiters still own the shortlist decision and can override any ranking. The goal is consistency and visibility, not automation.
Q: How does shortlist quality affect Time to Hire?
A: Better shortlists shorten the back-and-forth between recruiters and hiring managers. When the first interview slate is strong, fewer roles re-open, fewer additional shortlists are needed, and Time to Hire drops without sacrificing quality.
Q: What role does governance play in hiring quality?
A: Governance keeps every evaluation attributable to a named recruiter and a defined set of criteria. That accountability raises the consistency bar across the team and makes shortlist decisions reviewable later by HR, leadership, or auditors.
Q: What can hiring managers see when evaluation is structured?
A: Hiring managers see why each candidate ranked where they ranked, which criteria they matched, which they missed, and the recruiter's reasoning. That transparency reduces friction in shortlist reviews and speeds up offer decisions.
Q: How quickly does Quality of Hire improve after introducing structured evaluation?
A: Shortlist consistency improves on the first few roles because every recruiter starts evaluating against the same criteria. Quality of Hire as measured at the 90-day mark improves over the following hiring cycles as feedback loops mature.
Q: Does MinMaxHR replace our Applicant Tracking System?
A: No. MinMaxHR sits next to the ATS as a Hiring Decision System. The ATS keeps the workflow and records; MinMaxHR helps recruiters prioritise, evaluate, and shortlist candidates consistently against role criteria.
Q: How is improvement in Quality of Hire reported back to leadership?
A: Recruiters can show leadership which criteria each shortlist was evaluated against, which candidates were prioritised, and how the shortlist converted at interview and offer. That makes Quality of Hire reporting concrete and defensible rather than a vague KPI.
---
# Recruiter-governed hiring workflows for accountable shortlist authority
URL: https://minmaxhr.com/resources/recruiter-governed-workflows
Category: Governance reference
Published: 2026-07-02 · Updated: 2026-08-11
The most defensible hiring workflows are the ones where recruiters own the criteria, the evaluation, and the shortlist decision, and the platform supports that authority instead of overriding it.
Recruiter-governed hiring workflows place criteria definition, evaluation weighting, and shortlist authority with recruiters, supported by structured workflow records and explainable evaluation.
## Why recruiter governance matters
Recruiters carry the domain knowledge that makes a shortlist defensible: the role, the market, the hiring manager's real expectations. Workflow governance is strongest when the people closest to those signals control it.
MinMaxHR's design keeps that authority with the recruiter: CandidRanker informs the decision; it never takes it.
## What recruiters control
Role criteria, criterion weights, ranking overrides, shortlist composition, and the reasoning attached to every decision. The platform records these choices; it does not author them.
In CandidRanker, recruiters own the criteria, the review of every parse and ranking, and each shortlist decision.
## Consistency without removing autonomy
Shared role criteria keep shortlists comparable across recruiters. Within that frame, recruiters retain the judgment that makes hiring work for the specific role and team.
CandidRanker's deterministic scoring supplies the consistency; the recruiter supplies the judgment on top of it.
## Policy alignment through criteria
Organisational hiring policy is encoded into the criteria recruiters operate against. Policy alignment is therefore a property of every evaluation rather than a separate compliance project.
CandidRanker encodes policy in the role criteria recruiters themselves manage.
## Operational outcomes
- Shortlist decisions stay attributable to a named recruiter.
- Recruiter judgment is preserved as the source of hiring quality.
- Policy alignment is visible in the criteria, not hidden in a model.
- Workflow records support later review without slowing recruiters down.
These outcomes hold on CandidRanker whether one recruiter runs the role or a team of ten does.
## Frequently asked questions
Q: What does 'recruiter-governed' mean?
A: Recruiters define and own the role criteria, the evaluation weights, and the shortlist decisions. CandidRanker supports the workflow; it does not impose criteria or decide outcomes.
Q: Why does workflow governance live with recruiters?
A: Recruiters carry domain knowledge of the role, the market, and the hiring manager's expectations. Workflow governance is most defensible when the people closest to those signals are the ones controlling it.
Q: What can a recruiter change in the workflow?
A: Role criteria, criterion weights, ranking overrides, shortlist composition, reasoning notes, and the criteria revisions visible in the workflow record.
Q: How is recruiter governance kept consistent across a team?
A: Role criteria are explicit and shared. Two recruiters running the same role evaluate against the same framework, which keeps shortlists comparable without removing recruiter autonomy.
Q: Does recruiter governance conflict with hiring policy?
A: No. Organisational policy is encoded into the criteria the recruiter operates against. Recruiter authority operates inside that frame, not outside it.
Q: How does this compare to algorithmically governed workflows?
A: Algorithmically governed workflows make the model the policy author. Recruiter-governed workflows keep policy with the people, and use CandidRanker to apply that policy consistently and visibly.
---
# Recruitment audit trail as a time-ordered record of every workflow event
URL: https://minmaxhr.com/resources/recruitment-audit-trail
Category: Governance reference
Published: 2026-07-02 · Updated: 2026-08-11
Most hiring disputes come down to four questions: who evaluated what, against which criteria, when, and what shortlist they produced. A recruitment audit trail answers all four with a structured record.
A recruitment audit trail is the time-ordered, append-only record of criteria, ranking, recruiter reasoning, overrides, shortlist decisions, and access history that the hiring workflow generates.
## What the audit trail captures
- Criteria definition and any revisions, with recruiter and timestamp.
- Ranking and per-criterion reasoning at each evaluation step.
- Recruiter overrides and reasoning notes.
- Shortlist decisions and the named recruiter behind each one.
- Access history at the role and workspace level.
This list is CandidRanker's audit log in practice: criteria, rankings, reasoning, decisions, actors, timestamps.
## Append-only by design
The record is append-only. Criteria revisions and overrides are new events; nothing is rewritten. That property is what makes the trail defensible at review time.
CandidRanker's log works the same way: events are added, never edited, so the record stays trustworthy.
## Scoped, isolated access
Role-based access controls scope visibility to the recruiter, hiring manager, or administrator who needs it. Tenant isolation prevents any cross-tenant access to the trail.
On the MinMaxHR platform, the trail inherits workspace isolation: a client's reviewers see that client's record and nothing else.
## Retention as a recorded property
Retention is configured per workspace based on policy and regulatory frame. Retention configuration is itself a recorded property of the workflow.
CandidRanker keeps fulfilled roles' full history (candidates, rankings, decisions) reviewable after the role closes.
## Operational outcomes
- Hiring disputes have structured, evidence-backed answers.
- Recruiter accountability is recorded by default.
- HR, policy, and procurement reviews draw evidence directly from the system.
- Long-tail decision review remains possible months and years later.
With CandidRanker, the answer to 'can you show us?' is a lookup, not a project.
## Frequently asked questions
Q: What is a recruitment audit trail?
A: A time-ordered record of every workflow event in a hiring round (criteria definition, ranking, recruiter override, shortlist decision, access) with the recruiter and timestamp attached.
Q: What questions can a recruitment audit trail answer?
A: Who evaluated what, against which criteria, when, and what shortlist they produced. Those four questions cover most HR, leadership, and audit reviews.
Q: How is the audit trail created?
A: As a byproduct of the structured workflow. Recruiters do their normal work; the trail records itself.
Q: Can the audit trail be edited?
A: No. The record is append-only. Criteria revisions, overrides, and reasoning updates are new events; nothing is rewritten.
Q: Who can read the audit trail?
A: Role-based access controls scope visibility: recruiters see their roles, hiring managers see their requisitions, administrators see workspace-level history. Tenant isolation prevents cross-tenant access.
Q: How long is the audit trail retained?
A: Retention is configured per workspace based on the customer's policy and regulatory frame. Retention is itself a recorded property of the workflow.
---
# Recruitment automation, done calmly: where to automate and where to stay human
URL: https://minmaxhr.com/resources/recruitment-automation
Category: Workflow reference
Published: 2026-07-02 · Updated: 2026-08-11
Recruitment automation works when it removes the manual drag from screening and shortlisting without removing recruiter judgment from the decision. The line between the two is where most automation efforts succeed or fail.
Recruitment automation improves Time to Hire and shortlist quality when it automates candidate ranking and prioritisation but keeps recruiters as the shortlist decision-maker.
## The honest version of the automation pitch
Most recruitment automation tools promise to "screen candidates for you." In practice, that usually means a black-box model rejects candidates without recruiter visibility. The result is faster pipelines, weaker shortlists, and decisions no one can defend. The calm version of automation is narrower: automate the prioritisation, not the decision.
It is the pitch MinMaxHR makes for CandidRanker: automate the reading, never the deciding.
## What to automate first
Start with the steps where manual effort scales worst: scoring every candidate against the role criteria, surfacing the strongest matches first, and producing a per-criterion explanation recruiters can review. This is the highest-leverage automation in hiring and the lowest-risk one when the recruiter still owns the final shortlist.
CandidRanker automates exactly this slice: parsing, deduplication, and ranking at roughly 100 resumes a minute.
## What to leave to recruiters
Shortlist decisions, candidate rejections, hiring-manager alignment, and offer conversations. These require accountability, judgment, and context that automation cannot supply. Tools that automate these steps create legal, brand, and quality risks that almost always outweigh the time saved.
CandidRanker enforces the boundary structurally: no candidate is ever rejected without a named recruiter's decision and reason.
## How structured ranking changes the workflow
When ranking is structured against shared role criteria, the recruiter starts every shortlist from a prioritised list with visible reasoning. They override anything they disagree with, and the final shortlist is built from recruiter judgment applied to a consistent foundation rather than from raw resume triage.
In CandidRanker, the ranked list arrives with reasoning attached, so review starts from evidence instead of a blank pile.
## Measuring whether automation is actually working
Track shortlist consistency across recruiters, recruiter time per role, interview-to-offer conversion, and 90-day Quality of Hire. Automation that moves the first three but not the fourth is automation that has speeded up the pipeline without improving hiring outcomes, usually a sign the decision step has been over-automated.
CandidRanker's funnel analytics give you the before/after: time-to-shortlist, decisions per week, time-to-fill.
## Frequently asked questions
Q: What is recruitment automation?
A: Recruitment automation is the use of software to take repeatable steps in hiring (sourcing, screening, scheduling, ranking) off recruiters' plates without removing recruiter judgment from the decision.
Q: Which parts of recruitment should be automated first?
A: The highest-leverage automation is structured candidate ranking and shortlist prioritisation. These are the steps where manual effort scales worst and where recruiter time is most expensive.
Q: Which parts of recruitment should never be fully automated?
A: Final shortlist decisions, candidate rejections, and offer conversations. These need recruiter accountability and human context. Automating them creates legal, brand, and quality risks.
Q: How is MinMaxHR's approach to recruitment automation different?
A: MinMaxHR automates the prioritisation and explanation work, ranking candidates against role criteria with visible reasoning, while keeping recruiters in charge of the shortlist decision.
Q: Does recruitment automation replace recruiters?
A: No. Recruitment automation removes the manual screening drag so recruiters can spend their time on candidate conversations and hiring-manager alignment, not resume triage.
Q: What KPIs improve with structured recruitment automation?
A: Time to Hire, shortlist quality, recruiter throughput per role, and Quality of Hire all move when the screening and ranking steps are structured rather than ad hoc.
Q: How does recruitment automation fit with an existing ATS?
A: MinMaxHR sits next to the ATS as a Hiring Decision System. The ATS keeps the workflow and records; MinMaxHR runs the structured ranking and shortlist evaluation alongside it.
Q: Is recruitment automation safe under DPDP and GDPR?
A: When the workflow keeps recruiters as the decision-maker and preserves evaluation reasoning, recruitment automation aligns with DPDP (India) and GDPR (EU/UK) expectations for human-reviewed decisions.
---
# Resume ranking software: rank every resume against the job description
URL: https://minmaxhr.com/resources/resume-ranking-software
Category: Workflow reference
Published: 2026-07-09 · Updated: 2026-08-11
Resume ranking software answers a precise question: given this job description and these resumes, in what order should a recruiter read them? The answer is only useful if the ranking is anchored to the role and the reasoning is visible.
Resume ranking software scores every resume against a specific job description across defined dimensions, returning a prioritized, explainable list instead of a keyword match count.
## Ranking against the JD, not against a template
Generic screening scores resumes against an idealized shape: brand-name employers, linear careers, familiar keywords. Ranking software anchors to the actual job description: the role's skills, experience context, and requirements are the yardstick, and every candidate is measured against it.
CandidRanker ranks against the specific JD you upload. There is no generic 'good resume' template anywhere in the loop.
## The eight dimensions of a fit score
In CandidRanker, every fit score decomposes across eight dimensions: skills, experience, tools, education, title, certifications, projects, and semantic fit. Each dimension carries its own evidence, visible to the recruiter. Nothing is a single opaque number.
The score is deterministic: the same resume against the same JD produces the same score, every run. That consistency is what makes rankings comparable across batches and defensible in review.
## Skill depth and recency, not keyword counts
Two resumes can both say 'Python'. One used it daily for six years, ending last month; the other touched it in a course in 2019. CandidRanker weights how long a skill was used and how recently, the difference between matching words and evaluating capability.
## From upload to ranked list
- Upload the job description for the role.
- Drag in the resume pile: any format, including scans.
- Parsing runs in the background at ~100 resumes a minute.
- The ranked list surfaces with top matches highlighted.
- Open any candidate for the per-dimension breakdown.
In CandidRanker this takes about five minutes for a typical role, with parsing at roughly 100 resumes a minute.
## The plain-English explanation layer
A ranked list still needs a story for the hiring manager. One click generates a two-to-three-sentence explanation of why a candidate fits: grounded in the score evidence, ready to forward. The recruiter-to-hiring-manager handoff drops from a meeting to a message.
This layer is CandidRanker's match explanation: written for hiring managers, not data scientists.
## One candidate, many roles
Because ranking is anchored to the JD, the same candidate can be ranked against every open role. Strong applicants surface where they actually fit best, instead of being filed against the one role they happened to apply to.
CandidRanker scores the same candidate independently against each open JD, because fit is role-specific.
## What ranking changes downstream
- Recruiters read the strongest candidates first, not last.
- Shortlists carry visible reasoning per candidate.
- Rankings are consistent across batches and recruiters.
- Every ranking decision is logged and reviewable.
CandidRanker's funnel shows the downstream effect in numbers: faster decisions, steadier shortlists, a written record.
## Frequently asked questions
Q: What is resume ranking software?
A: Resume ranking software scores every resume against a specific job description and returns a prioritized list, so recruiters review candidates in order of role fit instead of upload order. CandidRanker adds per-dimension evidence and plain-English explanations to each rank.
Q: How does CandidRanker rank resumes against a job description?
A: Each resume is scored across eight dimensions (skills, experience, tools, education, title, certifications, projects, and semantic fit) against the specific JD. Scores are deterministic and break down with visible evidence per dimension.
Q: Can I rank resumes against a JD for free before buying?
A: You can see it on your own data first: open CandidRanker at app.candidranker.com and upload one job description with its applicants, or book a live walkthrough with the MinMaxHR team at minmaxhr.com/contact.
Q: Is AI resume ranking accurate?
A: Accuracy depends on anchoring and inputs. Ranking anchored to the actual JD, with skill depth and recency weighting, consistently outperforms keyword matching, and because CandidRanker's scores are explainable, recruiters can verify the reasoning instead of trusting a number.
Q: What does 'deterministic scoring' mean and why does it matter?
A: Same resume, same JD, same score. Every run. Without determinism, rankings drift between batches and cannot be compared or audited. Deterministic scoring is what makes a ranking defensible to hiring managers and auditors.
Q: How fast can resume ranking software process a large batch?
A: CandidRanker parses roughly 100 resumes a minute in the background. A 300-application role is ranked in a few minutes, and recruiters can keep working while it runs.
Q: Does resume ranking work on scanned resumes and images?
A: Yes. CandidRanker's parsing pipeline handles PDFs, Word documents, scanned images, and photos of paper resumes using OCR, so ranking starts from complete candidate data regardless of file format.
Q: Can the ranking be adjusted after the first run?
A: Yes. Recruiters can re-weight criteria, override rankings, add notes, and re-run. CandidRanker never auto-rejects. The ranked list is decision support, and the recruiter owns the final shortlist.
Q: How do hiring managers consume a ranked resume list?
A: Through the one-click ranking report: filtered, sorted, shortlist-first, with JD detail, exportable as CSV or a clean printable view. Plus a plain-English match explanation per candidate that a busy manager can act on in seconds.
Q: Does resume ranking software integrate with an ATS?
A: It sits next to the ATS. The ATS manages workflow and records; the ranking layer handles evaluation. CandidRanker also exposes a REST API and an MCP server, so rankings can flow into the tools, and AI assistants, a team already uses.
---
# Resume screening benchmarks: the numbers behind a defensible shortlist
URL: https://minmaxhr.com/resources/resume-screening-benchmarks
Category: Workflow reference
Published: 2026-07-09 · Updated: 2026-08-11
If you benchmark one thing in screening, benchmark this: a corporate opening attracts roughly 200–250 applications, a recruiter's initial manual scan lasts about 7.4 seconds, and modern ranking systems parse the same pile at roughly 100 resumes a minute. This page collects the reference numbers (industry figures with their sources, and CandidRanker's own published performance targets) in one citable place.
All CandidRanker figures below are the product's published operating targets, kept current with each release. Industry figures are attributed to their original studies.
## The volume benchmarks
- Applications per corporate opening: commonly cited at roughly 250 (Glassdoor's widely referenced figure), with campus drives and mass roles in India running far higher.
- Manual scan time: about 7.4 seconds per resume on initial review (The Ladders eye-tracking research).
- Manual reading time at 2 minutes per resume: over 8 hours of pure reading for one 250-applicant role.
- Automated parsing throughput: roughly 100 resumes a minute in CandidRanker's batch pipeline: about 3 minutes for that same 250-resume pile, including scanned PDFs and photos via OCR.
## The quality benchmarks
- Scoring dimensions: 8 per candidate in CandidRanker (skills, experience, tools, education, title, certifications, projects, and semantic fit) each visible to the recruiter.
- Determinism: identical resume + identical JD = identical score, every run. If your current tool cannot promise this, its rankings cannot be compared across time.
- Score scale: 0–100 for both the JD match score and the separate ATS quality score (how machine-readable the resume itself is).
- Auto-rejections: 0. No candidate is ever rejected by the system; every decision is made by a named recruiter with a recorded reason.
## The speed-to-decision benchmarks
- Upload to first ranked shortlist: about 5 minutes for a typical role in CandidRanker, the 'five minutes to your first ranking' workflow.
- Duplicate handling: duplicate resumes are caught by content hash before any AI runs, so batch counts and funnel metrics stay clean.
- Report generation: one click to a CSV or printable ranking report, share-ready for hiring managers.
## The governance benchmarks
- Decisions logged to a named recruiter: 100%. The audit trail is a byproduct of the workflow, not an extra step.
- Employment gaps: surfaced as interview talking points when six months or longer; never scored as penalties.
- Data residency: hosted on Google Cloud asia-south1 (Mumbai, India), with tenant-isolated workspaces, the configuration DPDP and GDPR reviews ask about first.
All three are CandidRanker workflow defaults, not configuration.
## How to use these numbers
Benchmark your own funnel against three of them: how long from role opening to first shortlist (target: same day, not same week), what fraction of resumes get a full read rather than a 7-second scan (target: all of them), and what fraction of decisions have a recorded reason (target: 100%). Any screening tool, CandidRanker included, should be judged on whether it moves those three numbers.
## Frequently asked questions
Q: How many applications does a job posting get on average?
A: The most commonly cited figure is roughly 250 applications per corporate opening (Glassdoor). High-volume contexts (campus drives, mass hiring in India, remote-friendly roles) routinely exceed it several times over.
Q: How long do recruiters spend reading a resume?
A: Eye-tracking research by The Ladders measured the initial scan at about 7.4 seconds. That scan decides whether the resume gets a real read, which is why structured ranking like CandidRanker's, where every resume is parsed in full, changes shortlist quality.
Q: How fast is automated resume screening?
A: CandidRanker's batch pipeline processes roughly 100 resumes a minute, including scanned documents and photos via OCR. A 250-resume opening parses in about 3 minutes; the full upload-to-ranked-shortlist workflow takes about 5 minutes for a typical role.
Q: What is a good time-to-shortlist benchmark?
A: Same day. If resumes arrive Monday morning, a ranked, explained shortlist should exist Monday afternoon, not the following week. Structured ranking makes that the default rather than the exception.
Q: Are these benchmarks independent?
A: The industry figures (250 applications, 7.4-second scans) come from third-party studies and are attributed inline. The performance figures (100 resumes/minute, 8 dimensions, 5-minute workflow, 0 auto-rejections) are CandidRanker's own published operating targets, stated so they can be tested on the free plan.
---
# Resume screening software: an honest buyer's guide for 2026
URL: https://minmaxhr.com/resources/resume-screening-software
Category: Buyer guide
Published: 2026-07-09 · Updated: 2026-08-11
Resume screening software promises one thing: fewer hours spent reading resumes that were never going to make the shortlist. The honest version of that promise depends on how the software screens: keyword filters, black-box AI scores, or explainable ranking against the role.
The best resume screening software ranks every candidate against the specific role with visible reasoning. It does not auto-reject, and it does not hide the score behind a black box.
## What resume screening software actually does
Resume screening software reads incoming resumes, extracts structure (skills, experience, education, tools) and evaluates each candidate against the open role. Good screening software returns a prioritized list a recruiter can act on. Weak screening software returns a keyword match count and calls it a score.
CandidRanker occupies the explainable end of this spectrum: full-text parsing and eight-dimension scoring against the specific JD.
## The three types of screening tools on the market
Keyword filters match text strings in the resume against text strings in the job description. They are fast and cheap, and they miss every strong candidate who described the same skill with different words.
Black-box AI screeners produce a fit score without showing the reasoning. They save time until a hiring manager, a candidate, or an auditor asks why someone was ranked down, and nobody can answer.
Explainable ranking systems, the category MinMaxHR's CandidRanker sits in, score every candidate against the specific role across defined dimensions, and show the per-dimension evidence behind every score. Same inputs, same score, every time.
## The buying checklist: eight questions that separate tools
- Does it rank against the specific role, or against a generic resume shape?
- Can a recruiter see why each candidate scored what they scored?
- Is the score deterministic: same resume, same JD, same score?
- Does it parse real-world files: PDFs, Word docs, scanned images?
- Can it handle volume, hundreds of resumes in one batch?
- Does it auto-reject, or does the recruiter keep the decision?
- Can it produce a share-ready report for the hiring manager?
- Where is candidate data hosted, and who can access it?
Ask CandidRanker the same eight questions. The answers are published openly on MinMaxHR's pricing and how-it-works pages.
## How CandidRanker screens: rank, explain, decide
Upload a job description and a stack of resumes. CandidRanker ranks every candidate against that role, not a keyword search, an actual fit score broken down across eight dimensions: skills, experience, tools, education, title, certifications, projects, and semantic fit.
Every score is deterministic and explainable. Open any candidate and the per-dimension evidence is visible, which criteria matched, which did not, and why. One click generates a plain-English match explanation ready to forward to the hiring manager.
## Parsing is where most screening tools quietly fail
Recruiters do not receive clean, uniform resumes. They receive two-column PDFs, scanned images, photos of paper resumes, and Word files with tables. CandidRanker's parsing pipeline reads all of them, including OCR for image-only files, so screening starts from complete data, not from whatever survived a fragile parser.
## Throughput: what 'fast' means in practice
For high-volume hiring, throughput is the metric that matters. CandidRanker batch-processes roughly 100 resumes a minute: drag in a whole folder, keep working while parsing runs in the background, and come back to a ranked list.
## Screening without auto-rejection
CandidRanker never auto-rejects a candidate. The software prioritizes and explains; the recruiter makes the shortlist decision. Every shortlist, select, and reject is logged with the recruiter's name and the reasoning visible at the time, which is what makes the screening defensible in a compliance review.
## What this changes operationally
- Hours of manual screening collapse into minutes.
- The strongest role-fit candidates are reviewed first.
- Hiring managers get shortlists with reasoning attached.
- Screening decisions are auditable, not anecdotal.
On CandidRanker these changes start on the free plan: ₹0 for 100 resumes and 10 job descriptions.
## Frequently asked questions
Q: What is resume screening software?
A: Resume screening software reads incoming resumes, extracts skills and experience into structured data, and evaluates each candidate against an open role so recruiters review the most relevant candidates first instead of reading every resume manually.
Q: What is the best resume screening software for high-volume hiring?
A: For high-volume hiring, look for three things: batch throughput (CandidRanker processes roughly 100 resumes a minute), parsing that handles messy real-world files including scanned images, and explainable ranking so the speed does not come at the cost of defensibility.
Q: How is AI resume screening different from keyword filtering?
A: Keyword filtering matches text strings and misses candidates who describe the same skill differently. AI screening like CandidRanker evaluates actual role fit across eight dimensions (skills, experience, tools, education, title, certifications, projects, and semantic fit) with visible reasoning per dimension.
Q: Does resume screening software reject candidates automatically?
A: Some tools do, and that is a compliance risk. CandidRanker never auto-rejects: it ranks and explains, and the recruiter always makes the shortlist decision. Every decision is logged to a named recruiter.
Q: Can resume screening software read scanned or image-based resumes?
A: Most tools cannot. CandidRanker's parsing pipeline handles PDFs, Word documents, scanned images, and even photos of paper resumes, using OCR for image-only files, so no candidate is dropped because of file format.
Q: How does explainable scoring work in resume screening?
A: Every candidate score breaks down across defined dimensions with per-dimension evidence. Recruiters and hiring managers can see exactly why a candidate ranked where they did. Same inputs always produce the same score, which makes the ranking auditable.
Q: How much time does resume screening software save?
A: Manual screening of 300 applications takes days of recruiter time. Automated ranking collapses that into minutes: resumes parse in the background at roughly 100 per minute and surface as a ranked list, so recruiter time shifts from scanning to judgment.
Q: Does resume screening software replace an ATS?
A: No. An ATS manages the workflow: postings, stages, status. Screening and ranking software like CandidRanker sits next to the ATS and handles the decision step: evaluating and prioritizing candidates. MinMaxHR calls this a Hiring Decision System.
Q: Is resume screening software safe to use under GDPR and India's DPDP Act?
A: It can be, if the tool is built for it: data hosted in-region, per-workspace access control, no automated rejection, and a preserved decision trail. CandidRanker hosts data in-region with malware scanning on uploads by default and full decision logging.
Q: Can I try resume screening on my own job description and resumes?
A: Yes. Open CandidRanker at app.candidranker.com, upload a job description and a batch of resumes, and review the ranked list with per-candidate reasoning. Or book a live walkthrough with the MinMaxHR team at minmaxhr.com/contact.
Q: How do I compare resume screening tools before buying?
A: Test with your own messy resumes, not the vendor's clean samples. Check whether the score is explainable and deterministic, whether parsing survives scanned files, whether it auto-rejects, and whether it can produce a report a hiring manager can act on.
---
# Role-based hiring workflows that scope candidate data to the work
URL: https://minmaxhr.com/resources/role-based-hiring-workflows
Category: Governance reference
Published: 2026-07-02 · Updated: 2026-08-11
Candidate data is sensitive and incidental exposure is a real workflow risk. Role-based hiring workflows scope visibility to the recruiter, hiring manager, or administrator who needs it for the work in front of them.
Role-based hiring workflows use role-based access controls and tenant isolation to scope candidate data to the recruiter, hiring manager, or administrator who needs it.
## Why scoped access is a workflow property
Open access produces incidental exposure that nobody intended. Scoped access keeps candidate visibility tied to the work each role is actually responsible for.
CandidRanker implements scoping at the workspace level, so access follows the work by construction.
## What each role sees
- Recruiters: the roles they own, end to end.
- Hiring managers: the requisitions they sponsor and shortlists prepared for them.
- Administrators: workspace-level configuration and access history.
CandidRanker scopes recruiters, hiring managers, and administrators to exactly the candidates and roles they work on.
## Tenant isolation as the workspace boundary
Tenant isolation keeps each customer's hiring data inside their own workspace. Role-based access then scopes visibility inside that boundary. The two together define the data perimeter for every workflow.
This is the MinMaxHR workspace model: one isolated tenant per team or client, with nothing crossing the boundary.
## Access events as workflow record
Access at the role and workspace level is part of the same workflow record that holds criteria, ranking, and shortlist decisions. Reviewers see who accessed what, when, and why.
In CandidRanker, access lands in the same audit log as decisions, so reviews cover who saw data as well as who acted on it.
## Workspace-scoped role definitions
Role definitions can be customised per workspace so customers can match their internal hiring model, without affecting the underlying governance properties.
CandidRanker defines roles per workspace, so an agency can grant a client reviewer access in one workspace without touching another.
## Operational outcomes
- Candidate data exposure stays scoped to the work.
- Procurement and policy reviews have direct evidence on access posture.
- DPDP and GDPR alignment is supported by default.
- Workspace governance scales with the team.
CandidRanker makes least-privilege the path of least resistance.
## Frequently asked questions
Q: What is a role-based hiring workflow?
A: A workflow where recruiters, hiring managers, and administrators see only the candidate data their role requires. Access is scoped to the work, not to the workspace, the model CandidRanker implements per tenant.
Q: Why does role-based access matter in hiring?
A: Candidate data is sensitive. Scoped access removes incidental exposure, supports policy and procurement expectations, and aligns with DPDP and GDPR-aligned governance.
Q: What does each role see?
A: Recruiters see the roles they own. Hiring managers see the requisitions they sponsor and the shortlists prepared for them. Administrators see workspace-level configuration and access history.
Q: How does tenant isolation interact with role-based access?
A: Tenant isolation is the workspace boundary; role-based access is the per-role scoping inside that boundary. Together they keep candidate data scoped to the people who need it and inside the customer's workspace, exactly how CandidRanker workspaces are built.
Q: Are access events recorded?
A: Yes. Access at the role and workspace level is part of the workflow record, alongside criteria, ranking, and shortlist decisions.
Q: Can access roles be customised per workspace?
A: Yes. Role definitions are workspace-scoped so customers can match their internal hiring model without affecting the underlying governance properties.
---
# MinMaxHR security and data handling: the procurement answers, stated precisely
URL: https://minmaxhr.com/learn/security
Category: Trust
Published: 2026-08-11 · Updated: 2026-08-11
MinMaxHR stores and processes candidate data in Mumbai, India (Google Cloud asia-south1), isolates every workspace at the database level, encrypts data in transit and at rest, scans uploads for malware by default, and time-bounds support access to a maximum of 24 hours with separate logging. CandidRanker acts as a data processor for workspace data.
This page is written for the people who actually read it: security reviewers, IT, legal and procurement. It states specifics rather than adjectives, and it says plainly where a control stops.
MinMaxHR implements SOC 2-aligned controls across access management, encryption, logging and data handling, with independent certification on the roadmap. Every control described on this page is testable on the free plan before any commercial conversation, verification beats assertion.
## Data residency
Customer and candidate data is stored and processed in Mumbai, India, on Google Cloud region asia-south1. This is the first question most Indian procurement teams ask and the first one many vendors answer vaguely.
MinMaxHR states residency as a fact about where the data sits. It does not present that as a blanket legal conclusion about every localisation or cross-border transfer requirement your organisation may be subject to. That assessment depends on your deployment, your sector and your contracts, and should be made with your own counsel.
## Tenant isolation and access control
- Every API request is checked against workspace membership before any data is returned.
- Database-level row security operates underneath that check as defence in depth, so an application-layer mistake does not become a data leak.
- API keys and AI assistant tokens are bound to a single workspace and carry only the scopes granted at issue.
- Roles scope what recruiters, hiring managers and administrators can see to the work in front of them.
- For staffing agencies this is the operative control: one isolated workspace per client, with nothing crossing the boundary.
## Encryption and credential handling
Data is encrypted in transit with TLS and encrypted at rest. API keys are stored as SHA-256 hashes rather than recoverable secrets, which means MinMaxHR cannot show you an existing key. A lost key is reissued, not retrieved. That is the correct behaviour, and it is worth knowing before you need it.
## Upload hygiene
Every uploaded file is malware scanned by default. A workspace setting can disable scanning; files uploaded while it is disabled are marked unscanned so the state is visible rather than assumed. Infected or unscannable files are quarantined and flagged.
The precision matters. An earlier version of MinMaxHR's own buyer material said every file is scanned, full stop. That was an overstatement, it was corrected, and the corrected wording is what appears here and everywhere else on this site.
## Support access
MinMaxHR support staff do not hold standing access to customer workspaces. Access is explicit, granted for a defined purpose, time-bounded to a maximum of 24 hours, read-only unless you grant more, and logged separately from ordinary workspace activity so you can review it independently.
## Deletion, retention and data subject rights
Deletion removes extracted data, rankings and stored files, including quarantined copies. Retention is a recorded property of the workspace rather than an informal habit.
Deletion is available today. One-click data-subject export is on the roadmap; if a subject-access workflow is a procurement requirement for you, raise it early so we can confirm where it stands for your timeline.
## Governance controls a reviewer can test
- No candidate is ever auto-rejected: shortlist, select and reject are human actions requiring a written reason.
- Every decision is attributable to a named recruiter, with the reason stored alongside it.
- Changes to scoring weights, ranking filters, skills, aliases and terminology are recorded with the person, the time, the before and after values, and a reason.
- Decision history, configuration changes, document edits and re-parses, membership changes and support access are all preserved in audit history.
- Scoring is deterministic, so the ranking reconstructed in an audit is the ranking the system actually produced.
These are testable on the MinMaxHR free plan before any commercial conversation. That is deliberate: a control you have verified yourself is worth more than a control we have asserted.
## Regulatory position
CandidRanker acts as a data processor for workspace data. MinMaxHR's design is aligned with India's DPDP Act and with GDPR expectations around automated decisions, principally by ensuring decisions are not solely automated. Legal conclusions for your specific deployment, sector and transfer requirements should be reviewed by your own counsel; this page is product and control documentation, not legal advice.
## Frequently asked questions
Q: Where does MinMaxHR store candidate data?
A: In Mumbai, India, on Google Cloud region asia-south1, in tenant-isolated workspaces with TLS in transit and encryption at rest.
Q: Is MinMaxHR SOC 2 certified?
A: MinMaxHR implements SOC 2-aligned controls across access management, encryption, logging and data handling, with independent certification on the roadmap. Procurement teams can verify every control described here directly on the free plan rather than taking it on trust. If a completed SOC 2 report is a prerequisite at signing for your organisation, tell us early and we will confirm where certification stands against your timeline.
Q: How are staffing agency clients kept separate in CandidRanker?
A: Each client gets a fully isolated workspace. API requests are checked against workspace membership and database-level row security operates underneath as defence in depth. API keys and assistant tokens are workspace-bound.
Q: Are uploaded resumes scanned for malware?
A: Yes, by default. A workspace setting can disable scanning, and files uploaded while it is disabled are marked unscanned so the state is visible. Infected or unscannable files are quarantined and flagged.
Q: Can MinMaxHR staff access our candidate data?
A: Not by default. Support access is explicit, time-bounded to a maximum of 24 hours, read-only unless you grant more, and logged separately so you can review it.
Q: Can we delete candidate data on request?
A: Yes. Deletion removes extracted data, rankings and stored files including quarantined copies. One-click data-subject export is on the roadmap.
Q: Is CandidRanker a data controller or a data processor?
A: CandidRanker acts as a data processor for workspace data. Your organisation remains the Data Fiduciary or controller for the candidate data you collect.
Q: What can a security reviewer verify without a contract?
A: Most of it. The MinMaxHR free plan lets a reviewer test deterministic scoring, per-dimension explainability, the absence of auto-rejection, named-recruiter decision records, and the audit trail on real data before any commercial commitment.
---
# Structured candidate evaluation as the foundation of consistent shortlists
URL: https://minmaxhr.com/resources/structured-candidate-evaluation
Category: Governance reference
Published: 2026-07-02 · Updated: 2026-08-11
Shortlist quality is a function of evaluation consistency. Structured candidate evaluation makes every candidate measurable against the same role criteria, so shortlists stop depending on which recruiter ran the role.
Structured candidate evaluation scores every candidate for a role against recruiter-defined criteria with the same weights, surfacing per-criterion reasoning and explicit ranking.
## Why unstructured evaluation produces drift
Without a shared frame, two recruiters reviewing the same role produce two different shortlists. Neither is wrong, but neither is comparable, and shortlist quality becomes a function of which recruiter ran the role.
CandidRanker removes the drift at its source: every resume is scored against the same criteria with the same weights, every time.
## What structured evaluation produces
An ordered list of candidates with per-criterion reasoning and a JD-fit explanation. The recruiter sees the strongest matches first, with the evidence behind each ranking visible at the point of decision.
In CandidRanker, the output is a ranked list with per-dimension evidence: comparable across candidates, recruiters, and weeks.
## Recruiter authority inside the frame
The structure is the frame; the recruiter is the decision-maker. Weights, overrides, reasoning notes, and shortlist composition stay with the recruiter.
CandidRanker keeps the recruiter in charge of the frame itself: they set the criteria and make every decision inside it.
## Where structure pays back
- Shortlists stay consistent across recruiters.
- Hiring managers receive comparable candidates from the same pipeline.
- Recruiter judgment goes where it matters, not into screening throughput.
- Workflow records support later review without extra effort.
Teams see the payback fastest in CandidRanker's funnel analytics: steadier shortlists, faster time-to-decision.
## Frequently asked questions
Q: What is structured candidate evaluation?
A: Scoring every candidate for a role against the same recruiter-defined criteria with the same weights, with the reasoning visible at each step.
Q: Why is unstructured evaluation a problem?
A: Without a shared frame, two recruiters reviewing the same role produce two different shortlists, neither of them comparable. Hiring quality drifts and hiring managers lose trust in the pipeline.
Q: What does the structure look like in practice?
A: Recruiter-defined criteria, criterion weights, per-candidate scoring, per-criterion reasoning, and an explicit ranking. Recruiters keep override authority over every step.
Q: How is structured evaluation different from a checklist?
A: A checklist filters; structured evaluation ranks. In CandidRanker, the recruiter sees ordered candidates with reasoning rather than a binary pass/fail.
Q: Does structured evaluation reduce recruiter judgment?
A: No. It frames where judgment is applied. Recruiters spend their judgment on candidates that matter, not on screening throughput.
Q: How does this support shortlist quality?
A: Because every candidate is evaluated against the same frame, the strongest candidates surface consistently. Shortlist quality stops depending on which recruiter ran the role.
---
# Structured hiring workflows for consistent recruiter evaluation
URL: https://minmaxhr.com/resources/structured-hiring
Category: Workflow reference
Published: 2026-07-02 · Updated: 2026-08-11
When evaluation drifts between recruiters, shortlists become unpredictable, hiring managers lose trust in the pipeline, and Quality of Hire suffers. Structured hiring workflows fix the workflow design, not the recruiter.
Structured hiring workflows help recruiters evaluate candidates using consistent criteria, reducing shortlist inconsistency and improving hiring visibility.
## Why hiring workflows become inconsistent
In most teams, the rules for evaluating a role live in three places at once: the JD, the hiring manager's head, and the recruiter's own pattern recognition. When those three diverge, evaluation drifts. Two recruiters reviewing the same role can produce two different shortlists, neither of them wrong, but neither of them comparable.
That inconsistency is invisible until a hiring manager pushes back on a shortlist or until a role has to be re-opened. By then, the shortlist that caused the problem is already closed.
This inconsistency is what CandidRanker's deterministic, criteria-anchored scoring is built to remove.
## The recruiter overload problem
When a role attracts hundreds of applications, manual screening forces recruiters to make shortlist decisions on partial information. Attention narrows to a few signals (a known employer, a familiar tool, a matching keyword) and stronger candidates with less obvious resumes get filtered out.
CandidRanker absorbs the volume side, parsing roughly 100 resumes a minute, so recruiter attention goes to judgment, not triage.
## What a structured workflow replaces
A structured workflow replaces the implicit, in-head evaluation with an explicit, role-anchored evaluation. The recruiter still owns the shortlist decision; the criteria are just visible, shared, and applied consistently across every candidate.
On the MinMaxHR platform, each replaced step becomes a recorded one: parse, rank, decide, report.
## Mechanism, in plain operational terms
Recruiters and hiring managers agree on the role criteria up front. Each candidate is scored against those criteria with the reasoning visible. The ranked list, the per-criterion breakdown, and the override controls are all in front of the recruiter as they shortlist.
This is CandidRanker's pipeline in generic terms. JD criteria in, ranked and explained candidates out, human decisions recorded.
## Recruiter visibility throughout the workflow
Recruiters see exactly which criteria a candidate matched, which they missed, and the reasoning behind each score. They can re-weight criteria, override a ranking, or add notes. Nothing happens silently in the background.
CandidRanker keeps every stage on screen: parse status, per-dimension scores, and the reasoning behind each rank.
## Workflow governance and policy alignment
Every evaluation is attributable to a named recruiter and a defined criteria set. Organisational hiring policy is encoded into the criteria themselves, which means policy alignment becomes a workflow property rather than a separate compliance project.
CandidRanker carries governance through the same structure: criteria encode policy, decisions carry names and reasons.
## Operational outcomes
- Shortlists stay consistent across recruiters and across hiring rounds.
- Recruiter attention shifts from screening throughput to evaluation judgment.
- Hiring managers receive shortlists they can review without re-litigating criteria.
- Workflow records support later review by HR, leadership, or audit.
These are the operational wins CandidRanker's structured workflow is designed to produce.
## Frequently asked questions
Q: What does 'structured hiring' actually mean for a recruiter team?
A: Structured hiring means every candidate for the same role is evaluated against the same set of role-specific criteria, with the same weights, by every recruiter. It is the opposite of letting evaluation drift between reviewers and hiring rounds.
Q: Why do recruiter workflows become inconsistent over time?
A: Workflows drift when role criteria live in someone's head, in a stale JD, or in a Slack thread instead of inside the evaluation system itself. Recruiters then apply their best judgment, which varies from person to person.
Q: How does manual screening create overload?
A: Manual screening forces recruiters to pattern-match through hundreds of resumes without a shared framework. The result is fatigue, narrowed attention, and shortlists built more on keyword scanning than on role fit.
Q: What does a structured hiring workflow look like end to end?
A: Role criteria are agreed up front, candidates are scored against those criteria, recruiters review the ranked shortlist with full reasoning visible, and the shortlist record is preserved with the criteria it was built against.
Q: Does structured hiring slow recruiters down?
A: No. It removes the slowest part of recruiter work, manually re-reading large piles of resumes without a framework. Recruiters spend their time on judgment, not on screening throughput.
Q: How does structured hiring handle roles with shifting requirements?
A: Criteria are recruiter-authored and editable for the role. When the requirement changes mid-hiring, the recruiter updates the criteria, re-runs the ranking, and the workflow record reflects the change.
Q: How is recruiter accountability preserved in a structured workflow?
A: Every shortlist action is attributable to a named recruiter and a defined criteria set. The workflow records who evaluated what, against which criteria, and what the resulting shortlist looked like.
Q: Can hiring managers see the structure behind a shortlist?
A: Yes. Hiring managers see the criteria the shortlist was built against, the ranking, and the recruiter's reasoning. That removes the 'why is this candidate even on the list' conversation in shortlist reviews.
Q: Does structured hiring help with high-volume hiring specifically?
A: Yes. High-volume hiring is where evaluation drift is most expensive. A structured workflow keeps every recruiter applying the same criteria, which is the only way shortlists stay consistent at scale.
Q: How is a structured hiring workflow different from an ATS workflow?
A: An ATS organises candidate records and tracks pipeline stage. A structured hiring workflow organises evaluation: how each candidate is scored against role criteria, who reviewed them, and why each shortlist decision was made. MinMaxHR adds the evaluation layer on top of the ATS.
---
# What is talent acquisition software?
URL: https://minmaxhr.com/resources/what-is-talent-acquisition-software
Category: Glossary
Published: 2026-07-02 · Updated: 2026-08-11
Talent acquisition software is the set of platforms that help HR teams evaluate, prioritise, and shortlist candidates against role criteria: a category spanning ATS, sourcing tools, ranking systems, and assessment platforms. This guide defines each layer and shows how to pick a stack that actually works together.
Talent acquisition software is the category of platforms that help HR teams source, evaluate, prioritise, and shortlist candidates against role criteria; it includes Applicant Tracking Systems, candidate ranking systems, and Hiring Decision Systems.
## The short definition
Talent acquisition software is the category of platforms HR teams use to source, evaluate, prioritise, and shortlist candidates against role criteria. It is broader than an ATS and narrower than the full HR tech stack.
MinMaxHR sits inside this definition as a Hiring Decision System, the evaluation layer of the stack.
## The five sub-categories that matter
Applicant Tracking Systems own the workflow and records. Sourcing platforms find candidates. Assessment tools evaluate skills. Candidate ranking systems prioritise the pile against role criteria. Hiring Decision Systems combine ranking and structured evaluation into the shortlist decision step. Most enterprise stacks run two or three of these in parallel.
MinMaxHR's CandidRanker belongs to the ranking-and-evaluation sub-category, designed to sit next to whichever ATS you run.
## How to pick a stack that actually works
Pick the ATS first based on hiring volume and team shape. Add a ranking layer or Hiring Decision System on top when shortlist consistency becomes the bottleneck. Add sourcing tooling only when you genuinely run out of inbound candidates. This order keeps cost and complexity proportional to the problem.
A working example: your ATS for workflow, CandidRanker for ranking and shortlist decisions, assessments only for the final few.
## What the procurement conversation should cover
Five questions: how consistent is candidate evaluation across recruiters, can hiring managers see why each shortlist was built, is the evaluation history audit-ready, does it integrate cleanly with the existing ATS, and does it move 90-day Quality of Hire. Anything else is a feature-list distraction.
For CandidRanker the answers are public: data in asia-south1 (Mumbai), tenant isolation, named-recruiter logging, prices on the pricing page.
## Where MinMaxHR sits in this picture
MinMaxHR is a Hiring Decision System. It sits next to an ATS and adds structured candidate ranking, explainable per-criterion evaluation, and recruiter-governed shortlist workflows. The ATS keeps the workflow; MinMaxHR runs the decision step.
## Frequently asked questions
Q: What is talent acquisition software?
A: Talent acquisition software is the category of platforms that help HR teams source, evaluate, prioritise, and shortlist candidates against role criteria. It includes Applicant Tracking Systems, candidate ranking systems, sourcing tools, and Hiring Decision Systems.
Q: How is talent acquisition software different from an ATS?
A: An ATS is one type of talent acquisition software. It owns the hiring workflow and candidate records. Talent acquisition software is the broader category that also includes ranking, sourcing, assessment, and decision-support tools.
Q: What are the main categories of talent acquisition software?
A: Five: Applicant Tracking Systems, sourcing platforms, candidate assessment tools, candidate ranking systems, and Hiring Decision Systems. Most enterprise hiring stacks combine two or three of these.
Q: Do small teams need talent acquisition software?
A: Below about 10 hires a year, a spreadsheet usually works. Above that, the cost of lost candidates and inconsistent shortlists outweighs the subscription cost of a basic ATS plus a ranking layer.
Q: How does MinMaxHR fit in the talent acquisition software stack?
A: MinMaxHR is a Hiring Decision System. It sits next to an ATS and adds structured candidate ranking, explainable evaluation, and recruiter-governed shortlist workflows.
Q: What should HR leaders evaluate when choosing talent acquisition software?
A: Five things: candidate-evaluation consistency across recruiters, hiring-manager visibility into shortlists, audit-readiness of evaluation history, integration with existing ATS, and impact on 90-day Quality of Hire.
---
# Who CandidRanker is for: solo recruiters, agencies, and enterprise TA teams
URL: https://minmaxhr.com/resources/who-is-candidranker-for
Category: Buyer guide
Published: 2026-07-09 · Updated: 2026-08-11
CandidRanker is built for anyone who has to turn a pile of resumes into a defensible shortlist, from a founder hiring their first five people in Bengaluru to an enterprise TA team filling fifty roles a quarter. The workflow is the same; the volume and the plan change.
CandidRanker fits solo recruiters (free plan, one workspace), staffing agencies (isolated workspace per client), and enterprise TA teams (unlimited volume, REST API, MCP integration), in India and globally.
## Solo and internal recruiters: one open role, a stack of resumes
The classic case: one role, a couple of hundred applications, a deadline this week. Upload the JD and the resume pile, watch parsing finish in the background, rank against the JD, and shortlist the top five to ten with reasoning attached. Verify anyone who ranked lower than expected using the per-dimension breakdown, then export the report for the hiring manager. The Free plan (100 resumes, 10 JDs, ₹0) covers this end to end.
CandidRanker's Free plan (₹0: 100 resumes, 10 JDs) covers this scenario end to end, no payment details required.
## Staffing and recruiting agencies: many clients, isolated data
Agencies run one workspace per client. Every client's JDs and candidates stay fully isolated by design, which is the answer to the first question a client's IT team asks. Rank each client's roles inside their workspace, share the branded HTML or CSV report, and invite client-side reviewers as members when needed. Growth (₹9,999 per 30 days, 1,000 resumes, 100 JDs) fits most agencies; continuous multi-client volume moves to Enterprise.
On the MinMaxHR platform, each client gets a fully isolated CandidRanker workspace, data never crosses the boundary.
## High-volume employers: hundreds of inbound applications
For teams drowning in inbound (walk-in drives, campus hiring, mass roles) batch upload processes the entire folder at roughly 100 resumes a minute. Set screening filters, rank everyone against the role, and review in ranked order so recruiter hours go to the strongest candidates. Nothing is auto-rejected; every skipped candidate stays searchable in the library.
CandidRanker parses roughly 100 resumes a minute, OCR included, campus-drive scale by design.
## Senior and specialist hires: experts vs keyword matchers
Senior searches are where keyword tools fail loudest, the strongest candidate describes the skill in their own words and gets buried. CandidRanker's work-history extraction weights skill depth and recency, so a candidate who used a skill daily for six years outranks one who listed it once. Career gaps surface as interview talking points in the drawer, never as a silent penalty.
## Hiring ops and TA leadership: the Monday funnel review
Every shortlist, select, and reject feeds the analytics page automatically: funnel counts, decisions per week, time-to-decision, and time-to-fill per role. Hiring ops opens analytics before the Monday meeting and answers 'where is everything?' with live numbers instead of a spreadsheet built the night before.
CandidRanker's funnel analytics produce this Monday view automatically from the decision log.
## Enterprise TA teams: integration, governance, and scale
Enterprise teams add the integration layer: a full REST API with workspace-scoped keys, and an MCP server so AI assistants like Claude can list jobs, rank candidates, and pull shortlists under OAuth consent. Data is hosted in-region with malware scanning on uploads by default, tenant isolation per workspace, and a complete decision audit trail, the checklist procurement and compliance actually ask for.
Enterprise CandidRanker adds unlimited volume, the REST API, and MCP integration with any LLM.
## India-first, globally usable
CandidRanker is built by an Indian team (Hab Business Solutions), hosted in Mumbai (asia-south1), priced in INR via Razorpay, and designed around DPDP-era accountability. The evaluation engine itself is market-agnostic: role criteria, not local keyword conventions, drive the ranking, so the same workflow serves a Chennai staffing agency and a global remote-first team.
## The fit test, in one sentence each
- Solo recruiter: you have more resumes than review time, start Free.
- Agency: you juggle multiple clients. One isolated workspace each, start Growth.
- High-volume employer: hundreds of inbound applications, batch upload and rank.
- Enterprise TA: you need API, MCP, unlimited volume, and audit-grade governance, talk to sales.
If any line fits, CandidRanker's free plan is the two-week test. A real role, ranked end to end, for ₹0.
## Frequently asked questions
Q: Who is CandidRanker for?
A: Anyone turning resume piles into shortlists: solo and internal recruiters, staffing and recruiting agencies, high-volume employers, and enterprise talent acquisition teams. Plans scale from a free tier for individuals to unlimited enterprise volume with API and MCP integration.
Q: Can a solo recruiter use CandidRanker for free?
A: Yes. The Free plan (₹0) includes 100 resumes, 10 job descriptions, and 10 hiring decisions: enough to run one or two live roles end to end with full ranking, explanations, and reports.
Q: Is CandidRanker good for staffing agencies with multiple clients?
A: Yes: agencies run one isolated workspace per client, so no client's data ever crosses into another's. Rank each client's roles in their workspace and share the CSV or clean HTML report. Growth covers most agencies; Enterprise removes volume limits.
Q: Does CandidRanker work for hiring in India specifically?
A: It is India-first by design: data hosted in Mumbai (asia-south1), pricing in INR via Razorpay, and governance built for DPDP-era accountability. The ranking engine is market-agnostic, so global teams use the same workflow.
Q: Can CandidRanker handle campus or walk-in hiring volume?
A: Yes. Batch upload parses roughly 100 resumes a minute in the background, including scanned and photographed resumes via OCR. A 400-application drive is ranked the same morning.
Q: How do hiring managers and non-recruiters use CandidRanker?
A: They consume the outputs: a ranked shortlist with a plain-English fit explanation per candidate, and a one-click report (CSV or printable) for the hiring committee. Team members can be invited into a workspace by email with role-appropriate access.
Q: What does an enterprise TA team get beyond the core product?
A: Unlimited resumes, JDs, and decisions, plus REST API integration and an MCP server so AI assistants like Claude can work with recruiting data under OAuth. Combined with tenant isolation, in-region hosting, and the decision audit trail, it covers procurement's security checklist.
Q: Does CandidRanker replace the recruiter or the ATS?
A: Neither. It is a Hiring Decision System that sits next to the ATS: the ATS keeps workflow and records, CandidRanker handles evaluation and ranking, and recruiters make every decision. Nothing is auto-rejected.
Q: How does a small business without an ATS use CandidRanker?
A: Many small teams use CandidRanker as their evaluation home: upload JDs and resumes directly, rank, decide, and export reports. An ATS can be added later; CandidRanker's role stays the same either way.
Q: How quickly can a new team get value?
A: The first ranked role takes about five minutes: upload the JD, drag in resumes, rank, and review the top matches with reasoning. Most teams see the workflow shift, judgment instead of scanning, on day one.