I work with Developer Relations.
In practice, that means helping developers understand tools faster, feel less frustrated, and actually enjoy using the products they choose. I spend my time turning questions, confusion, and feedback into content, like documentation, tutorials, and learning materials that make the developer experience smoother.
I've been doing this for over five years, from small startups to working with open‑source and developer‑first products, working remotely with global teams.
I help developer tools succeed by focusing on clarity, learning, and real developer needs.
My work is community-first. Writing usually is the tool I use to turn listening into better developer experience.
That usually looks like:
I stay close to where developers are.
I read issues, Discord threads, and questions. I also enjoy looking for patterns and when the same confusion shows up more than once, I don't answer it five times, I improve the docs.
I like collaborating early and often, validating details, reproducing issues, and making sure what we publish is technically correct and genuinely helpful.
My goal is simple: the next developer should have an easier time than the last one.
I've spent the last 5+ years working with developer-first and open-source products, focusing on documentation, onboarding, and developer education.
I've worked with global and regional teams at companies like GitHub, New Relic, and Nubank, as well as through my own consultancy, helping turn real developer questions and friction into clearer docs, better tutorials, and improved developer experience.
Rather than listing every role here, I use this space to explain how I work. You can find the full, detailed version of my experience on my resume or LinkedIn.
If you're building a developer‑focused product and care about documentation, learning, and long‑term developer experience, I'd love to chat.