Skip to main content
SCORE ENGINE SPECIFICATION

How DEV//REALITY Works

Every score, roast, and recommendation is calculated deterministically in application code. AI models never alter your scores.

Deterministic Score Model

Version 1.0.0

Zero AI Score Drift

When you submit a profile, DEV//REALITY fetches public data via GitHub GraphQL and PageSpeed Insights. Findings are normalized into an evidence array. Categories are weighted according to clear, published criteria:

GitHub Presentation (100 pts)

Profile Completeness15%
Repository Presentation20%
Documentation & Readability25%
Maintenance Signals15%
Technology Consistency15%
Discoverability & Pinned Repos10%

Portfolio Quality (100 pts)

Performance & Web Vitals20%
Accessibility (WCAG 2.2)15%
Search Engine Optimization15%
Security & Best Practices10%
Project Showcase & Demos25%
Mobile & Responsive Experience15%
Missing Category Normalization

If an external check fails (e.g. your website blocks automated PageSpeed checks), your score is normalized strictly over the available categories using the formula:

score = (sum(categoryScore) / sum(maxScore of available categories)) * 100

Score Interpretations

Strong Presentation

Outstanding public technical presentation with clear documentation and attention to detail.

90 – 100 pts
Solid Foundation

Good developer presence with a few areas that would benefit from polishing.

75 – 89 pts
Needs Refinement

Core projects and profile are present, but presentation weaknesses dilute first impressions.

60 – 74 pts
Major Improvements Needed

Noticeable documentation, organization, or portfolio gaps that hinder recruiter discovery.

40 – 59 pts
Time for a Rebuild

Public technical presence is sparse, outdated, or incomplete.

0 – 39 pts

Trust & Accuracy Charter

Core Evaluation Philosophy

DEV//REALITY evaluates public developer presentation: documentation quality, repository organization, portfolio quality, website quality and other publicly observable signals.

It does not measure real programming skill, system design ability, interview performance, employment readiness, professional experience, team collaboration, or private code quality.

Scores represent presentation quality, not developer worth. Low public activity does not mean low ability. Stars and commit counts are not proof of skill.