Senior Technical Writer, Ping Identity

• 5–8+ years of technical writing experience, including substantial work in a developer- or architect-focused domain
• Experience documenting identity and access management, security, or closely related infrastructure (authentication/authorization, policy engines, gateways, or identity governance)
• Working knowledge of modern identity standards and patterns such as OAuth 2.0, OpenID Connect, SAML, JWTs, and token exchange, and how they show up in real architectures
• Experience developing comprehensive, implementation-focused content for advanced technical users (solution architects, developers, administrators), while also demonstrating the ability to go beyond simple feature descriptions to provide clear, approachable guidance, making complex security concepts accessible to customers and prospects with limited prior knowledge
• Comfort working in Docs-as-Code environments (AsciiDoc/Markdown, Git/GitHub, code review workflows, and automated builds)
• Demonstrated ability to collaborate effectively with Engineers and Product Managers, ask the right questions, and negotiate for clarity in APIs, UX, and configuration
• Strong organizational skills: able to manage multiple doc streams, hit release dates, and communicate status and risks clearly
• Experience using AI tools (for example, large language models) to review, critique, and refine documentation while maintaining ownership of accuracy, voice, and overall quality
• Excellent written and verbal communication skills in English

Desirable

• We’re looking for a Senior Technical Writer to own day-to-day documentation for:
• Identity for AI use cases (agentic AI, token exchange, safe orchestration, and real‑world implementation patterns), and
• PingAM and Advanced Identity Cloud (AIC) journey/nodes documentation, including admin and developer-focused guidance
• You’ll be deeply hands-on with the products, writing clear, implementation-focused docs that help architects, developers, and admins design secure, AI-aware identity journeys. You’ll partner closely with Product, Engineering, Architecture, and Developer Experience, and you’ll help shape patterns and standards other writers can reuse in this space
• 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