Technical Writer

About Antithesis We provide a platform that helps engineering teams identify and resolve bugs that traditional testing approaches miss. Antithesis runs your entire system in a deterministic simulation, breaks it in every way imaginable, and hands you a root cause and a perfect reproduction — no flaky tests, no false positives, no "works on my machine". This allows engineering teams to debug faster and ship with greater confidence. The rise of AI-generated code has made what we do more important than ever. Agents can write code faster than any human — but faster code isn't better code if it's buggy, stuck in review, or issues are slipping through the cracks undetected. The verification bottleneck is real and it's growing. This is exactly the problem Antithesis exists to solve. We've been quietly reinventing how the world thinks about software reliability, and we're just getting started. We're well-funded, deeply technical, and building a platform that tackles one of the most complex yet important problems in modern software engineering. If that sounds like fun to you, keep reading. The role We’re looking for a Content Engineer to work on docs and educational content for Antithesis and our associated open-source projects, as well as our internal docs. Your work will enable the SWEs and SREs who use our product, as well as our own forward-deployed and support teams. This is a high-ownership role, with a broad remit to not only work on docs, but figure out where and how more education and enablement can help our customers in their journey. What you’ll do Add to and improve product docs – setup guides, tutorials, SDK material, best practices, and conceptual overviews. Create educational and enablement content: primers, how-to guides, annotated examples, and onboarding materials that help engineers understand and adopt DST and PBT. Collaborate closely with engineers and our various customer-facing teams to identify documentation gaps, gather feedback from users, and prioritize what gets written next. Keep documentation current as the product ships, tracking releases, updating affected pages, and flagging content that needs engineer review. What we’re looking for A genuine love of writing and language. We have a distinctive voice and tone, and you’ve got to be comfortable working with that. Demonstrated experience writing developer-facing technical documentation like API references, setup guides, SDK docs, or similar. Comfortable reading and reasoning about code in at least one language. You don’t need to ship production code, but you need to be able to read it, run examples, and spot when something doesn’t add up. Ability to learn complex systems quickly and explain them clearly. You’ll be working with a lot of distributed systems concepts. Strong information architecture instincts: you think about docs as a system, not just a collection of pages, and you know the difference between a tutorial, a how-to guide, a reference, and an explanation. Self-directed and comfortable with ambiguity – at an early-stage company, some of what you’ll document hasn’t been documented before, and you’ll need to figure out the right structure from scratch. Bonus points Previous professional experience as a software developer. Strong theoretical background in CS, or working knowledge of distributed systems or backend infrastructure. Previous docs experience at a dev-tool provider. Previous work on open-source projects. Previous experience at an early-stage startup. Working at Antithesis We work in-person at our Northern Virginia office. We think being together makes the hard problems easier and the wins more fun. We have a zero-tolerance policy for workslop. AI how you AI, but respect your readers’ and colleagues’ time with your own. Humans can produce workslop too. We move deliberately, prioritize quality over noise, and genuinely care about the long-term in our products, our team, and our relationships. We will never