Skip to content

Senior DevOps and Platform Engineer

Neill Shazly

Kubernetes platforms, CI/CD, and identity for enterprise teams.

Victoria, BC · Pacific time · Remote across North America · Open to contract and full-time roles

  • Kubernetes
  • Terraform
  • GitLab CI / GitHub Actions
  • HashiCorp Vault
  • AWS
  • GCP
  • Azure

Over 15 years of experience in software delivery, the last eight in DevOps, for enterprise teams in aviation, finance, healthcare, utility and public sector asset planning, and music. At INgrooves (Universal Music Group) I selected and built the Kubernetes platform for 30 applications and consolidated 1,000+ secrets into HashiCorp Vault. At Liatrio I led delivery of an IAM application managing 600+ Ping Identity configurations as code in Terraform, ran a team of 4 to 6 engineers on identity and infrastructure automation, led three enterprise GitHub migrations, and brought agent workflows into day-to-day development.

Highlights

30Apps and their CI/CD moved to the hybrid EKS/RKE platform I chose after costing 4 options
50%Hosting cost cut vs Rancher 1 by running dev environments as namespaces on shared nodes
300+Repos and 500+ users moved in the largest of three enterprise GitHub migrations I led
600+Ping Identity configurations in Terraform across 3 environments, custom providers in Go

What I do

Core areas · 3 · Also · 3

Kubernetes platforms

Selected, built, and ran Kubernetes platforms on EKS, GKE, and RKE, from platform selection and cost analysis through production.

Hybrid EKS/RKE platform for 30 applications at INgrooves.

  • Platform selection and cost analysis
  • Hybrid datacentre and cloud clusters
  • Helm charts, network policy, and namespaced environments

CI/CD and delivery pipelines

GitLab CI and GitHub Actions pipelines with shared templates, application-specific build environments, and zero-downtime production deployments.

Build reliability above 99% after moving off TeamCity.

  • Shared templates and reusable pipelines
  • Application-specific build environments
  • Zero-downtime production deployments

Identity and secrets automation

HashiCorp Vault, Ping Identity, and OIDC/JWT auth so applications and developers authenticate with existing identities instead of static keys.

Least-privilege EKS environment with audit logging for financial data.

  • Led delivery of an IAM application: 600+ Ping Identity configurations in Terraform across 3 environments, custom providers in Go
  • Vault design and consolidation of 1,000+ legacy secrets
  • On-call, root cause investigations, and Change Advisory Board representation
  • GitHub and cloud migrationsLed three enterprise GitHub migrations: planning, dry runs, hands-on execution, and runbooks so the team runs the next one.
  • Team enablementOnsite and remote training, reference solutions, onboarding and skills tracking for small teams.
  • AI-assisted developmentAgent workflows with Claude Code and local, open-source models, written up as standards of practice and adopted for company-wide training.

Technologies I work with

Delivery layers · 7
  1. Layer 01

    Plan and develop

    • Jira
    • Confluence
    • ServiceNow
    • Claude Code
    • Ollama
    • Go
    • Python
    • Java
    • Bash
    • Node.js
    • Spring Boot
    • Flask
  2. Layer 02

    CI/CD

    • GitLab CI
    • GitHub Actions
    • CircleCI
    • TeamCity
    • Argo CD
    • Docker
    • Helm
    • Packer
  3. Layer 03

    Provisioning and security

    • Terraform
    • Ansible
    • CloudFormation
    • Azure Bicep
    • HashiCorp Vault
    • Ping Identity
    • Active Directory
  4. Layer 04

    Orchestration and management

    • Kubernetes
    • Rancher
    • OpenFaaS
    • Temporal
    • Ambassador Gateway (now Gravitee Edge Stack)
  5. Layer 05

    Platform and runtime

    • AWS
    • GCP
    • Azure
    • Cloudflare
    • EKS
    • GKE
    • AKS
    • Linux (CentOS, RHEL)
  6. Layer 06

    Data and messaging

    • PostgreSQL
    • MSSQL
    • Oracle
    • MongoDB
    • Redis
    • Kafka
    • Apache Camel
    • Apache Drill
  7. Layer 07

    Observability and analysis

    • Prometheus
    • Grafana
    • Honeycomb
    • Datadog
    • Splunk

How I work

Hands-on, alongside the team

I work alongside the engineers who will own the result, with pairing, documentation, and runbooks in place before handover. On-call coverage, off-hours production deployments, and training small teams are part of the work.

Get in touch

Regulated environments

Change management and approvals, least-privilege and audit-logging defaults. Background check on request, references available.