Working closely with engineering and recruiter users, I designed an overhaul to the job search feature to meet the following desires:

• Reduce the number of fields I have to fill out
• Make it easy to get to past searches
• Easily filter by industry
• Easily filter or increase number of search results
• Easily get rid of those jobs I have no interest in
• Easily compare jobs to determine which ones I want to work

An engineering brain child, the candidate recommendation program was our attempt to matchmake a recruiter's inactive resumes on file in the system with the jobs in our system. This beta program needed to accomplish 2 things: Get the receommendation engine engineering had built integrated into the product, get users to give us thousands of resumes and then give us actionable feedback on how well the resumes matched the recommended jobs. These two goals were paramount in helping engineering improve their algorithms and the business determine if this was a viable product line to pursue. Setting these goals was vital to me in designing this beta, as well as defending my design decisions that pushed evaluation and quick feedback instead of easily being able to submit candidates to jobs.

I work with some very smart engineers. So smart that they engineered the BountyJobs product to dynamically take you to the application location that makes the most sense if you try to go somewhere that no longer exists. For example, if a user clicks on a link that takes them to a job page that no longer exists because the job has been closed, the application would evaluate that request and take users to the main "Find Jobs" page. In their minds, this eliminated the need for a 404 error page because the user would always land somewhere relevant. And while I apprecaite this very fine bit of engineering, I felt that the user would be confused by this behavior. Being redirected with no information as to why, feels like something went wrong or the application is broken. I argued that getting the expected, standard result to an action (a proper page not found error for a page not found) was a better user experience and prevailed.