Career Desk
Building a DevRel portfolio that protocols actually read
Shipped samples and incident write-ups outperform conference photos.
Conference photos aren't a portfolio
A surprising number of DevRel applications lead with photos from meetups and conference talks. They're a nice signal of visibility, but they tell a hiring team almost nothing about whether you can actually help a developer succeed with an SDK.
Ship a real quickstart
Publish a complete SDK quickstart for a real, existing chain or protocol — not a hypothetical one — that takes a developer from zero to a working integration in under thirty minutes. This is the artifact hiring teams look at first, because it directly mirrors the actual job.
Write a migration guide
Pick an SDK that's gone through a breaking version change and write the migration guide you wish had existed. This demonstrates you understand not just how to explain a new feature, but how to guide developers through the harder, more frustrating parts of an integration.
Publish one honest post-mortem
The single highest-signal piece of writing you can produce is a post-mortem of an integration that failed — yours or one you observed closely — written honestly about what went wrong and what should change. This is closer to the actual interview than anything else in your portfolio, because it shows judgment, not just technical writing ability.