Forward Deployed Engineer
Posted 26 days ago
The role in short
Embed with customers to lead technical discovery, build migration tooling and demo environments, and write production code to integrate Xata's Postgres infrastructure into their workflows.
About Xata
Xata builds Postgres infrastructure for agentic workloads. We let teams spin up isolated database branches in seconds so every AI agent (and every developer) can safely experiment, test, and run workflows against production-like data without putting production at risk.
We've raised $35M (Series A led by Index Ventures and Redpoint), backed by founders like Guillermo Rauch (Vercel), Shay Banon (Elastic), and Neha Narkhede (Confluent), with years of runway ahead.
We're a remote-first team focused on making branching, data movement, and lifecycle management feel fast and dependable for modern software development.
What You'll Be Doing
We're hiring our first Forward Deployed Engineer to be the technical force behind how customers evaluate, adopt, and succeed with Xata. You'll partner with our Head of GTM across the deal cycle and then keep going past the handshake: leading technical discovery, designing proof-of-value engagements, and guiding teams through real migrations onto Xata.
This is a hybrid pre-sales and technical delivery role, and it is hands-on by design. You'll run the discovery, build the demo, write the migration tooling, and debug the production edge case with the customer. As our first dedicated FDE, you won't inherit a playbook; you'll write it: defining how we engage technically, what "good" looks like, and the tooling and patterns the next FDEs will run on.
In this role, you will
- Lead technical discovery with developers, platform teams, and AI-native companies. Get to the root of what they're actually trying to build, not just the feature they asked about.
- Design and run proof-of-value engagements that prove Xata against the customer's real data and real constraints, then own them to a clear technical outcome.
- Guide and execute database migrations onto Xata, using our open-source tooling (pgroll, pgstream) and building whatever is missing to make the path smooth.
- Build the assets that make us credible: demo environments, reference architectures, migration scripts, and integration patterns for branching, replication, and lifecycle management.
- Be the technical voice in the deal cycle. Partner closely with GTM, handle the hard technical objections, and earn trust with the engineers in the room.
- Embed with customers and write code with them. Outcomes over artifacts: a working integration beats a polished slide every time.
- Close the loop with Product and Engineering. You'll see what's breaking and what's missing before anyone else, and you'll turn that field signal into a sharp, prioritized stream of feedback to our Data Plane, Control Plane, and Frontend teams.
- Set the technical bar and build the function: the playbooks, demo infrastructure, and engagement model that the FDE team will scale on as we grow.
About You
- You are a strong, hands-on engineer who is genuinely energized by being in front of customers. Both halves matter.
- You are a generalist problem-solver. Full-stack, data plumbing, scripting, debugging, infrastructure: you reach for whatever the problem needs and figure out the rest fast.
- You are deeply credible with engineers and comfortable in the weeds of databases, SQL, APIs, distributed systems, and developer workflows.
- You thrive in ambiguity and high ownership. You walk into an unclear, high-stakes situation, find the real problem, and drive it from idea to something shipped and adopted.
- You have a bias to build. When something is missing, you make it, rather than filing a request and waiting.
- You communicate clearly in writing and work effectively in a remote, async environment.
- You're comfortable being the first and only person in this seat, building the function and not inheriting it.
Nice to Have
- Experience as a forward deployed, solutions, or sales engineer, or a consulting background with real delivery ownership.
- Experience with AI agents, agentic workflows, or AI-native developer tooling.
- Deep familiarity with PostgreSQL, database migrations, replication, or PostgreSQL-adjacent products.
- Background in open-source products or communities.
- Experience with both product-led, self-serve motions and sales-assisted ones.
Working at Xata
- We're stable. We've raised $35M and have years of runway.
- We're remote-first and have more than a decade of experience building distributed teams.
- We work asynchronously and keep meetings to a minimum.
- You'll have significant autonomy, ownership, and the opportunity to shape both the product and the company.
- We're open source at our core and deeply care about our developer community.
- Small team, large impact.
- Opportunity to shape the future of Postgres infrastructure in the agent era.
- Xata is female-founded and has an all-female board of directors.
What We Offer
- Meaningful equity in a company defining a new category.
- Competitive salary and a compensation package that reflects the role.
- A real seat at the table. You'll shape how we engage customers, not just execute it.
- 30 vacation days, plus local public holidays, and a culture that expects you to use them.
- Comprehensive health insurance.
- Remote-first, async-first. Work where you do your best work.
- Budget for a co-working space of your choice.
- Learning budget for conferences, courses, and books.
- Two company off-sites per year, with partners and children welcome.
Prep for this interview
5 questions likely to come up at Xata.io, each matched to a line in this posting.
- 1LLMs, RAG and agents
They wrote: “Experience with AI agents, agentic workflows, or AI-native developer tooling.”
How do you know an LLM feature is good enough to ship?
How to answer
Why they ask: Evals are what separate a demo from production. Many roles list them by name.
- Write 50–200 real examples with expected outcomes, with customer experts
- Agree on a pass bar and the errors that are never acceptable
- Score automatically where possible; review a sample by hand
- Re-run on every prompt or model change, and watch live traffic after launch
Tip: Describe a test set built with the customer, a pass bar agreed up front, and checks that run on every change.
- 2Ownership and working with customers
They wrote: “You thrive in ambiguity and high ownership. You walk into an unclear, high-stakes situation, find the real problem, and drive it from idea to something shipped and adopted.”
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.
- 3Discovery and scoping
They wrote: “Lead technical discovery with developers, platform teams, and AI-native companies. Get to the root of what they're actually trying to build, not just the feature they asked about.”
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.
- 4Integrations and APIs
They wrote: “Build the assets that make us credible: demo environments, reference architectures, migration scripts, and integration patterns for branching, replication, and lifecycle management.”
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.
- 5Data and SQL
They wrote: “You are deeply credible with engineers and comfortable in the weeds of databases, SQL, APIs, distributed systems, and developer workflows.”
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.
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.