Teams · Technology teams
Evidence from code, tickets and delivery tools
Pull requests, reviews and tickets become evidence, and technical skills are defined per job role by your own engineers.

What matters to you
From the delivery tools
GitHub, Azure DevOps, Jira and the rest of the stack.
Technical skills per job role
Maintained by your own people.
Reviews count
The conversation around the work is evidence too.
How it works: A cycle, through your eyes
- 1
Connect the stack
Twelve months on day one.
Work-history import - 2
Define technical skills
Per job role.
Performance framework - 3
See them develop
Feedback Observations per skill.
Feedback Observations
Security and privacy
- Infrastructure is in the EU.
- Nextdot is ISO 27001 certified.
- No model is trained on customer data.
- Imported work is anonymous until claimed, and identities of people not yet invited are hidden from admins.
FAQ: Questions, answered
More in the FAQ.
Which engineering tools are supported?
GitHub, GitLab, Bitbucket, Azure DevOps, Gerrit, Jira, Linear and more. See Integrations.
Where to next
- FeatureWork-history importTwelve months of work on record on day one.
- FeaturePerformance frameworkYour own framework, not ours.
- FeatureFeedback ObservationsSee how colleagues see your skills, and how your feedback helps others.
- Use caseSkills visibilitySee how key and technical skills show up across teams and job roles.
- Use caseRun this year's review cycleRun the cycle that is about to start on twelve months of real evidence.
The best way to see it is on your own data
Happy to show it running on one team's tools — twelve months of work, your framework, your people.