jhonatan-oliveiradev Assessing Developer Proficiency
Establish a current capability baseline from evidence, not confidence theater. The result should make demonstrated strengths, uncertainty, and missing evidence explicit enough for another method to act on.
Build the evidence inventory
Start with the target role or capability set, then collect only evidence relevant to the current-state question:
- self-reported experience and confidence;
- conceptual explanations or knowledge checks;
- code-reading and technical-reasoning observations;
- implementation or debugging performance;
- authentic project artifacts and their provenance.
Keep claims separate from observations. Missing evidence is an unknown, not a low score.
Map evidence to fixed criteria
Use the capability definitions supplied by the product, assessment blueprint, or explicit evaluation contract. For each capability:
- identify which observable criteria are supported;
- respect required evidence dimensions and blocking gates;
- determine the highest level actually demonstrated;
- record the evidence IDs or artifacts supporting that conclusion;
- retain contradictions rather than averaging them away.
Do not invent a new definition of proficiency because the available evidence is inconvenient.
Derive confidence separately
Describe confidence from evidence strength, diversity, consistency, quantity, recency, and provenance. A strong level with old or contradictory evidence may legitimately be proficient / low confidence.
Self-report alone cannot establish proficient or advanced capability. External unverified artifacts may inform the baseline, but should remain explicitly unverified until independently reproduced or checked.
Report the baseline
Return a compact diagnosis with:
- demonstrated capability state;
- confidence for each state;
- evidence used;
- unknown or weakly evidenced areas;
- contradictions or stale evidence;
- recommended reassessment targets where uncertainty matters.
Prefer named capability gaps over a synthetic overall score.
Ownership boundaries
This method owns current-state diagnosis and uncertainty. It does not sequence a roadmap, teach the missing material, redefine assessment criteria, or prioritize gaps from job-market demand. Hand those decisions to their dedicated methods.