Arborbeta
Sign in with GitHub
Arbor beta · open taxonomy v0.4 · Free during beta

Your code already
shows who you are.

You've got 3–7 years in. Your resume says you know TypeScript; it doesn't show you designed the service, owns the on-call rotation, and mentored two juniors through it. We read what you've actually built and give you a profile that shows the difference — before your next job switch.

Connect GitHub — it's freePeek at a sample profile
Free during beta Public profile is yours to flip on Methodology is open
ZK
Zoe Kanazawa
@zk · arbor.dev/u/zk
Verified
Distributed systems
p72
TypeScript
p71
Go
p78
Property testing
p28
312 signals · 90d14 repos8 attestations
How it works

Three steps, no resume required.

01

Connect GitHub

OAuth in one click. We read your public repos — commits, reviews, pull requests. Nothing private, ever.

02

Assess

Our AI maps your activity to the open devskills taxonomy — 5 layers, 40+ skills. Peers can attest to what code alone can't show.

03

Share

Flip on your public profile. Link it anywhere. Methodology is open so anyone can verify how your levels were assigned.

Open taxonomy

Skills you can actually point to.

The taxonomy behind Arbor is public. Every level descriptor, every behavioral statement, every weighting rule is open for inspection. You should be able to see exactly how your credential was produced.

Three orthogonal axes make growth legible: an L3-across-the-board engineer knows the path to L4 runs through judgment and ownership — not learning another language.

View full taxonomy →
Layer 1Universal Craft

Code quality, testing, systems thinking, operational awareness, AI-assisted development. Skills every engineer needs regardless of stack.

Layer 2Technology Fluency

Languages, frameworks, infrastructure, databases. Evidence comes from what you actually ship, not what's on your resume.

Layer 3Contextual Mastery

Communication, mentorship, product thinking, organizational influence. Only peer attestation can assess these — code alone can't.

Methodology

Credentialing that can be audited.

Read full methodology →

Three signal sources

Public GitHub artifacts, peer attestation, and self-reported context. Each fills gaps the others can't reach.

Behavioral observation, not ranking

Peers affirm specific behaviors they've directly observed — drawn from level descriptors. No stack-ranking, no comparative framing.

Asymmetric discrepancy rule

Peer attestation can lift your public level but never lower it. This is intentional — peer feedback should expand credentials, not weaponize them.

Credential stability

Real-time engagement events are instant. Public-profile level changes run on a weekly cadence so your credential doesn't shift overnight from one new attestation.