Can Someone Finish Your Job Application on a Phone?
Before you post your next opening, follow the application from the job listing to the confirmation screen on a phone. Try one thing going wrong along the way.
How far can someone get through your job application without putting down their phone and finding a computer? The answer is hard to see from the screen where you wrote the job post. Open the listing on a phone, follow the Apply button and see what the form asks someone to do.
Start where a reader starts. Use the public listing if it is already up, rather than a link from your recruiting dashboard. Look for the same job title and location on the next screen. If Apply sends you to a general careers page, can you tell which opening you were trying to apply for? You know the role by heart; a person seeing it for the first time has only what is on the screen.
Recruitee's guide to job application design recommends trying the whole form on a phone, including how uploads work. For a hiring team, a useful way to make that advice concrete is to watch someone who did not build the form try it without help. What do they pause over? What do they have to go back and look up?
Notice where the work shifts to the applicant
A resume upload is a good place to look. Say an employer has a form that accepts PDF files only. In an illustrative test, a colleague tries to upload a sample Word document. The form responds with "Upload failed." The colleague has no way to tell whether to try the same file again or find a different one.
That test gives you two small changes to discuss with whoever manages the form. Tell people what file type you accept before they choose a file. If they pick the wrong type, say what to do next: "Choose a PDF file." In the test, check that a person can replace the file without losing the rest of what they typed.
Look for work that is easy to miss when you review a form on a big screen. If it asks people to attach a resume and type the same work history into several boxes, find out why both are there. The hiring team might need certain details in a consistent format. Ask which ones the team actually uses and whether people need to enter them twice. Fixing an unclear label may be within your reach today; changing a shared form may take a conversation with the person who owns it.
Try the part that does not go to plan
Use a test copy of the form and made-up details for anything you need to enter or submit. If you only have the live listing, stop before entering details and ask the form owner for a safe way to check the rest. A test should never land among real applications.
In the test copy, leave one required field blank. When you try to continue, does the form point to the field and say what is missing? Can you correct it without redoing the previous page? The W3C tutorial on form feedback recommends clear instructions for fixing errors and a clear message when a submission succeeds.
Give the last screen the same attention. "Thanks" is polite, but "We received your application for the shipping clerk role" tells the person what happened. If the form promises a confirmation email, check that the test address receives it. Keep the wording to what your team can reliably deliver.
Give the person who can fix it something to reproduce
"Applying on mobile is awkward" is an understandable reaction, but it leaves the person responsible for the form guessing. A note such as "On the shipping clerk application, I picked a Word file and saw 'Upload failed' with no hint about which file to use" gives them a place to start. Include the device and browser you used. Once the wording or behavior changes, repeat that same part of the walkthrough.
A phone test gives you a better view of one route through your application. It is a good first check, especially when time is tight. The point is to leave someone interested in the job with a clear next move, from the first tap to the moment they know their application went through.
If you're planning your next hire, explore Summit Careers' employer services.
