Technical communication

The challenge: staying genuinely helpful without ever being obvious, explaining Alfred’s concepts to an international audience aged 25 to 65. I leaned on strict information mapping, a deliberately shallow structure, and disambiguation hubs with clear cards — keeping terminology identical to the UI across every translation.

Documenting security-critical, invisible flows — OAuth/OIDC, passkeys, journey orchestration — with zero room for ambiguity, while APIs and SDKs across Web, iOS and Android keep evolving. I validate every flow hands-on so the docs stay as dependable as the product.

Standing up functional and backend API documentation from scratch, in fast Agile cycles, for an audience that’s half product, half engineering. The hard part: pulling scattered knowledge across Confluence, Backstage, Postman and Swagger into one coherent, searchable voice.

Jumping from one client and project to the next — industrial automation, printing machinery, finance — each with its own jargon, tools and reader. I used information mapping and plain language to make dense, regulated material usable, and published multi-output in MadCap Flare.

In healthcare admin and finance software, accuracy is compliance — a wrong step in a guide has real consequences. I owned the information architecture, kept docs in lockstep with a fast-moving product, and worked with UX to rewrite the interface text itself.

Sitting between support, product and R&D — turning real customer friction into clear help content and roadmap input. I produced bilingual (EN↔FR) Help Center articles and release comms built to cut tickets, not just describe features.

Carrying meaning, terminology and cultural accuracy intact across EN/FR → IT, from books to technical texts. It’s where I learned the precision and register discipline that underpins all my technical writing today.