Now I am IT Dev Chapter Lead at ING. My current position is fifty-fifty. 50% I work as a manager and 50% partially just engineer. Here at ING, we use a kind of matrix organizational structure that is widely known as Spotify Model.

So, 50% of my working time I spent on activities to manage delivery, people, stakeholder expectations, and processes. My style is to be reachable to anyone regarding any topic. I like to get pleasant surprises when a discussion that starts on an issue reveals an unexpected opportunity. As a leader, I encourage people to expand their horizons. Do not limit yourself by technology or role, break the walls of stereotypes and outdated experiences. I use inspiration as the main approach to helping people to make their job better.

The other 50% of my working time goes to solving engineering tasks. I like to solve puzzles. Designs, implementations, tech expertise, system architecture, and system performance. All that is my daily routine. As an engineer, my experience mostly is in Pega development. I see the big power of this technology. Same time I see a lot of limitations there. I do constantly expand my horizons. In my spare time, I do development and education on other IT engineering practices, technologies, and languages. Even though I still don't use those directly that skills but it gives me a lot of new ideas and approaches that I could not get just as a Pega developer. Should say that always been interesting to get a project where Pega is not the only technology to work as a developer.

Before ING I worked as Team leads in several Pega-based system development projects. But I started with Pega when I was a Business analyst and not a developer. Mainly I was inspired by Business process re-engineering. At that time this approach was mainstream in getting operational effectiveness. Just emerged BPMS seemed catalyst that boost the approach. I was looking for a project with BPMS implementation. The first project that I found was a project with Pega as the main technology. There was the only place to be an Engineer and not an analyst as I was at that time. And I asked myself why not. Since then my professional life is tightly linked with Pega.

Regarding education. I graduated with a master's in Aerospace engineering and should have built the rockets. But in Ukraine that time was tough for a young specialist who wants to build space- or aircraft. So did not select that for my professional career. Same time the main principles of engineering are the same everywhere. So it gave me a good background to start IT Engineer career.