layout: resume2 job_title: ‘Site Reliability Engineer’ title: ‘Chris Dukes Site Reliability Engineer’

Email from megan llod from hays “Mega with HAYS -checking in” March 4th

required: > https://boards.greenhouse.io/homeadvisorangieslist/jobs/5118161002 As a DevOps Engineer, you’ll be responsible for:

Supporting developer owned software releases on a daily basis Working to create continuous delivery pipeline to automatically push code through the environments Deploying, debugging and optimizing dev, test and production VM’s consisting of Linux, Apache, Tomcat Working with the team to own and maintain the production infrastructure - patches, backups, upgrades, AMI’s, and security Working to create tools to allow development teams to self-serve their platform needs Daily interaction with developers and participation in the development process Continuously iterating and improving our systems Creating documentation for supported systems and services Participating in on-call, and sharing in off-hours maintenance work The folks in this role are usually successful when they have 2+ years of experience in:

Hands on experience with K8’s and EKS clusters Software release experience At least one virtual hosting environment (AWS/Google Cloud Platform/Azure/etc.) Continuous integration tools, such as Jenkins, Bamboo, etc. Containerization tools, such as Docker Automation tools (Puppet, Chef, Ansible, etc.) Working in version control, especially with Git and Gitlab Excellent troubleshooting skills Working among multiple teams and communicating effectively to both technical and non-technical teammates Bonus points if you have:

History of professional growth, collaboration and excellent communication skills Experience in a fast-paced, demanding DevOps environment that requires collaboration Compensation & Benefits:

The salary band for this position ranges from $100,000-$140,000, commensurate with experience and performance. Compensation may vary based on factors such as cost of living. This position will be eligible for a competitive year end performance bonus & equity package. Full medical, dental, vision package to fit your needs Flexible vacation policy; work hard and take time when you need it Pet discount plans & retirement plan with company match (401K) The rare opportunity to work with sharp, motivated teammates solving some of the most unique challenges and changing the world —

I build what you need. Seasoned IT Professional turned DevOps with extensive experience designing, maintaining, and troubleshooting builds and private infrastructure. I make software builds consistent and automatic. I help teams push Quality Assurance, Operations, and Documentation left. And I write new code and fix existing when there is a gap. I’m not happy unless I can improve people, processes, policies, and infrastructure.

Favorite tools: Git, Jenkins, GCP, Docker, Docker Compose, Python, Bash, Make, Vagrant, Packer

Notable Experience, Projects, and Results

KMHA • Garner, NC • September 2018 to February 2021

Konica Minolta Healthcare Americas. Small responsive medical devices company (Software: PACS, RIS, DR, and Medical Billing; Imaging Hardware; Healthcare Managed IT Services). A Konica Minolta subsidiary.

DevOps Engineer

  • Build and Test Infrastructure as Code: Reduced QA and Build VM update and deploy times to 15 minutes. It was 120 minutes. Evaluating Puppet for declarative approach. Used Bash, Packer, PowerShell, and Vagrant on VirtualBox and vSphere for repeatable automated infrastructure creation. Deploy scripts usable standalone to enable testing upgrade scenarios. Used Windows Containers for Docker as an interim build solution. Prior build server and QA server creation were manual with poor procedures. Adhoc VM cloning was done without a consistent state.
  • Automatic Bill of Materials from Folders Reduced deploy code mistakes because a bill of materials file allowed a simpler config. Reduced data transfer required to update. Existing asset release management was manual from a file management GUI. Developed Python program to parse manual results to provide repeatable config for an automated install.
  • Build Automation through Jenkins CI Project: Enabled self-service builds. Ended 2 days wait for builds. Used declarative Groovy Jenkinsfiles with Jenkins Multi-branch pipelines. Used Ubuntu for Jenkins server.
  • PostgreSQL Schema Migration Testing: Reduced time to validate SQL schema change correctness. Leveraged initialization scripts with Postgres Docker image.
  • Google Cloud VMs for QA: Proof of concept Google Cloud’s standard Windows VM offerings were suitable for our product and build server deploy scripts. Worked. It was toped before we could begin updating Packer files and discussing self-service strategy.
  • GitLab Cloud-Native: Proof of concept of GitLab to replace BitBucket. Deployed to Microk8s (Kubernetes) with Helm. Worked. A director wanted us to remain on BitBucket Cloud with its limitations and outages.
  • Jenkins metrics collected in Prometheus. Should have collected Bitbucket cloud metrics. Difficult showing value-add in instrumenting C++ code for Prometheus.
  • Tried logs to Graylog. QA and Dev preferred remote desktop to Windows servers. Difficult showing value-add in centralized logs.
  • Regulated under FDA and DHHS (HIPAA)

Squirrely Girl Produce • Wake Forest, NC • May 2010 to Present

Hobby farm that raises ducks and geese for meat and eggs.

Owner

  • Farm Website in Google Cloud Platform: Wanted a web presence. Static site rendered with Jekyll with GCP DNS, Gmail, HTTPS proxy, and Storage.
  • Webstore Experiments: Evaluated GCP VMs and Run for dynamic content. Use MicroK8s (Kubernetes), Helm, Docker Compose, and Docker for on-premises experiments.
  • Environment is Ubuntu/Debian because the community offering matches the supported offering.
  • Regulated under NC DACS.

Cisco • Morrisville, NC • June 2018 to August 2018

A large company that creates command and control systems to prevent unauthorized communication.

Source Control Administrator

  • Ansible Cleanup Project: Cleaned up brittle procedural approach to Ansible to a resilient declarative approach.
  • Bitbucket on CRATE Proof of concept DevOps and Cloud-Native deployment strategy. Used Cisco’s internal Kubernetes/Rancher Private Cloud.
  • Everything is Red Hat Linux and required moderate sysadmin work.

Qualcomm • Raleigh, NC • December 2011 to May 2018

A medium company enables mobile communications and devices through chip design from the radio to the system-on-chip.

Senior IT Engineer: Devops, Cluster, Display

  • Jira Labor Reporting Project: Reduced 20 staff-hours per month to calculate project labor from Jira ticket history. Saved $10,000 per year for an equivalent product. Developed application in Python using Flask and Vue.js and MongoDB, deployed in Rancher with our from-scratch Docker images.
  • Intellectual Property Export Project: Reduced labor required for intellectual property exports with Django (Python). Leveraged Django REST Framework for clean frontend/backend interface. Initially evaluated RabbitMQ to pass event messages. A task queue worked better.
  • Jenkins on Private Cloud: Jenkins on Private Cloud with a mix of Docker Compose and Rancher based deploys. Used Prometheus for metrics collection and Splunk for log collection.
  • Gerrit on Private Cloud: Gerrit on Private Cloud with a deploy of Gerrit and PostgresQL containers in Docker Compose. Replaced brittle deploy in Ansible.
  • Some GoLang experience porting Bosun’s ‘scollector’ to Solaris and creating a collector for LSF metrics.
  • Other small data analytics in Python auditing Active Directory and LDAP for excessive user authorizations.
  • Extensive troubleshooting on 3rd party Kerberos authentication on Linux through Active Directory
  • Wrote many bash and python scripts to glue tools together.
  • Worked on revising critical resource authorization workflows.
  • Incidentals Git, homegrown Configuration Management, Ansible
  • Environment is SuSE Linux Enterprise Server, Red Hat, and Ubuntu and required deep sysadmin work on all platforms.

Prior Regulated Industry Experience

Glaxo Smith Kline 2006-2007

  • FDA’s CGMP and the UK equivalent
  • Sarbanes Oxley

Wacovia 2002

  • US Banking and Securities regulations

Contact

  • chris.dukes.aix+2021Jan@gmail.com
  • 919.455.5147
  • https://www.linkedin.com/in/chris-dukes/
  • https://github.com/cdd-aix/
  • https://neotoma.org/

Full Skill Matrix

On a scale of 1, is competent and not confident to 5, has mastered.

  • Operating Systems:
    • Part of all jobs since 1990.
    • Linux 5. AIX 5. Windows 3.
  • Programming Languages:
    • Part of all jobs since 1990.
    • Python 4. Bash and other POSIX shells 5. Ruby 3. Groovy 3. C 3. Perl 3. PowerShell 3. Javascript 3.
  • Networking:
    • Part of all jobs since 1990.
    • DNS 4. Firewalls 3. NFS 4. CIFS 3. SSH 4.
  • Virtual Machines:
    • Part of most jobs since 1990.
    • vSphere 4. Virtualbox 4. libvirt 4. HyperV 2.
  • Build Tools:
    • Part of all jobs since 1993.
    • Make 4. Grunt 3. Gulp 3.
  • Relational Databases:
    • Part of every job since 1993.
    • Postgresql 3. MySQL 3. DB/2 3.
  • Ticketing Systems:
    • Part of all jobs since 1993.
    • Jira 4. ServiceNow 4.
  • Backup Restore:
    • Part of most jobs since 1995.
    • Believe in establishing restore scenarios and procedures before going deep on a specific technology.
    • Tivoli Storage Manager 2. Netbackup 2. Backup Exec 2.
  • Configuration Management:
    • Part of most jobs since 1995.
    • Ansible 3. Puppet 2. Chef 1.
  • Content Management Systems:
    • Part of every job since 1995.
    • Jekyll 4. Confluence 3. Sharepoint 2.
  • Source Control:
    • Part of some jobs since 1995.
    • Git 4. Mercurial 3. Many Obsolete Source Control Systems 2.
  • Packaging Systems (Creating Packages)
    • Part of most jobs since 1997.
    • RPM 3. DEB 3. Docker 4.
  • Observability Tools (Log aggregation, indexing, metrics databases)
    • Part of every job since 2011
    • Splunk 4. Prometheus 3. Graylog 2.
  • Social Coding Platforms:
    • Part of most jobs since 2012.
    • Github 4. Bitbucket 4. Gitlab 3.
  • Containers:
    • Part of all jobs since 2014.
    • Docker 4. Podman 3. Dockerfile from scratch 4.
  • Orchestration:
    • Part of some jobs since 2014. Rancher 4. Docker Compose 4. Kubernetes 2. Ansible 3.
  • Continuous Integration and Deployment Engines:
    • Part of all jobs since 2016.
    • Jenkins 4. Bitbucket Pipelines 3. Github Actions 3.
  • Infrastructure as Code:
    • Part of all jobs since 2018.
    • Packer 3. Vagrant 4.