I'm a senior frontend engineer who'd rather be talking to your developers, making the content, and showing up in your community than shipping another internal feature. The warm, technical face your product has been missing.
Your engineers could, if cornered, write a docs page. What they usually can't — or won't — do is everything around the code: make your developers feel heard, create content that actually explains the product, show up in the community, and do the empathetic support that turns first-time users into advocates.
That gap is what quietly costs you developer activation and retention, long before anyone thinks to blame the docs.
Most teams start with a Launch Engagement to stand the function up, then keep it running on a retainer. Pick the one that fits where you are.
A fixed, focused sprint that stands up a real, working developer relations function instead of just rewriting your docs.
You're launching or relaunching a developer product and no one owns the developer experience yet.
The function, kept alive and growing: content, community, and a steady presence for your developers.
You've built momentum and need someone consistent to sustain it rather than a one-off push.
A fast, fixed-price audit of your docs and first-run developer experience. You get a prioritized report of gaps, confusing onboarding points, and quick wins — things you can act on immediately. Optional add-on: I execute the top fixes at a separate fixed fee, scoped after the audit.
I've spent six years building production frontends in React and TypeScript, including frontend platform work, so I can read your API and SDK the way your engineers do. The technical fluency is real.
The difference is that I genuinely want the public-facing, relational work most engineers avoid: the writing, the videos, the community, the patient support that makes developers feel taken care of. That combination is rare, and it's the whole point.
I've been the confused developer at 1am staring at a half-documented endpoint. I build the experience I wish I'd had, and I like doing it in public.
They can write a docs page if you push them. What they usually won't do is the ongoing relational work: the content, the community presence, the empathetic support and advocacy. That's the part that actually drives adoption, and it's the part that keeps slipping.
A technical writer documents; a community manager moderates. I do both, and I can read your code, so the content is accurate and the community gets real answers. It's one technical, people-first person owning the whole developer experience.
You're left with a working DevRel function you fully own. Most teams continue on a monthly retainer to keep it growing; some take it in-house using the system I've built. No lock-in either way.
A prioritized audit of your docs and first-run developer experience: where developers get stuck, what's missing, and what quick wins exist. Delivered as a report you can act on immediately, with an optional add-on for me to execute the highest-impact fixes.
I focus on developer-facing products: APIs, SDKs, platforms, and infrastructure tools. The work depends on actually understanding what developers are building with your product, which requires real technical fluency in the space.
Not currently. The consulting model is intentional: I can serve a few teams at a higher level than I could one company in a junior DevRel role. When that changes, I'll say so here.
Send a few lines about what you're building and where the developer experience hurts. I read every message myself and reply personally, usually within a day or two.