Privacy note: This is a composite account based on real patterns we see across teams. The name and photograph are illustrative only and do not depict any actual individual. Identifying details have been changed to protect privacy.
Daniel was a solid engineer who shipped reliable work without fuss. But the moments he genuinely came alive were different: explaining a tricky concept to a new joiner, writing the internal guide everyone bookmarked, answering the “how does this actually work?” questions in chat.
Quietly carrying the knowledge
Every team has someone whose explanations make everyone faster. That was Daniel. His code was good; his teaching was exceptional. Yet his role measured only the first, and the second — arguably his bigger contribution — was invisible to every review.
What Role Fit surfaced
Out of curiosity, Daniel ran Role Fit in the “for me” mode. The behavioural profile highlighted strong communication and a deep streak of curiosity. Patterns in his work showed much of his real impact came from enabling others rather than from his own commits. The analysis suggested developer advocacy as a direction — and pointed to the exact signals behind the suggestion, so it felt earned rather than assigned.
A conversation, not a verdict
The aim wasn’t to tell Daniel he was a mediocre engineer — he wasn’t. It was to show that a major strength was being spent in the margins. Role Fit offered supportive, conservative guidance and a few honest questions for his manager. The one that landed: “What do colleagues thank you for most?” The answer wasn’t his code. It was his explanations.
The move
Daniel moved into a developer advocacy role: writing documentation, building tutorials, running internal sessions, and representing the engineering team to a wider audience. The skill he had been giving away for free became the centre of his job.
The result
Documentation improved, onboarding got faster, and the guides Daniel produced kept paying back his old team long after he’d moved. His fit rose from “moderate” to “strong”, and the company turned a hidden strength into a visible, compounding asset.
What managers can take from this
The thing people thank a colleague for is often the role they should be doing. Role Fit makes that visible — whether you run it for yourself to understand your own edge, or for a team member to help them grow into theirs.