0% found this document useful (0 votes)
6 views2 pages

Interview Draft

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views2 pages

Interview Draft

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

Tell me about the project you are involved in your current organization/your past

organization

Iam currently working for (if you're currently working)


I was working for (Your past organization name). Our client is _________ (your
client name) of _______ domain. (some domain you should add here)
The application we work on is a java based application and our developers write
source code and build scripts based on the features assigned to them in sprints.
All the source code is uploaded by developers into remote GitHub servers.

As a DevOps engineer my responsibility is to perform CICD on the code. For doing


CICD activities, in our organization we configured Jenkins as a CICD tool. I have
integrated Jenkins with github in such a way that whenever developer uploads new
code / make changes to the existing source code, jenkins will notify us. I enabled
the process of automating the steps of downloading the source code, perform builds
based on the build script pom.xml by integrating maven with Jenkins, and deploy the
artifacts into test environments.

If the builds fail, jenkins notifies the development team and the qa team. For
doing this I configured email notifications at jenkins level. If the builds passes,
we configured jenkins in such a way that jenkins deploys the artifacts into tomcat
webapps directory of QA Environment. Jenkins then executes Selenium and Jmeter
automation test cases written by QA team in advance. Our Developers follow TDD
(test driven development) approach where the automated test cases are written by QA
in advance and maintained at Github level. If the test programs yield a failure
report, jenkins notifies the teams of Dev and QA. IF the tests passes, jenkins now
deploys the artifacts into Staging environment for UAT (User acceptance Testing).
Jenkins executes UAT test cases written in Jmeter and Cucumber on the artifact. If
UAT testing is completed, Jenkins takes approval from the Delivery team and deploys
the application into Production environment. For doing all these stages, I have
created a groovy script based JenkinsFile.

Since developers work on multiple functionalities parallely and upload all their
code into different branches and push them to github, we perform CI activities for
every branch separately and to do this I have created multi branch pipeline jobs in
Jenkins.

Our sprint duration is generally between 2-3 weeks and within the time duration we
have to review the application several times and make a stable release by the end.
To perform all the activities at a high level and reduce the load on Jenkins and
perform builds parallely, we have configured Master Slave Architecture.

I have integrated Jenkins with lot of other tools like SonarQube for code quality
checks, JACOCO plugin for java code coverage, nexus to preserve different versions
of artifacts. I'm good at performing jenkins administration activities too.

Since the last ___ (add your devops experience) years, we started implementing
Docker. We have created serveral multi container architectures at the level of
development qa and production environments. Iam well versed with creating multi
container architectures with docker-compose yaml files, packaging docker images
with Dockerfiles and hosting them to hub.docker.com and amazon ECR.

The application we work on is completely a microservices application with a


frontend application and a backend database integrated. The entire environment is
maintained at production level and we added all sort of orchestration capabilities
on our application. We maintained several of our configurations including
monitoring servers and applications, visualizing metrics with Prometheus and
Grafana by configuring them as docker containers.
We started implementing docker swarm at the level of production where we performed
activities like load balancing, high availability, performing rolling updates,
handling failovers, disaster recovery etc., In few projects, We adapted Kubernetes
and performed all sort of container orchestration activities with kubernetes
objects like deployments, replicasets, daemonsets, volumes, RBAC etc., So I got
exposure on both kubernetes and docker swarm to perform container orchestration
activities.

The production environment of our client is cloud based and we got the servers of
our client in the datacenters of US and Asia Pacific regions. We configured the
cloud infrastructure by automating and running terraform scripts. To configure the
servers and architecture created with Terraform IAC, i have created playbooks and
roles in ansible for remote configuration activities like installing packages,
runtimes, creating users, large scale deployments etc.,

In the recent times, we extended automation at every level by writing python


scripts and performed activities like python jenkins automation, python docker and
python ansible automation. We have created python scripts for automating builds on
multiple jenkins jobs, handling docker containers to perform autoscaling with
docker swarm, configure infrastructure with ansible etc.,

===================================================================================
===========
You can add your own resolutions here and modify this draft according to the
requirements in the Job Description.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy