JOB MATCH AND ALERTS
This design was begun as a two part requirement. Part one was to design a page where end users of a recruiting product could view their job matches and take some action based off the matches. Part two was to design a small flow to enable users to set up job alerts based on some defined criteria for both a desktop and mobile version.
USER RESEARCH SUMMARY
The user research for this project was primarily A/B testing of different design options and design validation through lab studies/eye tracking. Research concluded that a vast majority of users would want to see their matches prior to already applied jobs, favorites, and job alerts. Important information for each job was posting date, location, distance, and commute. Eye tracking concluded the first place people addressed was the percent match and thus led to that number being first per job match.
JOB MATCH
The first part of the requirement for this project was to create a page where users could view and take action on their job matches. Users could view details of each specific match as well as see surfaced information regarding each match such a date posted. The job match page also had the ability to create job alerts which is further explained below.
![]() | ![]() |
---|
MOBILE DESIGN
The second part of the requirement for this project was to have some method to manage job alerts across both desktop and mobile applications. The goal was to keep consistency of the experience between both platforms as well create a simple mobile friendly flow. An area to manage alerts was created along with an area to create/edit alerts.
![]() | ![]() |
---|
PROJECT LESSONS LEARNED
This project was a delve into the focus order of a page. Our research showed the typical left to right top to bottom focus order of our participants, but called out very quickly the placement of the job match percentage as being very important. Consistency of experience between desktop and mobile was also reiterated as having extreme value. Learned behaviors can be transferable between the two and inconsistency can cause a poor user experience.