DevCard Concepts

Key terms you'll see throughout DevCard.

Fit Score
How well a candidate's skills, experience, and cognitive strengths align with a job's requirements. Uses structured ontology mapping, not keyword matching.
Confidence Score
How much verified evidence supports a fit score. More project details, linked accounts, and peer verification increase confidence.
Transferability
The ability for skills in one technology to apply to related technologies. For example, React experience transfers to Vue because they share component architecture patterns.
Cognitive Archetype
A developer's dominant problem-solving style, derived from patterns in their work history. Not a personality test — it reflects how they approach technical challenges.
Ontology
DevCard's structured knowledge graph of technologies, skills, and their relationships. It enables matching beyond keywords by understanding how skills connect and transfer.

In the AI era, code is cheap.
Responsibility is not.

DevCard is for developers who carry real responsibility and want proof of it.

Build Your Record See how it works

Hiring for your team?

See how DevCard works for hiring teams

See it in action

This is Kyle's resume. Here's what DevCard does with it.

Stage 1 is private. You add your work history. DevCard breaks it down into what actually matters.

KB
Kyle Brennan
Resume says: Database Engineer · MySQL, PostgreSQL · 10 years
MySQL PostgreSQL Redis Python AWS RDS ETL
What's behind the resume

Designed and maintained sharding strategy for 2TB+ transactional database serving payment processing

Architect Data Infrastructure Production Accountability

Led zero-downtime migration from MySQL 5.7 to 8.0 across 14 production services

Operator Failure Exposure Legacy Systems

Built automated performance regression detection pipeline for query analysis

Implementer Internal Tooling Shipped to Production
Ownership: Decision authority, correctness ownership, on-call Duration: 4 years sustained at current role

How Kyle actually works

How you spend your time

Architecture
45%
Hands-on
32%
Operations
18%
Review
5%

Delivery strength

Shipping Reality
strong
Ownership Duration
strong
Ambiguity Handling
strong
Production Acct.
strong
Failure Exposure
strong
Review Rigor
solid
Stewardship
solid

Not what tools you used. How you carry work.

Kyle's resume says "Database Engineer." Where does he actually fit?

Stage 2 maps where your real capabilities carry. Roles you might never have applied for.

Transfer directions for Kyle Brennan

Data Platform Engineering Strong
sharding strategy migration safety performance tooling direct
Backend Infrastructure Strong
production ops failure handling system reliability transfer
Site Reliability Engineering Moderate
on-call migration safety partial gap: observability

Motivation & trajectory

Attracted to

Distributed data systems
Architecture ownership
Mentoring junior engineers

Moving away from

Routine DBA maintenance
Heavy on-call without ownership

Kyle's resume says "Database Engineer." His DevCard says he's ready for platform architecture.

When Kyle's ready, this is what a hiring team sees.

Stage 3 is opt-in. You choose when to share, and with whom.

KB
Kyle Brennan
for Senior Data Platform Engineer
2 claims verified
Direct Readiness 81

Strong data infra match. Sharding, migration, performance.

Transferable Capability 76

Systems reliability, tooling patterns carry.

Delivery Strength 84

Zero-downtime migration. Production on-call. Verified.

Motivation Alignment 79

Wants architecture ownership. Direction fits.

Kyle's resume said "Database Engineer." His DevCard showed a platform architect who ships reliably and wants more ownership. The right team found him.

Stage 1 Private exploration. Map your work. See your patterns.
Stage 2 Discover where you transfer. See possibilities.
Stage 3 Share on your terms. Evidence-backed matching.

Everyone can generate code now. Not everyone can carry a project to completion.

The gap between writing code and owning outcomes is getting wider. Resumes can't tell the difference. DevCard can.

Titles hide the real work
Resumes reward polish over substance
AI makes generic output cheaper
Real judgment is harder to see
Transferable strength gets missed
Quiet competence gets buried

See how you operate

The work you carry. The patterns you repeat. The problems that keep landing on your desk.

Architecture
45%
Hands-on
32%
Operations
18%
Review
5%

See where you transfer

Your patterns carry further than your title. DevCard shows where.

Infrastructure Engineering Strong
Platform Engineering Strong
Site Reliability Moderate

What compounds vs what trends

DevCard tracks what compounds over a career, not what trends on Hacker News.

Make the invisible work visible

The incidents you prevented. The migrations you landed. The decisions you made under ambiguity.

Shipping Reality Ownership Duration Ambiguity Handling Production Accountability Failure Exposure Review Rigor Stewardship

Built for the person they call when it actually matters.

You solve real problems in production
You own outcomes, not just tickets
You ship safely, not just fast
You're still learning, deliberately

Not for:

Interview optimizers / Keyword collectors / People who want a prettier LinkedIn

How it works

1

Build your record

Projects, responsibilities, systems, decisions, constraints, outcomes.

2

See the patterns

Work layers, transferability, specialization coherence.

3

Add trust

Peer verification on specific claims. Each one compounds your confidence score.

This is not LinkedIn. It's not a black-box score. It's not a better resume.

No resume theater

No pay-to-spam

No black-box AI ranking

No hidden enrichment

No flattening you into keywords

No public profile pressure

Every score traces to structured evidence. Every claim can be verified. Your data is yours. Export or delete anytime.

Deterministic scoring. No LLM in the matching loop. Your score doesn't change because we updated a prompt.

Your DevCard means something.

A real DevCard isn't claimed. It's built. Your devcard.com/username becomes available once your profile reaches a serious threshold, including Trust Network verification.

Verification is progressive. Even one confirmed claim lifts your confidence. You build it project by project.

Claim

"Owned retry and rollback logic for the multi-service payments migration"

Decision Ownership Architecture Responsibility Shipping Reality
Alex Reyes Engineering Lead · Same team

"She designed the retry strategy, owned rollback decisions, and was the escalation point when the migration hit edge cases in production."

Priya Sharma Staff Engineer · Adjacent team

"She was my primary contact for the payment flow integration. She understood the failure modes across both services."

Confidence:
Two independent confirmations. High confidence.

When your record is clearer, the right teams notice.

Developer-first. That's why the signal is worth trusting.

For Hiring Teams

The market is getting noisier. You don't have to.

Build a record of the work you actually carry. See where you transfer. Let it speak.

Build Your Record

Earn your devcard.com/username with a complete profile and Trust Network verification.