Last November, Damir celebrated his 5th anniversary as a part of our community. Today we are talking about his Symphony path and how he became one of the first Solution Architects in our Sarajevo office. Continue reading to learn about some of the essential features of his work as he knows it today.
We started with some of his first project and technology memories here at Symphony. Damir shared with us: "When I started working at Symphony, I encountered Python, Django, and Angular technologies both for the first and the last time. After that, I started working in Java and continued to do so, well, until this day."
Damir continued to share his first experience in transitioning to the Solution Architect role. This transition was a career shift, and he explained the very beginnings: "As a company - we developed fast. At one point, we found ourselves designing and developing systems for clients very often. Once you are in this process, many questions emerge - which constraints do we have, is the system on-premise, is it cloud, okay it is - but which cloud, what is the budget and duration? In that aspect, we realized that many pitfalls needed a professional analysis. Therefore, I started transitioning into the role of a Solution Architect to bring the best possible quality to our work."
Being a Solution Architect opens a path that enables you to focus on the system, design, integration, development, and architecture before the implementation itself. In this setup, you need to know what is feasible, but it is not essential to know how to implement those solutions.
Therefore, we asked Damir, from his perspective - what skills should a Solution Architect have?