UX/UI Design · TRR · Sole designer in a product team, from research to development-ready
Part of Sök jobb at TRR: see how the parts connectMaking the match profile easier to discover, create and keep up to date
At TRR, job seekers can create a match profile to receive relevant job suggestions and become visible to employers. But only three in ten users had one. Many didn’t know the feature existed, others weren’t sure what to enter, and existing profiles were rarely updated.
As the sole UX designer in the product team, I was responsible for redesigning the whole experience – from discovering the profile to creating, using and updating it. My work covered research and analysis, user-tested prototypes, completed interfaces for desktop and mobile, and design specifications that developers used to build the solution.
During the initiative, the share of users with a match profile increased from 30 to 50 percent.
- My role
- Sole designer, senior UX
- Year
- 2024
- Industry
- Career transition and working-life services
- Company
- TRR
- Scope
- 3 months
- Platform
- Web, desktop and mobile
The short version
The problem
Many job seekers never discovered the match profile. Those who found it struggled to choose relevant skills and roles, while existing profiles were rarely kept up to date.
The challenge was to make the profile easier to discover, complete and return to, without losing the information needed for relevant job matching.
What I did
I led and carried out the design work as the sole UX designer in a team with a product owner and developers.
Through interviews, surveys and behavioural data, I mapped the user journey and identified where people lost understanding or motivation.
I redesigned the entry point on the homepage, created a guided flow with personal suggestions, made job matches easier to understand and designed ways to keep the profile current. I took the work through to development-ready design and reviewed the implementation with the developers.
The result
The share of users with a match profile increased from 30 to 50 percent, and the share of complete profiles rose from 80 to 93 percent.
Those are increases of 20 and 13 percentage points respectively.
The changes were delivered as a team effort, and the figures show how adoption and completion developed during the initiative. They don’t establish the effect of any single design decision.
My responsibilities as the sole UX designer
Research and analysis
I conducted interviews and surveys, analysed behavioural data and mapped the user journey.
Flow and interaction design
I designed the full experience, from discovering and creating the profile to using and updating it.
Desktop and mobile UI
I created completed screens in Figma using components from TRR’s existing design system.
States and edge cases
I designed different form states, including with and without suggestions, errors and returning to edit a profile.
Development-ready handover
I wrote design specifications and carried out design reviews with developers during implementation.
Design and development collaboration
I worked closely with the product owner and developers to balance user needs, product goals and technical constraints.
Why people weren’t using the profile
At the start of the project, only 30 percent of users of TRR’s digital services had a match profile.
To understand why, I conducted user interviews and surveys, analysed behavioural data and mapped the user journey. I wanted to understand what prevented people from creating a profile, but also why many didn’t return to update it.
The research revealed three connected problems.
- Many people never discovered the profileThe match profile was tucked away under My settings, where people wouldn’t necessarily look for help finding a job.
Many users therefore didn’t know the feature existed or what they could gain from it. - Choosing the right information was difficultPeople who found the profile were often unsure which skills, roles and other matching criteria to enter.
It wasn’t sufficiently clear how that information would be used or why completing the profile was worth the effort. - Profiles became outdatedExperience, skills and career goals change over time, but many users rarely returned to update their profiles.
This meant matching could rely on incomplete or outdated information, reducing the chances of relevant job suggestions and being discovered by employers.
The design challenge
I realised that simplifying the form alone wouldn’t be enough.
We needed to treat the match profile as part of a longer journey: users should understand its value, get help creating it and have an easy way to return when something changes.
At the same time, the profile still needed enough information for relevant matching, and users needed to stay in control of what they included and whether they shared it with employers.
That became the starting point for my design work.
Three decisions that shaped the experience
The research showed that problems appeared at different moments: before users discovered the profile, while creating it and later, when their information needed updating.
I therefore focused on the whole experience, not just the form.
- Make the profile visible and explain its valueI moved the match profile from My settings to a prominent card on the homepage.
The card explains what the profile is for and offers a clear way to get started. Once the profile has been created, the same card displays matched jobs instead.
This gives the homepage a useful role both before and after someone creates their profile. - Offer personal suggestions while keeping users in controlMany people were unsure which skills and roles to enter.
I designed a flow where users could add a CV or LinkedIn link. Skill suggestions come from the CV, while selected skills inform suggestions for job roles. Nothing is added automatically.
Users can review, select and remove suggestions, keeping control over what their profile contains. - Show more potential opportunities and explain the matchesExact matching can miss jobs that are close to someone’s skills and goals.
The matching was therefore expanded to include adjacent roles. I designed job cards that explain why each opportunity was suggested, for example through the role, location and matching skills.
Users can also mark suggestions as not relevant and undo that choice.
One connected experience
These three decisions shaped a journey that begins on the homepage and continues after the profile is created. The next step was designing how it would work in practice.
From first visit to an up-to-date profile
The match profile isn’t a form users complete once and leave behind.
I designed a journey that starts on the homepage, continues through five steps to create the profile and then lets users explore job matches, update their details and confirm that the profile is still accurate.
The end-to-end flow
The nine-step diagram shows how the job seeker, the service, and employers and advisors interact.
Users discover the profile, can add a CV or LinkedIn link, receive suggestions for skills and roles, and complete their matching criteria. The service then presents both direct and adjacent job matches.
After a few months, users can confirm or update their profile.
- Job seekerSees the card on the start pageWhat a profile gives, with one button to start.
- Job seekerAdds a CV or LinkedInIt can be skipped, and the start page reminds the user later.
- The serviceSuggests skills and rolesTaken from the CV, so nobody starts from an empty page.
- Job seekerCreates the profile in five stepsSkills, roles, location and ways of working, and employment type and scope. A separate choice about sharing the profile with employers follows.
- The serviceMatches jobsDirect and adjacent matches, each with the reason it was suggested.
- Job seekerReviews matched jobsSees why each job matches. Not relevant hides a job, with Undo.
- Employers and advisorsFind the profileA shared profile is visible to employers, and advisors use profiles to suggest candidates.
- The serviceReminds after a few monthsThe start page asks if the profile is still right.
- Job seekerConfirms or updatesOne click confirms it, or each section has its own Change link.
In the flow I designedOutside the flow I designed
I designed the user journey and interface. Step 7, where employers and advisors use shared profiles, sits outside the flow I designed.
Discover the profile
Create the profile
Use and update the profile
Designing for different states
I also created detailed specifications for how the steps should work in different situations.
The skills step was drawn in five states: with suggestions, without suggestions, with selections made, with an error and when returning to edit.
This gave the developers a concrete reference for situations beyond the ideal flow.
The decisions behind the flow
The three problems from the research guided the design throughout: users needed to discover the profile, understand how to complete it and have a reason to keep it up to date.
The most useful solutions often came from small decisions made at the right moment.
Make it clear why someone should start
- Put the profile where users already areInstead of leaving the profile under My settings, I gave it a prominent place on the homepage.
The card explains its value before asking for any information. It also shows what the process involves, helping users understand the effort required. - Let users continue without a CVA CV or LinkedIn link can provide a useful starting point, but not everyone has the information available.
I made the first step optional. The homepage can later show what’s missing and offer a way to complete the profile.
Guide without taking over
- Start with information users already haveSuggestions from the CV help users get started with skills and roles. Selected skills also inform suggestions for relevant job roles.
But suggestions aren’t added automatically. Users decide what belongs in their profile. - Reuse familiar interaction patternsSkills, roles and locations require different information, but they don’t need completely different interfaces.
I reused search and selectable options so users could learn one pattern and recognise it in the following steps. - Show progressI divided profile creation into five steps, combining a progress indicator with text about what comes next. Users can see how far they’ve come without having to guess what’s left.
Make job matching understandable
- Explain why each job is suggestedEvery job card shows which parts of the user’s profile match the listing. This also applies to adjacent opportunities that don’t meet every criterion exactly.
Users can make their own judgement about whether a suggestion is relevant. - Let users dismiss suggestions and undoNot every job suggestion will be suitable.
I added Not relevant directly to the job card, with an undo option. Users can adjust their list without returning to edit the whole profile.
Keep users in control afterwards
- Make sharing a separate decisionSharing a profile with employers is a personal choice.
I placed the question after profile creation and explained what sharing means. Users can choose not to share and change their decision later. - Remind users when there’s a reasonI tied the reminder to when the profile was last updated. Users can confirm that their information is still correct or edit individual sections without starting again.
UI design for desktop and mobile
The match profile needed to feel like a natural part of TRR’s other digital services, despite asking users to make quite a few choices.
I worked from TRR’s design system, using clear hierarchy, familiar components and interaction states that support users throughout the flow.
An interface that feels familiar
- Consistent with the rest of TRRI used existing components, purple for actions, Raleway for headings and Open Sans for body text.
This made the match profile feel connected to the wider service and allowed developers to reuse components. - One clear primary action per stepNext uses a filled purple button, while Back is less prominent and Skip appears as a text button.
The way forward is easy to identify without removing other choices. - Progress communicated in several waysA five-part progress indicator is accompanied by text such as Step 2 of 5 and a description of the next step.
Progress is communicated both visually and through text, an important consideration for accessibility.
Distinguish information from choices
- Suggestions and selections look differentSuggested skills have an outline and a plus icon. Selected skills have a filled background and a remove icon.
Suggestions from the CV appear in a separate panel, making it clear what the service is proposing and what the user has selected. - Use colour alongside text and shapeTeal surfaces highlight supporting information, such as suggestions from the CV. Purple is used for buttons and interactive elements.
I combined colour with text, icons and distinct states so meaning didn’t depend on colour alone. - Explain things where questions ariseWhen a choice needs context, such as considering work in Denmark or Norway, a short explanation appears beside the question.
Users don’t need to leave the flow to find out what’s being asked.
The same journey on mobile
I designed the match profile for desktop and mobile, keeping the content and interactions consistent while adapting their presentation.
- HomepageThe matched-jobs card appears early and provides a clear route to the profile.
- SkillsCV suggestions, search and selected skills appear in one column. The progress indicator stays at the top.
- ProfileMatched jobs and activities are followed by the profile sections, each with its own Change link.
- Matched jobsFilters and job cards adapt to a single column. Each card explains why the job was suggested.
Buttons use the available width where appropriate, selectable options wrap across lines and the sharing question opens in a bottom sheet.
Accessibility in the design
I worked with short instructions, consistent labels, visible states and feedback that didn’t rely on colour alone.
I also designed error and editing states and specified how users would understand what was complete and what remained.
These were important parts of the design and the handover to developers.
Results and learnings
The changes were delivered by the product team during the match-profile initiative. We could see two clear improvements in usage.
- 30 → 50%More people created a profile. The share of users with a match profile increased from 30 to 50 percent, a rise of 20 percentage points.
- 80 → 93%More profiles were complete. The share of complete profiles increased from 80 to 93 percent, a rise of 13 percentage points.
What changed
For users, the match profile became more visible on the homepage and gained a guided flow with personal suggestions. Job matching expanded to include adjacent roles, and each suggestion came with a clearer explanation.
It also became easier to return, edit the profile and confirm that the information was still correct.
Expanding matching to adjacent roles increased the number of jobs that could be suggested.
What the work gave the team
The research gave us a shared understanding of why users weren’t creating or updating profiles.
Prototypes and design specifications helped us discuss priorities and build the solution. I stayed involved during implementation, adapting the design with developers when technical constraints required it.
The figures show the change during the match-profile initiative, rather than the impact of any individual design decision.
What I took with me
This project reminded me that an important feature has little value if people can’t find it or understand why they should use it.
Combining interviews and surveys with behavioural data helped me distinguish three different problems: people weren’t discovering the profile, were unsure how to complete it and rarely came back to update it.
That changed how I approached the design. Rather than focusing only on the form, I worked on the experience before, during and after profile creation.
I also took away the importance of offering guidance without taking decisions away from users. Suggestions from a CV can make getting started easier, but people should choose their own skills, roles and whether to share their profile.
For me, this was a clear example of the value of combining research, product understanding and detailed interaction design — then following how usage changes.