Member of Deployed Staff
Posted 15 days ago
The role in short
Engineers embed with customers to solve complex technical problems by writing production code, building integrations, and delivering solutions using Factory's AI platform.
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 hiring Members of Deployed Staff to solve engineering problems alongside our customers. You’ll use Factory to deliver projects such as migrations, large-scale refactors, federated systems, agent harness engineering, and security remediation.
You’ll own scoped technical projects from discovery through implementation, validation, and handoff. That means understanding the customer’s systems, agreeing on what success looks like, writing and debugging code, and working through deployment constraints.
This is a hands-on engineering role with direct customer responsibility. We default to candidates with a technical engineering background who combine development skills with product judgment and exceptional technical communication.
What you will do and achieve
- Work with customer engineers and leaders to identify a concrete problem, define scope, and agree on success criteria.
- Build and deliver solutions in customer codebases and environments, using Factory to accelerate the work.
- Design integrations with customers’ development tools, infrastructure, and agent harnesses.
- Diagnose failures across unfamiliar codebases, build systems, and production environments.
- Validate changes through tests, evaluations, and rollout plans appropriate to the project.
- Own delivery milestones, communicate risks, and leave customers with working software and a clear operational handoff.
- Turn successful implementations into reusable tools, reference integrations, and guides.
- Bring reproducible issues and field-tested recommendations back to Factory’s Product and Engineering teams.
Qualifications
- A technical engineering background, typically in software, infrastructure, platform, mobile, or security engineering.
- Hands-on ability to read unfamiliar code, make changes, debug failures, and validate the result.
- Strong understanding of software development, systems design, testing, and production operations.
- Experience taking an ambiguous technical problem through to a delivered outcome.
- Clear communication with engineers and non-technical stakeholders, including explaining trade-offs and setting realistic expectations.
- A deep passion for working with customers and delivering exceptional outcomes.
- Additional experience in tech lead or product management roles is a plus.
Nice to Have
- Migrations: Moving applications, databases, cloud infrastructure, ERP systems, or legacy platforms, including validation and cutover.
- Refactors: Making substantial changes to complex codebases, architecture, frameworks, or APIs while preserving required behavior.
- Federated systems and on-premises deployments: Helping customers build federated systems within complex enterprise architectures, working across infrastructure, identity, networking, and security boundaries.
- iOS / Android: Shipping mobile applications, with experience in platform-specific development, build systems, testing, and release workflows.
- Federal / public sector: Delivering technical systems in government environments and working through their security, authorization, and operational requirements.
- Agent harness engineering: Building agent runtimes or integrating agents into existing systems, including tools, orchestration, execution environments, and evaluations.
- Security: Application or infrastructure security, vulnerability remediation, secure development workflows, or validating security fixes.
We’re interested in what you personally built, the constraints you worked through, and how you verified that it worked.
Location and travel
This is a hybrid role. Based in San Francisco, New York, London, Washington, DC, Australia, or Singapore. Customer travel is typically about once a month, mostly within your region.
Prep for this interview
5 questions likely to come up at Factory, each matched to a line in this posting.
- 1Cloud, deployment and security
They wrote: “Federated systems and on-premises deployments: Helping customers build federated systems within complex enterprise architectures, working across infrastructure, identity, networking, and security boundaries.”
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.
- Learn their rules early: network limits, approved services, review process
- Package the product so it installs the same way each time (containers, Terraform)
- Plan how you'll get logs and updates without touching their data
- Run a test install with them before the real one
Tip: Talk about the conversation with their security team as much as the setup.
- 2Discovery and scoping
They wrote: “Work with customer engineers and leaders to identify a concrete problem, define scope, and agree on success criteria.”
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.
- Score each request by business value and by effort, with the customer in the room
- Pick one item that proves value fast and unblocks later work
- Write down what's out of scope so it doesn't creep back in
- 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.
- 3Integrations and APIs
They wrote: “Design integrations with customers’ development tools, infrastructure, and agent harnesses.”
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.
- Find who owns the system and get read access to a test environment
- Watch real traffic or logs to learn the data shapes
- Build a thin adapter with logging around every call
- 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.
- 4Ownership and working with customers
They wrote: “Experience taking an ambiguous technical problem through to a delivered outcome.”
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.
- The project and why requirements kept moving
- What you did to pin them down (short demos, written decisions)
- The trade-offs you made to keep shipping
- The result, with a number if you have one
Tip: Show how you reduced the change, beyond how you coped with it.
- 5Travel
They wrote: “This is a hybrid role. Based in San Francisco, New York, London, Washington, DC, Australia, or Singapore. Customer travel is typically about once a month, mostly within your region.”
How do you handle being on the road with customers for weeks at a time?
How to answer
Why they ask: Many FDE roles involve regular travel. They check you know what you're signing up for.
- Your past travel or on-site experience
- How you stay productive away from the team
- What travel level works for you, said plainly
Tip: Be honest about what works for you. A mismatch here hurts both sides later.
Not the one? Get the next one by email
New roles land here every day. Pick what you want to hear about.
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.