Forward Deployed Engineer

We are 13 people. We run Talonic in production for energy utilities, pharma distribution, automotive and US logistics. The platform works. What it takes to win each account is someone who can go deep on a real, messy customer problem and come back with a system that runs.

You are not handed tickets. You are handed a problem, a customer, and the platform — and you are expected to come back with something that works. We care much more about what you can ship than what your CV says you are.
Our strongest builder came to us as a product manager.

What you’ll do

Understand a messy real-world process — contracts, invoices, scanned engineering diagrams, forty-year-old archives — and design the schema that makes it queryable.

From data model to working extraction. You design it and you build it — not separate people.

Validation rules, normalisation, delivery into SAP, Ivalua, Dynamics, Snowflake — whatever the customer runs. The integration is part of the job.

Prototype fast with AI tooling, then harden what survives contact with production. The prototype is not the delivery.

Enterprise stakeholders, procurement, IT security, a skeptical CFO. You can hold the room and you can explain the decision they are paying for.

Who you are

// Strong fit

• You build constantly. You have shipped things nobody asked you to build. The instinct to make something is more important to us than the title on your CV. Show us what you’ve built.
• You are fluent with agentic coding tools and you use them as leverage, not as a crutch You can read the code they write and you know when it is wrong. AI is how you move faster — not how you avoid understanding what you ship.
• You have real technical depth somewhere Data modelling, backend, systems, ML, industrial process engineering. We do not care which one — we care that it is deep enough to matter when things get hard.
• You have product instinct You can tell the difference between what a customer asked for and what they need. That distinction is the job.
• You can hold a room Enterprise stakeholders, procurement, IT security, a skeptical CFO. You have explained a technical decision to someone paying for it and they trusted you.
• You dive into a problem until it is finished Reliability matters more here than speed. Prototypes that get declared victories are not deliveries.
• English fluent. German is a strong plus for our DACH accounts. Most of our enterprise customers are in the DACH market.

// This isn't the role if

• You want a defined backlog and a clear spec The spec is the customer problem. You write the backlog.
• You want to work only on core platform internals and never see a customer Customer delivery is not a side-effect of this role. It is the role.
• You ship a prototype, declare victory, and move on Production hardening is the job. The prototype is the starting point.
• You have never had to explain a technical decision to someone who is paying for it That moment is part of every delivery here. It is not optional.

Small team, high trust, context over control. Real ownership from week one, and a weekly heartbeat everyone ships to.

Monday

Monday Business requirements set

Thursday

Thursday Delivery

Friday

We are genuinely excited about where this technology is going and we follow it because we want to. You will be expected to do the same — not because it is your job, but because that is the kind of people who work here.

• We…