We provide IT Staff Augmentation Services!

Devops Engineer Resume

3.00/5 (Submit Your Rating)

Dallas, TX

SUMMARY:

  • 7 Years of experience in IT industry comprising of Software Configuration Management (SCM) &Development. Extensive experience includes SCM, Build/Release Management, Change/Incident Management, VMware and AWS Cloud computing, DevOps Engineer.
  • Experienced in Software Development Life Cycles and Agile Programming Methodologies.
  • Excellent knowledge of configuring Amazon EC2, Amazon S3, Amazon Elastic Load Balancing and other services of the AWS family.
  • Experience working in a variety of professional system support and solution based IT services for Linux Systems. 2+ years of experience with AWS+ DevOps experience with puppet and chef.
  • Extensively worked on Continuous Integration (CI) and deployment using various CI Tools like Jenkins, Puppet, Chef, and Nexus.
  • Developed Chef Cookbooks to manage systems configuration.
  • Experience in writing Cookbook/Recipes using Chef Resources, Ruby DSL, Chef Handlers, Test Kitchen, and Chefspec, setting up Chef Infrastructure, bootstrapping, node convergence.
  • Used security groups, network ACLs, Internet Gateways, NAT instances and ip tables to ensure a secure zone for organizations in AWS public cloud.
  • Setup Elastic load - balancers for different applications to ensure high availability of applications.
  • Used Amazon Route53 to manage DNS zones and give public DNS names to elastic load balancers.
  • Well Adverse to the principles and best practices of Software Configuration Management (SCM) processes, which include compiling, packaging, deploying and Application configurations.
  • Extensive experience using MAVEN, ANT, and Npm as a Build Tool for the building of deployable artifacts (war & ear) from source code.
  • Worked on infrastructure with Docker containerization, Docker files .
  • Developed Jenkins file to create dynamic Pipelines to support Continuous Integration and Continuous Delivery in Jenkins 2.
  • Extensively worked on setting up enterprise monitoring tools Like Nagios.
  • Ability in development and execution of XML, Shell Scripts, Perl and Python Scripts.
  • Experience in working on source controller tools like Subversion (SVN), IBM Clear case and Confidential, GitHub, Stash.
  • Expert in deploying the code through web application servers like WebSphere/WebLogic/ Apache Tomcat/JBOSS.
  • Good command in working with Tracking/Ticketing Tools JIRA, Remedy, and Confidential Quality center.
  • Good understanding of Operating Systems like Linux, UNIX, and Windows.
  • Experienced in Querying RDBMS such as Oracle, MY SQL and SQL Server by using SQL for data integrity.
  • Managed environments DEV, QA, UAT, and PROD for various releases and designed instance strategies. Experienced in handling Release Management activities.
  • Experience in integrating Unit Tests and Code Quality Analysis Tools like JUnit, Cobertura, PMD, Findbugs, Checkstyle and SonarQube.

PROFESSIONAL EXPERIENCE:

Build Tools: Ant, Maven, Jenkins, Nexus, Docker

Configuration Management Tools: Chef, Puppet

AWS Cloud Tools: EC2, S3, Cloud Formation, IAM, EBS, Confidential, Load Balancing, Autos calling, VPC, Route53, EMR.

Tracking Tools: JIRA, Confidential Quality Center

Monitoring Tools: Nagios, Cloud watch

Version Control: Confidential, SVN, CVS.

Operating Systems: Red Hat Linux, Unix, Ubuntu, Debian, Centos, Windows

Scripting Languages: Shell, Python, Ruby, JavaScript

Application Servers: WebSphere, WebLogic, JBoss

Web Servers: Apache Tomcat, IBM Http Server

Databases: Oracle, My SQL

Programming Languages: Java, C, C++, HTML, CSS

Protocols: SSH, TCP/IP, DHCP, IPV4, IPV6, DNS

WORK EXPERIENCE:

Confidential, Dallas, TX

DevOps Engineer

Responsibilities:

  • Automate infrastructure using Chef cookbooks/recipes to manage and deploy cloud instances.
  • Setup and Install Chef workstation, Chef Server and bootstrapping the Chef Clients using a knife.
  • Developed Chef Cookbooks/Recipes to deploy Java applications into Tomcat nodes.
  • Built continuous integration and Deployment (Infrastructure as code) for cookbooks with Lint (unit testing), rspec/cucumber (BDD), Test kitchen (integration tests).
  • Developed Cloud formation scripts to set up Blue/Green deployment infrastructure along with VPC, configuring subnets, EC2, Security groups, Confidential, Cloud Watch/Alarms, Lambda, AutoScaling, SNS, SQS, RDS in AWS environments.
  • Configured S3 to host static web content, Elastic Load Balancers ( Confidential ) with EC2Autoscaling groups and deployed CloudStack using AWS OpsWorks.
  • Migrated applications from the datacenter to AWS cloud Environment.
  • Developed Jenkins file to create dynamic Pipelines to support Continuous Integration and Continuous Delivery.
  • Designed, built and coordinate an automated build & release CI/CD process using Gitlab, Jenkins/Rundeck, Nexus and Chef on hybrid IT infrastructure.
  • Designed and built a Continuous Integration and Deployment framework for Chef Recipe Code using test-driven development
  • Experience designing, building, maintaining, and coordinating an automated build/release process using Confidential, Jenkins.
  • Installed, configured and web servers like Apache HTTP Web Server, Apache Tomcat and Websphere Application Server on Red Hat Linux.
  • Worked on the uDeploy creation of the process, components, and application to automate the deployments.
  • Created Dashboards for tracking build versions in different environments using Perl scripts and PHP.
  • Deploying JAR, WAR and EAR files to Websphere, Tomcat and Node Apps to Ngnix webservers.
  • Used Splunk for monitoring applications across the board.
  • Used Jira as Ticketing System Tool to handle the issues/tasks/service requests created by multiple team members across the project
  • Integrated JUnit, Cobertura, PMD, Find bugs and check style code quality tools
  • Designed workflows, screens, field configurations and components as part of Projects definition for JIRA as an administrator. Involved in periodic archiving and storage of the source code for disaster recovery.
  • Deployed the Java applications into web application servers like Apache Tomcat.

Confidential, Little Rock, AR

DevOps Engineer

Responsibilities:

  • Building and supporting environments consisting Testing, Development, and Production.
  • Performed the automation using Chef Configuration management.
  • Involved in chef infra maintenance including backup/monitoring/security fixtures.
  • Worked on Chef Server backups.
  • Worked with Knife command-line tool and creating Cookbooks.
  • Manage deployment automation using recipes, cookbooks for Chef using Ruby.
  • Implementing a Continuous Delivery framework using Jenkins in Linux environment.
  • Create pipelines for Jenkins jobs.
  • Using Jenkins Code Deploy plug-in to deploy to AWS.
  • Installed/Configured/Managed Puppet Master/Agent. Wrote custom Modules and Manifests, downloaded pre-written modules from puppet-forge. Up gradation or Migration of Puppet Community and Enterprise.
  • Create a new EC2 instance in AWS, allocate volumes and giving Provisionals using IAM.
  • Creating image of existing EC2 instance with all the required software for applications.
  • Used AWS Cloud Formation Templates to simplify provisioning and management on AWS.
  • Monitor the usage, health, and logs of application with the help of Amazon Cloud Watch.
  • Worked with Amazon Redshift to create simple, scalable data warehouse.
  • Responsible for nightly and weekly builds for different modules.
  • Implementing a CI/CD using Jenkins with build tools Maven, Ant.
  • Worked with Development Team Leads and testing teams to establish a build schedule, execute the builds and troubleshoot build failures, if any.
  • Extensively worked with Version Control Systems Confidential and SVN.
  • Work in migrating code from SVN to Confidential repo (stash/bitbucket), clean the Confidential repo (purging files).
  • Coordinated with the Development Teams to receive the correct versions of re- Confidential and dependent components and with Environment team for issuing/installing successful builds. Created Release Branches for Parallel development.
  • Used Remedy as a ticketing tool in the project.
  • Managed and Administered Sonatype Nexus artifacts storage tool.
  • Applied patches and packages on Linux servers using rpm and yum tools.
  • Worked with a scripting languages like Bash and Ruby.
  • Installation of third-party tools using packages.

Confidential, Boca Raton, FL

Build & Release Engineer

Responsibilities:

  • Expertise building and monitoring software project continuously with CI Tool Jenkins or other similar tools.
  • Create and maintain build scripts for J2EE (Maven) applications.
  • Expertise in using Maven to manage a project’s build, reporting, and documentation.
  • Create and maintain deployment scripts of Java/J2EE Applications to Web Logic Application Server.
  • Used SVN for branching, tagging, and merging.
  • Responsible for design and maintenance of the Subversion Repositories, views, and the access control strategies. Designed and implemented SVN metadata including elements, labels, attributes, triggers, and hyperlinks.
  • Experience writing implementation plans for installing software components on build agents, and working with application services team to execute the install.
  • Support QA regression deployments, monthly and weekly releases of applications.
  • Extensive experience with Maven builds process and repository managers like Artifactory and Nexus.
  • Working knowledge of Windows batch scripting, LINUX Shell scripting, ANT, PERL, SHELL.
  • Integrating the code quality analysis tools like Cobertura, Find Bugs, JUnit, PMD, and Checkstyle into the projects.
  • Worked with JIRA for Issue Tracking and monitoring.
  • Implemented Continuous Integration Builds using Anthil pro, automated deployments, and Notifications.
  • Worked closely with the Development Team in the design phase and developed use case diagrams using Rational Rose.
  • Worked with the Architects on SDLC process being the owner of post-development environments.

Confidential

Build and Release Engineer

Responsibilities:

  • Used SVN for branching, tagging, and merging.
  • Scripted ANT (Build.xml's) for Building Ant Projects.
  • Configured Hudson for Continuous Integration.
  • Established processes and tools to maintain code base integrity, including check-in
  • Validation rules and branch/merge processes.
  • Deployed to Web Sphere Application Servers.
  • Involved in troubleshooting of user interface using JSP.
  • Pushed releases to QA, Beta, and production environments.
  • Worked closely with the team to review code for compatibility issues.
  • Arranging Change Control Board Meetings, defining guidelines for Change Control Board.
  • Creation of Configuration Management Plans, Usage Models for different applications.
  • Expertise in developing and maintaining quality control processes, continually meeting corporate objectives and resulting in the highest level of client satisfaction.
  • Developed and maintained the Standard Operating Procedures for the software.
  • Experience as Rational Software Development Life Cycle Engineer.
  • Created scripts for Backup and restoring SVN repositories.
  • Installing, configuring, troubleshooting and modifying the software.

Confidential

System Admin

Responsibilities:

  • Installation, Configuration, up gradation and administration of Sun Solaris, Red-Hat Linux.
  • User account management and support.
  • Jumpstart &Kick-start OS integration, DDNS, DHCP, SMTP, Samba, Confidential, FTP, SSH, LDAP integration.
  • Network traffic control, IPSec, Quos, VLAN, Proxy, Radius integration on Cisco Hardware via Red Hat.
  • Responsible for configuring and managing Squid server in Linux.
  • Configuration and Administration of NIS environment.
  • Involved in Installing and configuring of Confidential .
  • Worked on Solari's volume manager to create file systems as per user and database requirements.
  • Troubleshooting the system and end-user issues.
  • Responsible for configuring real-time backup of web servers.
  • The log file was managed for troubleshooting and probable errors.
  • Responsible for reviewing all open tickets, resolve and close any existing tickets.
  • Document solutions for any issues that have not been discovered previously.

We'd love your feedback!