Cloud & DevOps Engineer
I take products from laptop to production and keep them there — Docker, CI/CD with GitHub Actions, AWS and OVHcloud, zero-downtime deploys, and the security hardening that production actually needs. I've led a full cloud migration and a 120+ finding readiness program.
What it is
Cloud & DevOps is everything between 'it works on my machine' and 'it runs reliably for users': containerization, automated build/test/deploy pipelines, infrastructure, observability, and security.
Why it matters
Velocity and reliability come from automation. Manual deploys and unhardened infrastructure are where outages and breaches start; pipelines and good defaults are how a small team ships safely and often.
My experience
I build CI/CD pipelines with Docker + GitHub Actions (multi-environment, automated testing, auto-deploys), run workloads on AWS (EC2/ECS/ECR/S3) and OVHcloud VPS, and led a Heroku→OVHcloud migration plus a 120+ finding production-readiness security program. This site ships with CSP, HSTS, and full security headers.
Projects
Architecture decisions & trade-offs
Every change flows through build → test → deploy automatically across environments; humans review, machines deploy.
Docker for parity between dev and prod; reproducible builds; small images.
Hardened headers, least-privilege access, secrets out of code, and a readiness checklist before release.
- Manual, undocumented deploys that only one person can do.
- Secrets in the repo or in client-visible config.
- Shipping without security headers or least-privilege access.
- Automate build/test/deploy end-to-end.
- Containerize for dev/prod parity.
- Harden by default: headers, least privilege, managed secrets.
- Have a production-readiness checklist and actually run it.
FAQ
Vercel or self-hosting for Next.js?
Vercel for speed-to-ship and great defaults; self-hosting (e.g. OVHcloud/AWS with Docker) when you need cost control or specific infrastructure. I've shipped both and pick per project.
Key takeaways
- Reliability and speed both come from automation.
- Containerize for parity; pipeline everything.
- Security is a default to design in, not a step to bolt on.