About Karandeep Singh About Karandeep Singh
Summary
I’m a Senior DevOps and Site Reliability Engineer based in Calgary, Alberta. I’ve spent over a decade in software and the last six-plus years focused on building, automating, and operating scalable AWS infrastructure — the kind that keeps companies running at 2 AM when the alerts fire.
What I work on
Cloud architecture, infrastructure automation, and CI/CD. In practice that means:
I’m a Senior DevOps and Site Reliability Engineer based in Calgary, Alberta. I’ve spent over a decade in software and the last six-plus years focused on building, automating, and operating scalable AWS infrastructure — the kind that keeps companies running at 2 AM when the alerts fire.
What I work on
Cloud architecture, infrastructure automation, and CI/CD. In practice that means:
- AWS — EC2, S3, Lambda, ECR, RDS/Aurora, VPC, IAM, CloudWatch, Step Functions, and Athena. The work runs from automating Linux patching with Lambda + Step Functions + CloudWatch Events to cutting S3 storage costs by tracking down orphaned objects with Athena and automating lifecycle policies with Ansible.
- CI/CD & Jenkins — owning a Jenkins platform end to end: the controller, the build-agent fleet, and shared-library pipeline tooling. Migrating the controller onto Packer-built AMIs cut deployment time from 40+ minutes to roughly 15, and made rebuilds fully repeatable and version controlled.
- Infrastructure as Code — Terraform, CloudFormation, Ansible, and Packer for immutable, reproducible infrastructure across multiple environments.
- Containers & Kubernetes — Docker, Amazon ECS/Fargate, and EKS. I’m CKAD-certified (Certified Kubernetes Application Developer).
- Security & reliability — credential rotation across Jenkins, Bitbucket, and AWS during a supply-chain incident; EDR rollout; secrets delivered through S3 and Secrets Manager; and the high-availability and disaster-recovery work that keeps systems dependable.
- Go — small operational tools that replace bash scripts once they cross the “needs tests and arguments” threshold. A task runner, a tmux session manager, a from-scratch container engine.
Why I write here
Most online tutorials skip the failure modes. They show you the happy path, hand you a working snippet, and leave you stranded the first time it breaks at 2:13 AM in production.
Articles here follow a different format:
- Start with a real problem.
- Try the simple solution.
- Watch it fail in a specific, documented way.
- Show the fix and why it was wrong before.
- End with the version that actually goes in the runbook.
If that means an article on sed is mostly about the time the GNU vs. BSD difference broke a deploy on a developer’s MacBook — that’s the version I’d want to read.
Certifications
- AWS Certified Solutions Architect – Professional
- AWS Certified Solutions Architect – Associate
- CKAD – Certified Kubernetes Application Developer (The Linux Foundation)
Where I’ve been
Calgary’s DevOps community is smaller than Silicon Valley’s, but the work is real and the stakes are real. I’ve spent the last several years in SaaS and infrastructure-operations roles at Calgary technology companies — environments where the system going down costs measurable money per minute, and where “we’ll fix it next sprint” is rarely an acceptable answer.
Connect
Reach out if you want to talk DevOps, compare notes on cloud architecture or CI/CD, or just argue about whether awk is the right tool for a given task (it usually is).
- LinkedIn: linkedin.com/in/karandeepdhaliwal
- GitHub: github.com/karandaid
- Email: karandaid@gmail.com
- RSS: /posts/feed.xml — new articles as they go out
- Browse all articles: /posts/
Contents