Many jobs.
Your focus.

Recruiters share an account, but not every job.

A large company can have many recruiters and vacancies in one account. Each recruiter only needs to work on some of those jobs.

Showing everyone the full list makes it harder to find the jobs they need. It also creates a notification problem if they receive updates for jobs they don’t work on.

My work on the mobile app.

I was involved in the end-to-end Employer Mobile App experience. Here, I’m focusing on job selection: how recruiters choose which jobs to see in the app and receive notifications for.

The wider app work included a Home hub with AI-generated content for employers. This story follows the job-selection decisions in more detail.

Finding a job was only part of the problem.

Recruiters had long lists to work through, often with similar job titles and locations. Changing which jobs to follow was difficult, and turning off notifications one job at a time became a lot of work.

We needed to address both: finding the right jobs and deciding which ones should appear in the app or send updates. Search alone wouldn’t solve the notification problem.

These were issues raised in the project feedback. I don’t have figures showing how common each was.

Choose your jobs once.
Keep work and updates together.

In the MVP, the recruiter chooses a personal set of jobs from the company’s wider list. That same selection controls both the jobs shown in the app and the job notifications they receive.

Choose from the company list.
Keep your own jobs in view.

In the MVP, Manage your jobs linked the two choices: selected jobs appeared in the app and sent push notifications. Recruiters could change their selection at any time.

A job title alone is not enough.

This list includes repeated job titles as well as paused and closed jobs. Recognising the right vacancy takes more than reading its title.

That’s why the explorations included search, filters, and more information to help tell jobs apart.

Make selection easier.
Explain what it changes.

Alongside the MVP, I explored ways to make long lists easier to use: search, filters, sorting, starred jobs, reference numbers, and posting details. These are design explorations, not a list of released features.

Show how many jobs are selected.

This mock-up puts the selected-job count next to the explanation and toggles.

The count shows the current selection. The text explains that it affects both the jobs in the app and their notifications.

Find

Search and filters help narrow down a long list. Sorting changes the order of the results.

Recognise

Posting details and reference numbers help tell similar vacancies apart.

Select

A count shows how many jobs are selected. Select all and unselect all apply to the current list.

Understand

Explain whether the choice changes visible jobs, notifications, or both. This differs between the MVP and future direction.

Filters and starred jobs worked differently in Jobs, Candidates, and Messaging. I wanted recruiters to know which jobs they were viewing as they moved between those parts of the app.

The company’s jobs.
Your jobs and notifications.

In the MVP, recruiters could select the jobs they wanted to see in the app and receive notifications for those same jobs.

One choice controlled both. Choosing a smaller set just for notifications was part of the future direction, not the MVP.

This describes how the MVP worked. I don’t have measured results for notification volume, hiring speed, or engagement.

See the jobs assigned to you.
Focus on what matters.

In the future direction, an admin or job poster assigns jobs to recruiters. The app shows those assigned jobs, rather than every job in the company.

Recruiters no longer start by searching the full company list. They start with their assigned jobs, then choose which of those jobs should send notifications.

MVP

The recruiter selects jobs from the company list. That selection controls both app visibility and notifications.

Future

An admin or job poster assigns jobs. The recruiter sees those assigned jobs and chooses which of them sends notifications.

The product screenshots on this page show the MVP. The future direction is illustrated with the diagram above.

A shared account still needs to work for each person.

Job selection wasn’t just about shortening a list. It also determined which updates arrived on a recruiter’s phone.

That’s the part I’d keep checking in a design review: does the person understand what their selection changes? The answer needs to be clear both in the job list and in notification settings.