Most employers have never applied for one of their own jobs. If you do it once, carefully, with a stopwatch and a notepad, you'll learn more about why good candidates drop out than any survey will tell you. This guide sets out a five-part audit you can finish in an afternoon, a scoring sheet, and the fixes that tend to matter most.
Before you start
Choose one open role, ideally one you hire for often. Set up a personal email address and phone number that your hiring team won't recognise. Tell one person, perhaps your HR lead, what you're doing so the test application can be quietly removed afterwards.
Keep a simple log: what you did, the time, and what you saw or felt. Note when you were confused or tempted to give up. Those moments are the findings.
Part 1: search for yourself as a job seeker (30 minutes)
Start where a candidate starts: a search engine, on a phone.
Search for:
- your company name plus "jobs" or "careers"
- the job title plus your city
- your company name plus "reviews"
Record what appears on the first screen. Is your own careers page there, or only job boards? Are your openings shown with titles and locations? What do employee review sites and social posts say, and does anything on your own site answer the recurring complaints?
You can't control what others write, but you can make sure your own pages give a fuller, truthful account. If your company doesn't appear in job results for its own openings, see how job posting markup works.
Part 2: read the careers page and the ad (30 minutes)
Open your careers page on a phone. Time how long it takes to find:
- the open role
- where it's located and whether it's remote or on-site
- the schedule or hours
- what happens after you apply
If any of those takes more than a minute, a busy candidate won't find it. Then read the ad itself and mark every sentence that could appear in any company's ad. Those generic sentences are the ones to replace with proof points from your employer value proposition.
Part 3: apply (30 minutes)
Now apply, on your phone, using your test identity. Record:
| Check | What you're looking for |
|---|---|
| Steps to apply | How many screens and fields? |
| Account creation | Were you forced to create a login? |
| Repeated data | Did you upload a CV and then retype it? |
| Time taken | Minutes from "apply" to "submitted" |
| Confirmation | Did you get a message saying it was received? |
| Expectations | Did anything tell you what happens next, and when? |
Every extra step loses people, and the most capable candidates, who have the most options, are often the least patient. If the application takes more than ten minutes on a phone, shorten it.
While you're there, note what personal information the application asks for and whether it explains how it will be used. Candidate data is personal information under Canadian privacy law. The Office of the Privacy Commissioner's summary of privacy laws in Canada explains which law applies where; your privacy lead should decide what you collect and how long you keep it.
Part 4: wait, and time everything (over the next two weeks)
This part runs in the background. Track:
- how long until a human, not an automated message, contacts you
- whether that contact is personal or a template with the wrong name in it
- whether anyone tells you where you stand
- if you're declined, whether you're told, and how
Because your test application may be screened out quickly, ask your HR lead to also pull the timestamps for the last ten real applicants who reached a phone screen: application date, first contact date, interview date and decision date. Those real numbers often tell the clearest story.
Part 5: talk to recent hires and recent decliners (60 minutes)
Spend fifteen minutes each with two people hired in the last six months and, if you can, two people who declined an offer or withdrew. Ask the same four questions:
- What almost made you stop?
- What did you wish you'd known earlier?
- What made you say yes, or no?
- What did you tell friends about the process?
Recent hires will be polite. Listen for hesitations rather than complaints.
Scoring what you found
Score each area from 1 (poor) to 3 (good):
| Area | 1 | 2 | 3 |
|---|---|---|---|
| Findability | Only job boards | Careers page appears | Openings in job results, own pages first |
| Clarity | Key facts missing | Facts present but buried | Location, schedule, process up front |
| Ease of applying | Over 15 minutes or forced login | 10–15 minutes | Under 10 minutes on a phone |
| Speed | Over a week to first human contact | 3–7 days | Within 2 business days |
| Communication | Silence | Generic updates | Personal updates and declines |
| Close | Finalists often withdraw | Mixed | Finalists rarely withdraw |
A total under 10 out of 18 means the process itself is losing people, and spending more on job ads will mostly fund withdrawals. A total of 14 or more means the next gains are probably in reach and messaging.
The fixes that usually matter most
In order of how often they're the main problem:
- Speed to first contact. Set a standard, such as two business days, give someone ownership of it, and track it. Our hiring process design work makes this routine.
- Decline messages. Write a template once; send it every time.
- A shorter application. CV plus a few screening questions is enough for most roles.
- What happens next. Add a short section to every ad and the confirmation message.
- The careers page. Answer the questions finalists keep asking in interviews.
Turning the audit into a habit
Write up your findings in a single page: score, top three problems, top three fixes, owner and date for each. Repeat the audit in a year, or sooner after a big change. Once you start fixing things, measure the effect through recruiting metrics rather than impressions.
If you'd like a second pair of eyes on your results, call, text or email through the contact page. More guides are on the guides index.
Frequently asked questions
What is candidate experience?
It's everything a job seeker sees, hears and waits for from the moment they look you up to the moment they start work or are turned down. It shapes whether good people finish your process and what they say about you afterwards.
Who should run the audit?
Someone who doesn't run hiring day to day, such as an owner, a manager from another team or a trusted outsider. The person who built the process tends not to see its gaps.
Is it a problem to apply to our own job?
Use a clearly internal test application and tell your hiring team afterwards, so nobody wastes time screening it. Delete the test record once the audit is done.
How often should we repeat it?
Once a year, and after any big change: a new applicant tracking system, a new careers page or a new hiring manager.