From technical implementation to responsibility: where I want to go

My background is in technical implementation. Over many years I have developed software, built platforms, integrated APIs, accompanied deployments and stabilised production systems. That technical foundation matters to me because it helps me understand contexts quickly and assess decisions not just in the abstract, but in terms of what is actually realistic. At the same time, I have realised over recent years that my greatest contribution no longer lies solely in writing code. I am most effective where technical topics need to be structured, priorities clarified, stakeholders aligned and initiatives reliably transitioned into operation.

I am consciously moving away from pure programming. That does not mean moving away from technology. On the contrary: my technical understanding is an important foundation for the roles I want to grow into. I do not need to write every line of code myself to be able to assess technical quality, risks, dependencies and architecture decisions. But I want to remain capable of talking with engineering teams as a peer, understanding technical concepts quickly and translating between business, IT and operations.

Responsibility is not a title for me — it is a mindset. When I am responsible for something, I want it to work. I get up to speed quickly, resolve open questions, bring structure to unclear situations and stay with topics until a reliable result is achieved. I enjoy taking on responsibility when it is connected to real impact: creating clear priorities, taking pressure off teams, preparing decisions, surfacing risks, aligning stakeholders and delivering results consistently.

Over the next few years I see myself in roles such as IT Delivery Lead, IT Project Manager, IT Manager, ICT Manager, Service Delivery Manager, Application Manager or Technical Delivery Lead.

I am aware that many leadership and management roles require additional methodological credentials. These can include certifications in areas such as ITIL, Scrum, HERMES, IPMA or PMP. I am willing to invest in them deliberately when they make sense for a role, a company or a next step in my development. What matters to me is that formal methods complement my practical experience rather than replace it.

I bring a combination that is valuable for these kinds of roles: a technical foundation from software development, platforms, APIs and cloud environments; experience in delivery, go-lives, operations, monitoring and handovers; the ability to prepare complex technical topics in a way that is understandable for management; quick onboarding into new systems and domains; and reliable communication with business, IT, engineering and external partners.

I want to take on a meaningful role in an organisation, but not for status reasons. What drives me is bearing responsibility for topics that matter and delivering results that others can rely on. When I take on responsibility, I identify strongly with the outcome. I do not just work through tasks — I think ahead: what does the organisation need, where are risks emerging, where is clarity missing, and what needs to happen for an initiative to be not just completed, but durably stable?

My next steps are clearly directed towards technical leadership and management responsibility. I want to move away from pure implementation and take on more responsibility for delivery, teams, stakeholders, operations and decisions. My strength lies where technical understanding, clear communication and the willingness to take responsibility come together. That is exactly the direction I want to develop in.