Progress & Signal Score
Signal Score Explained
Learn how code quality, debugging, and collaboration contribute to your score.
Signal Score is your verifiable evidence of engineering capability, visible to recruiters.
Capability Signal Dashboard
Open Account → Portfolio (`/account/portfolio`) for the live Capability Signal Dashboard: five categories (Problem Solving, Code Quality, System Design, Debugging Velocity, Collaboration Impact), an overall LIVE score, 30-day trend, and sparkline.
Five data sources
Your dashboard ingests telemetry from: code commits (lab submissions for everyone; optional GitHub webhooks if you link a repo), debug sessions (sandbox runs), peer reviews, standup participation (Jitsi attendance), and AI collaboration (hints, Shadow Pair, lab review).
GitHub linking (optional)
You do not need GitHub to build a Signal Score — completing labs, standups, and peer review is enough. If you use GitHub, add your username during onboarding (or a `github.com/you` portfolio URL) and optionally point a repository webhook at `POST /api/github/webhook` so pushes add extra commit telemetry.
Score Components
Legacy Signal Score dimensions (code quality, debugging speed, AI collaboration, completion rate, peer review quality, Git hygiene, communication) still feed recruiter search. The dashboard blends those snapshots with fresh telemetry boosts over a rolling 30-day window.
Improving Your Score
Focus on writing clean code, solving problems efficiently, participating in standups, and using AI tools thoughtfully.
Recruiter View
Recruiters see an anonymized version of your profile, filtered by Signal Score thresholds.