Staff/Principal Backend Software Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The posting includes "About The Company", "Role Summary", "What You’ll Do", "Who You Are", "Must Have", "Nice to Have", "Tech Environment (You Might Work With)", "Benefits", "Compensation Range". Also includes "Mission | On Site | Full Time | U.S. Citizenship Required / No Active Clearance Required". We need to not repeat job title as heading. Also not include Job ID etc. Remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove application instructions like "If this role sounds like you, apply and share with us your interest". Also remove "Due to U.S. government contract..."? That's relevant maybe but it's about citizenship requirement; we can keep as part of a short paragraph maybe. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short paragraph for location, employment type, citizenship requirement. We need sections only when there is real specific content. So we can have sections: About the Company, Role Summary (maybe as About the role?), Responsibilities (What You'll Do), Requirements (Must Have + Nice to Have? Could separate Qualifications and Skills). But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can choose to use only those that have content. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine. We have content: About the Company (company description). Role Summary (short paragraph). Responsibilities (What You'll Do). Requirements (Must Have). Qualifications maybe same as Requirements? Could treat Must Have as Requirements. Nice to Have could be Skills? Or we could have Skills section for Nice to Have. Benefits we have. Pay we have compensation range. Schedule maybe not given (full time). Could include Schedule as full-time? But we should not create Schedule unless posting actually states them. It does say Full Time in the metadata line. So we can include Schedule section with "Full Time". However we need to avoid filler like "not specified". It's specified as Full Time. So we can include. We also have location: Arlington, Virginia. Could include in a short paragraph. We need to output only HTML fragment, no /. Use
headings, - for lists,
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details from each bullet.
Let's extract content.
About The Company paragraph: "America is under sustained cyber attack. Our adversaries infiltrate our networks, steal our IP, and degrade the digital infrastructure that modern life runs on. They’ve learned—correctly—that those attacks rarely produce consequences. Twenty was founded to change that, by making our adversaries think twice before they attack us. Our vision is American and allied primacy in cyberspace—a future where they cannot contest us, deterrence is assured, and the free world remains secure. Founded in 2024, Twenty Technologies (www.twenty.io) industrializes offensive cyber operations for the U.S. and its allies. Headquartered in Arlington, Virginia, Twenty has raised $168M from Khosla Ventures, Accel, Caffeinated Capital, Friends & Family Capital, Point72 Ventures, General Catalyst, and In-Q-Tel."
We can keep that as prose under About the Company heading.
Role Summary: "You’ll design and build backend systems that turn real-time operational data into mission-critical capabilities. This role owns core services that need to be fast, reliable, and secure—operating across cloud and on-prem environments. You’ll make high-leverage architecture decisions, drive technical execution, and raise the bar through mentorship and engineering standards. You’ll partner closely with product, operations, and frontend teams to ship systems that work under real-world constraints."
We can put under About the role heading (or Role Summary). Use
About the role
then .
Responsibilities (What You'll Do): list items:
- Architect and build high-throughput backend services that process real-time operational data.
- Lead technical design reviews and choose pragmatic approaches for new features and system improvements.
- Design event-driven and distributed systems that are resilient, observable, and performance-tuned.
- Define stable APIs for internal and external consumers, partnering with frontend for seamless integration.
- Improve engineering excellence through code reviews, standards, testing strategy, and incident practices.
- Build and maintain CI/CD workflows that enable rapid, secure delivery.
- Troubleshoot complex production issues, lead incident response, and drive durable fixes.
- Partner with product and operational stakeholders to translate needs into deliverable technical plans.
- Contribute to technical strategy and roadmap planning across backend services.
- Support hiring by participating in interviews and helping define what “great” looks like.
We'll put under
Responsibilities
with - .
Requirements (Must Have): list:
- You have 10+ years building scalable backend systems in production environments.
- 4+ years of experience in Golang, or 4+ years writing server-side business logic in an object-oriented language (Java, Kotlin, C#, Python) or systems language (C, C++, Rust) with strong system design aptitude.
- You have led technical initiatives end-to-end, including architecture, execution, and delivery.
- You have experience designing distributed systems (e.g., event-driven architectures, messaging, consistency tradeoffs).
- You have built cloud-native services and operated them in production (AWS preferred).
- You have strong security fundamentals: secure coding, threat modeling, and defensible design choices.
- You have a track record mentoring engineers through code reviews, technical guidance, and feedback.
- You have strong communication skills and can align teams around clear technical decisions.
We'll put under
Requirements
with .
Nice to Have (Skills): list:
- You have experience designing data models and queries in graph databases (e.g., Neo4j, AWS Neptune).
- You have used relational databases (ex: Postgres, MySQL, or MariaDB) to solve business problems and are able to reason about query performance.
- You’ve worked on defense, intelligence, or security-focused products with real operational users.
- You’ve shipped large-scale data processing systems (streaming, near-real-time analytics, or similar).
- You’ve integrated ML/AI capabilities into production systems in a practical, measurable way.
- You have open-source contributions or personal projects that demonstrate strong engineering craft.
We'll put under Skills
with .
Tech Environment: could be part of Skills or maybe separate but we can incorporate into Skills or maybe omit as thin. The instruction: prefer few substantive sections. Could merge Tech Environment into Skills. But we have Skills already; we could add a sentence about tech environment. However we need to preserve all substantive information; we could include Tech Environment as part of Skills or as a separate section but that would be thin. Better to incorporate into Skills as a bullet list? But it's not a skill per se, it's environment. Could add a paragraph after Skills. But we can also create a section "Tech Environment" if we think it's substantive. It lists specific technologies: Go (Golang), AWS and hybrid cloud/on-prem deployments, Event-driven messaging (e.g., NATS), Containers and orchestration (Docker, Kubernetes), GraphQL and service-to-service APIs, Graph databases (Neo4j, AWS Neptune) and complex relationship data. That's substantive. Could be its own section. However we already have Skills for nice-to-have; we could treat Tech Environment as "Skills" but it's overlapping. To avoid too many sections, we could merge Tech Environment into Skills as additional bullets. But the instruction says "Prefer a few substantive sections over many thin ones." Having Skills and Tech Environment separate might be two thin sections? But each has multiple bullets; not thin. However we already have Requirements, Responsibilities, About the role, About the company, Benefits, Pay, Schedule. That's many sections. Could we combine About the company and About the role? They are distinct. The instruction says use headings like About the role, Responsibilities, etc. So we likely need About the role heading. About the company maybe not required but we have content; we could treat as About the company but not in list; still okay.
We need to avoid filler like "commensurate with experience". Not present.
Benefits: we have details. We'll put under Benefits
with .
Pay: compensation range: $192K - $455K. We'll put under Pay
with .
Schedule: Full Time. We'll put under
Schedule
with .
We also need to include location and citizenship requirement maybe as a short paragraph after About the company or after About the role. Could add a
after About the company: "Headquartered in Arlington, Virginia. Full-time, on-site role. U.S. citizenship required; no active clearance required." This is minor metadata; we can fold into short
.
We must not include boilerplate like EEO, equal opportunity, accommodation statement, etc. Remove those.
Also remove "If this role sounds like you, apply and share with us your interest". Remove.
Also remove "Due to U.S. government contract and security requirements, this role is limited to U.S. citizens. Some positions may also require eligibility to obtain and maintain a U.S. Government security clearance. Any active clearance requirement will be listed in the role description." We already captured citizenship requirement; we can keep short sentence about U.S. citizenship required; we can drop the rest about clearance as it's not specified.
Now produce HTML.
Structure:
About the company
... (company description)
Headquartered in Arlington, Virginia. Full-time, on-site role. U.S. citizenship required.
About the role
... role summary
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
$192K - $455K
Schedule
Full Time
Check that we didn't repeat job title. Good.
Now ensure we preserved all substantive info: Did we miss any? Let's verify.
From About the Company: we included all sentences. Good.
From Role Summary: we included all sentences.
From What You'll Do: we included all bullet points.
From Who You Are: we omitted! Oops we missed "Who You Are" section. That's substantive. We need to include that somewhere. Could be part of Requirements or Skills? It's about personal traits. Could be a section "Qualifications"? The instruction list includes Qualifications. We could treat Who You Are as Qualifications. So we need a section for Qualifications. Let's add Qualifications
with bullet list of those traits.
Who You Are bullet points:
- You’re motivated by high-stakes, real-world outcomes—especially in national security and cyber operations.
- You take ownership: you push projects from ambiguous problem to shipped, measured capability.
- You bring calm, high-judgment leadership during incidents, tradeoff discussions, and tight timelines.
- You hold a high bar for reliability, security, and maintainability—and you help others meet it.
- You communicate clearly with both technical and non-technical partners.
- You prefer simple, scalable designs
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details from each bullet. Let's extract content. About The Company paragraph: "America is under sustained cyber attack. Our adversaries infiltrate our networks, steal our IP, and degrade the digital infrastructure that modern life runs on. They’ve learned—correctly—that those attacks rarely produce consequences. Twenty was founded to change that, by making our adversaries think twice before they attack us. Our vision is American and allied primacy in cyberspace—a future where they cannot contest us, deterrence is assured, and the free world remains secure. Founded in 2024, Twenty Technologies (www.twenty.io) industrializes offensive cyber operations for the U.S. and its allies. Headquartered in Arlington, Virginia, Twenty has raised $168M from Khosla Ventures, Accel, Caffeinated Capital, Friends & Family Capital, Point72 Ventures, General Catalyst, and In-Q-Tel." We can keep that as prose under About the Company heading. Role Summary: "You’ll design and build backend systems that turn real-time operational data into mission-critical capabilities. This role owns core services that need to be fast, reliable, and secure—operating across cloud and on-prem environments. You’ll make high-leverage architecture decisions, drive technical execution, and raise the bar through mentorship and engineering standards. You’ll partner closely with product, operations, and frontend teams to ship systems that work under real-world constraints." We can put under About the role heading (or Role Summary). Use
About the role
then. Responsibilities (What You'll Do): list items: - Architect and build high-throughput backend services that process real-time operational data. - Lead technical design reviews and choose pragmatic approaches for new features and system improvements. - Design event-driven and distributed systems that are resilient, observable, and performance-tuned. - Define stable APIs for internal and external consumers, partnering with frontend for seamless integration. - Improve engineering excellence through code reviews, standards, testing strategy, and incident practices. - Build and maintain CI/CD workflows that enable rapid, secure delivery. - Troubleshoot complex production issues, lead incident response, and drive durable fixes. - Partner with product and operational stakeholders to translate needs into deliverable technical plans. - Contribute to technical strategy and roadmap planning across backend services. - Support hiring by participating in interviews and helping define what “great” looks like. We'll put under
Responsibilities
with- .
Requirements (Must Have): list:
- You have 10+ years building scalable backend systems in production environments.
- 4+ years of experience in Golang, or 4+ years writing server-side business logic in an object-oriented language (Java, Kotlin, C#, Python) or systems language (C, C++, Rust) with strong system design aptitude.
- You have led technical initiatives end-to-end, including architecture, execution, and delivery.
- You have experience designing distributed systems (e.g., event-driven architectures, messaging, consistency tradeoffs).
- You have built cloud-native services and operated them in production (AWS preferred).
- You have strong security fundamentals: secure coding, threat modeling, and defensible design choices.
- You have a track record mentoring engineers through code reviews, technical guidance, and feedback.
- You have strong communication skills and can align teams around clear technical decisions.
We'll put under
Requirements
with- .
Nice to Have (Skills): list:
- You have experience designing data models and queries in graph databases (e.g., Neo4j, AWS Neptune).
- You have used relational databases (ex: Postgres, MySQL, or MariaDB) to solve business problems and are able to reason about query performance.
- You’ve worked on defense, intelligence, or security-focused products with real operational users.
- You’ve shipped large-scale data processing systems (streaming, near-real-time analytics, or similar).
- You’ve integrated ML/AI capabilities into production systems in a practical, measurable way.
- You have open-source contributions or personal projects that demonstrate strong engineering craft.
We'll put under
- ... ...
- ... ...
- ... ...
- ... ...
Skills
with- .
Tech Environment: could be part of Skills or maybe separate but we can incorporate into Skills or maybe omit as thin. The instruction: prefer few substantive sections. Could merge Tech Environment into Skills. But we have Skills already; we could add a sentence about tech environment. However we need to preserve all substantive information; we could include Tech Environment as part of Skills or as a separate section but that would be thin. Better to incorporate into Skills as a bullet list? But it's not a skill per se, it's environment. Could add a paragraph after Skills. But we can also create a section "Tech Environment" if we think it's substantive. It lists specific technologies: Go (Golang), AWS and hybrid cloud/on-prem deployments, Event-driven messaging (e.g., NATS), Containers and orchestration (Docker, Kubernetes), GraphQL and service-to-service APIs, Graph databases (Neo4j, AWS Neptune) and complex relationship data. That's substantive. Could be its own section. However we already have Skills for nice-to-have; we could treat Tech Environment as "Skills" but it's overlapping. To avoid too many sections, we could merge Tech Environment into Skills as additional bullets. But the instruction says "Prefer a few substantive sections over many thin ones." Having Skills and Tech Environment separate might be two thin sections? But each has multiple bullets; not thin. However we already have Requirements, Responsibilities, About the role, About the company, Benefits, Pay, Schedule. That's many sections. Could we combine About the company and About the role? They are distinct. The instruction says use headings like About the role, Responsibilities, etc. So we likely need About the role heading. About the company maybe not required but we have content; we could treat as About the company but not in list; still okay.
We need to avoid filler like "commensurate with experience". Not present.
Benefits: we have details. We'll put under
Benefits
with- .
Pay: compensation range: $192K - $455K. We'll put under
Pay
with. Schedule: Full Time. We'll put under
Schedule
with. We also need to include location and citizenship requirement maybe as a short paragraph after About the company or after About the role. Could add a
after About the company: "Headquartered in Arlington, Virginia. Full-time, on-site role. U.S. citizenship required; no active clearance required." This is minor metadata; we can fold into short
. We must not include boilerplate like EEO, equal opportunity, accommodation statement, etc. Remove those. Also remove "If this role sounds like you, apply and share with us your interest". Remove. Also remove "Due to U.S. government contract and security requirements, this role is limited to U.S. citizens. Some positions may also require eligibility to obtain and maintain a U.S. Government security clearance. Any active clearance requirement will be listed in the role description." We already captured citizenship requirement; we can keep short sentence about U.S. citizenship required; we can drop the rest about clearance as it's not specified. Now produce HTML. Structure:
About the company
... (company description)
Headquartered in Arlington, Virginia. Full-time, on-site role. U.S. citizenship required.
About the role
... role summary
Responsibilities
Requirements
Skills
Benefits
Pay
$192K - $455K
Schedule
Full Time
Check that we didn't repeat job title. Good. Now ensure we preserved all substantive info: Did we miss any? Let's verify. From About the Company: we included all sentences. Good. From Role Summary: we included all sentences. From What You'll Do: we included all bullet points. From Who You Are: we omitted! Oops we missed "Who You Are" section. That's substantive. We need to include that somewhere. Could be part of Requirements or Skills? It's about personal traits. Could be a section "Qualifications"? The instruction list includes Qualifications. We could treat Who You Are as Qualifications. So we need a section for Qualifications. Let's addQualifications
with bullet list of those traits. Who You Are bullet points: - You’re motivated by high-stakes, real-world outcomes—especially in national security and cyber operations. - You take ownership: you push projects from ambiguous problem to shipped, measured capability. - You bring calm, high-judgment leadership during incidents, tradeoff discussions, and tight timelines. - You hold a high bar for reliability, security, and maintainability—and you help others meet it. - You communicate clearly with both technical and non-technical partners. - You prefer simple, scalable designs