Site Reliability Engineer Resume
Chicago, IL
SUMMARY:
DevOps professional with proven skills in managing application performance in both cloud (AWS) and on - prem integrations. Expertise includes applications and systems instrumentation, performance monitoring, emergency response, change management, capacity planning, and process efficiency development within a continuous integration / continuous delivery pipeline.
TECHNICAL SUMMARY:
AWS, Azure, Alibaba Cloud
Linux, Systems Admin
Docker, Docker Swarm
Jenkins, Bamboo
Ansible, Chef
Websphere, Weblogic
Familiarity with common scripting / programming languages
Apache, URL rewrite
CI / CD, Agile workflow
F5 BIG-IP, Domain / Cert mgmt
Active Directory, LDAP, TDS
ServiceNow, SalesForce, FreshService, OpsGenie
Splunk, Nagios, Sensu / Uchiwa, AppDynamics, Dynatrace
Akamai, Apigee, ActiveMQ
Kubernetes, OpenShift, VSphere
Adobe Experience Manager
Adobe Creative Suite
Microsoft Office
Hardware buildout
Disaster recovery
Drupal / CMS
Automic
Jira, Confluence
Git, Bitbucket, Artifactory
PROFESSIONAL EXPERIENCE:
Confidential, Chicago, IL
Site Reliability Engineer
Responsibilities:
- Manage support of critical online systems for a variety of clients ranging from multinational hotel groups to state lotteries to popular restaurants.
- Primary technical resource during client/developer deployments. Manage AWS, Azure, AliCloud, AEM, Jenkins, Bamboo, while monitoring and debugging any incidents that may hinder completion.
- Patching RHEL/CentOS/Ubuntu + kernel on a scheduled cycle.
- Disaster recovery efforts including backing up and restoring environments from snapshot, failover to backup hosts, and AEM package creation and installation to replace non-functioning instances.
- Up to speed with most client tasks within two weeks from hire, actively participating in resolving incoming issues and requests. Actively others new to the role within two months.
- 24x7 on-call response for automated alerting as well as client phone calls. Technical expert on bridge calls with management and clients.
Confidential, Chicago, IL
Middleware Engineer
Responsibilities:
- Instrumentation and administration of internal/external applications for company-wide use.
- Tasked to consolidate and streamline the maintenance of backend software.
- Ran initiative to aggregate all 3rd party software and defined Ansible configurations to upgrade it.
- Identified redundant software in use by multiple teams and coordinated the effort to replace it.
- Performed yearly failover exercise of all running systems ensuring Confidential ’s plan for continuity of business.
- Created CMS for internal teams to display messaging on screens throughout the office.
- Owned datacenter tape backup process for disaster recovery and data restore.
Operations Center Admin
Confidential
Responsibilities:
- Monitored and remediated Sev 1-3 conditions. Coverage included non-business hours shifts.
- Developed AppDynamics dashboards for monitoring site activity/degradation.
- Created and documented new/more efficient team procedures based on SRE experience.
Site Reliability Engineer
Confidential
Responsibilities:
- Maintained stability of multiple environments working as technical advisor to developer pods.
- Analyzed and diagnosed issues as releases were promoted through continuous delivery pipeline, correcting or rolling back applications if problems arose.
- Facilitated containerization of java-based applications with Docker that were originally coded and served through WAS.
- Created custom mobile app-specific dashboard to detect faults and display user feedback in real time.
- Minimized site degradation/downtime acting as point person during Sev 1 conditions.
Application Engineer
Confidential
Responsibilities:
- Transformed SiteOps monitoring and triage team to middleware Application Engineering team. Its responsibilities included the former SiteOps duties plus ownership of software used by many teams within the company.
- Detected multiple DDoS attacks, minimized their effectiveness, and maintained security.
- Upgraded IBM WebSphere 6.x to 8.5 across three nodes.
- Reduced three tier redundancy to two for cost saving measures.
