STRAHINJA MILOŠEVIĆ

Skills

Experience & Education

Bitvavo – Senior technical writer

November 2024 – Current

• Information architecture: Restructured the entire documentation site with improved top navigation, TOCs, breadcrumbs, anchor links, and clearer content hierarchy to enhance discoverability and user flow.
• Comprehensive documentation: Rewrote the full API reference and introduced new documentation types such as feature overviews and release notes to support broader product communication.
• Tooling and site infrastructure: Migrated documentation to Docusaurus, integrating plugins for OpenAPI rendering, site search, usage analytics, and other enhancements.
• Publishing pipeline: Set up a scalable publishing system with separate staging and production environments, automated linters, and content quality checks.
• Operational documentation: Revamped internal project management documentation and organized incident response runbooks to streamline knowledge sharing across teams.

Adyen – Technical writer

November 2021 – November 2024

• Information architecture: Revamped the IPP docs to enhance navigation and reduce clutter, resulting in a 25% increase in targeted traffic, decreased bounce rates, and improved SEO.
• Comprehensive documentation: Collaborated with development and product teams to document the entire IPP product portfolio, including cloud and local point-of-sale integration, payment processing, special user flows, and payment terminal manuals.
• API specs management: Wrote and maintained specifications for multiple APIs in the source code and migrated references from docs to the API explorer.
• OpenAPI specs mapping: Converted a non-REST API to OpenAPI specs and coordinated with engineers to develop a script, adjust tools, and set up a pipeline for publishing the official Terminal API reference.
• API review group impact: Influenced API design decisions as a member of the API review group, enhancing overall feature and endpoint consistency.
• User insight and analytics: Leveraged analytics and user interviews to gain insights into user needs and monitor documentation improvements.

ProGlove – Technical writer

July 2020 – November 2021

• Docs website: Single-handedly built the ProGlove docs website, migrating developer documentation into an XML authoring tool, and designing information architecture, UX components, media, and feedback widgets.
• Process improvements: Developed and implemented contributing and reviewing processes between documentation, product, development, and QA using a new CMS, eliminating review bottlenecks and expediting content publication.
• Developer docs portal: Authored and maintained the developers’ documentation portal through multiple product release cycles, utilizing Markdown, VS Code, Git, GitPages, Travis CI, and Amazon S3.
• Docs tooling setup: Worked with teams to select the tools and create pipelines for the live SDK and API pages.
• Targeted enhancements: Focused on specific documentation enhancements as quarterly OKRs, based on internal stakeholder feedback to address support and operations teams' pain points.

BlackRock – Technical writer

February 2020 – July 2020

• Agile SDLC: Authored software documentation within agile development teams, emphasizing content reuse, single sourcing, and establishing documentation processes.
• Taxonomy improvements: Categorized documentation topics for multiple products and maintained taxonomies as a single source of truth.

eFront – Junior Documentation Engineer

March 2019 – February 2020

• Internal developer docs: Created comprehensive product documentation for a new in-house image-to-text application, including setup instructions for .NET projects and environment configurations.
• Product manual: Authored a 150-page product manual for eFront Insight, an investor engagement platform for fund managers to compare investment performance using analytics dashboards and benchmarks.
• Team contribution: Actively participated in agile ceremonies, contributing to sprint planning, story refinement, and product reviews and demos.
• API docs: Authored and maintained API documentation in source code using Swagger, Visual Studio, and Git.

Freelance Translator (English – Serbian, Serbian - English)

2010 - current

• Translated legal contracts, agreements, drafts, papers, etc. from English to Serbian, and vice versa, for natural persons and legal entities using multiple web-based CAT tools.

NCR - ATM Incident management Intelligent Dispatch Agent

March 2015 – March 2019

• Monitored Barclays and National Australian Group’s ATMs via remote resolution ticketing systems.
• Advised Customer Engineers and on-site personnel on technical issues.
• Enforced security protocols during engineering calls.
• Navigated incident resolution between logistics teams, clients, and third-party companies.
• Oversaw the replenishment schedules of ATMs.

Kreativa Unlimited – Supervisor

December 2012 – April 2014

• Led promotion teams consisting of 2 - 10 promoters.
• Dispatched and inspected promotion equipment, items, and samples.
• Orchestrated shifts and location schedules per promoter availability.
• Supervised personnel on site and itemized inventory of equipment and promotion packages.
• Authored extensive reports for clients on the success of promotion campaigns and compiled customer feedback.

Alba Translations - Translator – collaborator

January 2012 – June 2013

• Translated literary and non-literary documents, papers, books, and screenplays from English to Serbian and vice versa.
• Subtitled and voice-acted films and documentaries.

Credit Agricole Srbija -Office assistant (intern)

November - December 2011

• Improved the customer accounts filing system.
• Refined everyday treasury and counter operations.
• Informed all current accounts’ owners of the new legislation requiring them to fill in the Know Your Client forms.
• Organized the Know Your Client filing system.

Education

University of Belgrade, Faculty of Philology, Department of English Language and Literature

• MA 2012
• BA 2010

Association of Scientific and Technical Translators of Serbia

• Technical translation course - 2012

Grammar School

• 2006

Projects

Enable a non-REST platform to scale through modern API tooling

Why

The Terminal API is foundational to in-person payments, but its legacy structure made it difficult to understand, maintain, and integrate with modern developer tooling. Improving its accessibility was critical for long-term platform scalability and developer trust.

What

The Terminal API is based on the nexo retailer protocol, not REST. For years, its only reference lived on a single page assembled from many HTML files, making it hard to navigate and incompatible with our OpenAPI-based API Explorer.

How

I mapped the full API structure by reconciling the official nexo PDF specification, existing documentation, and the OpenAPI requirements of our API Explorer tooling. I coordinated work between the team owning the Terminal API implementation in C and the platform team responsible for API reference pipelines.

We created a Python script to generate OpenAPI specs our tooling could consume and introduced a new page type in the API Explorer to present the API structure by request type.

Result

The migration brought a critical legacy API into the standard developer experience without altering its underlying protocol. It reduced long-term maintenance risk, improved discoverability, and increased confidence in a globally used payments API.

Reduce integration errors across hardware, OS, and data variability

Why

NFC integrations are prone to failure due to subtle differences between card types, terminal hardware, and operating systems. Clear guidance here directly reduces integration errors and support load.

What

Developers must construct four different request types (identify, read, write, or session), each with card-specific data structures. In addition, Adyen terminals run two operating systems that do not always offer feature parity.

How

I structured the documentation around user intent rather than API shape, organizing the page so developers could quickly identify the correct combination of card type, terminal type, and request type using existing CMS components.

Result

The resulting documentation reduced cognitive load in a complex integration flow and improved task completion for a feature area with a high potential for implementation errors.

Support supply-chain automation without exposing internal APIs

Why

The Logistics API enabled Adyen’s supply chain to automate delivery workflows and replace an aging messaging system under a fixed deadline, while remaining inaccessible to the public.

What

The API needed to be documented and usable by partners without appearing in official API reference tooling. Additionally, the API was still under development when documentation work began.

How

I authored the API reference directly from Stoplight mockups and designed an information architecture that made the API discoverable only to intended users through navigation and structure rather than tooling.

I also identified inconsistencies across endpoints and led efforts to simplify request and response schemas to improve integrability.

Result

The documentation enabled partners to migrate off the legacy system before the planned deadline and influenced API design decisions that made integrations easier and more reliable.

Improve content discoverability at scale through information architecture

Why

Navigation friction was preventing users from finding critical in-person payments content despite high overall traffic, negatively affecting usability and confidence.

What

The left-side navigation contained 67 items under 10 labels, creating cognitive overload and making it difficult for users to locate relevant information.

How

With a writer colleague, I conducted interviews with internal stakeholders and direct clients to understand how users consume content. We validated findings against Google Analytics data and rebuilt the information architecture around clearer conceptual groupings.

Result

The new structure reduced navigation items from 67 to 47 under 7 labels. One year after launch, analytics showed a substantial decrease in negative feedback, increased traffic to previously underused areas, and an overall traffic increase of approximately 25% across the IPP section.

Build a scalable documentation platform as the first writer

Why

ProGlove’s products were scaling faster than its documentation infrastructure, creating risk for onboarding, support, and partner integrations.

What

When I joined, documentation consisted of minimal content on a static MkDocs site. As the sole writer, I was responsible for tooling, content creation, structure, reviews, and delivery across hardware, software, and APIs.

How

I introduced Paligo to enable scalable authoring and faster review cycles, migrated all existing content using Pandoc and custom scripts, designed a new information architecture for the full product portfolio, and implemented OpenAPI references for public APIs.

I also customized HTML and CSS to align the documentation portal with the company’s visual identity.

Result

Within a year, ProGlove had a professional, multi-product documentation portal with versioning, release notes, media, and automatically updated API references, supported by sustainable documentation practices.

Contact

• LinkedIn
• GitHub

Elements

i = 0;

while (!deck.isInOrder()) {
    print 'Iteration ' + i;
    deck.shuffle();
    i++;
}

print 'It took ' + i + ' iterations to sort the deck.';