
Forward Deployed Engineer
Posted Sep 30, 2026
The role in short
Embed with enterprise customers to lead technical onboarding, build production integrations and tooling, and drive product improvements from field feedback.
About Campfire
Campfire is an AI-native ERP for financial operations. Accounting teams and fractional CFO firms at fast-growing companies use it to run their close, revenue recognition, AP/AR, consolidations and reporting. Ember, our AI layer, works alongside accountants on the ledger itself.
You'll be the engineer embedded with our largest enterprise customers, owning their technical onboarding from kickoff to go-live. You write real code — integrations, scripts, tooling — and turn what you learn in the field into product improvements. You report into Engineering and work side by side with Sales, Implementation and Product.
What you'll do
- Lead technical onboarding for enterprise customers: scoping, integrations, configuration, go-live
- Support customers with complex or custom data migrations from legacy ERPs and GLs (NetSuite, Sage Intacct, QuickBooks)
- Build and configure integrations with banks, billing, payroll and HRIS systems
- Write production-quality code, scripts and tooling to speed up each rollout
- Be the customer's technical point of contact; run working sessions with controllers and finance leads
- Turn repeated field work into product: file clear specs, ship fixes, and build reusable onboarding tools
- Partner with Sales on technical discovery and solution design for late-stage enterprise deals
What you bring
- 4+ years as a software engineer, solutions engineer or FDE
- Strong in Python or TypeScript and SQL; comfortable with APIs, data pipelines and messy data
- Experience leading customer-facing technical projects end to end
- Clear communicator with both engineers and finance teams
- Ownership mindset: you get customers live, not just unblocked
- Willing to travel to customer sites as needed
Nice to have
- Accounting knowledge: GL, close process, revenue recognition (ASC 606)
- Hands-on ERP migration or implementation experience
- Background at a fintech, ERP or enterprise SaaS company
- Experience with enterprise security and compliance reviews
Success in the first year
- Enterprise customers go live on time
- Onboarding time drops through tooling you built
- Field feedback ships as product improvements
- Customers name you as a reason they chose to expand
Prep for this interview
5 questions likely to come up at Campfire, each matched to a line in this posting.
- 1Data and SQL
They wrote: “Strong in Python or TypeScript and SQL; comfortable with APIs, data pipelines and messy data”
Write a query that finds each customer's first and most recent order.
How to answer
Why they ask: A quick check that you're comfortable with grouping, joins and window functions.
- Clarify the tables and what counts as an order (cancelled ones?)
- Use MIN/MAX with GROUP BY, or ROW_NUMBER() if you need the whole row
- Handle ties on the same timestamp, and customers with no orders
- Explain how you'd test it on a few known customers
Tip: Say what you'd check in the data before writing the query: duplicates, time zones, nulls.
- 2Cloud, deployment and security
They wrote: “Experience with enterprise security and compliance reviews”
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.
- Start from your company's standard answers (SOC 2 report, past reviews)
- Answer clearly; don't oversell
- Bring in your security team for anything you're unsure of
- Keep the new answers for the next customer
Tip: Reuse past answers, flag honest gaps, and offer a call for the hard questions.
- 3Discovery and scoping
They wrote: “Lead technical onboarding for enterprise customers: scoping, integrations, configuration, go-live”
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.
- 4Integrations and APIs
They wrote: “Build and configure integrations with banks, billing, payroll and HRIS 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.
- 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.
- 5Ownership and working with customers
They wrote: “Ownership mindset: you get customers live, not just unblocked”
Tell me about something you shipped that broke in production.
How to answer
Why they ask: Everyone has broken production. They want to hear you own it and change something afterwards.
- What broke and who it affected
- How you found out and what you did in the first hour
- The root cause, said plainly
- What you changed so it can't happen the same way again
Tip: Pick a real one with a cost. Spend most of the answer on what you changed.
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.