Pavlo S.

Your developers ship fast. Your docs don't keep up. I fix that. I write and structure API documentation, developer guides, and system design docs for SaaS and platform teams — the kind that reduces support tickets, speeds up integration, and makes your onboarding actually work. What I bring that most tech writers don't: → I read code. I work directly with OpenAPI specs, Java annotations, REST controllers, and CI/CD pipelines — not just screenshots from Postman. → I've built documentation departments from zero — twice. At GridDynamics and GlobalLogic, I designed the doc architecture, style guides, and review processes from scratch. → I work in your stack. Git, Markdown, Confluence, docs-as-code workflows — I commit to your repo, not a Google Doc. What I deliver: - OpenAPI/Swagger documentation generated from source code annotations - Developer onboarding guides and integration quickstarts - System design docs (architecture overviews, sequence diagrams, SRS) - Documentation style guides and tone-of-voice standards - API reference docs for internal and external developer portals Industries I've worked in: SaaS platforms, EdTech (Mate Academy), medical device software (ISO 13485 compliance at GlobalLogic), and enterprise microservices (GridDynamics). If your docs are slowing down your developers or your customers, send me a message with a quick description of what needs fixing. I'll tell you how I'd approach it — no pitch, just a plan.