A HireQwik Campus Resume Shortlist From PDF Files Only

The HireQwik campus resume shortlist I trust is the one finished the night before the hall opens, not the one a panel builds from a zip file at 8:40 a.m. I have watched that second version. A placement cell sends 180 PDFs after dinner. The coordinator’s laptop has no sheet of emails, only filenames like CS_2026_014.pdf. By the time someone has opened thirty files, the first panel is already calling names from the top of the zip. That order is the zip order. It is not a shortlist.

HireQwik can take that folder directly. This post is about the drive-day use of that upload, not the general mechanics. The stage-by-stage version of a file becoming a score is in the folder intake walkthrough.

What a placement cell usually sends to HireQwik

In India the file is rarely clean. One college sends PDFs exported from a portal. Another sends DOCX files students edited until midnight. A third sends scans of a stapled form. You will also get a student who submitted the same PDF twice because the portal timed out.

Plan for that mix before you promise a shortlist by morning. HireQwik will accept PDF and DOCX. Five hundred files is the ceiling, each one at most ten megabytes, and the whole drop at most half a gigabyte. A scan with almost no text will not score. A second copy with the same bytes will be skipped. Tell the cell, in the same email that asks for resumes, to send text PDFs or Word files, one file per student, named however they like. The name on the shortlist will come from inside the file, not from CS_2026_014.

If the pile is larger than 500 files, split it into two runs of the same job rather than dropping the tail. Both runs use the same ruler, so you can merge the exports. Do not raise the cap in your head and upload until it errors. The error rejects the oversized total. You lose time, not just a warning.

Pick one HireQwik job before any campus file goes in

A campus day often covers three requisitions and one shared inbox. HireQwik will not score “the drive.” It scores the job description you pick. I want that pick to be the role the panel will actually hire, with the skills the panel will ask about. If the Jobs page still has last year’s intern JD, you will shortlist last year’s intern.

Build or open that job first. If it has a scoring matrix, the matrix is the ruler and a loose skills list will not override it. If it has no matrix, HireQwik still judges whether the projects match this role, and raw years do not inflate a fresher who has never done the work. Freshers make this obvious. A three-page CV of workshops can outrank a one-page CV of a real project if you only count length. Matching freshers who have no job history is the argument for judging projects and skills, not page count.

Do not paste a new JD into the upload screen. That path is gone. Configure the role on the Jobs page only. If two panels need two roles, make two jobs and two uploads. Mixing them feels faster at 11 p.m. and is indefensible at 9 a.m. when a testing candidate is ranked on a sales ruler.

Run the HireQwik folder the evening before the hall

I start the run when the last college file lands, even if that is late. Scoring walks the files in batches of 50. You do not need a person sitting on each file. You do need someone to glance at the first completed rows, because a wrong job shows up immediately: every strong student looks weak, or every file fails to parse.

Leave the default cut at 60 for that first glance. It is a line, not a verdict on who gets a badge at the booth. In the morning, filter the table to shortlisted rows and sort by score. The panel lead should see dozens, not 180. If 60 kept almost everyone, the ruler is too soft or the folder is unusually on-target. If 60 kept almost no one, read the reasons before you drop the cut in a panic. Moving the HireQwik shortlist threshold explains why a lower number does not rescore anyone. It only changes which rows carry the mark.

A human still samples. Open the top score, a score just over the cut, and a score just under it. If the reason cites skills the JD asked for, the run is usable. If the reason cites a keyword that appears only in a coursework list, tighten the job before you print the list. Why scores bunch up in the middle is what a too-generic ruler looks like.

How I brief a panel on the HireQwik campus shortlist

The panel does not need the upload story. They need three lines:

• These names cleared a score of 60 or more against this role.
• The number is not a hire decision. It is who we will spend the slot on.
• Anyone missing had a file we could not read, or a score under the cut. Both are listed, not deleted.

That third line matters. Students ask why a classmate was not called. “The zip was too long” is a bad answer. “The file had no readable text” or “the score against this JD was 41” is an answer you can show. The review row holds the reason. The HR dashboard is where that review sits beside the other tools you will use once the hall opens.

I also separate colleges only when the roles differ. Same role, one shortlist, both colleges. Different roles, different shortlists. Comparing a college on a blended score is how a good testing student loses to a sales student who happened to be in the same zip.

What fails in HireQwik on a real drive morning

Three failures show up more than any product slide admits.

First, the cell sends phone photos of CVs. Those often yield too little text, so the row fails and keeps the filename. Pull the failures before you tell the cell the shortlist is final. A second ask for a text PDF is cheaper than losing a strong student. Files that never become a shortlist row walks through that status.

Second, the same resume arrives from the student and from the cell. Identical bytes are skipped, so the twin never becomes a second person. If the student edited one word, both copies remain. Glance for repeated emails after the names fill in. The upload does not merge different files for one person.

Third, someone tries to add a spreadsheet of the students who already booked a slot, in the same job as the loose PDFs. HireQwik will not take both sources in one job. If you already have a sheet of links, use the sheet intake. If you have a folder, use the folder. Choosing HireQwik direct resume upload over a link sheet is that fork. Forcing both into one run is how a drive morning starts with an error instead of a list.

Where a HireQwik campus list stops once the hall opens

The shortlist does not staff the booth, and it does not run the conversation. In one July 2026 production month, 24,327 resumes were screened and 1,074 became completed AI interviews. Most of the drop was the point of screening, not a broken invite. A campus day can stop even earlier: print the shortlist, meet those students, and leave the voice step for people you cannot see in the hall. The handoff into a voice screen is there when the hall is in another city and you still need a conversation.

NASSCOM’s 2023 digital talent study counted about 2.5 million STEM graduates in India in 2022-23. That supply is why a folder needs a ruler the night before. It is not why you should skip reading the reasons.

A widely cited look at recruiting funnels puts only a small share of applicants in an interview at all. On a campus day that share should be chosen, not accidental. The zip order is accidental. A score against the drive’s own job is a choice.

What I send the cell after the first HireQwik sample

Before the full zip, I ask for twenty files from the largest college and I run only those. Twenty is enough to see three things: whether the text layer exists, whether the parsed names look like students rather than headings, and whether the scores spread out or sit in a clump. If all twenty fail to parse, I stop and send the format note again. If all twenty clear 60 with reasons that only quote “teamwork,” the job description is too soft for a drive and I tighten it before the other 160 arrive.

The note back to the cell is short. It names the role, the file types that worked, and the count of files we could not read. It does not include scores. Scores are for the panel, not for a broadcast to every department coordinator. Students compare numbers in a group chat within an hour, and a 61 next to a 92 starts a fight the shortlist was not meant to settle.

I also write down which college each sample came from, in my own sheet, outside HireQwik. The file upload does not keep a college column. If the panel must balance two campuses, that balance is a human note on the export, not a field the parser will invent.

The night schedule I actually keep before a HireQwik campus morning

A drive fails in the gaps, not in the slogan. I write the night as a clock so nobody invents a new process at 11 p.m.

By 7 p.m. the job on the Jobs page must already match the booth. If the title still says last year’s intern, I fix it before a single CV is dropped. Changing the ruler after scores exist does not rewrite those scores. You would be ranking Tuesday’s students on Monday’s wording. I would rather delay the upload twenty minutes than discover the mismatch when the panel lead is already in the cab.

By 8:30 p.m. the first college zip should be in. College B can land later when college A is already big enough to test the files. A clean text PDF from college A tells me the format. A scan-only dump from college B tells me to call that cell before midnight, while someone is still at a desk. Waiting until both zips land feels polite and burns the only hour the cell can still resend.

By 9:30 p.m. I want finished rows, not a promise that it is “processing.” I open three students I know by reputation, if I have any, and three I have never heard of. The known ones are a calibration, not a favor. If a student the faculty already trusts sits at the bottom because the CV is a photo, that is a file problem and I ask for another copy. If that same student sits at the bottom because the projects are unrelated to this role, I leave the score. Faculty warmth is not a field on the CV, and HireQwik should not invent one.

By 10:30 p.m. the cut is either still the starting 60 or I have moved it and written the new number in the panel note. I do not slide it again at breakfast because a professor asked for “a few more names.” Those extra names get added by a human, with a reason, off to the side of the export. Quiet edits to the cut after people have printed the list are how two panels walk in with two different PDFs.

Morning is for the hall, not for parsing. The coordinator’s job at 8 a.m. is to know which names are on the list, which files came back unreadable, and which college still owes a resend. If that answer is “the laptop is still uploading,” the night schedule was skipped and the booth will improvise. Improvising from a zip is how the first table calls whoever the folder listed first.

I share the list as a PDF export plus the one-line note, not as a login for every panelist. Most panelists need the order and the reason, not the buttons. The recruiter who owns the job keeps the screen. When a panelist disputes a name, we open that one row together. We do not hand the whole queue to six people who will each sort it differently.

That clock is boring on purpose. Campus mornings are loud. The shortlist has to be finished while the building is quiet, against one role, with the unreadable files already sent back. If your cell cannot hit 8:30 p.m., tell them the list will be thinner, not that you will “run it live” in the hall. Live, in this case, means unread.

If your next drive is a folder and a date, tell us the role and we will run a sample batch against it before the cell sends the full set. The sample is where a weak JD shows up, while you can still fix it.