The Definition.

The title seems damn serious, but yeah, it is a crucial question interviewees encounter in the interviews. Let's break it down.

DevOps is a culture that improves the organizational ability to deliver a product.

Let's understand it with an example: suppose there's an organization or an IT company, CodeX, that needs to improve the version of its software from v1 (which has got a bug) to v2. The CodeX Team has taken 10-20 days to deliver the updated version to the end user. This indicates an ill-structured practice as the software is vulnerable for a longer time without getting updated.

whereas organizations like PUBG would solve the update in a few hours, which indicates a good-performing DevOps mechanism.

The DevOps Crucials.

Generally, when there is a discussion about DevOps, the CI CD pipeline grabs the important space. CI CD means Continuous Integration and Continuous Delivery. Let's take a simple approach to understand the essential objectives of DevOps :

1. Automation: To ensure that the processes happening in the pipeline are Automated and are strictly not manual.

2. Quality: The attestation of the End Product about the Quality of the product should be observed.

3. Monitoring: The quality of the product is ensured through monitoring.

4. Testing : The product is monitored through the tests of the product (usually app, script, etc).

Why DevOps.

The best way to understand the significance of technology is to study the traditional workflows where the technology was absent. DevOps is a technology that was introduced a decade ago. Let's understand the previous workflows :

The Objective of an IT company is to deliver a product to the end user that is developed, trained, and organized by the developers.

1. In the process, the developers would write the code and push it to a central location, where the code is accessible to all the teams.

2. This code now needs to be tested, which can't be done on local machines. Servers are created for this. A System Administrator creates the testing servers.

3. Before the deployment of the code in the server, there should be an application server that holds the app code. This application server is created by the Server Administrator

4. The code is then pushed to the testing server by the Build & Release Engineers.

5. The testers test the code, and after the attestation, the code will be pushed to either the production server or pre-production server (staging areas)

The whole process above would have taken over one month to deploy an app or several days to deploy a change in the app, making it time-consuming and inefficient. That's where DevOps found its place; automation took the spaces of multiple administrators, and monitoring-testing ensures the quality of the product.

How should a DevOps Engineer Introduce himself?

Learning the entire history of DevOps is crucial enough to clear the interviews and showcase the organization your potential to contribute in the tech-space.

Below are the important points one should consider in introducing himself as a DevOps engineer

1. The introduction need not be concise every time. Take your time and explain yourself.

2. Experience, Ex: 4-5 yrs of experience in DevOps (Don't say I have 10-15 years of experience, coz DevOps itself is a Decade old Tech)

3. Explain your roles and responsibilities in the previous company, you may have worked in the quality assurance team, etc.

4. Interviewers can specify some tools and ask you to dive in, ensure that you have knowledge of the tools.

In summary,DevOps is a culture that enhances software delivery by automating processes, ensuring quality, and continuous monitoring. It streamlines the historically inefficient software development process, making it crucial in the tech industry. When introducing themselves in interviews, DevOps engineers should highlight their experience, roles, and tool knowledge.

Join our DevOps learning journey with hashtags:
#SaiProDevOpsLearning #DevOpsWithSaiPro