Daniel Anderson

Фрилансер

DevOps Engineer

Berlin, Germany

DevOps Engineer

I've worked in DevOps for 3 years, setting up CI/CD, containerization, and monitoring for startups moving from manual deploys to something repeatable. I work with Docker, GitHub Actions, and common cloud providers, and I document the setup so the team isn't dependent on me for every deploy. I don't do deep application-level debugging — that stays with the development team. Typical setup takes 5-10 working days depending on the existing infrastructure.

DevOps Engineer

Навички

DockerCI/CDGitHub ActionsAWSMonitoringInfrastructure as code

Портфоліо

CI/CD for a Next.js app — Automation diagram

Automation diagram — Automated pipeline taking a Next.js app from push to production deploy.

Dockerized microservice setup — Automation diagram

Automation diagram — Containerized a set of backend services for consistent local and production environments.

Zero-downtime deploy setup — Automation diagram

Automation diagram — Rolling deployment configuration for a production API with health-check gating.

Staging environment automation — Automation diagram

Automation diagram — Automated spin-up of an isolated staging environment for every pull request.

CI/CD for a Next.js app — Automated pipeline taking a Next

Automation diagram — Automated pipeline taking a Next.js app from push to production deploy. A second, similar engagement for a different client.

Dockerized microservice setup — Containerized a set of backend services for

Automation diagram — Containerized a set of backend services for consistent local and production environments. A second, similar engagement for a different client.

Zero-downtime deploy setup — Rolling deployment configuration for a

Automation diagram — Rolling deployment configuration for a production API with health-check gating. A second, similar engagement for a different client.

Staging environment automation — Automated spin-up of an isolated staging

Automation diagram — Automated spin-up of an isolated staging environment for every pull request. A second, similar engagement for a different client.