Careers
Forward Deployed Engineer
Deploy and operate AI systems inside real operational environments. Build integrations, debug pipelines and work directly with clients.
- Contract
- Full time
- Based in
- Paris, Barcelona or Casablanca
- Internship
- 6 months, Paris, Barcelona or Casablanca
- Apply
- By email, with your resume and a project you are proud of
What a Forward Deployed Engineer does at Mirage
Forward Deployed Engineer is the core role at Mirage. Forward Deployed Engineers operate at the boundary between systems and reality: you deploy, monitor and improve AI workflows inside real operations.
Mirage builds and runs AI agents for complex operations in logistics, construction, mining and manufacturing. The agents run inside each client's environment, connected to the systems already in place, and they are built and operated by the engineers who deploy them. A person on the client's side reviews the exceptions and signs off.
You won't just write code. You'll understand operations, earn trust with clients and deploy systems that change how work gets done.
How every deployment runs
The same engineers carry a workflow from the first observation to production, then move on to the next one.
The Mirage deployment method
Five steps, in this order, for every deployment in every sector: Observe, Map, Build, Run, Expand.
Observe
Engineers spend time with the operational team before writing anything, to see how the work is actually done.
What it settles
- How the team really works
- Where friction appears
- Which decisions need a person
Map
Workflows, exceptions, data sources, manual checks and escalation points are mapped with the team.
What it settles
- The workflow to start with
- Its exceptions
- Its systems and data sources
Build
The system is built around the constraints observed on site, not around an idealized process diagram.
What it settles
- Connectors into the systems in place
- The client's own rules
- What goes to a person
Run
It runs in production with human supervision and feedback loops from day one.
What it settles
- Exceptions reviewed by the team
- Rules adjusted on live data
- Who signs off
Expand
Once a workflow is trusted, the same team moves to the next one.
What it settles
- The next workflow
- The same engineers
- The same platform
What a week can look like
No two weeks are the same. A typical week may include:
- Debugging a document extraction pipeline failing on scanned invoices
- Sitting with logistics teams to understand their actual workflow
- Building a custom integration between our platform and a client's TMS
- Presenting deployment results to C-level decision makers
Engineers frequently travel to operational sites depending on projects.
What the team has put into production
- An email to SAP Business One order pipeline for Biodéal, an organic dairy distributor: a median of 48 seconds from order email to order ready in SAP Business One.
- Two quoting agent environments connected to the TMS of OFRET Groupe, a freight forwarding group: more than 90% of standard quote requests answered automatically.
- A piping takeoff module for John Cockerill's Morocco operations that reads isometric drawings: 80 to 90% less time spent on piping takeoff.
- Takeoff, bid pricing and drawing consistency agents for OCBM, a construction company in Casablanca: three agents in production, every quantity traceable to its source drawing.
- Five systems across freight, fuel, mining and fleet at Transwin, a logistics operator in Morocco, grown from one document workflow.
What we look for
- Technical depth
- Strong fundamentals in software engineering, data systems or AI.
- You can debug a broken pipeline, build a custom integration or optimize a model.
- Operational curiosity
- You want to understand how real operations work, not just the theory.
- You ask how it actually runs before you build anything.
- Bias for building
- You ship code. You deploy systems. You move forward.
- You prefer working prototypes over perfect architectures.
- Comfort with ambiguity
- You can operate without clear specs, structured roadmaps or predefined playbooks.
- You figure things out as you go.
How the team works
- Ownership
- You own the outcome, not just the output. If a deployment fails, you debug it. If a client doesn't understand, you explain it.
- Operational reality
- We study real operations before we build, deploy inside real workflows rather than demos, and measure success by operational outcomes.
- Small teams, high trust
- Small, autonomous teams and direct communication. You talk directly to founders and clients.
- Speed over process
- Ship fast, learn fast, improve fast. Process exists to serve shipping, not the reverse.
Where the role is based
- Paris
- Barcelona
- Casablanca
Mirage has offices in Paris, Barcelona and Casablanca, and around fifteen people, all engineers. Engineers frequently travel to operational sites depending on projects. Mirage's clients are in France, Spain, Morocco, Egypt, Saudi Arabia and the United States.
Openings for this role
Forward Deployed Engineer
Paris: Full time
Forward Deployed Engineer
Barcelona: Full time
Forward Deployed Engineer
Casablanca: Full time
Forward Deployed Engineer Intern
Paris, Barcelona or Casablanca: 6 months
Software, AI and GTM engineering roles are listed on the careers page. See all open roles
How to apply
We care more about what you've built than where you worked. Send us:
- Your resume or LinkedIn profile
- A short note about a project you're proud of
- Links to code, systems or work you've shipped (if available)
Email:
FAQ
Is Mirage hiring Forward Deployed Engineers?
Yes. The careers page lists Forward Deployed Engineer roles, full time, in Paris, Barcelona and Casablanca, and a six-month Forward Deployed Engineer internship in the same three cities.
What does a Forward Deployed Engineer do at Mirage?
Deploys and operates AI systems inside real operational environments: builds integrations, debugs pipelines and works directly with clients. Every deployment follows the same five steps: Observe, Map, Build, Run, Expand.
Do Forward Deployed Engineers travel?
Yes. Engineers are based in Paris, Barcelona or Casablanca and frequently travel to operational sites depending on projects.
What should an application include?
Your resume or LinkedIn profile, a short note about a project you're proud of, and links to code, systems or work you've shipped if you have them. Mirage cares more about what you've built than where you worked.
How do I apply?
By email, with the Apply button on this page or on the careers page. There is no form to fill in.