Technical Writer

• Create Technical Manuals: Write architecture specifications, integration guides, and data sheets.
• Document Register Maps: Author detailed register descriptions and memory map definitions.
• Develop User Guides: Produce step-by-step guides for IP configuration, synthesis, and verification.
• Standardize Documentation: Establish templates, style guides, and documentation release workflows.
• Edit Engineering Drafts: Refine internal design notes into customer-facing collateral.
• Manage Version Control: Maintain documentation pipelines tied to hardware RTL release cycles.

• Contribute to the creation and maintenance of documentation for Identity for AI scenarios and PingAM/AIC journeys and nodes (what they do, how to configure them, when to use them, and how they behave in real flows).
• Write a mix of content types: concepts, configuration guides, end-to-end tutorials, troubleshooting topics, and reference content that connects APIs, nodes, and policies.
• Develop and test practical examples—sample flows, configuration snippets, diagrams—that show how to combine nodes, policies, APIs, and SDKs to solve real customer problems.
• Translate advanced identity topics—OAuth/OIDC, token exchange, journey orchestration, risk evaluation, modern auth patterns, and AI-agent architectures—into approachable content for architects and experienced developers.
• Work directly in the products and flows (PingAM, AIC journeys, Identity for AI examples) to validate behavior and ensure docs reflect reality, not just specs.
• Proactively identify confusing areas in the UX, call out risks or edge cases, and document recommended patterns rather than just options.
• Partner with Product Management, Engineering, and Architecture to understand roadmaps, refine feature designs, and surface doc requirements early.
• Participate in planning, backlog triage, and sprint activities to stay ahead of upcoming changes that affect journeys, nodes, and AI-related use cases.
• Work with other writers and editors to align on style, terminology, and reusable patterns for journey/node documentation and AI-focused content.
• Author content in our AsciiDoc/Antora, Git/GitHub-based toolchain, using branches, pull requests, and reviews to publish changes.
• Help keep builds clean by catching broken links, structural issues, and formatting problems before they reach production.
• Share tips, scripts, or small automation ideas that improve the consistency and efficiency of our documentation pipeline.

Senior Technical Writer

• The documentation you maintain and improve has a daily, visible effect on how people work — this is not documentation that sits on a shelf never to be read.
• Document new products from day one, setting the standard before complexity accumulates.
• Run documentation migration projects end-to-end: scope what needs to move (and improve), get buy-in from the team that owns it, and deliver it — from operations documentation to people documentation and beyond.
• Choose your work based on impact. You decide when to raise the bar and when documentation is finished.
• Shape how new departments adopt the Handbook. Work with teams that have never used Git, explain why their knowledge belongs in the Handbook, and either run the migration for them or support them doing it themselves.
• Mentor another technical writer — raise their standard by reviewing their work, sharing approaches, and role modelling how to run projects independently.
• Advocate for culture change: the documentation practices that worked for a startup of humans do not serve a scale-up of AI-builders. You’ll help iwoca recognise that and adapt.

See all jobs on JobTailor

Technical Writer

Senior Technical Writer

Senior Technical Writer