Senior Backend Software Engineer

We need to output HTML fragment with sections: About the company? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. The posting includes: - About The Company (description) - Mission | On Site | Full Time | U.S. Citizenship Required / No Active Clearance Required (metadata) - Role Summary (description) - What You’ll Do (list of duties) - Who You Are (list of traits) - Must Have (requirements) - Nice to Have (preferred) - Tech Environment (You Might Work With) (list) - Benefits (list) - Compensation Range: $159K - $263K (pay) - Also mention location: Headquartered in Arlington, Virginia (maybe location) - Some metadata: Founded in 2024, raised $168M etc. We need to decide sections: About the company (maybe "About the Company") could be a section heading. The instructions list example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But they say use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content exists. We need to include sections only when posting has real specific content. We have: - About the Company: yes, content. - Role Summary: could be "About the role" maybe. - What You’ll Do: Responsibilities. - Who You Are: maybe Qualifications or Skills? Could be "Skills" or "Qualifications". The Must Have and Nice to Have are requirements/qualifications. Could combine into "Requirements" and "Qualifications"? The instructions list both Requirements and Qualifications as possible headings. We could put Must Have under "Requirements" and Nice to Have under "Qualifications" or "Skills". But we need to avoid thin sections. Perhaps combine Must Have and Nice to Have into a single "Requirements" section with sublists? But they said use

  • for any list of duties/requirements/benefits. So we can have a section "Requirements" with two subheadings? Not allowed to add extra headings beyond

    . Could just list all requirements (must have and nice to have) as a single list, but we need to differentiate? Might be okay to just list them as bullet points without distinction. However we need to preserve all substantive information; we can keep the distinction by using separate

    with headings inside? But we cannot add extra headings besides

    . Could use

    to label "Must have:" then list. That's okay. Similarly, Benefits: we have details. Pay: we have compensation range. Schedule: not mentioned (maybe full-time). The posting says "Full Time" in metadata. That's schedule info. So we can include a Schedule section with "Full Time". However the instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Full Time (in metadata). So we can include Schedule. Also location: maybe not needed as a section. We need to remove boilerplate: EEO, equal opportunity, accommodation, etc. Also remove "If this role sounds like you, apply and share with us your interest" (application instructions). Also remove "Due to U.S. government contract and security requirements, this role is limited to U.S. citizens." That's maybe relevant? It's a requirement (citizenship). Could be part of Requirements. But it's also a legal requirement; we can keep as part of Requirements. Also remove "Twenty is an equal opportunity employer..." etc. Also remove "If you need a reasonable accommodation..." etc. Also remove "Mission | On Site | Full Time | U.S. Citizenship Required / No Active Clearance Required" maybe we keep the pieces: On Site, Full Time, U.S. Citizenship Required. We can incorporate into appropriate sections. We need to preserve all substantive information: company description, mission, founding, funding, headquarters, etc. Role summary, responsibilities, who you are, must have, nice to have, tech environment, benefits, compensation, schedule (full time), location (Arlington, Virginia), citizenship requirement. We need to format as HTML with

    headings and

    or

    • . Let's decide sections: - About the Company (maybe heading "About the Company") - About the Role (or Role Summary) heading "About the role" - Responsibilities (What You’ll Do) - Requirements (Must Have + Citizenship + maybe location? plus Nice to Have? Could separate Qualifications) - Qualifications (Nice to Have) maybe. - Skills (Tech Environment) maybe. - Benefits - Pay - Schedule But we need to avoid thin sections. Let's see if each has substantive content. About the Company: multiple paragraphs -> good. About the role: Role Summary paragraph -> good. Responsibilities: list of items -> good. Requirements: Must Have list (7 items) plus citizenship requirement -> good. Qualifications: Nice to Have list (5 items) -> good. Skills: Tech Environment list (maybe 8 items) -> good. Benefits: list -> good. Pay: compensation range -> good. Schedule: Full Time -> maybe thin but it's specific. Could combine with location? But schedule section is allowed if posting states it. It's just "Full Time". Could be okay. We could also include Location as a short p under maybe About the Company or separate? Not required. We need to avoid duplication: The posting also mentions "Headquartered in Arlington, Virginia". Could include in About the Company paragraph. We need to remove duplicated lines: The posting includes "Mission | On Site | Full Time | U.S. Citizenship Required / No Active Clearance Required". We'll extract pieces. Now craft HTML. We'll start with

      About the Company

      then

      containing the description. We need to ensure we preserve all substantive info: Let's extract the 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'll put that in a

      . Next, About the role: Role Summary paragraph: "You’ll build the backend systems that power Twenty’s cyber and electromagnetic capabilities—software that ingests real-time operational signals, models complex relationships, and serves high-throughput APIs at machine speed. You’ll design and ship reliable services in Go, working with known-hard problems like graph data modeling, event-driven architectures, and performance at scale. You’ll partner closely with product, frontend, and domain experts to turn operator needs into durable platform capabilities. This role spans both cloud and on-premises environments supporting mission-critical U.S. national security outcomes." Put in

      . Responsibilities: list of bullet points from "What You’ll Do". Let's extract each line: - Design and implement scalable backend services in Go that improve operator decision-making and response. - Build high-performance APIs that power customer-facing workflows and internal platform capabilities. - Model complex relationships in graph databases and optimize schemas and queries for speed and clarity. - Implement event-driven systems (e.g., with NATS) to process real-time operational data streams. - Develop and maintain automated tests to protect correctness, security, and performance as the system evolves. - Build and operate microservices deployed on AWS, with an eye toward resilience and cost-aware scaling. - Create and improve CI/CD pipelines that enable fast, secure delivery of new capabilities. - Partner with cyber operations experts to translate domain needs into robust product features. - Collaborate with frontend engineers on API contracts and data structures that are efficient and usable. - Evaluate new technologies and patterns that could unlock better operational outcomes. We'll put each as

    • inside
      . Requirements: Must Have list plus citizenship requirement. Must Have list: - You have 5+ years of professional software development experience building backend (or full-stack) applications. - You have strong proficiency with Go (Golang) and have shipped production services with it. - You have experience working with graph databases (Neo4j, AWS Neptune, or similar), including schema design and query performance. - You have working knowledge of event-driven architectures and message queues/streaming systems. - You have experience building and maintaining APIs (REST and/or GraphQL). - You have experience with cloud infrastructure, ideally AWS, and understand cloud-native deployment patterns. - You have hands-on experience with containerization and microservices architectures. - You have a strong foundation in secure coding practices and can reason about security tradeoffs. - You have a bachelor’s degree in Computer Science, Software Engineering, or a related field, or equivalent practical experience. Plus citizenship: U.S. Citizenship Required (from metadata). Also maybe "No Active Clearance Required" but that's not a requirement; it's a note. We'll include citizenship as a bullet. We'll put these as
      • . Qualifications: Nice to Have list: - You’ve delivered software in defense, security, or other mission-critical environments. - You’ve built systems for analysts, operators, or high-tempo users where speed and reliability matter. - You’ve integrated AI/ML capabilities into production systems (inference, pipelines, or tooling). - You have experience with large-scale data processing and analytics workloads. - You’ve contributed meaningfully to open-source projects. - You’ve used observability tooling (metrics, tracing, logging) to debug and improve production systems. That's 6 items. We'll put as
      • . Skills: Tech Environment list: - Go (Golang) - GraphQL/REST - Graph databases (Neo4j, AWS Neptune) and complex graph schemas - NATS and event-driven architectures - AWS, microservices, containers - CI/CD pipelines, automated testing frameworks, infrastructure-as-code patterns - Monitoring and observability tools We'll put as
      • . Benefits: list from Benefits section: - Health. Medical, dental, and vision plan options. Life / AD&D, disability coverage options. - Family. Paid parental leave for eligible full-time employees. 12 weeks for birthing parents, 4 for non-birthing parents, 6 weeks for adoptive, foster, or intended parents through surrogacy. - Vacation. Paid holidays and flexible PTO. Take what you need. - Retirement. 401(k) with pre-tax