UX/UI Design · Savvy Match · UX/UI design for a mobile app
From idea to mobile app for skills-based job matching
Two founders with extensive recruitment experience wanted to create a new way for candidates and employers to find each other. Their vision was to give skills, potential and cultural fit greater weight than bias related to factors such as age, gender and ethnicity.
As product designer, I worked closely with the founders to turn the idea into a mobile app for iOS and Android. I researched similar services, mapped the complete journey between candidates and employers, and helped prioritise what the first version needed to include.
I then designed the candidate experience, from setting match criteria and discovering relevant jobs to expressing interest, tailoring a profile and communicating with an employer.
I created wireframes, interactive prototypes, finished UX/UI designs and a design system for both platforms, supporting dark and light mode. I also worked closely with the developers, providing specifications and resolving design questions during implementation.
The outcome was a connected set of designs that the founders and developers could use to build and launch the product.
- My role
- Product Designer
- Year
- 2021–2022
- Industry
- Recruitment
- Company
- Savvy Match
- Team
- The two founders and the developers
- Platform
- Mobile app, iOS and Android
The short version
The problem
The founders wanted to change a recruitment process where candidates could be overlooked because of bias rather than assessed on their skills and potential.
But the product idea needed to become a practical service for both job seekers and employers, from the first match to communication and feedback.
The challenge was to create a simple mobile experience without losing the information and steps required for a relevant match.
My contribution
I mapped the complete journey for candidates and employers, researched matching services and helped the founders define the first version through user stories and shared MVP prioritisation.
I was responsible for the interaction design, candidate journeys and finished UX/UI designs for iOS and Android.
I also built the design system for dark and light mode and prepared prototypes and specifications for the developers.
The result
We moved from an early product idea to a connected, development-ready app design for skills-based job matching.
The founders and developers received prioritised user flows, interactive prototypes, finished screens for iOS and Android and a design system to build on.
From an idea for fairer recruitment to a product
The two founders behind Savvy Match had spent many years working in recruitment. They had seen candidates overlooked because of factors such as gender, age and ethnicity, even when they had the skills needed for a role.
They wanted to create a different way for candidates and employers to find each other, giving greater weight to skills, potential and cultural fit.
The vision was clear, but the product itself still needed to take shape.
Two sides that needed to work together
Candidates need to describe their skills, what they’re looking for and what matters to them in their next job.
Employers need to describe the role and its requirements, find relevant candidates and take conversations forward.
For matching to work, we needed to understand both sides of the service and what happened after someone expressed interest.
It wasn’t enough to create an app where candidates browsed jobs. Employers also needed to respond, communicate and close the recruitment.
Turning recruitment expertise into product design
The founders brought their recruitment experience and a clear understanding of the problems they wanted to address.
My role was to turn that knowledge into a connected digital experience.
I started with desk research into matching platforms and approaches to reducing bias in recruitment. Combined with the founders’ experience, this gave us a shared starting point for the tasks and decisions the service needed to support.
I then mapped the candidate and employer journeys, created early wireframes and helped define what the first version needed to include.
We needed a first version that worked from beginning to end, while leaving room for the product to evolve. That meant starting with the service journeys and decisions, rather than individual mobile screens.
The challenge was to turn an ambitious product idea into something concrete, understandable and ready to develop, without losing what made matching relevant for both user groups.
Shaping the complete service with the founders
To make the product idea concrete, we needed to understand the entire journey, from a candidate creating their profile to an employer filling a role.
I mapped both sides as a seven-step user story map. Each step described what people needed to do and why.
Together with the founders, I used the map to prioritise what had to work in the first release and what could wait.
-
Candidate
Get started
- Open the app
- Set match criteria
- Build the profile
As a candidate, I want to say where and how I want to work, so that I only see jobs that fit me.
Import the profile from LinkedIn
-
Employer
Publish a job
- Describe the job
- Set the requirements
- Show the workplace
As an employer, I want to set clear requirements, so that I meet candidates who match them.
Record a video from the workplace in the app
-
Candidate
Browse today’s jobs
- Swipe between jobs
- Read the card
- See why I match
As a candidate, I want to compare jobs before I decide, so that I don’t say no by mistake.
A notice when a strong match appears
-
Candidate
Show interest
- Ask a question
- Adjust the profile for this job
- Send
As a candidate, I want to choose what the company sees, so that I can lift what matters for this job.
An anonymous profile until the employer replies
-
Employer
Review interest
- See matched candidates
- Read the profile
- Reply
As an employer, I want to see how each candidate meets the requirements, so that I can decide quickly and fairly.
Compare candidates side by side
-
Both
Talk
- Chat in the job
- Suggest a time
- Follow the status
As a candidate, I want to see what is waiting for me, so that I never miss a reply.
Book a meeting or a trial shift in the app
-
Employer
Close the job
- Fill the role
- Tell other candidates
- Move to ended
As a candidate, I want to know when a job is filled, so that I can move on.
Feedback to candidates who weren’t chosen
A match is the beginning, not the end
The candidate journey starts with describing where and how they want to work and building a profile.
At the same time, employers need to describe a role and the skills they’re looking for.
Candidates then need to discover relevant jobs, understand why they match and decide whether to express interest.
But the service doesn’t end there.
Employers need to review interested candidates, read their profiles and respond. Both sides need to continue the conversation, follow its status and know when a role has been filled.
It became clear that successful matching required a complete journey, not just a way to discover jobs.
Defining the first complete version
We drew an MVP line on the story map.
Above the line, we placed everything needed for the service to work from beginning to end: from match criteria and published jobs to expressions of interest, employer responses, conversations and closing a role.
Below it, we kept ideas that could improve the experience later but weren’t essential from the start.
These included importing a profile from LinkedIn, notifications for particularly strong matches, comparing candidates side by side and booking meetings in the app.
Prioritising together, designing for the whole service
The founders brought their recruitment knowledge and understanding of what both candidates and employers needed.
I contributed research, user journeys, user stories and early wireframes that made the ideas easier to discuss and prioritise.
Once we’d agreed on the scope of the first version, I could design the candidate app with a clear understanding of what needed to happen on the employer side.
This shaped how candidates expressed interest, what information they could share and how replies and statuses appeared in the app.
The user story map helped us connect both sides of the service and prioritise a complete initial journey over extra features. It shows the planned MVP, not a verified list of exactly what launched.
Helping candidates compare before deciding
Savvy Match needed to make relevant jobs easy to discover. But I didn’t want it to become an app where people quickly swiped past opportunities without understanding them.
The design needed to make reading and comparing just as easy as moving on.
Swipe between jobs, scroll to read
I designed each job as a card with two different movements.
Users swipe horizontally to browse jobs and scroll within a card to read more about a role.
This keeps discovery quick without reducing a job ad to a title and a handful of details.
Show why a job matches
A prominent number, such as 3/5, shows how many of the role’s stated requirements the candidate meets according to the matching system.
Anyone wanting to understand the match can open a view showing the individual requirements.
The number isn’t a prediction of getting hired or an objective measure of a candidate’s worth. It helps users see which requirements match.
Three clear choices
I placed three labelled buttons beneath the card: Not for me, Save and Interested.
They distinguish between passing on a job, returning to it later and taking the next step towards an employer.
After Not for me, an undo option appears. This reduces the consequence of an accidental choice and makes it easier to continue browsing.
I wanted candidates to make a deliberate decision rather than having to interpret gestures or unfamiliar symbols.
Control over what employers see
Choosing Interested opens a view where the candidate can ask a question and review the profile the employer will receive.
The profile can be tailored for that specific role. Candidates can choose which experience to highlight and, for example, change their introduction video.
Only then do they send their expression of interest.
A confirmation explains what has happened and what they can expect next.
One decision at a time
The match number helps candidates understand relevance. The card provides space to read. The three buttons make the choices clear. And reviewing the profile gives people control before sharing their information.
Discovering a job should be quick. Expressing interest should be a considered choice.
From the first match to a conversation
The working prototype shows the candidate journey through Savvy Match, from getting started and discovering jobs to expressing interest and communicating with an employer.
The screenshots show a later iOS environment in the prototype, not an exact record of the app as implemented during the project period. Visitors can also switch to Android and between dark and light mode. The companies and people in the prototype are fictional.
Getting started and today’s jobs
Expressing interest
My jobs
Settings and match criteria
Try the candidate app
The prototype lets you browse today’s jobs, explore why they match, express interest and follow conversations in My jobs.
You can switch between iOS and Android, and between dark and light mode. The prototype is in Swedish and works on both desktop and mobile.
A design system for two platforms
I built the design system alongside the user flows.
The aim was to create a connected app for both iOS and Android, giving developers a foundation they could build on without designing every new screen from scratch.
One identity in dark and light
I developed a colour palette for dark and light mode, using lavender and deep navy as key colours for actions and match information.
A soft glow behind the job card helps give the app its own visual character.
I used Poppins as the shared typeface and defined a type scale for headings, body copy and the prominent match numbers.
Components for the important decisions
The design system includes the three decision buttons, match indicators, chips, statuses, tabs, list rows and switches.
I also designed components for brief feedback, such as undoing an action, and the app’s floating tab bar.
The components were designed for both dark and light mode.
A shared experience adapted to each platform
iOS and Android handle some system elements and interactions differently.
I kept the core journeys and visual identity consistent, while adapting details to each platform where needed.
This gave the app a connected experience without ignoring the differences between the platforms.
Designs the developers could build from
I prepared specifications, interactive prototypes and design system documentation.
I worked closely with the developers during implementation, answering questions and clarifying decisions as the designs were translated into code.
My deliverables were a connected, development-ready candidate app and a design system that could support further development.
What I took with me
This project gave me the opportunity to work closely with two founders who had a clear vision and deep knowledge of recruitment.
My role was to make their idea usable: understand both sides of matching, map the complete journey, prioritise a first version and design the interactions that brought it together.
One thing I particularly took away was the importance of looking beyond the first match. For a service to work, people need to take the next step, receive replies and understand what’s happening.
Building the design system alongside the app was valuable too. It helped me keep the details consistent and give developers clear guidance even as the product continued to evolve.
For me, Savvy Match became a concrete example of taking an early product idea through to a well-developed mobile experience by moving between the bigger picture and detailed design decisions.
“Mikaela was a rock who helped us get the flow in place and work out how the app should be designed, so that we could then build and launch it.”
The other side: Savvy Match for companies
The app only works if employers answer. I also designed the employer side, from a recruitment need to closing the job, and rebuilt it as a working prototype.
