Every Skill. Every Certification. One Place.
Build one shared catalogue of engineering skills, from languages and frameworks to cloud platforms. Record who holds each one and at what level, and keep certification dates on file. When a project needs a Kubernetes expert, find them in seconds.
Illustration. People, skills and dates are examples. Your organisation builds its own catalogue.
From Catalogue to the Right Person.
Four steps to a clear picture of your engineering team's skills.
Choose what you track
Switch on graded skills, qualifications, or both, for your organisation.
Build your catalogue
Add skills in Swedish and English. Micronomy spots near-duplicates as you type, so the catalogue stays clean.
Record who holds what
Engineers add their own skills, and leads update the team's, with a level or the dates a certification is valid.
Find the right person
Look up everyone who holds a skill, filtered by minimum level.
Skills Your Whole Organisation Speaks.
Available today.
One shared catalogue
- Swedish and EnglishEach skill has a name in each language, and everyone sees it in their own.
- Other names welcomeAdd the words engineers actually use, like k8s or dotnet, so searches find the right skill.
- No duplicatesClose matches are suggested before a new skill is created.
- Organised with tagsGroup skills with your own tags, such as Backend, Cloud or Security, and retire old ones without losing who held them.
Skills and qualifications
- Graded skillsRecord how strong each person is, from level 1 to level 5.
- Dated certificationsKeep the dates each cloud, security or testing certification is valid, in your organisation's time zone.
- Use what fitsTrack graded skills, qualifications or both. At least one always stays on.
Find and manage
- Who holds this skill?See everyone with a skill, filtered by minimum level.
- Self-serviceStaff keep their own skills up to date. Managers can update anyone's.
- Clear responsibilitiesAdmins curate the catalogue, managers manage the team, everyone manages their own.
- Always currentCatalogue and profile changes appear for everyone straight away.
On the Roadmap.
Skills-aware planning
Match assignments to the skills and valid certifications your engineers hold, as you plan the week.
Know your team. Find the right person.
Common Questions.
What's the difference between a skill and a qualification?
A skill is graded: you record how strong someone is, from level 1 to 5, such as C# or distributed systems. A qualification is something you either hold or don't, such as an Azure or Kubernetes certification, with the dates it's valid.
Does Micronomy come with a list of skills?
No. Every organisation builds its own catalogue, in its own words, so it matches how you actually work.
What if someone adds a skill that already exists?
Micronomy suggests close matches as they type, in Swedish and English. They can pick the existing skill, add their word as an alternative name, or create a new one.
Can staff update their own skills?
Yes. Everyone can manage their own skills. Updating other people's needs the manager feature, and changing the catalogue itself is for admins.
What happens when we retire a skill?
It stops being offered for new use, but the record of who held it is kept.
See Skills in Action.
Book a demo and we'll build the start of your engineering skills catalogue with you.