A mobile friendly job application checklist for recruiters
Use this mobile friendly job application checklist to test your apply flow on a phone and stop losing candidates to extra fields before they hit submit.
9 min read
Key takeaways
- Apply to your own job on your phone, on cellular data, and write down every place you get stuck.
- Let candidates apply without creating an account, and ask only what you need to decide whether to talk to them.
- Make the resume optional for hourly and volume roles, and offer short work history questions instead.
- Check that the step after the form, such as scheduling or a video interview, also works in a phone browser with nothing to download.
- Re-test the full apply flow after any change to your ATS or job boards, and at least once a quarter.
A mobile friendly job application is one a candidate can finish on a phone in a few minutes without zooming in or creating an account first. The fastest way to know if yours qualifies is to apply to your own open job on your phone, on cellular data, and write down every point where you get stuck. Below is how to run that test, which fields to cut, how to handle resumes, and what to fix in the steps that come after the form.
Why does a mobile friendly job application matter for recruiters?
Recruiters usually build and preview job postings on a laptop. Many candidates see the job for the first time on a phone, especially for hourly, shift, retail, warehouse, healthcare support, and call center roles. They might be on a break, on a bus, or waiting to pick up a kid. Some do not have a laptop at home at all.
That difference hides problems. A form that feels short on a big monitor can turn into a long scroll of tiny fields on a phone. A required resume upload that takes ten seconds on a desktop is a dead end for someone whose resume is a printed page in a folder.
When the apply flow breaks on mobile, you rarely hear about it, because the candidate just leaves. Your pipeline looks thin, and the job post gets blamed for a problem the form caused.
How do you test your application on a phone?
Set aside 15 minutes per application form. Different job types often use different forms, so test each one you use, not just the main careers page.
Step 1: Use real conditions
Use your own phone, signed out of every work account, on cellular data instead of office wifi. Try one iPhone and one Android if you can borrow one. Turn the phone's text size up one notch, since plenty of people read with larger text.
Step 2: Start where candidates start
Open the job from the place candidates actually find it, such as a job board listing, a link in a text message, a QR code on a flyer, or your careers page. Do not start from the direct apply URL you have bookmarked. The redirects between those places are often where things break.
Step 3: Apply all the way through
Fill in every field with realistic test data. Upload a file from the phone, ideally a photo. Hit submit. Then check that the candidate record shows up in your ATS and that the confirmation screen and confirmation message both came through.
Step 4: Write down every snag
Time the whole run. Note each moment you had to zoom, retype, scroll sideways, wait on a slow page, or guess what a field wanted. Each note becomes a line item to fix using the checklist below.
The mobile friendly job application checklist
Work through these in order. The job post comes first because a candidate who cannot read it on a phone never reaches the form.
Checks for the job post itself
| Check | What good looks like |
|---|---|
| Plain job title | Uses words candidates search for, with no internal codes or level numbers |
| Pay and hours near the top | Visible on the first screen along with the job location, before long company copy |
| Short paragraphs and lists | Readable without zooming, no walls of text |
| Apply button easy to find | On the first screen or pinned to the bottom as the candidate scrolls |
| Fast load on cellular | The page is usable within a few seconds |
Checks for the application form
| Check | What good looks like |
|---|---|
| No account required to apply | Account creation is optional and offered after submit, if at all |
| Few required fields | Contact details plus a handful of knockout questions |
| Correct keyboards | Number pad opens for phone number, email keyboard for email |
| Autofill works | The browser can fill name, email, phone, and address |
| Large tap targets | Buttons and checkboxes are easy to hit with a thumb |
| Labels above fields | The label stays visible while typing, not only as gray placeholder text |
| Clear error messages | The message next to the field says what to fix, and nothing already typed gets cleared |
| Progress shown | Multi-page forms say "Step 2 of 3" so candidates know how much is left |
| Progress saved | A dropped signal or the back button does not wipe the form |
| No downloadable documents | No PDFs that have to be printed and scanned |
| Works with larger text and screen readers | Nothing overlaps or gets cut off at bigger text sizes |
Checks for what happens after submit
| Check | What good looks like |
|---|---|
| Confirmation screen | Says what happens next and roughly when |
| Confirmation text or email | Arrives within minutes, from a name the candidate will recognize |
| Next step works on a phone | Whatever comes next, from scheduling to assessments to interviews, opens in the mobile browser |
| A way to ask questions | The candidate knows who to contact and how |
Which fields can you cut from the first application?
A good rule is that the first application should only ask what you need to decide whether to talk to this person. Everything else can wait for a later stage, when the candidate is more invested and you have a reason to ask.
| Field | First application? | Notes |
|---|---|---|
| Name and contact details | Keep | Ask for phone and email, and make phone the main contact for hourly roles |
| Availability and shifts | Keep | Often the first thing that decides fit for hourly work |
| Location or commute | Keep | One simple question is enough |
| Required license or certification | Keep | Yes or no, with details later |
| Work authorization | Keep if needed | Check with your legal team on wording |
| Full work history | Defer | Use two or three short questions instead |
| Resume | Optional | See the next section |
| References | Defer | Collect near the offer stage |
| Cover letter | Cut | Rarely read for volume roles |
| Long assessment | Move later | Send after a first screen, not before |
| Date of birth, ID numbers | Cut | Collect during onboarding if required |
| Pay history | Cut | Rules vary by place, so check with your legal team |
| Voluntary demographic questions | Separate and optional | Follow your legal team's guidance on how to ask |
For the knockout questions you keep, pick ones a candidate can answer with a tap. Our list of pre-screening interview questions and what each one tells you is a good source for wording that works in a short form.
How should resumes work on a mobile application?
Many hourly and entry-level candidates do not keep a resume file on their phone. Requiring one filters out people who could do the job well, and you never see them leave.
A few options work better on mobile:
- Make the resume optional and say so clearly next to the upload button.
- Offer two or three short questions instead, such as their most recent job and how long they worked there.
- Accept uploads from the photo library, so a candidate can snap a picture of a paper resume.
- Accept files from cloud storage, not just the phone's local files.
- If your system parses resumes, show the parsed fields as editable instead of making the candidate retype everything.
If you already score candidates on a short list of criteria, build the form questions around those criteria. A simple scorecard makes it clear which details you actually need up front and which ones you never use.
Does the step after the application need to work on mobile too?
Yes. A clean form followed by a desktop-only next step just moves the drop-off one stage later. Look at what you send right after someone applies.
Phone screens are a common bottleneck. Candidates who apply on a break often cannot take a call during work hours, and both sides end up trading voicemails. Many teams replace that first call with a short recorded screen. If you are new to the format, here is what a one-way video interview is and how recruiters use it.
Whatever the next step is, check it against the same standard:
- It opens from a single link in the mobile browser, with nothing to download.
- Instructions fit on one screen and say how long it will take.
- Candidates get a fair deadline, such as three to five days.
- Reminders go out if they have not finished.
- There is a practice question or a retake option so a first attempt on a phone is not final.
With DeepHire, candidates get one link and record their answers in the browser on a phone or any other device they have, and automated reminders go out to anyone who has not finished. Send candidates a short guide on how to prepare for a one-way video interview along with the link so they know to find a quiet spot and prop the phone up.
What are common mobile application mistakes, and how do you fix them?
These show up again and again when recruiters run the phone test.
- The job board sends candidates to a second site that asks them to create an account. Turn off required account creation or move it after submit.
- Field labels are gray placeholder text that disappears once the candidate starts typing. Put labels above the fields.
- A state dropdown with dozens of options is hard to scroll on a small screen. Use autofill or a type-to-search field.
- Date fields open a tiny calendar picker. For start dates, a simple "When can you start?" choice list is easier.
- The session times out while a candidate looks for a document. Extend the timeout and save progress as they go.
- Long links in texts or emails break across lines or look suspicious. Use a short link from a domain candidates will recognize.
- The confirmation email comes from a generic no-reply address. Send it from your company or recruiter name so candidates recognize it and open it.
How often should you re-check your mobile apply flow?
Run the full phone test any time your ATS or apply form changes, and whenever you add a new job board or screening tool. Outside of that, put a quarterly reminder on your calendar.
It also helps to ask recent hires how they applied and what annoyed them, since they will remember the step that almost made them quit. If your ATS shows how many people started an application versus how many finished, watch that gap by source and by device. A sudden drop on one job board usually means a broken link or a new redirect, and running the phone test from that board will show you where it happens.
Frequently asked questions
How long should a job application take on a phone?
For hourly and volume roles, aim for a few minutes from tapping apply to seeing the confirmation screen. Time yourself applying on your own phone, and if it takes much longer, cut or defer fields until it does not.
Should candidates be able to apply without a resume?
For most hourly and entry-level roles, yes. Many candidates do not keep a resume on their phone, so make the upload optional and ask two or three short work history questions instead.
How can I tell if candidates are dropping off on mobile?
Compare how many people start an application with how many finish, broken out by source and device if your ATS reports it. Then apply on your own phone from the source with the biggest gap to find the step that breaks.
Can candidates complete a video interview on their phone?
Yes, as long as the tool runs in the mobile browser and does not require an app download. Give a clear deadline with reminders, and allow a practice question or retake so candidates are comfortable recording on a phone.