System engineer – Swiss Army Knife of IT

Introduction


Ever wondered about the role of a system engineer in a software development company? Or about a system engineer’s role in general? Well, if so, you’re in the right place. In this podcast, we discuss what roles and responsibilities a system engineer has and, in particular, how does he/she fit into Authority Partners’ environment and culture.

In this episode, Dino Buljubasic, Lead System Engineer at AP, discusses how a system engineer fits in a software development world, the difference between system administrator, system admin, and system engineer, what are the most significant challenge, and much more!

 


About Dino

Dino completed his higher education at the prestigious Monash University in Melbourne, Australia, where he gained his Bachelor of IT & Systems degree. His career began at National Australia Bank, where he worked as a Business Analyst and gained knowledge of the banking industry. His more extensive experience was at IBM Australia as a Wintel System Engineer, where he worked on providing support for large corporate companies, including Toyota, Heinze, etc. After returning to Bosnia, he worked for one of the leading system integrators in BiH, King-ICT. This experience enabled him to enhance his knowledge and skills by working on various important projects in many different industries across the country, including the public and government sectors. Currently, Dino is a Lead System Engineer at Authority Partners. He is the Team Lead for the AP Infrastructure Team, who provides support and oversee the entire system and network backbone of Authority Partners as well as providing extensive support to clients. His skill set includes Microsoft technologies, virtualization, cloud administration and migration, and many more.

Here are few links to the most popular Podcast platforms for your maximum experience, but we are sure that you have already subscribed to the AP Podcast at your favorite platform.

Disclaimer: The views expressed in this podcast are the speaker’s own and do not reflect the view of Authority Partners.