Update: Taking consultations for work beginning in Feb. 2026!
Well, hello there.
Welcome, welcome! Take a look around.
I’m Michelle Peruskie, an API & SDK documentation engineer and software developer who helps complex products speak human. I combine deep technical knowledge with modern AI-assisted workflows to make documentation accurate, scalable, and genuinely enjoyable to read.
What I do
At Amazon Web Services (AWS), I spent my time authoring and launching large-scale developer documentation across the IoT and Compute portfolios.
I built end-to-end doc ecosystems that aligned content architecture, console help panels, API reference accuracy, and developer flow. I also created internal prompt-engineering frameworks to help writers and service teams safely integrate AI tools into their doc processes—speeding up draft creation without sacrificing correctness or style.
Beyond AWS, I’ve worked across developer platforms, CPaaS, fintech, and hardware—creating everything from API references and SDK guides to product manuals, curriculum, and proposal documentation. That broad background means I can adapt quickly to new domains, maintaining a consistent, user-centered narrative.
Through LightBulb Prospectors LLC, I’ll continue that work independently: helping startups and SaaS teams build future-ready documentation systems that blend human expertise with smart automation.
What sets me apart?
🤖 | 💻 | 🧩 | 🧭
AI-Assisted, Human-Validated Docs: I design prompts, validation layers, and editorial guardrails that turn LLMs into helpful partners and not hallucination machines.
Developer-First Approach: I think of docs as the product’s first user interface. Every example, JSON snippet, or walkthrough must earn its place.
Systems Thinking: My superpower is seeing the architecture behind content—how glossary terms, SDK snippets, UI strings, and tutorials all connect into one system.
Cross-Functional Glue: I’ve acted as project manager, editor, API tester, and translator between engineering, product, and design.
My approach to API docs
API documentation should be accurate, friction-free, and fast to navigate. It should explain without over-explaining.
That means:
- Code samples that actually run
- Examples that use relevant, real-world data
- Just enough visual hierarchy to guide the eye
And occasionally, a touch of humor—because developers remember the docs that make them smile.
A Little About Me
I’m equal parts strategist and storyteller—an INTJ with a sense of humor and a soft spot for well-structured Markdown. I believe great docs are equal parts empathy, architecture, and curiosity.
When I’m not writing, I’m creating pixel art patterns for crochet, volunteering with Knitted Knockers, or exploring new ways to automate creative workflows.
Current booking status
I’m officially booked until August 2026. However, I’m still available for small one-off projects and consultations. Tell me how I can help.