Senior Customer Success Engineer

That is the job. Not a queue, and not the easy half of one. Everything difficult that comes out of the run phase lands with you.

Two things sit alongside the case work, and they are what make this a senior job rather than a harder version of a junior one.

Stabilising accounts

When an account's health goes bad, you go in and stabilise it. Not as a permanent assignment, but as a small, highly skilled squad that takes a customer whose numbers or whose confidence have slipped, works out what is actually wrong across the whole picture, fixes it, and hands back a customer who is running properly again. It is the most concentrated version of this work there is.

Taking effort out permanently

Anything that keeps arriving in the queue is a signal, and the answer is usually not more people answering it. It might be better self-service for customers, a customer-facing assistant that resolves the routine questions before they reach us, better diagnostics, or a change in how something is configured at deployment so the problem never occurs. You are expected to find those, make the case, and drive them through. That is how a support organisation scales without scaling headcount one for one, and it is value the customer feels directly.

You work across the boundary between what our platform does, what the customer's ERP does, and what their data actually looks like. You are the one who can read a failing case end to end and say what really happened, and then say credibly whether the fix is configuration, data, process, or a genuine product issue. When it is a product issue, you are the counterpart to our engineering and product teams: you bring the evidence, and because you have seen the same structural problem across several customers, your case is the one that moves the roadmap.

You are also how this function gets better rather than just bigger. The diagnostic tooling, the patterns, the documentation that lets a first-year person resolve what used to take a senior one: that is yours to build. And the interns and specialists coming through the team learn this craft from you.

You do not deliver integrations and you do not run go-lives. Our integrations engineers and technical project managers own that. You own what happens once it is live and it is challenging.

What you'll do

• Own the technically difficult cases from our live customer base, end to end, to a verified root cause.
• Diagnose across boundaries: platform behaviour, ERP behaviour, master data and process logic.
• Decide what the real fix is, and make it: configuration, data, process, or a case for engineering.
• Go into accounts with a deteriorating health score, diagnose across the whole picture, stabilise them and hand them back running properly.
• Drive strategic initiatives that permanently reduce effort and improve the customer experience, from better diagnostics to customer-facing self-service and assistants.
• Act as the counterpart to Product and Engineering, with evidence strong enough to change priorities.
• Recognise structural problems across customers and push for them to be solved once.
• Build the diagnostic tooling, patterns and documentation that raise what the rest of the team can resolve alone.
• Mentor interns and earlier-career colleagues, and raise the technical bar of the function.
• Support Consultants and Customer Success Managers on the technical substance of customer escalations.

What we're really looking for

The following key attributes ensure success in this role:

• Root Cause, Not Symptom – You are not finished when it stops happening. You are finished when you know why.
• Cross-Boundary Reasoning – You hold platform, ERP, data and process in your head at once and find where the truth is.
• Credible Both Ways – You explain the same problem to an engineer and to a CFO, and both of them believe you.
• Leverage – Your instinct is to remove the next hundred cases, not only to close this one. You would rather build the thing that makes a problem stop arriving.
• Calm Under Escalation – When a business-critical process is stopped, you get more precise rather than faster.
• Stabilizer Under Pressure : An unhappy client is not a fire to put out. It is a relationship to rebuild. You bring the temperature down, put structure back into the account, and align next steps so trust returns, not just silence

What you'll bring

• Master's degree in a STEM field: computer science, engineering, information systems, mathematics, physics or similar. Strong candidates from a related field are welcome to make their case.
• 3+ years in a technical customer-facing role: application support at depth, technical consulting, solution engineering, integration engineering or equivalent.
• Demonstrable debugging ability across systems, not only within one. APIs, data mapping, interfaces, logs.
• Comfortable with data. SQL or equivalent, and the instinct to check rather than assume.
• German and English, both fluent. This is a hard requirement. Our customers work in German every day and our internal work runs in English.
• Nice to have: ERP experience with SAP, Microsoft Dynamics or similar, scripting in any language, or exposure to workflow automation and process mining.

What you'll get

• The hard problems, not the queue.
• Influence on the product, with a direct line to Engineering and Product.
• Room to shape the function, since the practice is still being built.
• Real growth – the path from here leads into Consulting, technical leadership within Customer Success, or Product.
• Employee ownership – be part of a majority employee-owned company with a best-in-class stock option programme.
• Amazing team – become part of a driven and collaborative group of innovators.
• Visits & offsites – including collaborative team offsites.

Ready to build the future of ERP automation? Join us and own your impact.

Learn more about blp and our values at blp.digital/company/careers .

Find more English Speaking Jobs in Germany on Arbeitnow

We show an excerpt and a link, and the full text when the source allows it. Brands and logos shown belong to their owners.

Source: Statistisches Bundesamt (Destatis), table; dl-de/by-2-0; StarIn's calculation