
Forward Deployed Engineer, Integrations
Posted Oct 1, 2026
The role in short
Owns customer integrations between the ION Factory OS and manufacturers' ERP/PLM systems, from discovery and build to running them in production.
Why this role matters
Our customers build rockets, satellites, eVTOLs, clean energy systems, robots, and autonomous vehicles. First Resonance builds the ION Factory OS — the operating system their factories run on.
Almost no factory runs on ION alone. Parts live in a PLM system, purchase orders in an ERP, costs in finance, and a surprising amount of critical process in spreadsheets and homegrown tools. Integrations are the difference between ION being the system of record for how something gets built and ION being one more tab. Right now that work is the single biggest lever on how fast a customer gets real value from us — and it needs an owner.
You will own it end to end: discovery, architecture, implementation, go-live, and keeping it running. Sometimes you will write the code. Sometimes you will direct an internal engineer or an external systems integration partner. Either way the outcome is yours. Over time you will turn what you learn into reusable connectors, reference architectures, and platform improvements, so the tenth integration costs a fraction of the first.
You will work day to day with Forward Deployed Engineering, Customer Success, Sales, Product, and Engineering, and directly with customer engineering and IT teams.
What you’ll own
- Customer integrations, end to end: Discovery and requirements through architecture, estimation, build, test, go-live, documentation, and handoff.
- The translation layer: Turn how a customer actually manages parts, BOMs, purchase orders, receipts, inventory, work orders, quality, and engineering changes into a design that holds up in production.
- Build-versus-partner calls: Decide when we implement directly, reuse an existing connector, enable the customer’s team, or bring in a systems integration partner — then scope the work, set acceptance criteria, review the quality, and hold delivery to it.
- Production reliability: Monitoring, alerting, retries, reconciliation, auditability, and incident response for integrations customers depend on every shift.
- Reusable leverage: Convert one-off implementations into connectors, reference architectures, test harnesses, runbooks, and documentation.
- Platform feedback: Find the recurring gaps in ION’s APIs, eventing, and data model, and work with Product and Engineering to close them for good.
What we’re looking for
- 6+ years in customer-facing or delivery-oriented engineering — solutions architecture, integration engineering, forward deployed engineering, or technical consulting — where you shipped production code yourself.
- You have taken at least one complex enterprise integration from a vague first conversation all the way to running reliably in production.
- Real depth in API-based integration: REST or GraphQL, webhooks, auth protocols, async processing, and data transformation — plus the distributed-systems instincts that go with it, including idempotency, ordering, retries, reconciliation, and observability.
- You are comfortable sitting with a customer’s manufacturing or IT team, hearing an ambiguous process description, and leaving with a scoped technical plan.
- You write and speak clearly enough to explain an architecture, a tradeoff, and a risk to both a staff engineer and a VP of Operations.
Nice to have
- Manufacturing systems experience — ERP, PLM, MES, procurement, finance, or warehouse platforms. Names we run into often: NetSuite, SAP, Dynamics 365, Teamcenter, Arena, Duro, SolidWorks PDM.
- Integration platforms or middleware such as Prismatic, Boomi, MuleSoft, Workato, or Informatica.
- Connectors, SDKs, or developer documentation you built that other people actually used.
- Comfort with enterprise security and deployment constraints: SSO/OAuth, audit requirements, regulated or on-premise environments, restricted networks.
- Background in aerospace, defense, or advanced manufacturing.
Benefits & Perks
- Health Insurance; medical, vision, dental, & life insurance.
- Paid Parental Leave.
- Employee Stock Option Plan.
- Team outings, group lunches, open office, happy hours.
- Paid holidays, sick days.
- Flexible Friday and PTO.
- 401K.
First Resonance is an equal opportunity employer dedicated to building an inclusive and diverse workforce.
First Resonance participates in E-Verify. As part of our onboarding process, a new hire's Form I-9 information will be shared with the federal government to confirm they are authorized to work in the U.S.
Pay is based on factors such as (but not limited to) scope and responsibilities of the position, candidate's work experience and skillset, and location.
First Resonance accelerates the speed and reliability of hardware development for companies manufacturing the next generation of hardware products. This includes space exploration, electric airplanes, autonomous vehicles, nuclear reactors, robotics, and more. We are a group of software, hardware, and manufacturing engineers that are bringing the best of modern UX and data science to an industry that has been overly rigid in its innovation. We are removing the barriers preventing radical advancement by providing tools to manufacturing engineers and operators to move information more freely, collaborate with their teams more easily, and use the power of data to predict problems and provide insights that result in better hardware quality and delivery.
Prep for this interview
5 questions likely to come up at First Resonance, each matched to a line in this posting.
- 1Discovery and scoping
They wrote: “Customer integrations, end to end: Discovery and requirements through architecture, estimation, build, test, go-live, documentation, and handoff.”
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.
- Map the current process: who touches a claim, in what order, with which systems
- Find the slowest or most error-prone step and ask what it costs them
- Agree on one measurable goal (for example time per claim, or error rate)
- 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.
- 2Integrations and APIs
They wrote: “Comfort with enterprise security and deployment constraints: SSO/OAuth, audit requirements, regulated or on-premise environments, restricted networks.”
How would you set up single sign-on for a large customer?
How to answer
Why they ask: SSO (SAML or OAuth/OIDC) is a common first task in enterprise deals and a common source of delays.
- Confirm their identity provider (Okta, Entra ID, Google) and protocol
- Exchange metadata and test in a staging tenant first
- Map user groups to roles in your product
- Plan for user removal: what happens when someone leaves the company
Tip: Mention the people involved, and the protocol second. The customer's identity team usually controls the timeline.
- 3Data and SQL
They wrote: “Platform feedback: Find the recurring gaps in ION’s APIs, eventing, and data model, and work with Product and Engineering to close them for good.”
The customer's data is spread across five systems that disagree. How do you get one clean view?
How to answer
Why they ask: Real deployments rarely have one source of truth. They want a practical approach, not a perfect one.
- List each system and what it's the best source for
- Pick matching keys and decide how to handle records that don't match
- Load into one place with clear rules, and keep the raw copies
- Show the customer the mismatches; they often fix the source
Tip: Name the system the business trusts most for each field, and get the customer to agree.
- 4Coding
They wrote: “6+ years in customer-facing or delivery-oriented engineering — solutions architecture, integration engineering, forward deployed engineering, or technical consulting — where you shipped production code yourself.”
How do you keep quality high when you ship fast at a customer site?
How to answer
Why they ask: Speed is the job, but broken code at a customer is costly. They want your guardrails.
- Tests for the parts that touch customer data or money
- Code review even when it's fast, ideally by someone on the product team
- Feature flags and an easy way to roll back
- Clean up the shortcuts in the next release, and write them down
Tip: Name the few checks you never skip, and what you skip on purpose.
- 5Ownership and working with customers
They wrote: “You are comfortable sitting with a customer’s manufacturing or IT team, hearing an ambiguous process description, and leaving with a scoped technical plan.”
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.
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.

