5 August 2026
Time to first screen on a phone-sized hiring app
The clock from submit to first human look is a real hiring-app number — but weekends, public holidays, and night-time applies in Malaysia bend it out of shape.
Time-to-first-screen sounds precise. A candidate submits at 21:40 on a Thursday from a bus in Kajang. A recruiter opens the file at 10:15 on Monday. The hiring app reports 84 hours. Leadership asks why the team is slow.
The clock did not notice Friday, the weekend, or the fact that store-role reviewers in that company do not work Sunday nights. It also did not notice that the candidate submitted twice, and the first row — the one the clock used — was the failed attempt.
When we include time-to-first-screen in a findings pack, we ask three dull questions first:
- When does the reviewer team actually sit, including after public holidays?
- Which timestamp is “submit” — first tap, last successful submit, or recruiter-console created-at?
- Do night-time applies (common on mobile hiring apps) wait in a queue until morning, and is that wait named?
A campus app we read in Shah Alam looked slow until we split weekday daytime submits from everything else. Daytime files were opened within a working morning. Night files waited, as everyone in the room already knew, but the chart had been averaging them into a single embarrassment.
If your recruitment app shows a single average time-to-first-screen, treat it as a conversation starter, not a verdict. Split by hour of submit, by working calendar, and by whether a human actually opened the file or an auto-reject rule did. Auto-reject is a screen too. It should not hide inside an average.