Engineering Manager

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

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 "Mission | On Site | Full Time | U.S. Citizenship Required / No Active Clearance Required" is metadata; we should fold minor metadata into a short

or drop it. We should not repeat job title as heading. We should not include Job ID etc. We need to include sections only when posting has real specific content. So we can have sections: About the Company (maybe "About The Company" heading). Role Summary (maybe "Role Summary" as heading). Responsibilities (What You'll Do). Requirements (Must Have). Qualifications (Nice to Have? Actually Nice to Have could be Skills or Qualifications). Skills (Tech Environment). Benefits. Pay (Compensation Range). Schedule? Not given; we have On Site, Full Time maybe schedule info. The posting includes "Mission | On Site | Full Time | U.S. Citizenship Required / No Active Clearance Required". That gives schedule: On Site, Full Time. So we can include Schedule section with that info. Pay section: Compensation Range. We must not include filler like "commensurate with experience". Not present. We need to preserve all substantive info; do not invent or summarize away detail. So we need to include the text content under each heading appropriately, using

for prose and

• for lists. We need to strip boilerplate: EEO, equal-opportunity, scam-warning, application instructions, etc. Also remove duplicated lines. The posting includes "If this role sounds like you, apply and share with us your interest" and later "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. Twenty is an equal opportunity employer...". Those are boilerplate; we should remove them. Also "If you need a reasonable accommodation..." etc. Remove. We need to keep the substantive content: About The Company paragraph, Role Summary paragraph, What You'll Do bullet list, Who You Are paragraph, Must Have bullet list, Nice to Have bullet list, Tech Environment bullet list, Benefits bullet list, Compensation Range sentence, and maybe schedule info (On Site, Full Time). Also maybe mention "U.S. Citizenship Required / No Active Clearance Required" as part of schedule or requirements? Could be part of Requirements? It says "U.S. Citizenship Required / No Active Clearance Required". That's a requirement. We could include under Requirements or maybe a separate note. Since we have Must Have list includes eligibility to obtain a U.S. Government security clearance. The metadata says "U.S. Citizenship Required / No Active Clearance Required". Actually the posting says: "Mission | On Site | Full Time | U.S. Citizenship Required / No Active Clearance Required Role Summary". So it's a requirement: U.S. Citizenship Required, and No Active Clearance Required (meaning you don't need an active clearance but must be eligible). We'll incorporate that into Requirements maybe as a bullet. We need to avoid duplication: The Must Have list includes "You must be eligible to obtain a U.S. Government security clearance." That's similar. We'll keep that. Now produce HTML. Structure:

  About the Company

  ... (the About The Company paragraph)

  Role Summary

  ... (Role Summary paragraph)

  Responsibilities

  • Lead and develop a cross-disciplinary team of engineers spanning frontend, backend, and infrastructure.
  ... etc for each bullet under What You'll Do.

  Requirements

  • You have 5+ years of professional software engineering experience.
  • You have 3–5 years of engineering management experience, with a track record of delivering on time at high quality.
  • You've led teams of mixed discipline (frontend, backend, and/or infrastructure engineers) and managed engineers across seniority levels.
  • You have strong technical breadth across modern web platforms and backend services: you can read the code, evaluate architecture, and understand interface contracts without being a specialist in every layer.
  • You've owned a technical roadmap and made sound prioritization calls under real constraints.
  • You've built and maintained platform or shared-service capabilities consumed by other engineering teams, or are eager to grow into this responsibility.
  • You have a track record of developing ICs: clear expectations, regular feedback, and coaching that creates growth.
  • You must be eligible to obtain a U.S. Government security clearance.
  • U.S. Citizenship required.
  But note "No Active Clearance Required" is not a requirement but a statement that you don't need an active clearance. Could be included as a note but maybe not needed. We'll include as a bullet: "No active security clearance required (but eligibility to obtain one is required)." However the Must Have already says must be eligible. We'll add note.

  Qualifications

  (Nice to Have items)

  Skills

  (Tech Environment items)

  Benefits

  • 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 and Roth options. HSA/FSA options, dependent care FSA. Benefits vary by location, role, and eligibility. Full plan details provided during the interview and offer process.

  Pay

  Compensation Range: $197K - $354K

  Schedule

  On Site, Full Time

  We need to ensure we didn't include any boilerplate like EEO etc. Also we removed "If this role sounds like you, apply..." etc. Check that we preserved all substantive info: About The Company paragraph (two paragraphs? Actually there is a paragraph about America under sustained cyber attack, then vision, founded 2024, headquarters, raised $168M from list). We need to keep that exactly. Let's copy: "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

  . Role Summary paragraph: "You will lead the Data Marketplace Team—the engineering group building the signal engine that aligns cyber capability supply with operational demand. Your team will turn target intelligence from an upstream target-intelligence system and operational performance data from an operational performance and feedback system into gap analysis, high-confidence vendor demand signals, automated capability matching, and decision metrics for government buyers. This is a data-intensive, marketplace-oriented role with meaningful customer, vendor, privacy, and security considerations. Much of what your team builds connects internal operational systems with buyer- and vendor-facing workflows, making your work a critical dependency across the product ecosystem. You'll own the technical roadmap and partner closely with a Product Manager who owns the product roadmap. Day to day, you'll lead a growing team of engineers across frontend, backend, data, and infrastructure—setting direction, running projects, resolving technical dependencies, and shipping a trustworthy marketplace. This is a player-coach role. Your primary function is management and delivery, with occasional hands-on technical contributions when they accelerate the team." We'll put that in

  . What You'll Do bullets: we need to list each bullet exactly as in posting. List: - Lead and develop a cross-disciplinary team of engineers spanning frontend, backend, and infrastructure. - Own the technical roadmap; partner with the Product Manager on the product roadmap. - Run projects and workstreams end-to-end—setting timelines, resolving blockers, and keeping the team moving. - Guide architecture and technical decisions across the platform stack to keep systems coherent, secure, and scalable. - Establish and enforce engineering quality standards: design reviews, testing discipline, documentation, and security practices. - Define and maintain the interfaces and shared capabilities that feature teams consume. - Hire, onboard, and develop engineers; give direct feedback, build growth plans, and cultivate technical leadership within the team. - Run structured hiring end-to-end: define the bar, build the interview process, run rigorous debriefs, and close strong candidates. - Collaborate with feature teams and other internal consumers to ensure platform capabilities meet their needs. - Coordinate cross-team dependencies and communicate clearly on timelines, risks, and tradeoffs. - Occasionally contribute hands-on—code review, implementation, or debugging—when it unblocks the team or accelerates delivery. We'll put each as

• . Who You Are paragraph: "You're equally comfortable in a data-model review, a customer conversation, and a 1:1—you bring the same rigor to each.You think in systems: data pipelines, marketplace incentives, interfaces, trust boundaries, team structure, and delivery dependencies—not just tickets.You can turn ambiguous operational needs into clear engineering problems, measurable product outcomes, and executable plans.You hold a high bar without creating drag—you know when to push and when to get out of the way.You execute: you drive projects to completion, make decisions under uncertainty, and actively resolve ambiguity before it becomes drift.You communicate crisply with engineers, product partners, operators, vendors, and leadership without losing technical truth.You bring calm, structured decision-making to sensitive, fast-moving problem spaces where data quality, privacy, and security matter." We need to keep the spacing; but we can just put as

  with the text. Must Have bullets: list exactly as in posting. - You have 5+ years of professional software engineering experience. - You have 3–5 years of engineering management experience, with a track record of delivering on time at high quality. - You've led teams of mixed discipline (frontend, backend, and/or infrastructure engineers) and managed engineers across seniority levels. - You have strong technical breadth across modern web platforms and backend services: you can read the code, evaluate architecture, and understand interface contracts without being a specialist in every layer. - You've owned a technical roadmap and made sound prioritization calls under real constraints. - You've built and maintained platform or shared-service capabilities consumed by other engineering teams, or are eager to grow into this responsibility. - You have a track record of developing ICs: clear expectations, regular feedback, and coaching that creates growth. - You must be eligible to obtain a U.S. Government security clearance. Add U.S. Citizenship required and No Active Clearance Required as separate bullets maybe. Nice to Have bullets: list exactly. - You have experience in defense, intelligence, national