Open to DevOps / Cloud / SRE / Platform Engineering opportunities

DevOps Intern at Springer Capital · Remote, Chicago, USA

Automating Reliable Infrastructure at Scale.

I ship Dockerized apps through GitHub Actions to AWS, then watch them with health checks, logs and alerts. I learn by breaking real systems and fixing them.

Every push

Triggers CI, then deploys when green

3

AWS deployments shipped end to end

1,000+

CI errors traced to one root cause

Observable

Health checks, logs & alerts

01.

What I Solve

I take code from a commit to a reachable, observable production URL.

My work sits between application code and a running system: CI pipelines, Docker images, AWS deployments, and the debugging that starts when a green pipeline still is not reachable.

I am a DevOps Intern at Springer Capital. Every project below is a real pipeline or server that broke at least once, and I write down what broke, because that is where I learn the most.

production-mindset.sh

$ ship every change

push, lint, test, build, deploy

$ keep it reliable

systemd, rollouts, stable endpoints

$ keep it visible

Loki logs, uptime checks, alerts

$ debug before guessing

nc, curl, Security Groups, logs

02.

Technical Arsenal

03.

Projects & Impact

Four projects that show how I connect deployment, reliability and observability, with the real problems I hit along the way.

Also shipped: a Grafana Loki label-cardinality audit (Jira DEV-290) and an n8n evaluation in an isolated staging environment.

PRODUCTION EVIDENCE

Case Studies

04.

How I Think About Production

05.

Journey

BUILD • SHIP • OBSERVE • IMPROVE

Real systems over theory.

A green pipeline means nothing until the app is reachable in production. That is the standard I hold my own work to.