Rich Goldstein - Senior DevOps / Site Reliability Engineer / Unix Linux SysAdmin
yes.sre.rich@gmail.com
| (802) 473-1010 | www.awk2me.com
NYC Metro Area and Louisville, CO
Senior DevOps and Site Reliability Engineer with extensive experience designing, automating, and operating cloud-native and hybrid infrastructure. Expienced in AWS, Kubernetes, Infrastructure as Code, CI/CD pipelines, and observability. Proven record supporting developers, scaling platforms, and improving system reliability and performance.
|
• |
Designed AWS infrastructure supporting production workloads with Terraform and Infrastructure as Code. | ||
|
• |
Built secure CI/CD pipelines integrating automated testing, security scanning, and deployment validation. | ||
|
• |
Implemented monitoring, centralized logging, alerting, and metrics collection for production systems. | ||
|
• |
Improved deployment reliability through infrastructure automation and repeatable release processes. | ||
|
• |
Partnered with software engineering teams to improve platform reliability, scalability, and operational efficiency. |
|
• |
Cloud Platforms: AWS (EC2, EKS, ECS, Lambda, MSK, S3, VPC) and hybrid (AWS Outposts) | ||
|
• |
Container and Orchestration: Kubernetes, Helm, EKS, OpenShift, Docker | ||
|
• |
Infrastructure as Code (IaC): Terraform, Terragrunt, CloudFormation, AWS CDK | ||
|
• |
CI/CD and Automation: Jenkins, GitHub, Ansible, SaltStack, CircleCI, Bosch | ||
|
• |
Observability and Monitoring: New Relic, Datadog, Prometheus, Grafana | ||
|
• |
Programming and Scripting: Python, Go, Bash, Ruby, Rust |
|
• |
Designed Terraform modules that standardized deployment of production AWS infrastructure across multiple environments, reducing provisioning time by 80%. | ||
|
• |
Implemented centralized logging and monitoring using CloudWatch, Prometheus and Grafana, improving incident detection and reducing MTTR. | ||
|
• |
Built CI/CD pipelines integrating automated testing, security scanning and infrastructure validation. | ||
|
• |
Developed Python automation eliminating repetitive operational tasks and improving deployment consistency. | ||
|
• |
Collaborated with software engineering teams to improve platform scalability and production reliability. |
Remote (NYC & Denver) - July 2023 — Present
|
• |
Automated security and compliance workflows across AWS environments | ||
|
• |
Performed GitHub security audits and remediation | ||
|
• |
Supported Python developers using Django and Flask | ||
|
• |
Technologies: AWS, SaltStack, New Relic, Sentry, MySQL, Python, Ruby on Rails |
Remote (NYC & Denver) - November 2022 — July 2023
|
• |
Migrated legacy Kubernetes and EKS clusters to modern EKS platforms | ||
|
• |
Scaled worker nodes from single digits to over 1300 during processing workloads | ||
|
• |
Standardized CI/CD pipelines using Jenkins shared libraries | ||
|
• |
Supported AI/ML teams running Airflow on AWS EKS | ||
|
• |
Automated infrastructure using Terraform, Terragrunt, Vault, and Consul | ||
|
• |
Implemented observability using Prometheus, Grafana, New Relic, and Instana |
Remote (NYC & Denver) - November 2020 — November 2022 Deployed microservices-based sportsbook platforms on AWS and AWS Outposts
|
• |
Deployed Outposts in multiple states. Within each state: |
inventory AWS Output equipment and provision required local resources
|
• |
using terraform, deploy infrastructure on Outposts including EKS, S3, OpenSearch, Elasticache, Consul, Kafka | ||
|
• |
connect and insure new state infrastructure communicates with and shares cloud-based data | ||
|
• |
deploy applications within the new state envrironment using terraform, helm, jenkins pipelines, and (basically) AWS Controllers for Kubernetes | ||
|
• |
Managed Kubernetes (EKS), Consul service mesh, Kafka (MSK), OpenSearch, ElastiCache
|
• |
Built CI/CD pipelines using Jenkins, Docker, and Fargate |
|||
|
• |
Implemented monitoring and alerting across cloud environments |
NYC & Denver - April 2019 — November 2020
|
• |
Supported Ruby on Rails and Node.js applications |
|||
|
• |
Automated infrastructure using Terraform, Ansible, and Jenkins |
|||
|
• |
Operated Docker and Kubernetes platforms |
Remote / San Antonio, TX - April 2018 — March 2019
|
• |
Worked under Google SRE model with equal focus on development and operations | ||
|
• |
Administered OpenStack and AWS environments | ||
|
• |
Automated operations using Python, Go, and Bash |
Denver, CO - June 2017 — May 2018
|
• |
Provided DevOps support for navigation APIs and data platforms |
|||
|
• |
Built CI/CD pipelines using Jenkins, Terraform, Packer, and Chef |
|
• |
Developed Rust-based tooling for infrastructure automation and internal platforms | ||
|
• |
Created developer tooling to standardize CI/CD workflows |
Bachelor of
Science in Computer Science / Electrical Engineering
Stony Brook University (SUNY), Stony Brook, NY
|
• |
DevSecOps: IAM policy reviews, Secrets Manager, Vault, AWS KMS | ||
|
• |
Operating Systems: Linux (Debian, Ubuntu, RHEL, CentOS, Rocky, Alpine), BSD, Solaris | ||
|
• |
Databases: MySQL, PostgreSQL, MongoDB, DynamoDB, Redis | ||
|
• |
Tools: Git, GitHub, Nexus, Artifactory, Nginx | ||
|
• |
Additional Skills: Daily use of AI-assisted development tools including ChatGPT, GitHub Copilot and Claude to accelerate infrastructure automation, scripting, testing and documentation. |
AWS, Kubernetes, Terraform, Jenkins, Linux, Git, Vim
Technology, social causes, hiking, camping, skiing, woodworking, home improvement
|
• |
||||
|
• |
||||
|
• |
|
• |
Created several document and documentation systems for end users. Some are simple in implementation yet present full content at a fraction of the cost and use fewer resources, resulting in additional cost savings. | ||
|
• |
This page started out as an interesting effort to present resumes while allowing them to be updated with nothing more than a few basic toosl - github, {gtn}roff, make, homebrew (optional). | ||
|
• |
A result of this ’fancy’ was a local computer based, resume management system that allowed recruiters to travel, and carry around a small subset of resumes (active candidates, if you will) that can be pulled up as simply as typing man <candidate-name> installed by a simple homebrew formula (brew install <candidate-name>) and removed by another (brew uninstall <candidate-name>) |