Signup Flow Redesign

Improving the signup experience for jobseekers
Problem Statement
Our signup flow is not providing, nor capturing, the information required for success on the app for jobseekers or hirers.
Objectives & Goals
Improve the look and usability of the signup flow
Define and capture the minimum info to provide value to a profile
Business Challenges
Updating/making changes to signup flow during a growth period
Impact of the signup flow on other areas throughout app
Small team, limited resources
Product Users
Hirers - Leadership/HR Professionals
Talent - Web3 industry (mostly developers)
Recruiters - All levels of experience

The Project

With a market opportunity to develop a SaaS product, we began an iterative process alongside two 2 clients to build an embedded white label SaaS version of our product on their own website.

The Target Audience

Leaders of Web3 ecosystems, the companies within their ecosystems (mostly early-stage startups), and the talent that they would attract (mostly developers).

The Goal

To re-create the experience and benefits of the HireVibes app via a branded iFrame embedded into a client's website.

My Role

Sole designer producing prototypes and first point of contact for testing with clients and gathering feedback on features. Worked alongside dev team & product manager.

The Impact

44% increase in talent pool during updates and a 3.4X increase, 6 months after launch.
Current Flow
Screen 1 of 2
Screen 2 of 2
Competitive Benchmarking
I researched some industry leaders to see what type of onboarding was currently commonplace in the market for similar user types. We included direct competitors, different job-related platforms, and Web3 platforms offering non-job-related services.
New User Flows
We wanted to accomplish two things when defining the new flow.

1. Reduce time and effort involved in the signup flow - from landing on the app to applying to/posting their first jobs.

2. Gather sufficient jobseeker info so that the user profile is of value to hirers straight away. This was based off of feedback we had gathered from hirers/recruiters on what minimum information they felt they needed to see.
New Design
Before
After
Some fundamental changes to the screen layout included:
  • Removing nav bar on the left-hand side. Not only a distraction, links were taking users out of the flow with no role assigned and no way to return.
  • The progress section at the top right corner was refined. The space underneath now serves as an opportunity to add value rather than another section to be read through.
  • We removed unnecessary fields and introduced suggestions. This would aid users with answers they may be uncertain about at this stage.
Remaining Screens:
2 of 4: We introduced a tag system, which linked to a smart job matching system.
3 of 4: We made the user aware of our main networking feature, and a chance to signup.
4 of 4: A portfolio link can be a quick and easy way to direct a hirer to all they need to see.
Giving Back
Breaking up the signup flow to different screens would hopefully improve usability. However, we felt that we were asking a lot of the users, without giving them anything in return. With the space recovered from the old design, we added an auto-populating profile card that would updat in real-time as the users adds their information. We hoped to encourage users to fully complete their profile by showing how their profile would be seen by hirers.
Completion Screen
Based on user feedback we realised there were some education gaps on other important elements of our product. We identified a few opportunities to improve the product onboarding at the end of the signup flow, including:
  • Congratulate and welcome the user on joining the app
  • Guide them on the next steps with two CTA buttons.
  • Educate them about the benefits of using HireVibes
Final Prototype

The Impact

During the weeks in which we were making the changes, Stacks reported that the talent pool went from 191 members to 275 members. Although this meant an increase of 44%, the user base and pool were still quite small overall.

6 months later, the talent pool reached 935 members, meaning a 3.4X increase. This is only made more significant as the crypto industry was going through a significant bear market at this time.

44%

increase during updates

3.4 X

increase 6 months later

Conclusion

In working with blockchain ecosystems, we will be able to refine our understanding of how they are using our platform and how ecosystems like these are hiring.
‍
By powering the profiles on our backend, the scaling of the client's ecosystem in turn increases our database of talent and jobs. Improving this product and onboarding more ecosystems can exponentially grow our core product as well as revenue.
‍‍
As we continue to gather feedback from clients, some potential updates in our roadmap include:

  • Enable referrals via the client's embed page
  • Add more customisable features, eg. inherit font and other design elements from the client's website page
  • Integrations such as Zapier can allow ecosystems to tap into their current workflow. Auto-posting new jobs to ecosystem Discord or Slack channels etc.

You can see the HireVibes Talent Portal live at: www.stacks.co/jobs

Updating jobseeker list to improve talent searching process

Overview

Living in Las Palmas and being a member of the public bike rental scheme "Sitycleta" for 7 months, provided me with lots of experiences of the highs and lows of using the public bike systems. With a variety of issues experienced throughout the entire user journey, I wanted to highlight and iterate on the one area that I thought could have the most impact on the overall cohesion of the system.

Scope & Constraints

Living

Research

Being

Design

Being

Validation

Being

Outcomes & Results

Being

Lessons Learned / Future Iterations

Being a foreigner in Las Palmas, my experience may be quite different to locals who equal over 90% of the population. My network is distributed heavier towards English speakers, so of the people I spoke to during my research, many were also foreigners. This is of course, not an accurate representation of the largest sector of users, and I feel this would negatively impact the validity of my results.

Implementing Smart Contract functionality into the HireVibes app

Overview

Living in Las Palmas and being a member of the public bike rental scheme "Sitycleta" for 7 months, provided me with lots of experiences of the highs and lows of using the public bike systems. With a variety of issues experienced throughout the entire user journey, I wanted to highlight and iterate on the one area that I thought could have the most impact on the overall cohesion of the system.

Scope & Constraints

Living

Research

Being

Design

Being

Validation

Being

Outcomes & Results

Being

Lessons Learned / Future Iterations

Being a foreigner in Las Palmas, my experience may be quite different to locals who equal over 90% of the population. My network is distributed heavier towards English speakers, so of the people I spoke to during my research, many were also foreigners. This is of course, not an accurate representation of the largest sector of users, and I feel this would negatively impact the validity of my results.

Building ATS integrations into the HireVibes app

Overview

Living in Las Palmas and being a member of the public bike rental scheme "Sitycleta" for 7 months, provided me with lots of experiences of the highs and lows of using the public bike systems. With a variety of issues experienced throughout the entire user journey, I wanted to highlight and iterate on the one area that I thought could have the most impact on the overall cohesion of the system.

Scope & Constraints

Living

Research

Being

Design

Being

Validation

Being

Outcomes & Results

Being

Lessons Learned / Future Iterations

Being a foreigner in Las Palmas, my experience may be quite different to locals who equal over 90% of the population. My network is distributed heavier towards English speakers, so of the people I spoke to during my research, many were also foreigners. This is of course, not an accurate representation of the largest sector of users, and I feel this would negatively impact the validity of my results.

Thanks for reading!

Want to see another one?
Talent Portal
Creating a Job Board SaaS Product

HireVibes - Smart Contracts

Implementing smart contract functionality into the HireVibes app

See Case Study