COLAB33 - Web App

Job Quest

A web app that helps overwhelmed entry-level job seekers take step-by-step instructions to progress their job search

Problem Background  

The job search process is overwhelming, especially for entry-level job seekers who lack experience and confidence in what steps to take. Many job seekers struggle with staying organized, prioritizing job applications, and maintaining motivation throughout their job search journey. With so many tools offering disparate solutions, there’s a need for a single, structured system that helps users focus on the right actions and stay motivated without feeling lost or overwhelmed.

Our problem statement:
How might we help entry-level job seekers prioritize their time so they take more consistent and effective actions to land more interviews?

Why Now?

There are 40 million job seekers each week on LinkedIn (market size). We estimate the total addressable market focused on entry-level job seekers to be 4.4 million who regularly use LinkedIn. This is based on an estimate from Standout Resume Australia of 26 applicants per entry-level job (in line with other estimates), and LinkedIn stating there are 169,000 entry level roles advertised at any one time.

From our survey research findings of 75% of entry-level job seekers experiencing overwhelm during job search, this means our total obtainable market is 3.3 million job seekers weekly.

With this level of competition among job seekers, there is a significant need for a tool that helps job seekers take consistent action and engage meaningfully in networking. By addressing these pain points, Job Quest aims to help job seekers build habits, reduce overwhelm, and take strategic actions that increase their chances of landing interviews.

User Pain Points & Research Insights

1. Lack of interviews from actively searching: 42% of job seekers we surveyed have been actively searching for a job for 3-12 months, yet 67% hadn’t landed a single interview.

Forms response chart. Question title: How long have you been actively searching for a job in this field?. Number of responses: 12 responses.

2. Lack of Clear Direction: 67% of job seekers we surveyed don’t set daily or weekly goals, resulting in scattered efforts. Many only apply for jobs when they see an opportunity, with no strategic networking or follow-ups.

Forms response chart. Question title: Do you currently set daily or weekly goals for your job search?. Number of responses: 12 responses.

3. Job search process overwhelm: Job seekers feel overwhelmed by the job search process and are unsure where to focus their efforts. 76% of those surveyed said they often feel overwhelmed by the job search process, with this being one of their biggest demotivators.

Forms response chart. Question title: What demotivates you or causes you to procrastinate in your job search? (Select up to 2). Number of responses: 12 responses.

Feedback

Our user interviews shed more light on the statistics found from our survey around job search overwhelm and its effect on motivation, with one interviewee sharing:

“The lack of motivation is coming from the lack of direction and being overwhelmed by the vastness of the task of finding a job”.

Other users suggested there was no way of prioritising efforts for jobs you are most interested in on platforms like LinkedIn and job tracking tools like Huntr, so this feature was requested.

Solution Explanation

Based on our users' pain points, and assessing technical feasibility given our current team skills and resources, we proposed to build Job Quest, a web application that simplifies the job search process by providing structured guidance through Quests, Missions, and a Job Follow-Up Board. 

The key features include:

1. Quests & Missions:

Job seekers can follow specific Quests to tackle major job search goals step-by-step. Each Quest, such as “Optimize My LinkedIn Profile” or “Tailor My Resume,” is broken down into Missions that guide users with actionable instructions and tips.

2. Job Follow-Up Board:

A streamlined board where users can track their applications, view their highest priority jobs with options to rank how motivated users are for each job, and monitor follow-up dates, including receiving email reminders for when to follow up applications and with who. This feature helps users maintain focus and stay organized without relying on complex tools.

3. Do This Next Button:

Users are prompted to take the most impactful next step in their job search journey, whether it’s following up with a recruiter or sending a connection request on LinkedIn. This helps alleviate decision fatigue and keeps users progressing with small, consistent actions.

Low Fidelity Sketches

High Fidelity Wireframes

Login/Sign-Up Flow
Quest Flows

Iterative Design Learnings

After we let users test our app in front of us, they shared important feedback in live calls:

Quests feature

There should be more instructions in one Quest card. Two users stressed it would be more useful to take more significant actions before clicking to the next set of instructions, as they both found the amount of clicking needed was annoying

Before
  • Spacing so each instruction card wasn’t such a block of text was also highlighted.
  • It would be good to make the Mission instructions clickable, so when asking user to open LinkedIn, Indeed, provide clickable hyperlinks to job search pages. 
  • This was prioritised and the Quest feature was totally redesigned by the team, both by our designer and the developers.

Job Follow Up Board & Add Jobs Feature
  • Create a Notes field in the Add/Edit jobs section for users to add notes (multiple users said this)some text
    • This feature was agreed by the team to be low effort and medium impact for the user, so we built this for the MVP after this feedback.
Before
After

After building our MVP, feature requests from user testing indicated having an Advanced Networking Quest, as well as a Mock Interviews and Interview Questions Quest, so these are features we would consider to build which help achieve the goal of landing interviews and also jobs for users.

Technical implementation

Our tech stack:
  • We’re using Flask as our backend framework, React.js as frontend framework, tailwind for css frameworks, and our database choice was MySQL.
  • Our app is hosted in GCP(Google Cloud Platform)
High level journey of a request:
  • We chose these frameworks because of the high level of familiarity we have working with them, as well as being robust tools that are industry standard.
  • Our app saves different elements in the database such as user information for login, quests information that helps us display them in the page and jobs that users can save, update and delete in the page and we display it for them in a table. Here’s a gif of how we’re doing all of this functionalities using HTTPi:

Technical challenges

Hardest part of development has been figuring out logic for features like keeping track of user progress and buttons not working the way it's intended. Fortunately, our app doesn’t have any major issues as of now.

The key takeaways for us have been how much we can still improve our skills and how valuable working with your teammates is, especially when you’ve hit a roadblock.

Future Steps

We will not be continuing the project, however have reflected on what we would do if we were to continue. We would plan to iterate the development of features already built from further user testing and feedback. 

Due to time and technical feasibility constraints, we originally proposed to make this app into a Chrome extension and build a scraping tool to collect job information automatically into our Job Follow Up board. We would have liked to incorporate this into our core product with more time to learn how to do this technically, as it would have made a big difference to usability.

Other feature requests from users in the backlog included:

Learnings

Product Manager Learnings:

Matt Garrow-Fisher

  1. Communication: Regular check-ins, stand-ups and one-on-ones enabled high team commitment levels.
  2. Prioritization: Always trade-offs of what to build first and leave out  to maximize value with tight deadlines.
  3. Testing: Shipping early and imperfectly provides valuable user feedback that trumps building late and guessing what users want.

Designer Learnings:

Ayo Obayomi

  1. Junior Designer: Learned from a more experienced designer what is required during the hand-off process to allow developers to understand the flow and logic. 
  2. Cross-Functional Communication: Actively informing the team with the progress of the designs as well any hindrance in order to move forward in our sprints. 
  3. Design Best-Practices: I learned to validate design decisions by testing and seeking feedback when unsure if an element followed best practices, ensuring intuitive designs.

Designer Learnings:

Jo Sturdivant

  1. Adapting to an Established Team: Joining the team in week 6 of 8 was challenging, as I had to quickly adapt to existing workflows, dynamics, and goals. This mirrors real-world situations where you often integrate into teams mid-project, and flexibility is essential.
  2. Work-Blocking for Efficiency: With only two weeks to complete the project, I learned the importance of a structured work-blocking system. This approach allowed me to manage my time effectively and meet deadlines under pressure.
  3. Making Data-Driven Design Decisions: Unlike my past projects, I had to rely on research conducted by others. This was a valuable experience in using pre-existing data to guide design decisions, helping me focus on the core insights without starting from scratch.

Developer Learnings:

Nicolas Rodriguez

  1. Communication: Being open and honest about what each team member thinks is the best way to move forward.
  2. Prioritization: Going for things that are set in stone, has a high value to the user and doesn’t require much effort to develop is always the best way to prioritize features.
  3. Testing: Make a commitment to an approach but also make alternative plans in case user testing goes sideways.

Developer Learnings:

Vanady Beard

&

As the back-end developer, I learned how important it is to create efficient and reliable systems that support the entire application. This experience also taught me the importance of optimising the database and ensuring the backend is scalable and easy to maintain.

Developer Learnings:

Stephen Asiedu

&

As a back-end developer, I've come to understand the importance of being familiar with various database systems and modules. This knowledge enables me to build diverse applications and maintain versatility in my work. I've also learned that the responsibility for making the right choices rests on my shoulders, guided by my best judgement.

Developer Learnings:

Anthony Hernandez

&

  1. Align with Product Vision: Working with a team presented its share of struggles: The lack of creative control was challenging for me, However I adapted to align myself with the team’s vision.
  2. Be flexible to redo code: Quickly integrating extra help, including a new UX designer, required us to overhaul everything we had done. Tearing everything apart and starting from scratch was overwhelming in just 1 ½  weeks.
  3. Hard work pays off: Despite the initial challenges and the lack of fun in redoing our work, the final product ended up much better than we originally imagined.

Developer Learnings:

Maurquise Williams

&

  1. Process of Creating an MVP: Developing a Minimum Viable Product (MVP) taught me how to focus on delivering core functionalities balancing between essential features and avoiding scope creep.
  2. Collaboration in a Real-World Tech Setting: This experience taught me how to collaborate efficiently in a fast-paced tech environment, keeping the team aligned and productive, even while working remotely across time zones.
  3. Sharpening Critical Thinking and Problem-Solving Skills: This experience honed my ability to think critically and solve problems efficiently. By tackling challenges and finding quick solutions, I sharpened my decision-making and troubleshooting skills in a dynamic, real-world setting.

Developer Learnings:

Jeremiah Williams

&

All in all this experience was very awesome I learned that in coding with others being transparent is key

Developers Learnings:

Justin Farley

&

I learned how important communication is when working with a team. Communication provides understanding, advice, ideas, and much more. While working with the product team, I’ve found that communication keeps everything flowing smoothly. Working with a team also showed me that every member brings something different to the table and we all have to work together in order to align and meet our end goal.

Full Team Learning

Cross-Functional Collaboration:

By frequently checking in and updating each other on progress, we were able to pivot quickly when needed and keep the project moving forward despite challenges.

Remote Teamwork and Communication:

Working remotely across different time zones provided valuable experience in managing distributed teams. We learned the importance of maintaining clear and consistent communication, using tools like Slack, Google Meet and Discord to stay connected and aligned.

Adaptability and Overcoming Roadblocks:

Every team member faced challenges, whether it was learning new frameworks or adjusting to unforeseen technical limitations. However, we quickly learned how to adapt, revise our approach, and move forward when we encountered obstacles to deliver on time.