The evidence behind a candidate match.
Help people understand the reasons behind a match.
Where this work fits
A score can suggest that someone fits a role without explaining why. The person reviewing it needs to see which requirement is supported, which conflicts with the profile, and which cannot yet be answered.
I brought matching factors and their reasons into candidate and job views. People could inspect supporting experience and distinguish a match from a mismatch or an unanswered question. Shared components kept those meanings consistent across the interface.
Open the reasoning behind a result
From a verdict to the evidence.
Built an inventory API and background jobs to sync product records.
Experience 01 + 02MatchRelevant work supports this requirement.
Each factor connects a job requirement to the candidate’s experience.
A job requirement is paired with the experience that supports it. Other factors reveal a mismatch or a question that still needs an answer.
Missing evidence is different from a mismatch.
A simpler display would have been misleading if it flattened every factor into yes or no. The work preserved match, mismatch, and unknown states, then let people inspect the evidence without making them read everything at once.
The skills behind the work
- Vue / Nuxt
- Connect backend behavior with a usable, responsive product interface.
- API contracts
- Keep the meaning and format of information consistent between communicating systems.
- Evidence attribution
- Connect a claim or skill with the experience that supports it.
People could move from a verdict to the reason and the experience behind it. The interface made uncertainty visible and reduced conflicting presentations of the same candidate.