Twenty
Twenty4 open roles

Forward Deployed Software Engineer, Technical Lead - TS/SCI

$192–455kFort Meade, MD; Chantilly, VAOn-siteSeniorFull-time

Posted yesterday

The role in short

Lead technical discovery and personally build, test, and deploy production software solutions for government customers at their site.

About the Company

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.

Mission | On Site | Full Time | Active TS/SCI with CI Polygraph

Role Summary

Twenty builds software for national security missions. You will work at a government customer site, partnering with users and Twenty’s product teams to turn operational problems into software that works in the customer’s environment.

You will lead the technical side of discovery, scope practical solutions and personally build and deliver them. Product Managers and Mission Architects will partner with you on priorities, workflow requirements and acceptance criteria. Engineering specialists will support work that calls for deeper data, infrastructure or AI expertise. Your responsibility is to connect those inputs into a useful, maintainable solution, not to be an expert in every discipline.

Who You Are

  • You can take an unclear customer problem, ask useful questions and identify a practical first step.
  • You are a hands-on software engineer who can explain design choices and then implement them.
  • You communicate directly with technical and nontechnical users and make tradeoffs clear.
  • You distinguish local fixes from reusable product opportunities.
  • You recognize when specialist guidance or a product decision is required and seek it early.

What You’ll Do

  • Investigate customer workflows with users, Product Managers and Mission Architects to identify the engineering problem and success criteria.
  • Propose technical approaches, explain tradeoffs and agree a deliverable scope with the relevant owners.
  • Design, implement and test customer-facing features, extensions and integrations.
  • Coordinate releases through the customer’s approved deployment process, including validation and rollback planning.
  • Diagnose application failures, document findings and engage the appropriate engineering specialists.
  • Gather user feedback and recommend which capabilities should become shared product features.
  • Keep designs, tests and runbooks clear enough for colleagues outside the customer environment to support your work.

Must Have

  • 5+ years of professional software engineering experience, with demonstrated ownership from an ambiguous customer problem through technical discovery, design, implementation and production delivery.
  • Strong programming ability in a modern language such as Go, Python or TypeScript.
  • Experience testing and debugging production software across component boundaries.
  • Evidence of effective collaboration with customers or operational users.
  • Sound judgment about scope, reliability, security and when to escalate.
  • Ability to work on-site at a government facility in Fort Meade, Maryland.
  • Active TS/SCI security clearance with CI polygraph.

Nice To Have

  • Experience in restricted or air-gapped environments.
  • Experience with data integrations, containerized applications, Linux or observability tools.
  • Experience converting a customer-specific solution into a reusable capability.
  • Familiarity with government mission workflows or collaboration with domain specialists.
  • Experience building AI-backed features with specialist support.

Benefits
What's on the table:

  • 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.

If this role sounds like you, apply and share with us your interest

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. We consider all qualified applicants without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, age, veteran status, disability, or any other protected status, consistent with applicable law.

If you need a reasonable accommodation during the hiring process, let us know and we will work with you.

Prep for this interview

5 questions likely to come up at Twenty, each matched to a line in this posting.

  1. 1Coding
    They wrote: “Strong programming ability in a modern language such as Go, Python or TypeScript.”

    Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.

    How to answer

    Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.

    1. Read with a proper CSV parser; check the header first
    2. Validate each row and collect errors, not crash on the first one
    3. Send in batches with retries and a clear report at the end
    4. Write one or two quick tests for the parsing

    Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.

  2. 2Cloud, deployment and security
    They wrote: “Active TS/SCI security clearance with CI polygraph.”

    The customer's security team sends a 200-question review. How do you handle it?

    How to answer

    Why they ask: Security reviews often block deals. FDEs help get through them.

    1. Start from your company's standard answers (SOC 2 report, past reviews)
    2. Answer clearly; don't oversell
    3. Bring in your security team for anything you're unsure of
    4. Keep the new answers for the next customer

    Tip: Reuse past answers, flag honest gaps, and offer a call for the hard questions.

  3. 3Ownership and working with customers
    They wrote: “5+ years of professional software engineering experience, with demonstrated ownership from an ambiguous customer problem through technical discovery, design, implementation and production delivery.”

    Tell me about a project where the requirements kept changing. What did you do?

    How to answer

    Why they ask: Ambiguity is the norm. They want proof you can keep moving without a clear spec.

    1. The project and why requirements kept moving
    2. What you did to pin them down (short demos, written decisions)
    3. The trade-offs you made to keep shipping
    4. The result, with a number if you have one

    Tip: Show how you reduced the change, beyond how you coped with it.

  4. 4Discovery and scoping
    They wrote: “Propose technical approaches, explain tradeoffs and agree a deliverable scope with the relevant owners.”

    How do you decide what to build first when a customer wants ten things?

    How to answer

    Why they ask: FDEs have limited weeks per customer. This tests judgment about value, effort and risk.

    1. Score each request by business value and by effort, with the customer in the room
    2. Pick one item that proves value fast and unblocks later work
    3. Write down what's out of scope so it doesn't creep back in
    4. Revisit the list after the first release, with real usage data

    Tip: Show a simple way to rank the list and name what you'd leave out on purpose.

  5. 5Integrations and APIs
    They wrote: “Design, implement and test customer-facing features, extensions and integrations.”

    Walk me through connecting our product to a customer's internal system that has no documentation.

    How to answer

    Why they ask: This happens weekly in the job. They want a calm, step-by-step method.

    1. Find who owns the system and get read access to a test environment
    2. Watch real traffic or logs to learn the data shapes
    3. Build a thin adapter with logging around every call
    4. Agree on how failures get reported, and who fixes what

    Tip: Talk about finding the owner of the system first. The code is the easy part.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

Want the job, not just the posting? Learn how FDEs work.

FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.

Free. One email a week. Unsubscribe in one click.

More at Twenty

Similar roles at other companies

Twenty

$192–455k · On-site

Apply