Eeshaan Sawant

Technical Writer, Developer Advocate at ONLYOFFICE

Meet Eeshaan Sawant, a Computer Science Graduate from Pune, India. Eeshaan's primary interests lie in Developer Relations and Technical Writing. Currently, he works as a Technical Writer and a Developer Advocate at ONLYOFFICE.

Eeshaan also possesses a keen interest in Cloud-Native Technologies, and he has been a hands-on contributor and maintainer of various CNCF projects. He has also been an integral part of various Open-Source Programs like Open Source Promotion Plan (OSPP) and Outreachy, and is a recipient of the Dahn Kohn Scholarship.

When away from his beloved laptop, Eeshaan enjoys lifting weights and brewing a cup of good coffee.

Social accounts

Eeshaan Sawant

Session

What if Your DevRel Could Also Write? PS: The Secret Weapon in DevRel

What if your DevRel Engineer wasn’t just a speaker, demo builder, or community face, but also your strongest communicator on paper?


For many developers, documentation is their first, and sometimes the only touchpoint with your product. It conveys your tone, your values, and your attention to detail. If your docs aren’t clear, accessible, and globally relevant, your community won’t be either. And yet, the people who craft this experience—the technical writers, are rarely acknowledged as part of the DevRel equation.

This talk shines a light on the overlooked role of technical writers in Developer Success. From first-touch onboarding to long-tail adoption, I’ll show how good docs are doing DevRel’s most critical work, quietly and at scale. I will also share how my experience as a technical writer organically led me to take on DevRel responsibilities, and why this hybrid model is more powerful (and sustainable) than most teams realise.

Through out this talk, we will dig into:

  • How technical writing impacts onboarding, adoption, and community health
  • Where and How DevRel teams are losing efficiency by not investing in writing
  • How to elevate technical writers as contributors in DevRel strategy, within the existing workflows, without changing your org chart.

Language: English