“So how did you end up in IT?” The honest answer: by a roundabout route. Or more precisely, through stations that at first glance have little to do with servers, storage systems and tickets. Looking back, none of them was wasted.
The stations
2001 to 2008: DHL, logistics and operations. Seven years in which structure, speed and customer focus weren't buzzwords but everyday work. Shipments have to go out, processes have to run, even when things get tight.
2008: STRATO, now IONOS, in customer care. My entry into the cloud world: hosting, domains and the first steps with sync & share. This is where I learned to explain technical problems in a way that actually helps customers move on.
Since 2018: Specialist Support Engineer at 2nd/3rd level. Cloud storage and collaboration – Nextcloud, HiDrive, S3 object storage. This is where the tickets land that are no longer simple.
Since 2023: AI and automation. LLMs, RAG, agents – a second passion that has become a fixed part of my working day.
A parcel is never “just a parcel”
The most important thing I took from logistics isn't technical knowledge but an attitude: behind every parcel, someone is waiting. Someone who needs that delivery to carry on.
Tickets are exactly the same. A ticket isn't a number in a queue. Behind every incident there is a person who wants to get back to work – on files they can't open right now, or with a team waiting for a share. That perspective changes how you prioritise and how you write: what does this person need right now to be able to act again? And what can wait until the root cause is found?
What each station contributed
Logistics: thinking in processes
A supply chain is a chain of handovers. When something doesn't arrive, you look for the point where it got stuck. That is how I approach issues today: where does a file leave the client, where does it reach the server, where is it processed? Systems are just processes with handover points.
Customer care: being able to translate
In customer care you learn that the technically correct answer isn't automatically the helpful one. People describe problems in their own words. The job in support is to translate that description into a technical question – and the answer back again.
2nd/3rd level: causes, not symptoms
At the higher levels a workaround isn't enough. The work is root cause analysis and escalation management: finding out why something happens and making sure it doesn't happen again.
A career change isn't a detour
People who switch careers often feel they have to catch up. Technically that's true – you don't pick up Linux, networking or storage systems on the side. But a different background isn't a deficit. It's a different angle.
What counts in support is a mix: technical understanding, which you can work your way into, and the ability to put yourself in the position of the person on the other side. Career changers often bring the second half with them already.
What I'd tell career changers
- Don't hide your background. It explains why you approach problems differently.
- Take the fundamentals seriously. Linux, DNS, HTTP and email show up somewhere in almost every ticket.
- Build things yourself. A server of your own, a small script, an automation – you understand systems best when you run them.
- Stay curious. My own direction widened again from 2023 onwards, towards AI and automation.
My path wasn't straight, but it had a direction: getting things to run reliably – for the people who are waiting on them.