JOB SEARCH RESULTS

I had just joined Glassdoor as a Senior Product Designer in charge of Jobs, both B2B and B2C experiences. I was part of a small team that consisted of myself as the designer, a PM, a Front End engineer, a Back End engineer, and a QA engineer. As the sole designer on the Jobs team, I was responsible for the UX/UI design, prototyping, user testing, and any other deliverables needed. 

Upon joining Glassdoor, I was immediately tasked with redesigning the Job’s B2C page. The Job’s B2C experience had been largely ignored; previously, the main focus had been on Reviews and building out the Job’s B2B platform. The result was that while many people came to Glassdoor to read reviews on companies they were looking to apply to, many of these users did not use Glassdoor to apply to said company.

After running a search, a user would select a job that would pique their interest from the results shown in the listings page. Clicking on a job would take the user to the job details page.

From here, a user wanting to learn more about the company would click on About, which would take them to a new page showing additional information on the company. They would then click on reviews to see employee reviews for this company, which would also take them to a new page. Once they’ve decided to apply for this job, they now have to go back to the job details page to apply. They repeat this process for each job.

I had an idea of what I wanted to change in the experience. I wanted to make changes to the layout to improve readability and findability. More importantly, no more having to click through multiple pages to learn about the company you are considering applying to. The job description, the about page for the company and reviews, everything a user needed to inform them whether they should apply to a job would be available without leaving the job listings page. With these changes, I believed I could empower users to easily and quickly find the right job for them. 

To test my hypothesis and see if this idea had potential, we opted to experiment with a MVP version of the page. With minimal changes to the existing design, I added the features I thought the users would find helpful.

I basically shoehorned the information I felt users needed into the old design. It wasn’t pretty, but we wanted something we could turn around fast. The sooner we found out if the idea had merit, the sooner we can either work on improvements or move on to something else.