DevOps Engineer

Learning DevOps by automating my own projects

I have not held a DevOps Engineer title yet. This page documents the automation and deployment practices I have implemented, current limitations, and areas where mentorship would be valuable.

What I have

Personal CI scripts and deployment checklists for personal projects.
Local Docker Compose labs to practice repeatable environments.
Documentation practices that record failures and remediation steps.

What I don’t have yet

Ownership of production CI/CD workflows or multi-team delivery pipelines.
On-call rotations or enterprise incident response.
Deep observability stacks beyond basic logs and alerts.

What I’m doing next

Stronger rollback patterns and approval steps in CI/CD.
Monitoring practice beyond Lighthouse and console logs.
Policy-as-code exercises for secrets and access control.

Personal automation (public)

GitHub Actions pipelines for personal sites and demos, including linting, type-checking, and deployment to Netlify and GitHub Pages.
Docker Compose labs to standardize Node, Python, and Zig tooling in local development environments.
Scripts and deployment notes documented in repository READMEs.

Guided exposure (lab-style)

AWS internship exposure to ticket triage and CloudWatch dashboards in lab-style environments.
Guided rotations only; no ownership of production changes or independent resolution of live customer tickets.

Docker Multilang

Compose file standardizes Node, Python, and Zig tooling for onboarding.
Manual smoke tests are used in place of automated test suites; README documentation lists missing health checks.
Pipeline uses GitHub Actions to build images and run linting; caching best practices are still being evaluated.

Proof links: Containerization notes

Portfolio deploys

Netlify and GitHub Pages workflows validate builds before publishing personal portfolio sites and static templates.
Release notes and documentation logs are used in place of formal change-management processes due to the absence of a team environment.
Accessibility and Lighthouse checks run via CLI scripts; build failures block deployments until issues are resolved.

Proof links: CI/CD workflow notes

GitHub Actions — personal CI basicsNetlify CLI — personal deploysDocker / Docker Compose — local dev labsAWS CLI labs — lab onlyBash scripting — local automationTerraform — tutorial stagek6 smoke tests — local only

Each repository documents which tools are operational, experimental, or planned to indicate maturity and reliability.

Designing CI/CD for teams bigger than me, including approvals and rollbacks.
Monitoring stacks beyond Lighthouse + console logs (e.g., Prometheus, Grafana).
Hardening secrets management and policy-as-code beyond .env files.
Incident response drills in real production environments.

If you are hiring for junior DevOps or platform roles and provide coaching in these areas, I am open to discussing opportunities.

DevOps Engineer

Learning DevOps by automating my own projects

Clear scope, upfront

What I have

What I don’t have yet

What I’m doing next

What 'DevOps' means in my world today

Personal automation (public)

Guided exposure (lab-style)

Evidence (student/volunteer level)

Docker Multilang

Portfolio deploys

What I'm practicing (always with AI pair-programming)

Where I still need guidance