As enterprise architects we do not only work on a software architecture but also on an architecture capability and architecture governance. In addition we evangelize methodology like domain-driven design, that can improve the understanding of problems to create better solutions. In this ongoing process, I presently focus on governance, meaning collaboration with product leadership. Naturally, I am involved in the other topics and also mentor solution architects and tech leads, helped by my experience as a senior software engineer.

As a software architect you need to make the technique support the long term strategy and product vision of the company. This combines a holistic view with technical deep-diving and very high-level system design. It requires collaboration with less-technical people to ensure fundamental platform concepts are on road maps in-time, as well as enabling teams and product-cells to grow and enable them to take on the challenges that come with the transition from monolith to a service oriented architecture. The combination of making visions, explaining stuff and teaching, makes this job fun.

As a senior developer my responsibilities were various.First, I designed, developed and maintained a number of frameworks in our application. We were too early for a lot of existing frameworks in combination with our and our customers requirements. So we invented our own database abstraction layer, business logic layer (including rule engine) and presentation framework (browser-independent displaying of GUIs). Later, I was mainly responsible for the first two.Second, my goal was to spread knowledge better. Because of some organizational, that goal was only reached partially - though a lot improved lately.Third, the task of a senior is also to improve other developers. This can be done in combination with the second goal. However, trying to create awareness is also part of the game.