Exploratory research into how job board apps use push, in-app, and SMS notifications. The goal was to map the competitive landscape, find where Reed was falling short, and surface the highest-value opportunities.
Context
Reed.co.uk had a solid job search product, but the app's notification system had grown piecemeal. Job alert emails existed, a basic push setup existed, but nobody had looked at the full picture: what were competitors doing, where were the gaps, and what would actually bring users back to the app?
I was asked to run an exploratory research piece before any design work started. The brief was deliberately open: understand the notification landscape across the market, identify what Reed was missing, and come back with a prioritised set of opportunities.
Method
I audited the notification systems of every major job board available in the UK: Reed, Indeed, Glassdoor, LinkedIn, Welcome to the Jungle, Monster, Totaljobs, CV Library and Adzuna. For each platform I mapped every notification type across four channels: email, push, in-app and SMS.
For each platform I installed the iOS app, created a fresh account, and mapped every configurable notification setting and every notification type I could trigger. I also cross-referenced with their web settings panels, since some platforms split notification management across devices.
Key findings at a glance
Finding 1
Across all 9 platforms, email was the one notification channel that everyone had. Push existed in most but was used narrowly — almost exclusively for job alerts. The more nuanced notification types (company updates, recruiter outreach, expiry reminders) barely appeared anywhere.
Totaljobs, CV Library and Adzuna were at the bottom of the pack. They offered bare-minimum job alert notifications with no personalisation and no secondary channels.
Finding 2
Push notifications depend on users granting permission. Many don't. Of the 7 app-based platforms in the audit, only 2 had built an in-app notification centre that would catch alerts when push wasn't available or hadn't been seen.
The logic is simple: if a user opens the app and has a pending job alert they never received as a push, there's nowhere to surface it. The in-app channel closes that gap. Reed had nothing in this space.
Finding 3
Company-specific notifications — following a company and getting alerts when they post jobs — was only available in a small number of platforms. LinkedIn had built this well. Glassdoor allowed following on web but forced users to manage it in the app. Otta (now Welcome to the Jungle) had a version too.
For Reed, this was a gap. Job seekers targeting specific employers had no way to follow them and get notified. They had to rely on keyword alerts, which generate too much noise.
Finding 4
Users save jobs and forget them. Job listings expire. Monster and Totaljobs had both built reminders that fire before a saved job closes. Totaljobs had recently removed theirs — but the fact it existed at all validated the concept. Reed had no equivalent.
This is a low-effort, high-value notification type. It requires no new data. Reed already knew when listings expired. The reminder just needed to be built.
Finding 5
Glassdoor was the only identified competitor using salary insights as a notification surface. They pushed salary range updates for roles users had saved or searched for. Reed already had a salary checker tool — but it was passive. Users had to find it.
Turning salary data into a proactive notification was an opportunity nobody else was taking. Done right, it brings users back to the app for a reason that isn't "you have a new job alert" — which creates variety and reduces notification fatigue.
Finding 6
LinkedIn's "your profile appeared in X searches this week" is a powerful re-engagement mechanic. It triggers a response ("who was it?"), nudges users to optimise their profile, and brings them back to the app with positive intent rather than task-based urgency.
No other job board in the audit had replicated this. Reed's tech team already tracked profile views from recruiters. The notification itself would need investment, but the data existed.
Opportunities
What I took away
The most useful thing this research did was give the team permission to prioritise. Before it, notifications were seen as a low-priority engineering task. After it, we had a clear picture of where Reed was behind, which gaps were cheap to close, and which would require tech investment.
The in-app notification centre and expiry reminders went into the next sprint. Salary insights and profile views were scoped as a larger initiative. Company following became part of a longer product roadmap conversation.
Competitive research isn't always glamorous. But knowing exactly what the market has built — and hasn't — is what makes design decisions defensible.