Forward Deployed Engineer - EMEA & APAC
Posted 11 days ago
The role in short
Embed with Western European customers to design, build, and ship production-grade AI agents and workflows using SpaceXSI's Grok models and infrastructure.
SpaceX was founded under the belief that a future where humanity is out exploring the stars is fundamentally more exciting than one where we are not. Today, SpaceX is actively developing the technologies to make this possible, with the ultimate goal of making life multiplanetary and expanding consciousness to the stars.
SpaceXSI is building Super Intelligence to help humanity understand the universe. Our teams are building the full Super Intelligence stack: from our Colossus supercomputers, to Grok models, to our suite of applications, including Grok Bot, Grok Build, Grok Imagine, Grok Voice, and X. We're creating a powerful flywheel where more compute trains better models, better models power more useful products, and what we learn from people using those products shapes what we build next.
FORWARD DEPLOYED ENGINEER - WESTERN EUROPE
You embed directly with customer teams as the engineer on the ground: own an outcome, ship a production-grade SpaceXSI system that still runs after you leave, and become the critical technical feedback loop from the field back to product engineering. The work is the project. One week you might take a messy business workflow and put a production agent on it: pick the use case, stand up the architecture, wire it into the customer's auth, data, and tools, then harden it with evals until the team actually uses it. Another week you might live in a customer's repo and delivery system and ship an agent-powered path for a migration, a PR review loop, or an incident-to-fix flow, behind tests, review, and rollout rather than in a chat sidebar.
RESPONSIBILITIES:
- Lead discovery with the customer: orient in their codebases and workflows, find the real bottleneck and the use case worth building, and define clear success metrics
- Design and ship production agents, AI applications, and coding-agent workflows on Grok and our models, on live business processes and inside the customer’s engineering org
- Get a first version live in days, then harden it over weeks with rollout, monitoring, and iteration from real usage
- Own production quality: tracing, evals, debugging model or delivery failures, and latency and cost tradeoffs
- Build the systems around the model (tools, MCP servers, retrieval, rules, skills, CI gates, and evals) and integrate them into the customer’s auth, data, workflow, and delivery systems; decide when prompting, architecture, data, process, or a model change is the right lever
- Measure the outcome that matters (revenue, cost, hours saved, error rate, cycle time, escaped defects), not seat adoption
- Work directly with Staff+, platform, and domain leaders, going deep in their systems while communicating clearly about tradeoffs and results
- Leave the customer team able to run what you built, and turn what you learn into reusable patterns and improvements to SpaceXSI products
BASIC QUALIFICATIONS:
- You have 5+ years of experience in software engineering, machine learning engineering, or data science
- You’ve owned a customer or operator outcome, not just a slide or a prototype, and can turn a fuzzy problem into a scoped, shipped system
- You’ve built and owned AI-native workflows or agents in production (using Python, JavaScript/TypeScript), and debugged real production failures (model, tool, data, pipeline, or delivery path)
PREFERRED SKILLS AND EXPERIENCE:
- 2+ years in a customer-facing role, leading discovery conversations and being accountable for outcomes for external stakeholders
- Hands-on depth in several of: agents and tool-calling, eval harnesses, retrieval and context systems, CI/CD or developer platforms, and AI-native coding workflows in a real repo
- Experience as a forward-deployed, solutions, or platform engineer embedded with customers, or as a founding engineer who owned an AI product end to end
Prep for this interview
3 questions likely to come up at Cursor, each matched to a line in this posting.
- 1Discovery and scoping
They wrote: “2+ years in a customer-facing role, leading discovery conversations and being accountable for outcomes for external stakeholders”
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.
- 2Coding
They wrote: “You’ve built and owned AI-native workflows or agents in production (using Python, JavaScript/TypeScript), and debugged real production failures (model, tool, data, pipeline, or delivery path)”
Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.
How to answer
Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.
- Read with a proper CSV parser; check the header first
- Validate each row and collect errors, not crash on the first one
- Send in batches with retries and a clear report at the end
- Write one or two quick tests for the parsing
Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.
- 3LLMs, RAG and agents
They wrote: “Own production quality: tracing, evals, debugging model or delivery failures, and latency and cost tradeoffs”
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.
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.

