AI-native execution, from first draft to live documentation.
API references, developer guides, SDK docs, and onboarding flows — documentation that reduces friction and helps teams ship faster.
Tutorials, blog posts, and long-form content that explains complex concepts clearly — writing that bridges the gap between engineers and their audience.
Representing a product to the developers who build with it — through technical content, community engagement, sample code, talks, and feedback loops that bring the developer voice back into the product. I bridge the gap between what engineering ships and what developers actually need to succeed with it.
Every engagement runs on an AI-native workflow — writing, building demos, auditing coverage, and catching inaccuracies using tools like Claude. The result: documentation, code samples, and content that would normally require a team, delivered with the precision of someone who knows the product deeply.
I sit at the intersection of writing and engineering — creating documentation that developers actually want to read, while building the software tools that make it all possible. Based in Lagos, Nigeria.
On the blog, I share what I learn about technical writing, developer experience, and building with modern tooling.
More about meA few things about me.
A selection of recent work.
Developer documentation for Woodcore's cloud-native core banking platform — API references, integration guides, and onboarding docs for fintech developers.
Refactored a monolithic OpenAPI YAML into a modular, maintainable architecture — with full schema documentation and verified example data for every endpoint.
Developer documentation for Alchemy's blockchain infrastructure platform — Node APIs, Data APIs, Smart Wallet infrastructure, and rollup guides across 70+ chains.
Full documentation refresh for StepSecurity's CI/CD security platform — covering the main docs suite, Harden Runner README, and GitHub Actions Goat README.
Feedback from people I've worked with.
"Opemipo has a rare ability to take deeply technical concepts and translate them into documentation that actually makes sense to developers. The API docs he delivered cut our support questions significantly."
Kyle Pippin
Head of Product, Boost Security
"What sets Opemipo apart is that he writes code. He doesn't just describe the endpoints — he tests them, catches the edge cases, and makes sure every example actually runs. The docs feel like they were written by someone who uses the product."
Toyin Olasehinde
Co-founder & CEO, Woodcore
"Our API docs went from something developers complained about to something they actually praised. Opemipo restructured the entire reference, rewrote the quickstart, and added code samples that worked on first paste. The difference in developer sentiment was immediate."
John Fahl
Founder, Ayrshare
"Opemipo brought genuine product understanding to the documentation work — not just good writing. He'd spot inconsistencies between how we described a flow and how it actually behaved, then fix both the docs and flag the issue to engineering. That kind of rigour is rare."
Damilola Teidi
Developer Relations, Paystack
Engineering orgs pour millions into reliability for systems they consider mission-critical, then let their docs rot. Teams that break this pattern treat documentation like infrastructure.
A full breakdown of how I took an Astro 6 template and turned it into a production portfolio — covering identity, content, tooling, SVG banners, deployment, and the AI-augmented workflow behind it.
The role sits between writing and software engineering — here's what that looks like in practice, and why it matters for developer-facing products.
Whether it's an API that needs a reference, a product that needs onboarding docs, or a blog post that needs a technical expert — I'd love to hear about it.