Currently the sole technical writer for PayPal World
Hi, I’m Akaash.
I write the docs that make complicated systems feel obvious.
I’m a senior technical writer with 8+ years of documenting APIs, admin portals and operations processes for regulated financial and enterprise software. Developers, admins, ops teams and partners all read my work, usually without noticing they’re reading it. That’s the goal.
- 8+
- years writing docs for developers, admins and ops teams
- 200+
- API references and SDK guides across 30+ releases at Kissflow
- 5
- wallet networks (UPI, M-Pesa, WeChat Pay and more) on the product I document
- 1
- technical writer on PayPal World. It’s me.
Try the API
I’ve spent years documenting APIs, so it felt wrong not to have one. Pick an endpoint, switch languages, and send a request. (Try the deprecated one.)
// Press “Send request” to call the (simulated) API.Simulated in your browser. No requests leave this page, and no tokens were harmed.
Why these docs look like docs
A resume tells you I write clear documentation. This site tries to show you instead. It’s organised the way I’d organise a developer portal: a quickstart for people in a hurry, a changelog for the full history, guides that go deep, and reference pages you can scan. If you can find what you need in under a minute, that’s the portfolio working.
My career as release notes
From v0.0.1 (a CS degree) to v4.0.0 (PayPal World), with breaking changes clearly marked.
Case studies
How I became the sole docs owner of a brand-new cross-border payments network.
Writing samples
An API reference, a quickstart, an SOP, a style guide and interactive before/after rewrites.
AI-augmented docs
How I use Claude Code, Codex and custom Cursor rules, and where humans still have to check.
What I’m good at
Owning the whole surface
API references, integration guides, admin and portal guides, dispute SOPs, network rules input and partner emails. On PayPal World I own all of it, for every audience.
Ramping up fast
Cross-border payments, wallet interoperability, disputes, fraud monitoring. I learn the domain well enough to ask engineers the questions that catch problems before readers do.
Docs as code
Git, Markdown, PR reviews, OpenAPI and Postman. I test the endpoint before I document it, and I ship docs the same way engineers ship code.
Raising the bar for others
I wrote the style guide PayPal World developers follow, built Cursor rules that enforce it, and mentored two junior writers at Kissflow.
Reviewed and approved
“From the beginning, Akaash, you’ve done some incredible work. […] I’m confident you’ll continue to accomplish excellent work while maintaining your learning mindset.”
Try the style checker
Paste a paragraph into my style checker and see what I’d flag in a review: passive voice, wordy phrases, “click here” links, Latin abbreviations and more. It runs entirely in your browser.
Known issues
Every honest product ships with a known issues list. Here’s mine.
| Issue | Status | Workaround |
|---|---|---|
| Silently fixes passive voice in other people’s drafts | Won’t fix | Enable track changes |
| Strongly pro Oxford comma | By design | None |
| Tests every API example in Postman before publishing | By design | Budget 10 extra minutes |
| Asks “who is reading this?” in every meeting | By design | Answer the question |
Thanks! Every doc I ship gets better with feedback, including this one.