Building the Engineering Passport: A New Standard for Developer Credentials

The Credential Crisis

Your resume says you're a senior backend engineer. But what does that actually mean?

The problem with traditional credentials:

• Job titles vary wildly between companies (a "Senior Engineer" at one company is a "Junior" at another)
• Years of experience conflates growth with time served
• Degrees expire — a CS degree from 2015 says nothing about your current skills
• GitHub can be gamed with popular repos maintained by others
• LinkedIn is a collection of endorsements from people who've never seen you code

What Is an Engineering Passport?

The Engineering Passport is a portable, verifiable record of demonstrated engineering skills. It's not a score — it's a comprehensive profile built from actual evaluated work.

Core Principles

1. Evidence-based — every skill rating is backed by evaluated code submissions
2. Time-weighted — recent work counts more than old work (skills decay over 12+ months)
3. Multi-dimensional — no single score, but a profile across 10+ engineering dimensions
4. Portable — it follows you between companies, assessments, and platforms
5. Verifiable — each assessment is timestamped and signed by our evaluation system

How It Works

The passport aggregates every assessment a developer completes into a unified profile:

interface EngineeringPassport {
  overall: number;       // Weighted average across all pillars
  pillars: {             // 10 engineering dimensions
    Backend: { proficiency: number; skills: Skill[] };
    AI: { proficiency: number; skills: Skill[] };
    Cloud: { proficiency: number; skills: Skill[] };
    DevOps: { proficiency: number; skills: Skill[] };
    Leadership: { proficiency: number; skills: Skill[] };
    Testing: { proficiency: number; skills: Skill[] };
    Security: { proficiency: number; skills: Skill[] };
    Architecture: { proficiency: number; skills: Skill[] };
    Communication: { proficiency: number; skills: Skill[] };
    SystemDesign: { proficiency: number; skills: Skill[] };
  };
  confidence: {          // How much we trust this profile
    score: number;
    totalEvaluations: number;
    totalCodingHours: number;
    timeframeMonths: number;
  };
}

The Confidence Score

Single assessments can be misleading. Luck, topic familiarity, or an off day can swing a score by 15-20 points. That's why we compute a confidence score alongside every profile.

How Confidence Is Calculated

def compute_confidence(profile: Profile) -> float:
    base = 30  # Starting confidence for new users

    # More evaluations = higher confidence
    eval_score = min(profile.evaluation_count * 4, 30)

    # More coding hours = higher confidence
    hours_score = min(profile.total_coding_hours, 40)

    # Consistency = higher confidence
    consistency = 100 - (profile.score_std_dev * 5)
    consistency = max(0, min(consistency, 50))

    # Technology breadth
    breadth = min(profile.technology_count * 2, 20)

    return base + eval_score + hours_score + consistency + breadth

Skill Decay and Freshness

A verified React skill from 18 months ago is worth less than a fresh verification from last month. Our skill decay model accounts for this:

Freshness	Time Since Last Verified	Decay Multiplier
Fresh	< 6 months	1.0× (full value)
Aging	6-12 months	0.8×
Stale	> 12 months	0.5×

This creates a natural incentive for developers to regularly update their passport with new assessments, which benefits both the developer (higher scores) and the platform (engagement).

Engineering DNA

Beyond scores, we capture a developer's engineering DNA — their natural stylistic tendencies:

• Functional vs Object-Oriented — which paradigm comes naturally?
• Optimization First vs Readable Code — where's the trade-off?
• Risk-Taking vs Conservative — how experimental are their solutions?
• Documentation Heavy vs Code-As-Documentation — communication style?

Think of it as Spotify Wrapped for engineers — a personality profile that helps companies understand not just what you know, but how you think.

Growth Graph

The passport isn't static. Every new assessment updates the profile, and developers can see their growth over time:

Score
^
|                          ● (4.7)
|                    ● (4.4)
|              ● (3.8)
|        ● (3.4)
|  ● (3.2)
+-------------------------------->
  Jan   Mar   Jul   Oct   Dec

This creates a powerful retention loop — developers want to keep improving their passport, which means they keep using the platform.

For Companies

The passport transforms how companies evaluate candidates:

Before

• Review 200 resumes for 1 opening
• 40 phone screens
• 15 technical interviews
• 2-3 months to hire

After

• Search passport database by verified skills
• 10 candidates with 85%+ confidence in exactly the skills needed
• Review actual code evidence for each
• 2-3 weeks to hire

The Future

We're building toward:

• Third-party verification — GitHub, LinkedIn, and university credentials linked to the passport
• Company endorsements — verified work history with skill ratings from past employers
• Open standard — passport data exportable and portable to any platform
• AI-powered matching — connect candidates to roles based on passport data, not keywords

Your resume says what you've done. Your passport shows what you can do. The difference is everything.

---

Build your Engineering Passport. Start your first assessment →