fullstackmafia.github.io

Reloadly

I joined Reloadly as a leading Developer Advocate in April 2021. There was no structure at the time for developer experience save for a few SDKs, a Postman collection, and an API reference hardcoded with HTML.

Scaling Developer Relations

I was hired to create a developer relations framework for the company and I started with revamping the developer docs. After conducting a series of developer surveys, and considering the budget of my team, I went with a collaborative, open source workflow built with GitBook. I built this from scratch and got both the engineering and product teams contributing to the docs within my first six months at the company.

Highlights

• I created product docs and API references for two products from scratch.
• I created a docs-as-code workflow with input and collaborations from team mates in engineering and product.
• I set up analytics to track developer searches and satisfaction index on the docs site. This was extrmemely helpful in adpating and modifying the docs to suite the feedback of developers.
• I set up and managed our internal CI/CD pipeline with BitBucket for the developer docs.

Publicly Available Portfolio Pieces

• Sample docs on GitBook: The company’s docs which I created from scratch. We pivoted from this to an internal docs repo.

• Sample docs - Webhooks: I rewrote this from legacy docs.
• Sample docs - Airtime Service: I wrote this from scratch.
• API reference repo: Reloadly’s API reference (this is an external copy). I created this using Redocly.
• Reloadly Developer Blog: Blog Posts, tutorials, and how-to guides which were written to familiarise developers and end users about the product.

Postman

I created a Postman Collection to help our customers with integrating our APIs more seamlessly. There was a gap in testing our APIs which I identified. First, I asked our support and solution teams if they had any pre-existing Postman collections for Reloadly. Once I got these, I revamped them, split requests into Live and Sandbox mode, organized them, and published them.

See the collection here

Current Technical Writing Work

After launching the latest iteration of our developer documentation in September 2022, I focused on improving feedback collection from our documentation users and improving the quality of our documentation by regular updates and identifying documentation gaps. I also create technical tutorials on new features and use cases for our APIs.

This site is open source. Improve this page.