
Forward Deployed Engineer Intern
Posted yesterday
The role in short
Build and deploy AI agents and integrations for Fortune 500 procurement systems while working directly with customers in a live environment.
Forward Deployed Engineer Intern (all genders) – Munich
Procurement touches every company, every product, every euro spent, and it’s still one of the most traditional spaces out there. We’re rebuilding it with AI.
At Lio, we’re building the AI workforce for procurement. We lead the largest AI deployments in procurement, at Fortune 500 companies around the globe, and we’re growing like few companies ever do. We need exceptional engineers to build what comes next, and we want you to start with us early.
What this internship really is
- AI-native, from the ground up. No pre-AI SaaS legacy. You help build AI products and agents from scratch, from agents across the whole procurement process to voice avatars in strategic negotiations.
- Wired into real enterprise systems. You work on connecting AI agents to the systems that run Fortune 500 companies: SAP, Oracle, Coupa, Databricks, Snowflake. Millions of orders, contracts and suppliers, live.
- Real responsibility from day one. You take ownership of concrete pieces of real customer projects, from integrations and data pipelines to agent configurations and debugging in live environments, with experienced Forward Deployed Engineers at your side.
- Built for one customer, live at many. You help design solutions for a customer’s problem and see how they become part of the product everyone runs on.
- Agentic speed. We ship to production every week, often every day, and fix fast. High intensity, and the steepest learning curve you’ll find.
- No boundaries. You work with the latest frontier models, without limits, and use any means to reach your goals as fast as possible.
- More than an engineer. You get a look at the whole picture: customer workshops, demos, go-lives and conversations with Fortune 500 teams. Where you want to grow is up to you.
What you should know before you apply
- We’re in the office five days a week.
- This is not a 9 to 5 job. We grow faster than our processes can keep up, and there are weeks when a project needs everything you have. In return, you’ll learn more in a few months than in years anywhere else.
What you bring
- You build with AI. You use AI coding tools and agents daily, have solid coding fundamentals, and are comfortable with APIs and data. Personal projects, hackathons, open source or previous internships count. Show us what you’ve built.
- Ownership and curiosity. You grab opportunities instead of waiting for them, teach yourself whatever the problem needs, and don’t give up when something breaks.
- Customer mindset. You want to understand a problem before you solve it, you enjoy working with people, and you hold your work to a high bar.
- You’re currently enrolled in Computer Science, Business Informatics, Engineering or a similar field.
- Fluent English is a must, German is a plus.
Procurement knowledge or experience with ERP systems such as SAP or Oracle is a plus, but not a requirement.
Why Lio
Lio is backed by Andreessen Horowitz (a16z) and built at Y Combinator, with offices in Munich and New York. We’re winning, and every employee is a shareholder, so you win with us.
You’ll work with some of the smartest, most driven and unconventional people in Europe, and no two weeks look the same: one week a16z drops by for a lecture, the next you’re on a flight to a client.
On top of that, you get an unlimited AI coding budget, the newest tools within a week of release, free breakfast and dinner, an office gym, a subsidized Wellpass or Deutschlandticket, and events from hackathons and game nights to Wiesn.
Sounds like you? Let’s talk.
Prep for this interview
2 questions likely to come up at Lio, each matched to a line in this posting.
- 1LLMs, RAG and agents
They wrote: “Wired into real enterprise systems. You work on connecting AI agents to the systems that run Fortune 500 companies: SAP, Oracle, Coupa, Databricks, Snowflake. Millions of orders, contracts and suppliers, live.”
A customer wants a chatbot over their internal documents. How do you build it?
How to answer
Why they ask: RAG is the most common first project. They want the whole path, from messy files to answers people trust.
- Collect and clean the documents; handle permissions per user
- Split them into chunks, embed, and store with source links
- Retrieve, then answer with citations; say “I don't know” when retrieval is weak
- Build a test set of real questions with expected answers before launch
Tip: Spend more time on the data and on testing than on the model.
- 2Ownership and working with customers
They wrote: “Ownership and curiosity. You grab opportunities instead of waiting for them, teach yourself whatever the problem needs, and don’t give up when something breaks.”
Tell me about something you shipped that broke in production.
How to answer
Why they ask: Everyone has broken production. They want to hear you own it and change something afterwards.
- What broke and who it affected
- How you found out and what you did in the first hour
- The root cause, said plainly
- What you changed so it can't happen the same way again
Tip: Pick a real one with a cost. Spend most of the answer on what you changed.
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.

