Project Summary

Probably you have searched for a job through different websites and services and know how hard it could be to manage all those communications and keep track of all applications in all those different services, I tried to solve this problem by creating a single service for users to keep track of all their applications in one place.

I created a usability research plan which I described what the problem is and how and why I want to solve this problem. What is the context of my research, who are my target users, what I want to ask and what is my plan for researching.

What Was the Problem?

Searching for jobs, communicating with recruiters, applying to jobs, following up and ... all of these are very time consuming and hard to do. I wanted to explore this area to see if I can find a better solution to manage all of these tasks in one place easily.

What I Did?

Started asking questions from people who were in job market and finding their pain points. Then sketched some ideas and created a prototype in Axure to test it with users.

Who Did I Work With?

Since it was a personal project I was only one who worked on it.


Research Focus

I want to learn how the job seekers manage their job seeking process. How hard is to track all the applied jobs? Is it possible to make this process easier to track and manage? Background As a recent job seeker I found job seeking websites too complicated and tracking all the applied jobs are very hard work, there were times that I applied to one job for multiple times without knowing it. Each site has a different approach for applying to a job, some of them you have to fill a lot forms before applying to a job every time, some of them suggest old and expired positions.


Mostly in home where applicants are searching for the jobs with their computer. Participants I recruit people from my friends and family or coworkers.

Key Questions

  • What is the media that they are using to search for the job?
  • Are they satisfied with current methods in searching and applying for the jobs?
  • How they managed their applied jobs and keep track of them?

Research Plan

Research will be held at participant place, or outside in coffee shop with the user own device. The interview will last about 60 minutes, will include short briefing and questions, interview and observation the job seeking process with the user’s device. The user will be asked to search for some desired jobs, apply to them and manage the applied jobs.

Job Seeker Research Questionnaire

Next step was to create a list that contains the questions that I wanted to ask from your participants.

  • Tell me more about yourself
  • What is your daily routine?
  • What technologies do you use?
  • Why are you looking for a new job?
  • How do you search for a new job ? What devices do you use? Why you use them?
  • Which method for searching for a new job is better? Why is that?
  • What websites do you use? Why you use them?
  • Do you register yourself on those websites? Are you feel comfortable registering yourself on those websites?
  • Which one of those websites is your favorite? Why is that?
  • Do you use any job searching app on your mobile? Why?
  • How do you keep track of all your applied jobs?
  • Can you show me how do you search for a job and apply it on your device?
  • Are you satisfied with your current job searching method? Why?
  • What is the most important factors in your job searching routine? Why?
  • How do you select the jobs that you want to apply? What factors do you consider before applying to one of them?
  • How many jobs did you apply in the last week?
  • What happens after you applied for a job? How do you follow up with that job?
  • What is your idea of the best job searching app or website? What are the most important factors in your desired job searching app?
  • Is there anything else that you can add to our conversation?


After I found my participants and ask my questions, I needed to create some persona. persona is fictional characters created to represent the different user types that might use a site, brand, or product in a similar way. For this project I asked from two participants and the below image shows the persona that I created.

As you can see in this picture, I categorized the pain points this persona had and ideal features that this persona wanted.


Story Boarding

After the interview I created story boarding to show the overall progress of our application.


User Flow

Now it’s time to create some user flows for the project to help what I am going to create, and its easy to iterate before diving into the design. It helped me to understand possible scenarios, choices and errors.


A site map is a visual representation of a website or app’s structure. It shows how the navigation will be structured, shows relationships between pages or screens. It’s generally created before wireframes, and can help with scoping.


Low Fidelity Prototyping

Sketches and paper prototypes help the designer explore and capture early ideas, test broad hypotheses, facilitate internal discussions, and communicate provisional design intent. After sketching some ideas we can test them with other people, describe the process to them and get their feedback and ideas about the design. As you see in these pictures I sketched some Lo-Fi wireframes and other people added some questions and feedback about my designs with some sticky notes.

High Fidelity Prototyping

High fidelity prototypes commonly explore a few detailed interaction moments in the entire user experience. Those moment can, and often do, involve motion and detailed visual design. After I created some Lo-Fi wireframes the next step is to turn them into Hi-Fi wireframes with interactions and more details. I use Axure to create these wireframes.

User Research

After creating wireframes in Axure I ran some usability testing with some users to find:

  • How do users react to the landing page?
  • Are they able to discover key product features?
  • Do more people opt to search or browse for content?
  • Are users able to successfully complete the primary flow?
  • Where do users get stuck?

Dashboard Before and After


  • Dashboard data was not clear for users. They wanted to see their applications status in dashboard and easily do some functions without going to its related page.


  • Now it shows the applications that need attention, their unread messages and some shortcut to mostly used functions.
Dashboard Before Dashboard After

Recruiter’s Page Before and After


  • Clicking on recruiter’s name goes to contacts page with list of all recruiters.


  • Now it will open recruiter’s contact details page with list of recent conversations and applications.
Recruiter Before Recruiter After

Applications + Messages Before and After


  • Applications and messages were separated before and made some confusion, they couldn’t find related messages to applications easily.


  • Now applications and messages are in one view and each application will show unread messages in its row.
Before After

Application Detail Before and After


  • Application page was hard to understand for users and they couldn’t easily find the related tasks in this page.


  • Now it has a cleaner design and has a better structure to show, edit and add data.
Before After

Messages Before and After


  • Users have problems to find the compose box in messaging page.


  • By moving to compose box to the top now its more clear to users.
After After

Wireframes With Annotations After Usability Research