Stéphanie Filion: Executive Program Manager
Thomas Fitzpatrick: Illustrator
When job candidates landed on our careers portal, they were faced with a long list of over 150 job postings. We were expecting to experience a lot of growth, and therefor hire a lot of new Hopper humans, so we knew it would be necessary to make it easier for candidates to find relevant job postings.
After going through multiple formats, I landed on one that simplified the process and would help to educate prospective candidates on our new organizational structure. I removed the filters from before and opted for a simple search bar, so if users wanted to search by teams, business units (later renamed to job categories), or locations, they could enter that specific funnel and learn more about that part of the company.
I was working on this project while simultaneously designing and building the Interviewing at Hopper Guide (check out my case study!), so I also included a module underneath our job search funnels to encourage people to read it even before applying.
Hopper had also recently solidified all of their new culture material and we wanted to showcase all of the work our CEO had done to foster the culture of growth, curiosity, and support that eventually developed. By letting prospective candidates read about our culture before applying, we also gave them a chance to figure out if we would be a good culture fit for them before filling out an application. For this reason, I also sourced testimonials from multiple employees in multiple languages from all of our office locations so every user could read what it was like to work at Hopper, ideally in their native language.
Before the redesign, if a user made a search with no job results, they would just receive the message "no positions found matching your search". Not very helpful, eh?
I designed a dead end that was friendly and helpful, suggesting some of our most commonly searched positions, or to search by location, team, or job category instead. This was intended to cover the case if there was a position open that did match their desired job but our nomenclature just didn't match their search query.