The Field Recruiting App (affectionately known internally as ‘the FRAPP’) is an app that allows users to capture candidates’ resumes offline. The typical persona for this app would be a recruiter at a job fair or university recruiting event, or a retail store manager taking applications at a specific location. The app was designed and built in Android and iOS.
I worked on this project in late 2016 with our mobile team (one iOS developer, an Android developer, and our product manager). The idea came from an internal hackathon, during which the team created a way to take a picture of a resume and parse the information into the core app.
We began our research by conducting contextual inquiries. The product manager (Kelly Fang) and I went to a job fair, and spoke with the recruiters and the candidates to discern what the pains and complications were with the process, as well as understand whether our app would be useful to them. The idea was indeed well-received, and would be solving various issues for them.
We also spoke with some of our customers about their pains, and how they might use the app. One of our companies, Alaska Airlines, relies heavily on job fairs to draw in potential pilots and flight attendants into their talent pool. Other companies would use the app to take applications in-store instead of directing their candidates to apply online.
As far as we could find, there are no other apps that perform this specific function, so our competitive analysis was directed towards apps that have a similar interaction in that they have an employee flow and a customer flow. We looked at sign-in apps like Envoy, check-out apps like Square, and even in-store help apps like the ones at Target.
From our conversations with users and potential users, we were able to identify some key problems we could solve with the FRAPP.
I began by creating a paper and pen wireframe that I put into a prototype. From the conversations we had, we knew that this app would be primarily used on a tablet. Because of this, I created the prototype in a tablet size and tested it on an iPad.
The solution was to create two flows; one for internal users to set up which jobs, source, and brand they wanted prospective candidates to see (kiosk mode), and one for candidates to quickly submit their resumes.
The product manager and I tested this prototype internally, and once we refined the flows we were faced with a few more questions:
With these questions in hand, we returned to users with a higher fidelity prototype to test and understand their needs better.
We tested several methods for unlocking kiosk mode and getting back to build mode including:
The touch option seemed the most secure and simple, so we went with that.
From our talks with users, we determined that they needed to specify these three things:
As we found during our interviews, not all candidates have resumes. This meant that we had to create a super-quick alternate experience for these users.
During our contextual interviews, we found that recruiters will typically write a note in the white space of a candidate’s resume to be able to remember them when they sort through the pile later. We considered many options on how we could do this using the app, but realized the format simply wasn’t conducive to that. The candidate would have to hand the app back and forth, and the flow of information would be lost.
Luckily, there is already a way to do this using the companion app. As the candidates are coming in, they will show up inside the app, and recruiters can take notes there if they talk to a candidate they want to keep track of.
With the flows sorted out, I moved on to the visual design and branding of the app. It needed it’s own logo and style that would make it seem like part of a suite, but also a separate app.
In general, I kept the styles closely aligned to Google’s Material Design guidelines and Apple’s Human Interface Guidelines. I kept our bright brand green, and chose a deep purple to compliment it.
I also designed an icon for it. I went through several iterations, focusing on the “field” aspect of it.
In the end, the team opted to go with a simple option that is similar to the companion app.
The end result is a simple experience for setting up a quick job list landing page, and a simple apply. We demoed the application flow at our first annual Hiring Success Conference in April of 2016.