For talents
You are more than a keyword list
You have done things a job ad never names. A recruiter here reads what you actually did, what backs each claim, and how close your last role is to the posted one. The right role stops depending on whether you guessed the right words.
One profile. Every team that reads it sees the reasoning.
Your skills
Grouped the way hiring reads them
Skills come grouped and levelled. Each skill can point at the work behind it. The recording walks through adding one.
Your profile, from the other side
A claimed skill should have evidence supporting it, and that has never been easier
This is your profile as a recruiter reads it. Every skill opens into the reason it counts. The reason is either a relation to what the team asked for, or the places you have used it.
Candidate's relevant skills
- Micro Frontends
- Frontend Development
- HTML
- Node.js
They asked for React. You never wrote React. Four skills you did write lean toward React. The requirement is part-covered, and the recruiter can see by what.
Mara Lindqvist
Staff Engineer · Stockholm · open to Platform roles
Frontend
3 skillsPlatform & tooling
4 skillsDocker
"Our build and deploy images, from CI through to production, for four years."
- Used in project pgslice-rs
- Using it now at Nordbank AS, as Staff Engineer
- Used at Nordbank AS until 2024, as Site Reliability Engineer
- Certified by CNCF — CKA
Four places you used Docker, pulled from entries already on your profile. The chip carries the count, so the evidence shows on the profile before anyone opens it.
Link a skill to the job you hold now, and the skill reads as in use now. The dates come from the entry you linked, so nobody has to trust a self-reported year.
What you keep control of
Your profile, on your terms
You decide what people can see about you
The public profile, the contact details, being open to work, being recommended to teams, and which talent pools hold you are each a choice you make and can change.
Keep several CVs and pick one per job post
Your CVs live in a library instead of overwriting each other. Send the platform version to one post and the tailored version to the next.
Build a profile with more than jobs on it
Desired roles, projects, education, certificates with their credential number and link, languages, and links of your own. Each entry can back a skill, so the profile and the evidence grow together.
One application can lead to a different job
A team can keep you in their talent pool after a no. You show up on their next post, with the reading already done, and you can leave the pool whenever you want.
Make your profile stand out
Tell the story behind your experience
A story lets you talk about an experience in your own words. What went right, what went wrong, and how you dealt with it. It shows your skills not as just a list of words, but rather validated skills within context and evidence.
My responsibilities
Say what you were responsible for and who you worked with. A job title says the rank, and this says the work.
What I'm proud of
Name the thing that went well and what changed because of it. The skills you pick here carry the story with them.
Failures and lessons I learned from them
Say what went wrong and what you would do differently now. A recruiter reads this as judgement, which no skill list can show.
Get started
Post a role and read the pile with the reasons already written. Or keep one profile and be found for the work you have actually done.