This list contains only the countries for which job offers have been published in the selected language (e.g., in the French version, only job offers written in French are displayed, and in the English version, only those in English).
Forward Deployed Engineers turn what our models can do into things customers actually rely on. You embed with a customer, learn their workflow, define the problem with them, and build the system that solves it — in production, with their data, with their constraints. You own the relationship and the code. When something is missing in our platform, you build around it. When the same gap shows up across customers, you work with R&D to turn that pattern into product. This is engineering at the edge, where ambiguity is the default and 'what should we build?' is yours to answer.
Job Responsibility
Work directly with customers to understand their workflows, constraints, and goals
Define the problem — there is no PRD waiting for you
Build production systems on Luma's APIs, models, and internal tools
Prototype, ship, iterate, and maintain systems that customers depend on inside of real environments with real data
Own projects end-to-end, from first conversation to deployed system
Identify the patterns worth productizing and feed them back to platform and R&D
Requirements
Bachelor's degree in Computer Science or equivalent practical experience
2+ years of professional software engineering experience
Strong proficiency in at least one general-purpose language (Python, TypeScript, Go, or similar)
Experience building and shipping software end-to-end
Ability to work across the stack and learn unfamiliar systems quickly
Ability and interest to travel as needed to client sites
Nice to have
A track record of shipping real systems with real users, not just completing assigned tasks
High agency and strong prioritization skills — you can figure out the core problem and move
Comfort defining your own path when there isn't one
Evidence of working directly with customers or users, and translating what you heard into what you built
Clear communication, including explaining a technical decision to a non-technical stakeholder