The Framework
12 dimensions. Every one scored with evidence.
The dimensions are calibrated to the role brief, not a generic developer scorecard. The 12 are weighted differently depending on whether you’re hiring a founding engineer, a senior IC, or a team lead.
S1
App Ownership & Scale
Have they owned a product at production scale? User numbers, reliability ownership, and platform impact, not just feature contribution.
S2
Architecture & System Design
Evidence of meaningful design decisions, not architectural familiarity. We look for choices made under real constraints.
S3
Core Stack Mastery
Depth in the specific stack the role requires, not headline familiarity. Evidence in public work, patents, or verifiable deliverables.
S4
Product Thinking & UX Impact
Does the candidate think beyond the ticket? We assess whether their past work shows product intuition or purely execution instinct.
S5
Performance & Reliability
Crash reduction, latency improvement, and uptime ownership: measurable reliability signals from their actual work history, not self-reported claims.
S6
Engineering Rigour
Testing culture, code review ownership, documentation standards. Evidence of habits that separate engineers who scale teams from those who slow them down.
S7
Startup & Ambiguity Tolerance
Zero-to-one versus scale experience. Excellent engineers from large, stable companies frequently struggle in founding or early-stage environments.
S8
Hands-On Execution Gate
The hard pass/fail gate. Can they build the thing? Evidence of shipped, production-grade work. GATE PASSED or GATE FAILED, no grey area. Candidates who fail are not presented.
Required
S9
Mentorship & Team Building
For senior roles, evidence of mentorship, code review culture, and the ability to raise a team’s floor, not just their own ceiling.
S10
CI/CD & DevOps Maturity
Pipeline ownership, deployment cadence, infrastructure-as-code familiarity. Weighted higher for roles where production reliability is directly in-scope.
S11
Domain Relevance
How well does the candidate’s domain background map to the target? Domain gaps are named, impact-rated, and addressed in coaching notes.
S12
Public Evidence & Portfolio
Verifiable external evidence: patents, open-source contributions, published apps, conference talks. We check what can be checked.