On average, people apply to 100-200+ jobs to get one job offer (Career Center, hirelehigh.com). How can they possibly be on top of each one?

I started off by interviewing individuals who would be potential users to the web app, and analyzed current job tracker tools on the market.

I interviewed 7 people who have job searched before, or are currently job searching. I asked questions about their job-applying process, and how they keep track of their applications.

I took a look at current tools people are using to track job applications and compared their useful functions.

1. Job tracking should be customizable and personable, since there are so many diverse careers that have different hiring processes.

2. Organizing job applications should be made easy and seamless, to take away one less worry off job appliers.

After compiling research insights, I started coming up with ideas for the different parts of the web app.

After sketching out my ideas, I started laying out what each page would look like.

With the new style guide, I updated the visuals for the hi-fi wireframes.

You can track all of your job applications through tracker boards that you can easily customize and optimize to your liking!

To support your job hunting journey, the dashboard is crafted to help you with visualize/understand other parts of the journey.

Staying on top of every job application requirements can be a hassle, but this to-do list helps organize all your assignments with which job application!

As I began designing the remaining frames necessary for development, the three of us soon realized that the current flows were confusing and needed to be redone. Alongside these redesigns, I decided to also update the UI and color palette.

1. Being comfortable talking and asking questions to your engineers is so important. Designing alongside engineers is much more efficient than designing alone and then shipping the product to engineers. The engineers and I often had conversations about how certain user flows should look and function like, and trying to optimize these flows required me to have an understanding what the engineers could code within their project scope/limitations.

2. Don’t fall in love with the first thing you design. When I initially designed Deki, I was creating it by myself for a case study project. I quite liked it and included it in my first portfolio. Afterwards, I found engineers who were willing to turn my vision into life. But shortly after, we realized there were several flaws with my logic and reasoning for already designed user flows and that I needed to redo them. For version 2, I redesigned the previous user flows, included more flows required for the minimally viable product (MVP), and updated the UI and color palette. Design is really a never-ending process of iterating and making previous things better!