❇️ Clark Ritchie
A Senior Staff Platform / Site Reliabilty Engineer with a diverse background of experiences. Hands-on building and operating scalable SaaS cloud-native systems for over 15 years as both an IC and leader.
I am passionate about building and operating world-class applications that delight its end users.
Connect with me on:
💬 TL;DR
- Core skills: Linux, Kubernetes, Python, Go (Golang), infrastructure as code (Pulumi, Crossplane, Terraform), CI/CD, cloud (GCP, AWS), observability (Datadog), and loads of experience with tools like GitHub Actions
- I am a developer, but also very close to infrastructure
- I approach software development with an SRE’s mindset – scalability, fault-tolerance, optimizing spend, monitoring and alerting – these things, and more, are always part of my thinking
- Sometimes good is better than perfect; I like to ship early and ship often
- Let’s go!
📌 Career TL;DR
- BS in Computer Science, Univ. of Puget Sound (‘96)
- Early career — Intel factory automation, Hewlett-Packard, a startup (’96-’11)
- MS in Computer Science, Oregon State Univ. (‘01)
- Experience at 4 startups
- 12 years writing software for fixed wireless networks in US low-income and throughout East Africa, Haiti, The Philippines
- Co-founded an ISP in Kenya (’13-’18)
- 5 Years as Platform Engineer at Specialized Bicycle Components (’18-’23)
- Principal Engineer at Blueboard, a failed HR SaaS startup (’23-’24)
- Senior Staff SRE Software Engineer at Dexcom (‘24-present)
Current Stack
These days I am using Kubernetes (GKE), Helm charts, GitHub Actions, Python, Go, GCP (Cloud Run, Secret Manager, Cloud SQL, Spanner) and Datadog.
For infrastructure as code it is mostly Pulumi and Crossplane. A lot of my recent work is observability as code – managing Datadog monitors, synthetics and service level objectives across dozens of environments in three global regions, plus the Python service that runs the synthetics themselves.
I also spend a fair amount of time on AI-assisted engineering workflows – reusable skill definitions, repo-level agent instructions, and permission guardrails that keep destructive cloud and state operations under human review.
🗒️ Random Things on my GitHub
Dislcaimer: This is all very, very old!!!
A lot of this is elementary stuff – sometimes I use these just to prove out a basic concept or maybe to provide myself a template for future use. Some of the Terraform is more sophisticated.
Go Things
- Basic Go Things
- gRPC – gRPC example of a “Hello World” server in Go, with clients in Go and Python
- Produce camelCased JSON from a Go Struct – I was asked in an interview how to do this… I’ve always referred to this technique as “JSON Hints”, but maybe that’s incorrect? I think that
json.Marshal was all they were looking for.
- GitHub for doing things with GitHub repos
- s3-static-hosting Very simple web hosting on S3, no https
- s3-remote-state Terraform to create the Terraform backend state on AWS, so meta
- The Docker Swarm section is a series of bespoke Terraform projects I made to create a VPC, subnets, EC2s, ELBs, bootstrap a Docker Swarm cluster, stand up Postgres and MySQL (Serverless) and Elasticache (Redis) instances, as well as SNS for alarms, and more
- AWS Guard Duty A truly minimalistic setup of Guard Duty
Python Things
Docker Things
GitHub Actions Things
Random Things
Additional other random notes and code snippets that I did not explicitly link to are here