About the job
About Us
At Twenty, we tackle one of the paramount challenges of our era: safeguarding democracies in the digital landscape. Our innovative technologies operate at the confluence of cyber and electromagnetic domains, where operational speed surpasses human perception and complexity exceeds traditional limits. Our team goes beyond problem-solving; we achieve transformative outcomes that significantly influence national security. As pragmatic optimists, we recognize the difficulties of our mission to protect America and its allies, yet we believe in our potential for success.
Role Overview
In this pivotal role, you will serve as the critical link on-site at a government client location, ensuring the reliability and performance of Twenty's mission-essential platform within a secure, air-gapped AWS setting. Your responsibilities will encompass defining reliability metrics, leading incident responses in a restricted environment, and acting as the primary technical conduit between on-site activities and the engineering team based in Arlington. Collaborating closely with the DevSecOps engineer, you will ensure compliance with government security standards, and partner with product engineers to translate operational insights into actionable recommendations. Reporting directly to the VP of Engineering, this position is ideal for individuals who thrive in autonomous, high-stakes scenarios and derive satisfaction from ensuring the reliability of complex systems.
Who You Are
You take ownership of reliability results, defining what "healthy" looks like and ensuring the system meets those standards.
You are equally adept at drafting runbooks and managing production incidents, even with limited tools and no safety net.
You excel with minimal remote assistance , ambiguity does not hinder you, and you distinguish when to escalate issues versus resolving them independently.
You build trust effortlessly with external parties, including government clients, and can simplify complex technical situations under pressure.
You view manual processes as opportunities for automation: if a task is done more than twice manually, you automate it.
You communicate with accuracy , your incident reports and runbooks are designed for clarity and correctness for readers who were not on-site.
You acknowledge that, in a restricted setting, you are the feedback loop , and you approach this responsibility with utmost seriousness.
