Customer Success Engineer (Internship)

Think of this role as the modern Sherlock Holmes — new puzzles to solve and new people to work with, every single day.

This role sits exactly at the intersection of technology and business, and that is not a figure of speech. On one side you are in the system, in the data, working out what actually happened. On the other you are on a call with a finance team explaining it and agreeing what to do. You need both, every day.

Our customers run their finance and supply chain processes on blp. When something does not behave the way they expected, a document that did not post, an exception that should have resolved itself, a number in a dashboard that looks wrong, they write to us. That is where your work starts, and it is also where you become the face of blp for that customer. What reaches them is you: your answer, your explanation, your judgement about what to do next.

You will not be reading from a script and escalating. You investigate what the system did, what the data says and what the customer's process actually requires. You have the access and the authority to change configuration when that is the answer. And when it is not, you know who to bring in and what to give them.

The role grows with you. You start on cases where the pattern is known and someone is close by. As your expertise builds you take the harder ones, and your exposure to customers grows with it: from written answers, to calls, to being in the room when a customer wants their most pressing problem solved now.

This goes well beyond tickets. We are a fast-moving organisation and a lot of what needs to exist does not exist yet. You will take on and drive initiatives that make the whole operation scale: a recurring problem that should be solved once rather than fifty times, a piece of tooling that does not exist, a way of working that has outgrown itself. Interns here have shipped things that the team still uses.

• Answer incoming customer requests through our support channel, and be the person they hear back from.
• Own incidents end to end: investigate, resolve, and confirm with the customer that it is actually fixed.
• Work out why a workflow, document or posting did not behave as expected.
• Adjust configuration where that is the right fix.
• Recognise when a problem is bigger than one case, and hand it on with proper evidence.
• Join customer calls to work through urgent issues directly, as your experience grows.
• Take on initiatives beyond the queue: things that should be fixed once rather than answered repeatedly.
• Document what you learn so the next person does not have to learn it twice.