Factory
Factory2 open roles

Software Engineer, Federal

Remote (US); San Francisco, CA; Washington, DCRemoteMidFull-time

Posted 19 days ago

The role in short

Deploy and harden Factory's AI platform in secure government environments while embedding with federal customers to integrate agentic systems into their workflows.

About Factory

Our mission is to create a world where software builds and improves itself.

We build the platform for self-improving software development, helping the world's largest enterprise engineering teams turn their organizations into autonomous software factories. Customers including Nvidia, Blackstone, Royal Bank of Canada (RBC), Palo Alto Networks, Adobe, and T-Mobile run Factory to ship code, review PRs, run tests, and deploy continuously - getting smarter with every cycle.

In 2026, we raised $200M at a $5B valuation, bringing our total funding to over $400M. We are backed by world-class investors and operators including Khosla Ventures, Sequoia, Blackstone, Ali Ghodsi (CEO of Databricks), and Frank Slootman (Former CEO of Snowflake).

About the Role

Factory is looking for innovative Software Engineers to join our founding Federal team. You will build and evolve cutting-edge AI systems that transform how government software organizations accelerate their productivity and innovation. You will work directly with the Department of War, the Intelligence Community, and federal civilian agencies to bring Factory to secure, classified, and air-gapped environments, helping the nation's most critical software teams operate as autonomous software factories.

What you will do and achieve

  • Innovate at the forefront of AI by designing, developing, and deploying AI-driven agentic systems that enhance Factory's core AI capabilities for federal missions
  • Deploy and harden the Factory Platform in secure government environments, including GovCloud, on-premises, classified, and fully air-gapped networks, so it runs with limited or no internet connectivity and with self-hosted or government-approved models
  • Build security and compliance into everything you ship, partnering with Security and Infrastructure to achieve and maintain authorizations such as FedRAMP High and DoD Impact Levels (IL5/IL6), including access controls, audit logging, and continuous monitoring
  • Build multi-layered guardrails, observability, and explainability into our agents so government users can trust, audit, and understand how an agent reached its output
  • Engage directly with federal customers, on-site when needed, to understand their missions and workflows, define requirements with stakeholders, and own delivery from first prototype to accepted production deployment
  • Integrate Factory with the tools government engineering teams already rely on, including on-premises source control, CI/CD pipelines, ticketing systems, and DoD software factories
  • Work with product, engineering, and Federal go-to-market teams to integrate emerging AI research findings into practical, mission-focused solutions
  • Engage in iterative development processes, rapidly prototyping and refining AI functionalities based on real-world feedback to meet the evolving needs of government developers and program offices
  • Take the initiative in identifying and addressing product stability and scalability challenges, ensuring the Factory Platform reliably supports large-scale operational demands in high-consequence and resource-constrained environments
  • Lead the exploration and integration of large-scale data processing techniques to improve the reliability and effectiveness of our AI systems
  • Serve as the voice of the federal customer, bringing field insights back into Factory's core platform so that capabilities built for one mission become reusable across the public sector
  • Help build our Federal team from the ground up, partnering with leadership on technical proposals, capture strategy, and the product roadmap for our public sector business

Qualifications

  • 2+ years of hands-on experience in software engineering roles post-acquisition of a Bachelor's or Master's degree in Computer Science, Engineering, AI, or a related technical field.
  • Demonstrated proficiency with LLMs and a track record of applying AI/ML techniques to solve complex, unstructured problems, ideally within the domain of software engineering or related areas.
  • Self-motivated and autonomous, with a proven ability to navigate ambiguous projects from conception to impactful deployment, ideally as part of a founding team, a new initiative, or a forward-deployed engineering group.
  • Strong communication skills that enable you to articulate technical concepts and strategies clearly at all levels, including to non-technical government stakeholders, coupled with a strategic mindset oriented towards innovation.
  • Comfort working directly with customers, including time on-site at customer locations.
  • A passion for public sector work and a belief in the potential of government institutions to deliver better outcomes through technology.
  • Experience deploying software in regulated or secure environments (e.g., AWS GovCloud, Azure Government, FedRAMP, DoD Impact Levels, or classified and air-gapped networks) is highly desirable, though not mandatory.
  • Familiarity with government work and its complexities, including procurement, compliance, and the accreditation (ATO) process, is a plus.
  • Experience with data-intensive applications and familiarity with the software development lifecycle are highly desirable, though not mandatory.

Location:

We offer location flexibility for this role, with a preference for candidates based in our San Francisco, CA (HQ) or Washington, D.C. (remote).

Prep for this interview

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

  1. 1Discovery and scoping
    They wrote: “Engage directly with federal customers, on-site when needed, to understand their missions and workflows, define requirements with stakeholders, and own delivery from first prototype to accepted production deployment”

    A customer says “we want AI in our claims process.” What do you ask in the first meeting?

    How to answer

    Why they ask: Most FDE work starts this vague. They want to hear you find the real problem before you pick a tool.

    1. Map the current process: who touches a claim, in what order, with which systems
    2. Find the slowest or most error-prone step and ask what it costs them
    3. Agree on one measurable goal (for example time per claim, or error rate)
    4. Ask what data you can access, and who signs off on security

    Tip: Ask about the work, not the technology. Who does it today, how long it takes, what a mistake costs, and how they'd know it got better.

  2. 2Cloud, deployment and security
    They wrote: “Experience deploying software in regulated or secure environments (e.g., AWS GovCloud, Azure Government, FedRAMP, DoD Impact Levels, or classified and air-gapped networks) is highly desirable, though not mandatory.”

    A bank wants our product inside their own cloud account, with no data leaving it. How do you approach it?

    How to answer

    Why they ask: Self-hosted and private-cloud deployments are common in regulated industries.

    1. Learn their rules early: network limits, approved services, review process
    2. Package the product so it installs the same way each time (containers, Terraform)
    3. Plan how you'll get logs and updates without touching their data
    4. Run a test install with them before the real one

    Tip: Talk about the conversation with their security team as much as the setup.

  3. 3Integrations and APIs
    They wrote: “Lead the exploration and integration of large-scale data processing techniques to improve the reliability and effectiveness of our AI systems”

    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.

  4. 4LLMs, RAG and agents
    They wrote: “Innovate at the forefront of AI by designing, developing, and deploying AI-driven agentic systems that enhance Factory's core AI capabilities for federal missions”

    A customer wants a chatbot over their internal documents. How do you build it?

    How to answer

    Why they ask: RAG is the most common first project. They want the whole path, from messy files to answers people trust.

    1. Collect and clean the documents; handle permissions per user
    2. Split them into chunks, embed, and store with source links
    3. Retrieve, then answer with citations; say “I don't know” when retrieval is weak
    4. Build a test set of real questions with expected answers before launch

    Tip: Spend more time on the data and on testing than on the model.

  5. 5Ownership and working with customers
    They wrote: “Self-motivated and autonomous, with a proven ability to navigate ambiguous projects from conception to impactful deployment, ideally as part of a founding team, a new initiative, or a forward-deployed engineering group.”

    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.

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 Factory

Similar roles at other companies

Factory

Remote

Apply