Forward-Deployed Engineer, Customer Processes

The company

Embreier builds Kalyr, the consequence record for enterprise AI. For every recurring decision in an operation, human or AI, Kalyr seals the forecast before action, records what was permitted and done, and settles the outcome after it in the company’s own economics. Platforms run the work; Kalyr proves what it earned, and learns from it. We are building intelligence that learns from reality wherever consequential work is done.

The role

You work where the process runs. You sit with the teams who carry it, find where knowledge disappears and where the same decision keeps returning, and turn their history into episodes Kalyr can predict and score.

Projects start with an open question: “Why does every changeover cost us the first hour?” or “Which fix actually holds when the same fault returns?” Your job is to go and answer it, then bring what repeats back into the product, so every deployment is faster than the last. That is how services become software.

What you will do

• Map the recurring problem. The decision, the moves available, and the outcome that comes back.
• Connect evidence where it lives. Read-only, with a purpose and a permission on every read.
• Turn history into episodes. The state before, the move, and what followed, ready to predict and score.
• Replay with the experts. Walk the past with the people who lived it, and capture their corrections.
• Show what held. Present what Kalyr predicted and what happened, from the line lead to the executive team.
• Bring it home. Turn what the field taught you into product and research, so it compounds.

What you bring

• Engineering in real environments. Data integration, APIs, SQL and Python where the data is messy and the stakes are real.
• Range. At ease on a site floor, in a lab or a control room, and in the boardroom afterwards.
• Patience first. You understand a process before you propose to change it.
• Plain speech. Clear writing, and the habit of saying what the data shows, especially when it disappoints.

What you will work with

SQL, Python and the APIs of the systems a plant already runs: MES, historians, ERP and quality systems, reached read-only and under the customer’s controls.

Strong additions: OPC UA, PI or Ignition, changeover and maintenance data, operational excellence or lean experience.

This is for you if

• You love the moment a messy process finally makes sense, and you want to turn it into software.
• Long, intense stretches on site give you energy, and you stay precise and grounded deep into them.
• You can earn trust on the floor and in the boardroom in the same week.
• You want your name on what customers can see and count.

To apply

The application asks two questions in place of a cover letter. What is the hardest system you have personally built, what broke, and what would you change? And: Which recurring decision in a plant you know would you put into Kalyr first, and how would you know it worked? A strong answer is a test you could run, not an opinion. We read the answers before the CV.

Who we hire

Original thinkers. People who learn a rule well enough to follow it, then bend it to build something better. You contribute in work others can build on, and you measure yourself by it. You are glad to be known by what you create and by what you give. Proud of the work, humble in the room. The shared result comes first. Accountability here means being the first to say the true thing that needs saying, for the good of the mission we share.

Life at Embreier

Embreier is a Swiss company based in Lausanne. Engineering, research and people who know operations from the inside build in one team, across languages and disciplines. High standards and appreciation live side by side here: the work is demanding, and the people doing it are seen.

Need an adjustment to apply? Write to careers@embreier.com and tell us how we can help.