Resume screening that shows its work
Every application is scored against the role's blueprint, and the score arrives with the lines of the resume that produced it. A recruiter can disagree with it in one click, and the override is recorded.
Applications, AI screening, WhatsApp and voice outreach, scheduling, scorecards and offers. Built for bulk and lateral tech hiring in India.
Careers page
Roles published from the ATS. Applications land in the pipeline.
AI screening
Every resume scored against the role blueprint, with its evidence.
Outreach
WhatsApp templates and AI voice screening from one queue.
Scheduling
Panelist availability, candidate slot picking, calendar invites.
Scorecards
A structured scorecard per round, not a note in a thread.
Offer
Approval chain, e-signature, and the audit trail behind both.
Measured on our own hiring, since July 2026. NxtWave runs its engineering and instructor hiring on this product.
Most teams run this on six tools that do not talk to each other, and lose candidates in the gaps between them. This is the same work in one record.
Every application is scored against the role's blueprint, and the score arrives with the lines of the resume that produced it. A recruiter can disagree with it in one click, and the override is recorded.
Template messages, replies routed back to the candidate record, and AI screening calls placed from the same list your callers work. Suppression and do-not-call are enforced at the point of dialling, not per campaign.
Panelist availability, candidate slot picking, calendar invites and reschedules.
A scorecard per round against the same rubric, so two panelists are answering the same question.
Approvals, e-signature and an audit trail of who changed what, and when.
Import open requisitions and the rubric each one is judged against, or start from a template. Your careers page publishes from the same record, so a role goes live once.
Your WhatsApp sender, your mail domain, your panelists' calendars. Candidates begin arriving in the pipeline instead of in an inbox.
Screen, call, schedule, score and offer against one live role, end to end, before you move the rest of the team across.
Template sends and inbound replies, routed to the candidate record.
Transactional and campaign mail from your own verified domain.
Panelist availability and interview invites, with reschedules.
Requisitions and joiner data synced with your HRMS.
Offer letters out for e-signature and back, tracked in the pipeline.
Subscription billing and metered usage for your workspace.
You are handing us candidates' names, phone numbers and resumes. These are the three things worth checking before you do.
Every row carries the workspace it belongs to, and the storage layer appends that predicate to each query it builds rather than trusting the calling code to remember. Postgres row-level security policies keyed on the same workspace claim sit behind that as a second layer, and are being switched on workspace by workspace.
The database runs in AWS Mumbai and the application runs in Vercel's Mumbai region. Candidate documents live in object storage in the same region.
A candidate's consent is recorded with its timestamp and source when they apply. You can export your whole workspace on demand. Deleting a workspace happens in two steps thirty days apart, so a mistake is recoverable, and the rows are then purged rather than hidden.
Read the full security note for the detail your security review will ask for.
It is built for technology hiring, which is where the screening rubrics and the call scripts are strongest. Nothing in it is restricted to engineering, but a non-technical requisition gets less out of the screening than a technical one does.
No. It runs the hiring up to the signed offer. Darwinbox and systems like it keep the employee record, and requisitions and joiner data sync between the two.
Plans and their limits are on the pricing page. We have not set final prices, so the page tells you what each plan includes and asks you to talk to us for the number rather than quoting one we would have to change.
A score never rejects anyone on its own. It arrives with the evidence behind it, a recruiter can override it in one click, and the override is recorded against the application.
The stages, the rubrics, the rejection reasons and the mail and message templates are yours to configure. The parts that are not configurable are the ones that exist to keep an audit trail honest.
Your open roles and what each one is judged on. A WhatsApp sender, a mail domain and your panelists' calendars can be connected afterwards, in whatever order suits you.
Start on the free plan with one open role, or bring us a requisition you are struggling with and we will walk through it together.