Untapped: Candidate Dashboard
Increasing profile completion through a compelling dashboard
Untapped: Candidate Dashboard
Increasing profile completion through a compelling dashboard
Untapped: Candidate Dashboard
Increasing profile completion through a compelling dashboard
Untapped: Candidate Dashboard
Increasing profile completion through a compelling dashboard
Product Design
Content Strategy
User Research
Market Research
Untapped connects early-career talent with tech job opportunities, where recruiters post positions and job seekers create profiles to apply to jobs and browse company events.
Recruiters were dissatisfied with low profile completion rates among candidates (average 56% complete), which limited their ability to find qualified talent because valuable candidate information was missing. Simultaneously, our business metrics showed that our current tactic—directing candidates to the Communities page upon login—wasn't driving job applications, our key business metric.
Activities
UX Design, UI Design, Rapid Iteration, Prototyping, Funnel Optimization, Data Analysis
Activities
UX Design, UI Design, Rapid Iteration, Prototyping, Funnel Optimization, Data Analysis
Activities
UX Design, UI Design, Rapid Iteration, Prototyping, Funnel Optimization, Data Analysis
Timeline
4 weeks
Timeline
4 weeks
Timeline
4 weeks
Team
Jacob Newman (Product Manager)
Zama Mohammed (Engineer)
Elizabeth Browne (Engineer)
Aaron Brown (Engineer)
Team
Jacob Newman (Product Manager)
Zama Mohammed (Engineer)
Elizabeth Browne (Engineer)
Aaron Brown (Engineer)
Team
Jacob Newman (Product Manager)
Zama Mohammed (Engineer)
Elizabeth Browne (Engineer)
Aaron Brown (Engineer)
Company Type
B2B
B2C
Marketplace
Recruiting
Series C
Company Type
B2B
B2C
Marketplace
Recruiting
Series C
Company Type
B2B
B2C
Marketplace
Recruiting
Series C
Hypothesis
Showing a job-centric page to candidates upon login would boost both profile completion and average number of applications per candidate.
Hypothesis
Showing a job-centric page to candidates upon login would boost both profile completion and average number of applications per candidate.
Hypothesis
Showing a job-centric page to candidates upon login would boost both profile completion and average number of applications per candidate.
As a team, we brainstormed and agreed upon features for the new dashboard.
I led a workshop with our product team to prioritize features for the new page, voting on which would provide the most value while staying within our engineering constraints.
Upon login, users landed on the Communities page—a product area with low engagement that rarely led to applications. We needed a new approach that would benefit both users and our business goals.
As a team, we brainstormed and agreed upon features for the new dashboard.
I led a workshop with our product team to prioritize features for the new page, voting on which would provide the most value while staying within our engineering constraints.
Upon login, users landed on the Communities page—a product area with low engagement that rarely led to applications. We needed a new approach that would benefit both users and our business goals.
As a team, we brainstormed and agreed upon features for the new dashboard.
I led a workshop with our product team to prioritize features for the new page, voting on which would provide the most value while staying within our engineering constraints.
Upon login, users landed on the Communities page—a product area with low engagement that rarely led to applications. We needed a new approach that would benefit both users and our business goals.
As a team, we brainstormed and agreed upon features for the new dashboard.
I led a workshop with our product team to prioritize features for the new page, voting on which would provide the most value while staying within our engineering constraints.
Upon login, users landed on the Communities page—a product area with low engagement that rarely led to applications. We needed a new approach that would benefit both users and our business goals.
Existing page: Upon login, users landed on the "Communities" page—a feed with low engagement that rarely led to applications.
Workshop outcomes: We identified features that we thought would perform well, ones that we could test to get signal to understand if we should invest more time, and ones that would be too difficult to build for this MVP.
With profile completion as our most important metric, we explored designs that would yield highest conversion on data completion.
Recruiters search and filter for candidates, so having a complete profile is crucial for candidates to be found by recruiters. We went through a rapid iteration process to explore design options.
With profile completion as our most important metric, we explored designs that would yield highest conversion on data completion.
Recruiters search and filter for candidates, so having a complete profile is crucial for candidates to be found by recruiters. We went through a rapid iteration process to explore design options.
With profile completion as our most important metric, we explored designs that would yield highest conversion on data completion.
Recruiters search and filter for candidates, so having a complete profile is crucial for candidates to be found by recruiters. We went through a rapid iteration process to explore design options.
With profile completion as our most important metric, we explored designs that would yield highest conversion on data completion.
Recruiters search and filter for candidates, so having a complete profile is crucial for candidates to be found by recruiters. We went through a rapid iteration process to explore design options.
Profile completion module: We took inspiration from 23andMe's approach, creating a step-by-step question flow that made profile completion feel less tedious.
Permutations: Since our profile page used another frontend framework, this page required designs for every profile question.
Success states: Due to engineering bandwidth, we couldn't build all the questions for the MVP. We designed custom success states to let students know if they had more information to fill out on their profile page.
The rest of the page pulled in various features to test engagement.
We deliberately included multiple new features on the page to test which would drive engagement. This experimental approach allowed us to measure user interaction with each section and make data-driven decisions about future development. With limited engineering resources, we reused existing components where possible while ensuring a cohesive experience.
The rest of the page pulled in various features to test engagement.
We deliberately included multiple new features on the page to test which would drive engagement. This experimental approach allowed us to measure user interaction with each section and make data-driven decisions about future development. With limited engineering resources, we reused existing components where possible while ensuring a cohesive experience.
The rest of the page pulled in various features to test engagement.
We deliberately included multiple new features on the page to test which would drive engagement. This experimental approach allowed us to measure user interaction with each section and make data-driven decisions about future development. With limited engineering resources, we reused existing components where possible while ensuring a cohesive experience.
The rest of the page pulled in various features to test engagement.
We deliberately included multiple new features on the page to test which would drive engagement. This experimental approach allowed us to measure user interaction with each section and make data-driven decisions about future development. With limited engineering resources, we reused existing components where possible while ensuring a cohesive experience.
Prototype: We focused heavily on the main Content Library page and the subject-specific page, which was broken down into units and topics, a standard across all high school curriculums.
After launching, we fast-followed with an update to reduce support tickets.
In response, we created a tiered completion system that clearly explained what was needed at each level (low/medium/high discoverability) and how to achieve full completion, linking them to their profile page where they could fill out the remaining fields.
When we launched, the profile completion module was the most-engaged section of the page. However, for the MVP, engineering didn’t have the bandwidth to add all profile fields as modules, and we immediately received 100+ support tickets from confused job seekers who couldn't figure out how to reach 100% completion.
After launching, we fast-followed with an update to reduce support tickets.
In response, we created a tiered completion system that clearly explained what was needed at each level (low/medium/high discoverability) and how to achieve full completion, linking them to their profile page where they could fill out the remaining fields.
When we launched, the profile completion module was the most-engaged section of the page. However, for the MVP, engineering didn’t have the bandwidth to add all profile fields as modules, and we immediately received 100+ support tickets from confused job seekers who couldn't figure out how to reach 100% completion.
After launching, we fast-followed with an update to reduce support tickets.
In response, we created a tiered completion system that clearly explained what was needed at each level (low/medium/high discoverability) and how to achieve full completion, linking them to their profile page where they could fill out the remaining fields.
When we launched, the profile completion module was the most-engaged section of the page. However, for the MVP, engineering didn’t have the bandwidth to add all profile fields as modules, and we immediately received 100+ support tickets from confused job seekers who couldn't figure out how to reach 100% completion.
After launching, we fast-followed with an update to reduce support tickets.
In response, we created a tiered completion system that clearly explained what was needed at each level (low/medium/high discoverability) and how to achieve full completion, linking them to their profile page where they could fill out the remaining fields.
When we launched, the profile completion module was the most-engaged section of the page. However, for the MVP, engineering didn’t have the bandwidth to add all profile fields as modules, and we immediately received 100+ support tickets from confused job seekers who couldn't figure out how to reach 100% completion.
Fast-follow: We added this module to the candidate profile page, which was similar to a resume. As they filled out their profile data, the score automatically updated.
Outcomes
By focusing on user needs and removing barriers to engagement, our redesign delivered significant, measurable improvements across all our KPIs. The data validated our hypothesis that emphasizing jobs and profile completion would drive meaningful business results.
Outcomes
By focusing on user needs and removing barriers to engagement, our redesign delivered significant, measurable improvements across all our KPIs. The data validated our hypothesis that emphasizing jobs and profile completion would drive meaningful business results.
Outcomes
By focusing on user needs and removing barriers to engagement, our redesign delivered significant, measurable improvements across all our KPIs. The data validated our hypothesis that emphasizing jobs and profile completion would drive meaningful business results.
70%
increase in profile completion score for diversity data (gender, ethnicity, identifying groups) compared to before launch, from 16% to 86%
70%
increase in profile completion score for diversity data (gender, ethnicity, identifying groups) compared to before launch, from 16% to 86%
70%
increase in profile completion score for diversity data (gender, ethnicity, identifying groups) compared to before launch, from 16% to 86%
36%
increase in profile completion scores, from an average of 56% to 92% for active users
36%
increase in profile completion scores, from an average of 56% to 92% for active users
36%
increase in profile completion scores, from an average of 56% to 92% for active users
2x
more applications submitted compared to before launch
2x
more applications submitted compared to before launch
2x
more applications submitted compared to before launch
Outcomes
By focusing on user needs and removing barriers to engagement, our redesign delivered significant, measurable improvements across all our KPIs. The data validated our hypothesis that emphasizing jobs and profile completion would drive meaningful business results.
Outcomes
By focusing on user needs and removing barriers to engagement, our redesign delivered significant, measurable improvements across all our KPIs. The data validated our hypothesis that emphasizing jobs and profile completion would drive meaningful business results.
70%
increase in profile completion score for diversity data (gender, ethnicity, identifying groups) compared to before launch, from 16% to 86%
70%
increase in profile completion score for diversity data (gender, ethnicity, identifying groups) compared to before launch, from 16% to 86%
36%
increase in profile completion scores, from an average of 56% to 92% for active users
36%
increase in profile completion scores, from an average of 56% to 92% for active users
2x
more applications submitted compared to before launch
2x
more applications submitted compared to before launch
Interested in working together?
© Courtney Sabo, 2025