Professional Documents
Culture Documents
Devops Engineer Responsibilities: Profile Summary
Devops Engineer Responsibilities: Profile Summary
Profile Summary:
Hands on experience with SCM tools like Git for branching, tagging and version management
Hands on experience with code coverage tools like sonarqube.
Hands on Linux Administration (Installation, Configuration & Troubleshooting)
Responsibilities
Support on RCA ( Root cause analysis ) for production issues
RT - Technologies Purushotham Reddy +91-9019995361
Setup and maintain log-monitoring using Elastic Search, Fluentd and Kibana
Identification of root causes on critical problems throughout the platform, incident reports
and the organization of the engineering team members in steps to resolveissues
Participation in project meetings with other technical staff and business owners and subject
matter experts.
Managing Continuous Integration and Continuous Delivery (CI/CD) using Jenkins and release
management using JIRA
Configuring the Day and Night Builds for the sprint teams in Jenkins
Configuring CRON Jobs for executing daily activities such as Backup/Archive etc in Ansible
Automated the deployments to DEV and QA Environments by picking up builds from Jenkins
using chef/puppet
Created dockerfiles for easier replication of DEV, QA Environments in local machines
Automation of the compilation, continuous integration, testing, packaging, and
distribution of software
Setting up and maintaining monitoring & alert systems for servers
RT - Technologies Purushotham Reddy +91-9019995361
Checking Emails
Checking alerts
Checking JIRA / Any ticketing tool for pending / scheduled tasks.
Clear notifications of alerting system.
Ensure if any new server is created and monitoring has been set up on that.
Verify if all the service running on that server are covered under monitoring system.
Check and automate if any server is running out of disk.
Taking backup of instance and restoring if required.
Taking backup of prod DB and providing that DB to developers on staging/testing environment for
testing of any issue.
Automation setup for daily tasks like jenkins backup.
In case of new project setting up new jenkins job.(Free style/pipeline)
Making config changes on servers using(Ansible).
Writing playbooks for automating daily tasks.
Deploying code on Development and production servers.
Insuring that post deployment sanity of code is done and proper sign-offs are given.
Seeking for approvals from(Business/QA/UAT and Security Sign-offs).
Providing assistance during Audits.
Ensuring that access on servers are given to the required users only that too after proper approvals.
RT - Technologies Purushotham Reddy +91-9019995361
I am responsible for -
Build and Release process.
Managing user access on resources(Grant/Revoke)
Managing Git branches.
Automation(Jenkins/Ansible)
Server & Application support.
Ensuring backup and creating backup policy
Jenkins jobs creation on various environments
Troubleshooting Jenkins build issues
Configuring the jenkins
RT - Technologies Purushotham Reddy +91-9019995361
My self <your name > I have three years experience as a DevOps engineer in my past experience, I
worked with Git and GitHub as a version control system tools, and worked with build tool as a maven,
and good experience with the jenkins as a continuous integration tool in the Jenkins, and in the
jenkins I worked on multiple activities like for installing the plugins, As per the project requirement and
creating the slaves on various environments, and taking care of the Entire Jenkins administration part,
like for providing the user level, and admin level access to the development team, as well as the testing
team, and I worked with the Docker as a containerization tool, whatever application we have
generated in the Jenkins itself in the form of JAR file will convert that jar as a Docker image, with the
help of custom Docker file.
And we are using Docker hub for storing our application, Docker images. So, and I worked with
Kubernetes as a container orchestration tool. So with the help of orchestration process we are
managing the Docker containers in the form of production environment, and we are using as a JIRA as
a ticketing system tools like. So my development team will use jira for contacting to the Devops team
So, while creating the ticket, they will add the priority. So if they need any immediate help from the
DevOps, they will add high priority like P0. sometimes they will add P1 also so according to the
priority will take action on that particular ticket.
Apart from I have good knowledge on some of the AWS services like EC2, S3, ELB, AUTOSCALLING,
IAM, AMI.
RT - Technologies Purushotham Reddy +91-9019995361
CI Workflow
Application_workflow
easy
What is JIRA used for
Jira Software is part of a family of products designed to help teams of all types manage work.
Originally, Jira was designed as a bug and issue tracker. But today, Jira has evolved into a powerful
work management tool for all kinds of use cases, from requirements and test case management to
agile software development.
What is JIRA Dashboard
Your dashboard is the main display you see when you log in to Jira. ... Dashboards are designed to
display gadgets that help you organize your projects, assignments, and achievements in different
charts. To view all of your dashboards, choose Dashboards > View all dashboards.
JIRA ticket
A ticket in Jira, or any other service desk platform, is an event that must be investigated or a work
item that must be addressed.
In Jira Service Desk, tickets entered by customers are called requests. Within a Jira Service Desk
queue or in Jira Software, a request is called an issue
RT - Technologies Purushotham Reddy +91-9019995361
Sprint in DevOps
a sprint is a set period of time during which specific work has to be completed and made ready for
review. ... During the meeting, the product owner (the person requesting the work) and the
development team agree upon exactly what work will be accomplished during the sprint
They are accountable for the entire project scope, the project team and resources, the project
budget, and the success or failure of the project