Placement drives that survive the day
Import a batch, randomise a paper per candidate, hold each slot to its window, and watch the whole drive from one console. Built for the volumes campus hiring actually produces.
- CSV batch import
- Randomised papers
- Resume after a dropout
Built for volume
The things that break at scale
A drive with two thousand students fails differently from an interview with one. These are the parts that matter.
Import the whole batch
Paste or upload a CSV of candidates. Duplicates are matched rather than re-created, so re-uploading a corrected list does not double your cohort or your bill.
A different paper each
Question pools draw a fresh selection per candidate from the same specification, so students in the same lab do not benefit from looking sideways.
Scheduled login windows
Set when candidates may start. The window closes on its own, which is what keeps a two-slot drive to two slots.
One console for the whole drive
Every active attempt with progress and flags in one view. Message, pause, extend or force-submit without leaving it.
Connection reality
Answers and code save as they type, and a candidate who drops off resumes the same attempt. Campus networks fail; a drive should not.
Rank the cohort
Leaderboards and score distributions across the batch, with section and question breakdowns so you can see which topics the cohort actually knows.
The drive
How a placement season runs
- 01Step
Build once, reuse each year
Assessments and question pools are saved. Next year's drive starts from last year's paper, not a blank page.
- 02Step
Import the batch
Upload the list from the placement cell. Each candidate gets their own link and a system check before they start.
- 03Step
Run the slots
Login windows hold each slot to its time. Invigilators watch live and handle problems while they can still be fixed.
- 04Step
Shortlist from evidence
Scores arrive with integrity signals and plagiarism comparisons across the cohort. Export the shortlist to Excel or PDF.
Honest planning
Tell us about the big day in advance
A drive where three thousand candidates start within the same ten minutes is a capacity question, not a plan question. We would rather size it with you beforehand than discover the ceiling together on the day.
- Give us the date, expected concurrency and whether coding is included
- We confirm capacity, or tell you honestly that we cannot serve it
- Large events can be reserved rather than assumed
- If a slot is genuinely at capacity, you find out before you send invitations
Why we ask
Code execution is the constrained resource in a coding drive: every submission needs a sandbox. Knowing your peak lets us have that capacity ready instead of queuing your candidates.
What to send
Date, slot times, candidates per slot, and whether the paper includes coding. That is enough for us to answer properly.
Questions
What placement teams ask first
How many candidates can sit an assessment at the same time?
What happens when a candidate's connection drops mid-assessment?
Do students need to install anything or use a specific laptop?
Can we run the same assessment across multiple colleges?
Is there special pricing for institutions?
Do candidates see our institution's name or yours?
Try it on one batch first
Run a single slot on the free trial before you commit a whole season to it.
Have questions? Email sales@parikshafy.com