Forward Deployed Engineer; German-speaking

The Role

You're the bridge between a customer's operational chaos and our product. You embed with logistics teams like freight forwarders, carriers, and 3PLs, learn how their operations actually run, and turn that mess into AI Workers that handle it end-to-end.

Part engineer, part product owner, part the person a customer calls when something has to work by tomorrow. You own the outcome from the first onboarding call to a system running live on their inbox and phone lines. You write the code, design the workflow, sit across from the ops manager, and ship.

This isn't a support role, and it isn't a pure backend role. It's the most direct line between real customer pain and what we build.

• Embed with logistics operators, learn their workflows, and map the chaos into clear system design.
• Own onboarding end-to-end. Take new customers from first call to AI Workers running in production.
• Integrate with the messy reality of the enterprise logistics stack: TMS, ERP, email, telephony, EDI, SFTP, event queues, including the undocumented parts.
• Build fast across the stack (Python/FastAPI backend, front-end, LLM and agent workflows) to make each deployment actually fit the customer.
• Tune the AI. Prompts, agent workflows, evals, whatever it takes to make the Worker reliable on live operations.
• Feed what you learn on the ground straight back into product and technical direction.
• Own the outcome. If it's not working for the customer, you make it work.

• You take full ownership, from a customer's problem to a deployed, working system. No tickets, no waiting for a spec.
• You move fast and iterate, and you know when to shift from a quick fix to something robust and scalable.
• Você build with AI, not just around it. AI native development is how you think. Oops sorry, that phrase is mis‑typed; the correct text is "AI-native development is how you think."
• You can sit with a non-technical ops manager and a database schema in the same hour, and be clear with both.
• You're comfortable with ambiguity and energized by being close to the customer.
• You want to be in the room. Munich office, in person. This isn't a 9-to-5, and it isn't remote.

• Strong software engineering fundamentals:
  Python, JavaScript/Type Script, SQL, REST APIs.
• Hands‑on experience integrating with someone else's stack: APIs, external systems, and the messy data in between.
• LLMs in production: prompt engineering, API integration, evals, agent tooling.
• Familiarity with enterprise data flows, event‑driven architectures, or background job processing.
• Native or fluent German, plus the communication skills to be trusted in front of customers.
• Very big bonus: logistics, supply chain, or freight domain experience.

We move fast. Expect a decision within a week.

• Application. Send your CV and the one thing we care about most: an AI coding session. A transcript or log from Claude Code, Cursor, Codex, or whatever tool you build with. It can be .md, .txt, several sessions, or a hosted link. We want to see how you actually work.
• Online interview. One conversation covering technical depth, how you think about customers, and team fit. No multi‑round gauntlet.
• Technical session (60 min). Build a small service from scratch with an AI assistant (we provide it). We watch how you work, then you walk us through your decisions.
• Decision. Feedback and a potential start within a week.