Technical Writer

Snyk is the leader in secure AI software development, helping millions of developers develop fast and stay secure as AI transforms how software is built. Our AI-native Developer Security Platform integrates seamlessly into development and security workflows, making it easy to find, fix, and prevent vulnerabilities — from code and dependencies to containers and cloud.

Our mission is to empower every developer to innovate securely in the AI era — boosting productivity while reducing business risk. We’re not your average security company — we build Snyk on One Team, Care Deeply, Customer Centric, and Forward Thinking.

It’s how we stay driven, supportive, and always one step ahead as AI reshapes our world.

We're looking for a talented Technical Writer who loves turning complex security ideas into simple, helpful documents that developers find enjoyable to read. You'll contribute to our Snyk platform’s documentation, creating content that genuinely helps our customers keep their systems safe. This role involves understanding user needs, becoming a product expert, and creating documentation that makes their work easier and more efficient.

• Creating impactful documentation by writing clear, accurate, well-structured content that supports developers and security pros. Establish scalable frameworks, templates, and style guidelines for our expanding product suite.

• Becoming a product expert by testing features, exploring workflows, understanding edge cases, and providing valuable feedback to engineering teams. Your hands-on experience will make your documentation authentic and practical.

• Collaborating across teams. In a collaborator-first framework, partner with engineers, product managers, designers, and customer-facing teams to stay ahead of product changes and align documentation with the broader customer journey.

• Championing the user perspective. Represent documentation needs in product discussions, advocate for user experience improvements, and ensure our content reflects real customer workflows and use cases.

• Managing multiple projects strategically. Prioritize documentation initiatives, coordinate with stakeholders, and deliver high-quality content on schedule without compromising quality.

• 3+ years of experience in creating documentation for technical audiences: developers, DevOps engineers, security professionals, or IT operations teams. You know how to write for people who skim, search, and need answers fast.

• Strong technical foundation. Whether through formal education (degree in technical writing, computer science, communications, or related field) or hands-on experience, you have the technical depth to grasp complex systems quickly.

• Exceptional English communication skills. Native-level fluency or equivalent, with the ability to write clearly and adapt your tone for different contexts, from quick-start guides to in-depth technical references.

• Learning agility. You're comfortable diving into unfamiliar technologies, asking smart questions, and distilling complexity into clarity. You understand your audience and write with their context in mind.

• Modern documentation tools experience. Hands-on experience with docs-as-code workflows, platforms like GitBook or Docusaurus, Markdown, OpenAPI specifications, or similar tools. You're comfortable working in Git-based workflows.

• Information design skills. You don't just write‌, you architect information. You know how to structure content logically, create intuitive navigation, and make complex information accessible.

• Content strategy and planning skills. You excel at organizing information architectures, creating content roadmaps, and thinking strategically about documentation at scale.

• Project management strengths. You're skilled at juggling multiple priorities, managing stakeholder expectations, and delivering quality work under tight deadlines.

• Security or DevOps domain knowledge. Familiarity with application security, CI/CD pipelines, developer workflows, or DevSecOps practices.

• Portfolio or writing samples. Examples of technical documentation, API docs, or developer-focused content you've created.

• Open-source contributions. Experience contributing to documentation for open-source projects.

#LI-TF1