How I currently practice these roles
This section explains how I currently practice different engineering roles. I have not held most of these titles professionally. Each page shows the projects, experiments, and limitations of my current experience so expectations stay realistic.The goal here is transparency, not title collecting. These pages are meant to show what I actually practice, what I can point to, and where I still need mentorship.
- Proof-based: Every claim links to a real demo, repo, or blog post (even if it’s a rough draft).
- Transparency: Each role page opens with a reminder that these are practice reps, not claimed professional titles.
- Guidance needed: I call out the gaps I still need mentorship on (algorithms, large-scale ops, etc.).
Professional experience I am still working toward
These gaps are shared across most of the role pages below, so I am stating them once here instead of repeating the same list five times.- Owning production systems with real user traffic and business impact.
- Working inside larger team environments with shared CI/CD, observability, and on-call expectations.
- Handling incident response and troubleshooting in live production settings.
- Designing enterprise-scale systems with long-lived operational ownership.
Pick a focus
Cloud Engineer
AWS labs, small public deployments, cost-aware write-ups, and serverless practice with clear limits.
DevOps Engineer
GitHub Actions, Docker Compose, build checks, and deployment workflows that block obvious mistakes.
Backend Engineer
Node and FastAPI experiments focused on auth, APIs, persistence, and honest documentation of limits.
Full-Stack Engineer
Frontend and backend projects where the main goal is getting the whole flow to work together.
AI / Automation Engineer
Local model workflows, FastAPI experiments, prompt orchestration, and small automation tools.