Job application forms: resumes, screening, and review
Build a job application form with resume uploads, a short screening quiz, a shared response sheet, and a closing date. See what still needs human review.
Start with the information a reviewer needs before an interview. For a support role, that might be contact details, a resume, two questions about a documented support procedure, and a short written example. A portfolio upload can wait if the role does not need one.
The job application form collects those answers in one place so reviewers can read the same material, while the hiring team remains responsible for deciding who to interview.
Set up resume collection
Choose a Google Drive destination for the template's included resume upload field, using a folder name such as "Support applications October 2026" that reviewers can recognize when applications arrive. Verify the connected account and give the hiring panel access to the folder in Drive.
A resume field could accept one PDF up to 5 MB, although you should adjust that example limit to the files your applicants will reasonably have. Thunder Forms currently caps each file at 12 MiB. Avoid collecting photos or identity documents unless the hiring process needs them.
A compact application might ask for the applicant's name and one contact route, the role they are applying for, one or two role-related screening questions, a resume, and an optional work sample when the role needs one. Keep questions about availability or location only when they affect the stated role requirements. Put the expected file type and size beside the upload field so applicants can prepare the document before starting.
A screening example with four available points
Use questions whose answers can be checked against instructions applicants have received. Suppose you provide a short refund policy. One single-select question asks which record to check first, and another asks which of several tickets needs the earliest response. Assign two points to each and mark the correct option.
Add a paragraph asking how the applicant would explain a delayed refund to a customer. Leave it ungraded. Read it during review. The two scored questions total four points, with no extra points for the paragraph.
If you choose a threshold of two out of four to organize review, call it your example rule. It is not a universal hiring benchmark, and the form does not enforce an automatic rejection workflow. Our quiz guide explains supported answer keys and manual grading.
Keep the response sheet separate from reviewer notes
Connect Google Sheets before opening applications, then submit a test application with a resume and check that its new row contains a working upload link accessible from a reviewer's account. The upload guide covers folder access and limits.
Sheets sync includes submission identifiers, timestamps, and field answers. Quiz scores stay in Thunder Forms. Check those in the Thunder Forms response dashboard, and keep interview decisions and follow-up notes in a separate tab linked by submission ID. Avoid rearranging the tab managed by sync.
Closing the application window
For a Friday deadline, enter the closing time in the form settings and put the same time and timezone in the description. Adding a response cap can close the form before Friday when it fills, so explain the cap alongside the advertised deadline before applicants begin their answers.
Google Forms also offers automatic closing and quizzes with answer keys and grade release. These features alone do not require a migration. Compare the actual upload organization, editing, and review workflow with your team.
Prepare a consistent review process
Write the review criteria before applications arrive. A practical first-pass checklist could include whether required documents are present, whether the applicant meets a stated experience requirement, and whether a scored question meets the threshold your team selected. Keep open-ended answers for a human reviewer. A quiz score can help organize applications, but it does not replace reading the evidence or making a hiring decision.
Use the same criteria for each applicant and record the reviewer and date in a separate notes tab. Limit access to resumes and responses to the people who need them for this recruitment. Decide how the team will remove or retain those files when the hiring process ends, according to its own policies. Thunder Forms collects answers and file links; it is not an applicant tracking or automated shortlisting system.
Frequently asked questions
Short answers to the questions every reader asks next.
Before sharing the link, test one complete application and one with a missing required answer. Use a copy to test the expiry limits, then open the builder to prepare the live application.