Profile / Senior Technical Writer
About
I am Steev Kundukulangara — a senior technical writer who kept noticing that the hard part was never the writing.
The hard part is what happens on release five, when the same sentence lives in four places and three of them are wrong. So most of my work now sits upstream of the prose: the content model, the source of truth, the build, and the checks that stop drift before it ships.
In practice that means OpenAPI specs that generate their own reference, style rules that run in CI instead of in review comments, and structured authoring that survives contact with a real product roadmap. I write about all of it here, in public, mistakes included.
I am also unreasonably interested in making abstract systems visible — which is why half of what I publish ends up as a diagram.
What I do
Four things, properly
Documentation architecture
Working out what the content model should be before a single page gets written — sources of truth, reuse boundaries, and how it all gets built.
API reference systems
OpenAPI as the contract. Split, linted, bundled and rendered, with client-specific views generated rather than maintained by hand.
Docs-as-code pipelines
Style linting, link checking, previews and deploys in CI — so documentation gets reviewed and released with the same rigour as code.
Visual explanation
Diagrams and animated infographics for the concepts prose keeps failing to land.
Contact
Say hello
Best for: documentation audits, API reference builds, docs-as-code setup, or a second opinion on a content architecture that is starting to hurt.
sk@stevekundukulangara.comUsually replies within a day or two.