Skip to main content
Technical writing covers several specializations, which I describe in Discovering technical writers. My work spans most of them, so I group my skills by specialization, each with the tools I use for it.

​
API and developer documentation

I write REST, WebSocket, and FIX API references, getting-started guides, and code samples. At Bitvavo, I document 8 APIs as the sole writer for the Exchange domain. At Adyen, I led the OpenAPI migration of the Terminal API as well as worked on all API docs relevant to In-person payments.
  • API and SDK documentation
  • REST, WebSocket, and FIX API references
  • OpenAPI Specification (OAS) and AsyncAPI
  • Getting-started guides, tutorials, and code samples
  • API governance and API design review
  • Developer experience
Tools: OpenAPI (Swagger), AsyncAPI, Postman, Stoplight, Redocly, docusaurus-openapi-docs.

​
Documentation engineering

I build and run docs platforms: docs-as-code pipelines, automated API reference generation, and developer portals. I built portals from scratch at Bitvavo and ProGlove.
  • Docs-as-code
  • Docs platform selection, setup, and content migration
  • CI/CD publishing pipelines with preview and staging environments
  • Automated API reference generation
  • Search and analytics setup
  • Scripting and command-line (CLI) work
  • DevOps
Tools: Docusaurus, Astro, Redocly, Paligo (CCMS), Pandoc, Git, GitHub, GitLab, Azure DevOps, Team Foundation Server (TFS), Travis CI, Docker, Kubernetes, Cloudflare, Amazon S3, Algolia, Markdown, HTML, CSS, XML, Python, Java, TypeScript, PowerShell, Visual Studio Code, IntelliJ IDEA.

​
Content strategy and information architecture

I treat documentation as a product. I research how people use it, measure it, and restructure it. At Adyen, I cut the in-person payments navigation from 67 items under 10 labels to 47 under 7.
  • Docs as product
  • Content strategy, content planning, and content governance
  • Information architecture
  • Content and knowledge architecture
  • Audience analysis and user research
  • Product and industry research
  • Documentation practices and style guides
  • Project planning and prioritization
Tools: Google Analytics (GA4), Algolia, Confluence, Figma, Miro.

​
Technical and UX writing

Writing is the craft, and everything else serves it. At ProGlove, I wrote the UX copy for the web portal, the scanner displays, and the iOS and Android apps.
  • Technical writing and software documentation
  • Topic-based and structured authoring
  • Single sourcing and multi-channel publishing
  • End-user manuals, user guides, and tutorials
  • Release notes
  • UX writing and content design
  • User requirements documents
  • Editing and proofreading
  • Mockups and prototyping
Tools: Paligo, Markdown, XML, Confluence, Google Docs, Microsoft Office, Figma, Zeplin, Miro.

​
AI-augmented documentation

I write for humans and AI agents, with a person at the end of every query. I use AI tools daily and structure content so agents can read it.
  • AI-augmented workflows
  • Agentic workflows and automation
  • LLM-readable docs (llms.txt, context files)
  • Model Context Protocol (MCP)
  • Claude skills
Tools: Claude, Claude Code, Cursor, Codex CLI.

​
Collaboration

I work with product managers and engineers from feature inception. At Adyen, I mentored technical writers and interviewed dozens of candidates.
  • Cross-functional collaboration with product, engineering, and QA
  • Mentoring technical writers and interviewing candidates
  • Agile and Scrum
  • Incident management and troubleshooting
  • Customer support
Tools: Jira, YouTrack, ClickUp, Azure DevOps.

​
Languages

  • Serbian: native (C2)
  • English: fluent (C2)
  • Spanish: conversational (A2)
  • Dutch: conversational (A2)
  • Translation between English and Serbian, including legal and technical translation
© 2026 Strahinja Milošević | Author of all-maker.com, a part of the tech writing blog webring