Devops Engineer Resume
Seattle, WashingtoN
SUMMARY
- Experienced Systems Engineer with extensive technical and analytical skills
- Spinning up Infrastructure using IaC Tool Terraform
- Exceptional troubleshooting, training and documentation skills
- Excellent verbal and written communication skills, effective in dealing with all technical levels within and without the organization
TECHNICAL SKILLS
Platforms / OS: Nix Systems CentOS, RedHat, Ubuntu; IBM Z/OS MVS, AS/400; VMWare; Microsoft Windows 2003 Server, Windows 2008 Server.
SQL Databases: DB2, Oracle9i, SQL Server2000 and 2005, MySQL.
NoSQL Databases: Apache Hadoop (Cloudera / Hortonworks), Neo4J
Languages: Java (1.2 and up), Python, Go, Ruby
Tools: / IDEs: Eclipse, IntelliJ, UML.
Application Servers: WebSphere Application Server V6.0 / V6.1, WebSphere Process Server 6.0, Gemfire 6.5.
Application Integration: Websphere MQ Versions 5.3, 6.0 and 7.0 (also known as MQ Series), Sonic MQ Version 7.5.1.
Monitoring: ProActiveNet, Sensu, Rsyslog.
Cloud Computing: Amazon AWS, Microsoft Azure.
Big Data: Apache Solr, Ceph, Swift.
CI/CD: Git/Stash, Perforce, Chef, Jenkins.
Infrastructure Tool(s): Terraform, CloudFormation
Containers: Docker, Kubernetes
PROFESSIONAL EXPERIENCE
Confidential, Seattle, Washington
DevOps Engineer
Responsibilities:
- M ember of the SysOps team based out of Seattle. Working on migrating application from the DC (VSphere based) to Azure Cloud using Terraform and Chef. Writing new Chef Cookbooks as needed. Creating modules in Terraform for Azure RM .
- Helping application groups in creating entire environments (Staging/UAT/Prod) using the same Terraform modules (Vnet/Subnets/VMs/Scale Sets/LBs/Vault). Also, helped in spinning up Azure AppService apps using Terraform modules for a common logging platform.
- Working on Creating Azure Governance processes. Creating a Hub and Spoke architecture for Azure Subscriptions with eventual Vnet Peering for access control, etc.
- Migrating Chef artifacts (Nodes/Cookbooks/Roles/etc.) from an older Chef Server to a newerone configured by Hearst Corporation.
- Working on configuring and spinning up Kubernets Clusters in Azure (AKS) using Terraform (Helm Charts). Helping application groups deploy their containers to these clusters through CI/CD pipelines (Azure DevOps). Configured Azure based as well as external logging and monitoring for the K8S clusters - EFK (ElasticSearch/FluentD/Kibana) stack as well as DataDog.
Confidential, Bellevue, Washington
DevOps Engineer
Responsibilities:
- Deploying and maintaining applications in AWS. Builds of applications (mostly backend developed in PHP & Postgres) using Jenkins. Releasing these application into AWS stack in a blue/green deployment process using S3 buckets, Auto Scaling Groups / Launch Configurations (using AMIs created by Jenkins jobs).
- Working on coming up with a more appropriate CI/CD process using Chef (using the Amazon marketplace AMI for Chef Server).
- Creating a local YUM repository for securing and maintaining packages for CentOS 6 & 7.
Confidential, Seattle, Washington
Infrastructure Cloud Engineer
Responsibilities:
- OpenStack cloud deployment - working in a team in configuring the various components of Openstack cloud platform using Chef cookbooks. These cookbooks are configured in Git/Stash and tested locally using Kitchen and eventually pushed to various environments using Jenkins.
- Working in configuring a high-performance storage for the OpenStack cloud environment (hardware RAID-10).
- Spinning up Quanta servers using Cobbler for various configurations.
Confidential, Seattle, Washington
Senior Engineer - Test Data Management
Responsibilities:
- Worked on a POC (Proof of Concept) to create a connected graph database for Configuration Management (CM) for all applications and environments using Neo4j Enterprise.
- The POC work is done in the hybrid cloud environment in the AWS (Amazon Web Service) VPC (Virtual Private Cloud). The services used for this POC are EC2 (Instances, Security Groups, Elastic Load Balancers, etc.), S3, CloudFormation Templates.
- Deployed the various components for an in-house developed application for portable devices. The components (Neo4j database, Tomcat container and the application artifacts) were deployed at various component levels in the AWS environment fronted by the ELBs using various security groups.
- Designing, developing and maintaining a portal using Grails and Neo4J for masking and data for testing applications in various environments in the development lifecycle.
- Masking production data (subset) in Oracle using various scripting mechanisms for PCI / PII compliance in the various test environments.
Confidential, Washington
Senior Systems Engineer
Responsibilities:
- Responsible for maintaining and administering Sonic MQ Version 7.5.1 in the production and pre-production environments.
- Configuring high availability and failover cluster(s) for Sonic Brokers using SDM toolset and applying patches.
- Configured and deployed a highly available Apache-SOLR cluster within Tomcat (6.0.25) and managed by ZooKeeper for use in a customer search application. This system runs in a Linux (CentOS 6.0) operating system.
- Responsible for deploying and configuring a highly memory intensive and highly available caching system called Gemfire (from VMWare previously known as Gemstone) in a Linux (CentOS) environment. This application is used for high throughput caches required by some front end applications.
- Adding monitoring for various Sonic artifacts through Sonic Event Monitors and using ProActiveNet to deliver graphs regarding various performance metrics.
- Configuring and adding metrics and alerts for systems in ZenOSS - Server as well as JMX counters.
- Proactively engaging new development environments to assess capacity in the Sonic MQ environment and patterns of messaging through the SOA messaging committee.
- Also as a member of the OPS team, deploying applications into production using a combination of Perforce source control and Bladelogic. Once deployed setting up monitoring for these applications on their servers through ProActiveNet and LogLogic. Also setting up NetScaler VIPs for load balancing for specific applications.
- Creating and maintaining capacity information about production systems using Caplan from Neptuny (Milan, Italy) for extrapolation and growth.
- Also, maintaining the WebSphereMQ (MQ Series) Version 6.0 environment at Confidential .
Confidential, California
Senior Technical Consultant
Responsibilities:
- Designing and developing integration components within Boeing between different business partners using IBM’s WebSphere Integration Developer - 6.0.
- Deploying these applications in IBM’s WebSphere based WebSphere Process Server - 6.0, in a Cluster environment.
- These integration applications are developed within a Service Oriented Architecture framework using the SCA components.
- Integration with the business partners is done using MQ Series, FTP, DB etc.
- Also, re-architected the custom made logger to use the MQ Trigger Monitor.
Confidential, Seattle, Washington
Application Architect
Responsibilities:
- Worked as a Technical Consultant/Application Architect to the Store Systems Group.
- Reviewing architecture of systems from POS Registers to Store Servers to back end Unix Servers.
- Establishing communication patterns using MQ Series - point-to-point (raw MQ and JMS).
- Reviewing server side code developed in Java using MQ/JMS etc.
- Educating the group in good coding practices, helping out the different segments in their testing for various releases for the POS platform.
- Worked on a proof-of-concept project to encrypt PCI sensitive data using devices from vendors (Ingrian / Vormetric).
- Member of a work group coming up with standards and best practices for Web Services and Service Oriented Architectures (SOA) within the company.
- Researching new technology solutions for the new applications to be developed by the group.
- Helping Project Managers in their estimations for resources for new projects.
- Worked on an effort to migrate old message driven applications to J2EE MDBs in the WAS (WebSphere Application Server) environment.