Quickstart for recruiters

Everything you need in about 60 seconds. If you only read one page, read this one.

✓

Prerequisites: none. You don't need a technical background to read this page, and that's on purpose.

Step 1: Know who I am

I’m a Senior Technical Writer at PayPal, where I’m the only technical writer on PayPal World. It’s a cross-border network that lets wallets such as UPI (through NPCI), M-Pesa, Mercado Pago, WeChat Pay and PayPal work together. I own its documentation end to end: API references, integration guides, portal guides, dispute SOPs and partner communications.

Before PayPal, I spent nearly four years at Kissflow writing 200+ API references and SDK guides, mentoring two junior writers, running localization with Crowdin, and building most of the customer-facing video library. That work earned me the company’s Technical Writing Rockstar Award.

Step 2: Check the fit

I’m looking for:

Role Why I’m a fit
Senior / Staff Technical Writer 8+ years, API-first, comfortable owning a product’s entire docs surface alone.
Documentation Lead I’ve written style guides, set up review processes, mentored writers, and run localization. I keep docs in step with releases across eight product managers in four locations.
AI-focused documentation I use Claude Code, Codex and Cursor every day. I run cost-aware multi-agent loops (Opus orchestrates, Sonnet writes, Haiku verifies) and build custom Cursor rules that make developers write better docs.

Domains I know well: payments and fintech, enterprise SaaS, developer platforms, and auth and security (OAuth 2.0, API keys, Okta SSO).

Step 3: Verify the claims

Don’t take my word for it. Skim one or two of these:

Step 4: Get in touch

→

Email me at akaash.amalraj@gmail.com or message me on LinkedIn. You can also download my resume (PDF).

That’s it. You’re integrated. 🎉

© 2026 Akaash Amalraj · Built with Astro, written by a human, reviewed by a style guide. · llms.txt

esc