My experience #

I have worked in IT and R&D for more than 25 years. During that time, I have worked with many parts of technology: systems architecture, integration, infrastructure, software delivery, DevOps, and cybersecurity. This broad experience helps me understand how a decision in one area can affect the whole system.

Over the years, I have led teams of R&D developers and IT technical professionals. I have also mentored several young professionals, helping them grow their technical skills, confidence, and understanding of the wider organization.

DevOps and cybersecurity #

DevOps has been an important part of my work. This includes CI/CD, build pipelines, release processes, source control, automation, and the platforms that support the software development lifecycle.

Cybersecurity has also been present throughout my work as an architect and solution designer. I have dealt with security requirements, risks, and issues in many systems and projects. I have never worked as a member of a dedicated cybersecurity team, so I see cybersecurity as an important part of my architecture experience rather than my main area of specialization.

What I focus on #

• Understand the problem. Start with what people need, what limits exist, and which ideas need to be tested.
• See the big picture. I can often understand the wider situation from a small amount of information. This helps me connect separate topics, find dependencies, and identify effects that may not be obvious at first.
• Make decisions clear. Explain the options, costs, risks, and long-term effects in language that everyone can understand.
• Connect people and technical areas. Bring business, product, engineering, operations, and governance into the same conversation.
• Stay aware of cost. I understand profit and loss (P&L), EBITDA, budgeting, service costs, and the financial effect of technical decisions.
• Build for the future. Make practical choices today without losing sight of scalability, maintenance, and future change.
• Support delivery. Turn a direction into steps that teams can build, review, and improve.

How I approach leadership #

I value curiosity, clear communication, transparency, and practical thinking. People should understand what is happening, why a decision was made, and what is expected from them.

I take emotions and human relationships seriously. Trust, empathy, and good social connections are very important for a team to succeed. Every professional is also a person, with a private life, pressures, and challenges that may not be visible at work. A leader needs to be aware of that.

We are all human, and we all make mistakes. The important thing is to speak openly, learn from the mistake, correct it, and use the experience to improve together.

My professional career provides more background. If you would like to discuss a technology challenge, connect with me on LinkedIn.