Forward Deployed Engineer
This is the employer's own posting, not a copy on a job board.
What we know
Is it still open?
Confirmed still open
Last checked 8h ago — checked against the employer's own applicant tracking system, which is the company answering directly.
We re-read the employer's own applicant tracking system and the posting was still there. That is the company answering directly.
How old is it?
Posted 52d ago
The date the source published, not the day we noticed it (2026-07-24). Last seen at its source just now.
Is it remote?
Remote, INT
That is the location the employer filed this posting under. Quoted as written — we do not re-word the source's own location.
Who may apply?
Munich
The description states no restriction of its own. This is the source's own tag.
Pay not stated
Similar roles pay €102.5k–123.6k/yr
Middle 50% of 16 listings that do state pay — Engineering · all levels · Germany · EUR/year. This employer has published no salary; this is what comparable listings we hold disclose, never converted between currencies or periods. How this is calculated.
Skills named in the ad
Recognised terms only, from a fixed vocabulary — this is what CV matching compares against.
Carried by 1 source
-
ashby employer's own board first seen 32d ago · last seen just now
- location not stated
The listing
Forward Deployed Engineers turn what Luma's models can do into systems customers actually rely on. You embed with a customer, learn their workflow, define the problem with them, and build the production system that solves it, with their data and their constraints. You own both the relationship and the code.
This is engineering at the edge, where ambiguity is the default and "what should we build?" is yours to answer. It's built for people who've already been the single point of ownership on a hard problem: a technical founder, the engineer who flew out and rebuilt a customer's workflow, a consultant who actually wrote the system. If you need a PRD and a well-defined ticket queue, this isn't it.
What You'll Own
Work directly with customers to understand their workflows, constraints, and goals, and define the problem yourself.
Build production systems on Luma's APIs, models, and internal tools.
Prototype, ship, iterate, and maintain systems customers depend on in real environments with real data.
Own projects end to end, from first conversation to deployed system.
Build around platform gaps when something's missing, and feed recurring patterns back to platform and R&D to productize.
Use AI to accelerate implementation, while the core of the work stays engineering judgment: what to build and how to make it reliable.
First 90 Days
One way the first 90 could unfold.
Days 1–30 — Immerse & Diagnose: Embed with a first customer, learn their workflow, and define the real problem.
Days 30–60 — Ship & Validate: Build and deploy a production system they actually use.
Days 60–90 — Scale & Systemize: Spot the pattern worth productizing and work with R&D to turn it into platform.
What You Bring
2+ years of professional software engineering, with software shipped end to end.
Strong proficiency in at least one general-purpose language (Python, TypeScript, Go, or similar).
Ability to work across the stack and learn unfamiliar systems quickly.
Bachelor's in Computer Science or equivalent practical experience.
Willingness to travel to client sites as needed.
Nice to Have
A track record of shipping real systems with real users, not just assigned tasks.
High agency and strong prioritization: you find the core problem and move.
Comfort defining your own path when there isn't one.
Evidence of working directly with customers and translating what you heard into what you built.
Clear communication, including explaining a technical decision to a non-technical stakeholder.
Luma's mission is to build unified general intelligence that can generate, understand, and operate in the physical world. We believe multimodality is critical for intelligence — the next step beyond language models comes from vision. Luma is an equal opportunity employer.