When HireQwik Direct Resume Upload Beats a Spreadsheet

HireQwik direct resume upload is the intake I switch to when building a link sheet would be the whole job. I watched a recruiter lose a Sunday to it. Ninety resumes sat in a folder. The old path wanted each one in Drive, then a row carrying the person’s name, their email, and a URL. By evening the sheet had 90 links and three broken permissions. Scoring had not started. The files had been ready at breakfast.

Both doors still exist on the Shortlist screen. This post is only the choice between them. The file path itself is mapped in the upload-to-cut walkthrough.

What each HireQwik intake actually needs from you

The spreadsheet door wants an Excel file. HireQwik looks for a name column, an email column, and a resume-link column. The link is usually a Drive URL. If those headers are missing, the file is rejected before any score. That door is right when an ATS export or a form already produced the columns. You are not retyping. You are pointing at a list that exists.

The file door wants PDF or DOCX, selected together. There is no header row. HireQwik stores the files, reads the text, and fills the name and email from the resume. Until that read succeeds, you see the filename and a blank email. There is nothing else to map, which is the point. There is also nothing else to keep. A “college” column you loved in Excel does not survive, because it was never in the file upload.

You cannot attach both to one job. The create call rejects the mix. I agree with that refusal. A row from a sheet and a row from a file do not share a shape. Merging them inside one run would hide which name came from a typed cell and which name came from a parser. Run two jobs if you truly have both piles. Point both jobs at one role so a 70 means a 70.

When the spreadsheet is still the better HireQwik door

Keep Excel when the list is alive. A careers page that appends a row every hour should stay a sheet, or better, the trigger that watches a sheet and scores new rows without a fresh upload. That always-on path is when a sheet drop becomes a screening campaign. Direct upload is a batch. It does not sit and wait for tomorrow’s applicant.

Keep Excel when the link is the resume and your team already controls sharing. A public or correctly shared Drive link is something the downloader can fetch. A restricted link looks fine in your browser, because you are logged in, and fails for HireQwik. When a Google Sheet does not trigger covers that permission trap. If you are about to upload files only to escape a permissions mess, check the sharing first. You may not need a second intake.

Keep Excel when extra fields decide the panel. Source, phone, notice period, college code: if a human typed them and the resume does not, the sheet is the record. Direct upload will not invent them.

When HireQwik direct resume upload is the better door

Use files when the artifact is the folder. Placement cells, a founder’s downloads, a vendor who zipped CVs, a recruiter who exported PDFs from a mailbox. The cost of the sheet is not the scoring. The cost is the hours before scoring, plus the broken links.

Use files when you do not trust the typed email. On the sheet path, a typo in the email cell is the email of record. On the file path, the email is whatever the resume text contained. That can still be wrong, if the candidate wrote it wrong, but it is not a second transcription. I would rather argue with the CV than with a copy-paste from WhatsApp.

Use files when you are under a same-day clock. A Sunday of link-building is a failed screen even if Monday’s scores are perfect. The limits are still real: PDF and DOCX only, no more than 500 documents, 10 MB on each document, and 500 MB for the pile. A folder of 40 files is a comfortable direct upload. A folder of 2,000 needs to be split, or it belongs in a system that already has rows.

Identical copies are skipped by a hash of the bytes. You will not pay attention twice for the same PDF saved under two names. A rewritten file still creates its own row, because the bytes no longer match. That is a feature of honesty, not a duplicate detector for people.

What stays the same in HireQwik after you pick a door

The job description is required either way. Scoring does not care whether the bytes came from Drive or from the upload. When a resume scoring matrix is already saved on the role, that matrix runs. Otherwise HireQwik judges role fit, and a keyword pass is only the fallback. A 0 to 100 score lands on the row. The default shortlist mark is 60 and up. The threshold, and what moving it does, is identical for both doors.

So is the review. Filter to who cleared the cut, sort by the number, open the file beside the written reason, and mark the people you will actually call. Stop the run if you picked the wrong role. None of that changes because you skipped Excel.

What changes is the failure mode. A sheet fails on a bad link or a missing column, often before scores exist. A file upload fails on type, size, empty text, or a hash duplicate. Those file failures are visible as rejected files or as rows that never received a score. Do not debug a file batch with the sheet checklist. You will look for a Resume Link column that was never there.

A small HireQwik test before the team standardizes

Take ten real files and, if you have it, the sheet that would have held them. Run the files as one job. If the sheet already exists and the links work, run that as a second job on the same JD. Then compare.

I look for three gaps. Names that disagree with the CV. Emails that are blank on the file side because the text never contained one. Scores that diverge because one side fetched a different document than the file you thought you had. If the scores match and the names match, pick the door that costs less human time next week, not the door that feels more “integrated.”

How HireQwik matches resumes to the job explains the score you are comparing. The intake should not change that explanation. If it does, one of the two sources is not the resume you think it is.

SHRM’s note on moving AI in HR from hype to measured use is a fair standard here. A second upload button is not a strategy. A written rule is: folder means files, living list means a sheet, never both in one job. The seven-second resume glance is what you are buying back. Those seconds should be spent on the borderline scores, not on pasting URLs.

For a campus folder specifically, the drive-morning sequence is in that placement-day writeup. For a list that never stops growing, stay on the sheet trigger and do not force it through direct upload just because the button is newer.

A Monday I would not repeat inside HireQwik

The Sunday sheet I mentioned had three broken links. On Monday the recruiter still wanted scores before a 2 p.m. standup. We did not repair Drive sharing. We took the original PDFs from her laptop, the same documents the links were supposed to point at, and ran them as files against the job she had already configured. By late morning the review table had names parsed from the CVs, not from her WhatsApp notes. Two files failed because they were photos. She pinged those candidates for a text PDF and left the other eighty-eight on the table.

That is the decision rule I now write on the team wiki. If the document is already a file in front of you, upload the file. If the document lives behind a link that a form will keep appending, keep the sheet and fix sharing. Do not convert a healthy sheet into files just to try the newer button. Do not convert a folder into a sheet just because last quarter’s playbook said Excel. Write the rule where the team will see it on Monday, not in a slide that nobody opens during a standup.

The standup used the shortlist, not the story of the intake. Nobody asked which door we picked. They asked why two names were missing. The answer was the photo files, which is a better answer than “the Drive link was restricted and we did not notice.”

What I ask before HireQwik opens either door

The argument in most teams is not technical. Someone likes spreadsheets. Someone is tired of Drive permissions. I make them answer six questions on paper before anyone clicks. The answers pick the door. Taste does not.

Where do the documents sit tonight? If they are already PDFs on a laptop, the file door is the short path. If they are links inside a form that will gain rows tomorrow, the sheet door is the short path. “We could convert” is how Sunday disappears. Conversion is a project. Intake should not be a project.

Who typed the email? If a coordinator copied it from WhatsApp into a cell, that cell can be wrong even when the CV is right. The file door reads the address off the CV instead. If payroll already trusts the sheet address because the offer letter will use it, keep the sheet and treat the CV address as a check, not as the record. Do not discover the mismatch at joining.

Do you need a college code, a source, or a phone that is not on the CV? Loose files will not carry those. I have watched a team upload 200 PDFs and then rebuild the college column by hand, which is the spreadsheet they refused to make at the start. If the extra column is the point of the list, start with Excel. If the extra column is a nice-to-have, drop it for this batch and type it later on the people you will actually call.

Is the list going to grow after tonight? A file drop is a batch. It ends. A connected sheet can keep accepting new applicants without a fresh upload. Forcing tomorrow’s applicants through another manual drop feels flexible and creates two jobs to reconcile. One role, one door, for the life of that requisition. Switch doors only when the source of candidates changes, and say so in the job note.

Can you open three sample documents right now? If the sample is a photo, neither door will save you. Fix the file before you debate the button. If the sample link asks you to request access, the sheet will fail the same way for HireQwik. Share the file, or abandon the link and upload the bytes you already have.

Who will explain a missing name tomorrow? Write that person’s name on the note. The door you picked changes the explanation. A missing sheet row is “we never received the link.” A missing file row is “the document contained no text we could read” or “a second copy was the same bytes and was skipped.” Those are different sentences. Train the person who will say them. Do not leave it to whoever picks up the phone.

I keep the six answers in the requisition folder next to the JD. When a new recruiter joins mid-drive, they should not re-litigate the button. The folder already says which door this role uses and why. That is the whole standardization. It is one page, not a workshop.

If your team is split on which door to standardize, bring both samples. Ten files and one real export are enough to settle it.