image

The main tasks and responsibilities of DevOps Engineer

DevOps Engineers operate at the intersection of IT operations and software development – understanding what it takes to maintain IT infrastructure while also being able to write code and deploy new services. They also collaborate with IT and security teams to ensure quality releases.

Non-tech people, as well as recent college graduates, often find the role of DevOps Engineer difficult to understand. This is because DevOps come from several IT backgrounds, start their careers in different roles of the IT sector, and move into DevOps after gaining sufficient experience and having developed the right skillset.

To better understand all the tasks, responsibilities and challenges that DevOps face, we asked our DevOps engineers to describe them.


 

Ana Jovanovska 

Junior DevOps Engineer at Managed Services Division

(almost 1 year of experience)

Ana in DevOpsland

 

 

 

 

 

 

 

 

 

 

 


 

 

Zoran Lazareski

Intermediate DevOps Engineer at Managed Services Division

(almost 1 year of experience)

 

DevOps Life in Seavus

 

What is DevOps?

  1. There is not one strict definition of DevOps, because if you ask different IT professionals you will probably get different answers
  2. Basically, it is an advanced set of practices that power the development, testing, and deployment using the latest tools and technologies to automate the processes.
  3. It increases an organization’s ability to deliver applications and services faster than traditional software development processes
  4. The benefits of DevOps are: Speed, Rapid delivery, Reliability, Improved collaboration, Security…

 

 

If you are a DevOps Engineer you probably use most of these tools every day

DevOps Life in Seavus

  1. To be part of the DevOps team in Seavus is big opportunity to grow your expertise using various popular technologies and DevOps tools, as well as to work with professionals in many fields on different projects.
  2. I found DevOps position in Seavus very challenging where you can show your affinities and qualities, and where effort and successfully completed work are valued.
  3. To implement quality technical solutions that will meet the customer’s requirements we (the DevOps team members) work closely and help each other when necessary.  In our team there is always friendly working atmosphere and mutual respect. From my experience that work approach always gives the best and the desired results at the end.
  4. When someone asks me why I love my job as DevOps engineer, I answer because of the freedom to create and to come up with solutions for the new problems every day, and also to choose which approach is the best for the particular problem to be solved.
  5. Deploying applications to test and production environments, CI/CD pipelines, Infrastructure as code, Monitoring and alerting setup, Configuration management, creation of scripts in different scripting languages are some of my activities as a DevOps engineer in Seavus.
  6. From my experience, we (the DevOps engineers), should always keep ourselves up to date with every technology and tool we use and to be flexible to changes, otherwise we might implement outdated solutions.​

 

 

Filip Trajcevski

Technology & Business Development Manager at Managed Services Division

(more than 13 years of experience)

 

DevOps Engineer… a Hero or a Myth?

It’s neither and both.

Neither, as DevOps Engineer is a human like everyone else, you, me, the colleague sitting next to you or passing by in a hallway. As well, DevOps Engineer is not a myth, as it exists in real life.

And both, as DevOps Engineer is as one from Marvel Universe, with his/her own superpower, just like the Developer, or the QA Engineer, the Security Engineer, or the IT Operations Engineer, or… And a myth, as the stories as what DevOps Engineer actually is, vary from being a Software Developer and IT Operations Engineer at same time, to being only a cultural philosophy and practices, or…

In reality, a DevOps Engineer, is actually the bridge that was created to remove and connect the silos in which earlier Software Developers, QA Engineers, Security Engineers, Sys Admins, Network Engineers and IT Operations Engineers worked or sometimes still work.

The DevOps engineer is here, to work with Software Developers in order to understand how to application that needs to be deployed is coded and works, to automate it’s deployment, to create the infrastructure as code and as well automate it’s deployment, to incorporate some level of security into all of it working sometimes alongside with Security Engineers, to introduce on some level automated tests working with QA Engineers when applicable, to as well deploy the monitoring and possibly self-healing, and afterwards handover the system to the IT Operations Engineers and work together with them on improvements, further automation and incident management. I am pretty much sure, that along this path, I have missed to list some activities, but you get the picture.

The “bridging” comes, both from the moment that the DevOps Engineer works in parallel with all others, Software Developers , QA Engineers , Security Engineers, IT Operations Engineers, etc… and has the ability to look and understand the system from all sides and from different perspectives, but in same time by connecting all of them into a single team/group while trying to “translate” the different perspectives from one to another, with a sole purpose of making easier and faster delivery of system (solution) in question (initially and afterwards) , system (solution) which is more stable, with higher quality and performance , more secured, and more easily operable.

DevOps Engineer can come from different backgrounds. It can be a former Software Developer, or Sys Admin, or Network Engineer, or IT Operations engineer, or… And he/she builds the skillset along the way, in the CI/CD tooling, Infrastructure as a code language, Cloud and On-prem hosting providers, Containers and container orchestration, Networking, Monitoring, etc…  Oh, no, the DevOps Engineer is neither all-mighty, nor all-knowing, but he/she has a touch here and there with all of the listed, sometimes much more, and usually a qualified/full expertise in only some of them.

Being a DevOps engineer is a challenge, especially given the expanded technology stack one needs to be in touch, have some knowledge or be expert in, and as well have constant communication and work with different engineer profiles already listed above (not to forget the Service Delivery and Project managers) on almost daily level while trying to find “the middle ground” between them and/or implement everyone’s requirement. Let’s clear out, the challenge is not more than every day’s challenge all other engineer profiles have, but it is a different one, as they all other are from each other. But, working with DevOps engineers closely, I can tell you, if you want an adventures and never boring life, becoming a DevOps engineer is for sure a path in that direction…


 

 

Filip Petrushevski

Intermediate Cloud Engineer at Managed Services Division

(1 year of experience)