Add friction at the top. Your later stages will thank you.
The standard advice is to reduce application friction. That's right if your problem is pipeline volume. It's wrong if your problem is signal quality, and for most technical hiring, it is.
The standard advice is to remove friction from your application process. Shorter forms. One-click apply. Reduce drop-off.
Reasonable, if your problem is pipeline volume. For most technical hiring, where you're making a small number of high-stakes decisions, your problem is signal. Optimizing for volume at the top degrades signal everywhere else.
Every stage should earn its place
A simple test for any step in your process: does it help you make a better decision? If yes, keep it. If no, cut it, regardless of whether it's "normal."
A large, unfiltered applicant pool forces crude screening: keyword filters, years-of-experience thresholds, degree requirements. The I-O psychology research on this is fairly settled: these signals are weak predictors of actual job performance. Structured, role-relevant evaluation beats resume screening by a wide margin.
The better approach: add meaningful friction early. Not bureaucratic friction. Signal-generating friction. Ask applicants to do something that reveals fit.
A question bank, not a form
Most ATS platforms treat the application as a fixed form: name, resume, maybe a cover letter, submit. Every role gets the same shape. The hiring team has no real lever to ask the things they actually care about for this role, at this stage.
Nexus inverts that. Each stage in your pipeline has its own prompt set, a small question bank the hiring team configures per role. Short text, long text, single or multi-select, dates, file uploads with type restrictions. Mark them required or optional. Reorder them. Different stages can ask different things.
A first screening stage might ask two pointed questions about a real problem in the domain, the kind of thing a thoughtful candidate will spend twenty minutes on and a low-effort one will skip. A later stage might attach a work-sample upload. The bar moves with the stage. The data you collect is structured, comparable, and tied to the decision you're about to make.
Optimizing for volume at the top degrades signal everywhere else.
Friction that resists the LLM era
Text answers are increasingly compromised. Cover letters, written responses, even take-homes can be LLM-generated in minutes. That doesn't mean text prompts are worthless (a sharp, specific question still filters effort and interest), but it does mean you should think about what kind of friction generates real signal now.
One pragmatic move available in Nexus today: ask candidates to attach a short video as part of a screening stage. A Loom link in a text field, or an MP4 upload on a file-upload prompt. You see how someone communicates, whether they can be concise under light pressure, how they think on their feet. The person on screen is the person who shows up to the interview.
First-party video recording and structured async-video prompts are on our roadmap, a natural next iteration of the question bank. For now, the file-upload prompt covers the use case for teams who want it.
What this looks like
- Keep the initial application simple: name, resume, apply.
- First screening stage in Nexus, configure two or three prompts on the stage: a focused written question, maybe a video or work-sample upload. Mark the ones you actually need as required.
- Everything downstream is high-signal by design: phone screen, structured interview, deeper work sample, each stage carrying its own prompt set tuned to what that step is meant to learn.
Fewer applications isn't a failure mode. For technical hiring, it's the goal. The question bank is the lever that makes "fewer, better-qualified" a configuration choice, not a hope.