DevopsInfra
CS student at Carleton University focused on what happens after the code is written — containers, pipelines, deployment, and infrastructure that doesn't break at 2am.
I'm a 2nd/3rd year CS student at Carleton who got into infrastructure through the back door, shipping fullstack features and then realizing I cared more about the pipeline that deployed them than the features themselves.
My internship at an early stage startup had me wea: fullstack engineering, wiring Docker environments, building CI workflows from scratch. That hands-on chaos is where I developed a taste for reliable, well-observed systems.
I learn from first principles. I won't use a tool I don't understand, and once I understand it, I'll probably go way too deep into how it works.
Description will be updated...
Description will be updated...
Description will be updated...
Full-stack monorepo — Go backend, Next.js frontend. Structured with Clean Architecture (domain → use cases → ports → repositories). Local infra managed with Docker Compose via Colima.
Designed and implemented a deployment pipeline from zero at my internship. Automated build, test, and deploy stages. Eliminated manual deploys for a team that had none before.
Self-hosted environment for learning below the abstraction layer — networking, container internals, system config, and service management. Intentionally broken and fixed repeatedly.
- ›Docker / Compose
- ›Ubuntu
- ›Shell scripting
- ›Git
- ›GitHub Actions
- ›CI/CD Pipelines
- ›Go
- ›C / C++
- ›PostgreSQL
- ›Python
Let's
build.
Targeting Winter 2027 DevOps and infrastructure internships. If you're building systems that need to stay up, I want to help.