Technical Writer

About the role

You are a Content Engineer focused on making complex distributed systems understandable and actionable for developers through precise documentation and educational material. This role owns the clarity and accuracy of all developer-facing content for Antithesis and its associated open-source projects, ensuring that users can successfully adopt and derive value from the platform. You will own the end-to-end lifecycle of documentation, from identifying gaps and structuring information to producing clear guides and maintaining content over time. You will work closely with engineers and customer-facing teams to translate technical concepts into practical guidance that accelerates adoption and reduces friction. This is a high-ownership role where your decisions directly shape how users experience and trust the product. You will play a key part in reducing the verification bottleneck created by AI-generated code by ensuring that the supporting documentation is robust, reliable, and easy to follow. If you enjoy turning complexity into clarity and taking ownership of how knowledge is shared, this role is a critical part of our mission.

Key facts

What you'll do

Add to and improve product documentation, including setup guides, tutorials, SDK material, best practices, and conceptual overviews that help users navigate the platform.

Create educational and enablement content such as primers, how-to guides, annotated examples, and onboarding materials that explain deterministic simulation and property-based testing concepts.

Collaborate closely with engineers and customer-facing teams to identify documentation gaps, gather direct feedback from users, and prioritize the most impactful content to create next.

Track product releases and updates to ensure documentation stays current, updating affected pages and flagging content that requires review from engineering contributors.

Develop information architecture that organizes documentation as a coherent system, distinguishing between tutorials, how-to guides, reference material, and conceptual explanations.

Work with distributed systems concepts on a regular basis, learning new components and workflows quickly so you can explain them clearly to both technical and non-technical readers.

Write with a distinctive voice and tone that matches Antithesis, ensuring consistency across all content while remaining approachable and precise.

Contribute to internal documentation that supports forward-deployed and support teams, helping them serve customers more effectively.

Identify opportunities for education and enablement that help customers progress through their journey with Antithesis and its open-source projects.

Maintain a high standard of quality by reviewing existing content, spotting outdated or confusing sections, and proposing improvements backed by user feedback.

Requirements

A genuine love of writing and language, with comfort working within a distinctive voice and tone that reflects the Antithesis brand.

Demonstrated experience writing developer-facing technical documentation, including API references, setup guides, SDK documentation, or similar materials.

Comfortable reading and reasoning about code in at least one programming language, without needing to write production code, but able to run examples and spot inconsistencies.

Ability to learn complex systems rapidly and explain them clearly, including distributed systems concepts such as simulation, determinism, and verification.

Strong information architecture instincts, treating documentation as a system rather than a collection of independent pages.

Self-directed and comfortable with ambiguity, able to structure documentation for topics that have not been documented before.

Ability to collaborate effectively with engineers and customer-facing teams to gather requirements, clarify technical details, and incorporate feedback.

Commitment to accuracy and quality, with the patience to update content as products evolve and to flag material that requires engineering review.

Nice to have

Previous professional experience as a software developer, which provides deeper insight into how developers consume and use documentation.

Strong theoretical background in computer science, or working knowledge of distributed systems and backend infrastructure concepts.

Previous documentation experience at a developer-tool provider, where you understand the specific needs of engineering audiences.

Prior work on open-source projects, demonstrating comfort contributing to public repositories and collaborating with maintainers.

Previous experience at an early-stage startup, where ownership, adaptability, and fast learning are essential.

Practical notes

This role requires in-person work at the Antithesis office in Northern Virginia. We believe that working together in person helps solve hard problems more effectively and makes achievements more enjoyable. The position is full-time and permanent, and we expect consistent availability during standard business hours. We have a zero-tolerance policy for workslop. AI how you AI, but respect your readers' and colleagues' time with your own work. Humans can produce workslop too. We move deliberately, prioritize quality over noise, and genuinely care about the long-term success of our products, our team, and our relationships. We will never ghost you during the hiring process; for clarity on how we evaluate interviews, please read our No Ghost Policy and our guidance on how to succeed in an interview before applying.