Cloud & DevOps Internship

Make deployment boring, repeatable and reversible.

Containers, pipelines, infrastructure as code and observability — built on free tiers so nothing here costs you money. The skill being taught is making a deploy so routine that nobody dreads it.

Intermediate4 weeks · remote4 briefs · complete any 2Free to join

What you'll be able to do

Containerise an application properly
Build a pipeline that blocks bad code
Define infrastructure as code and rebuild it from scratch
Instrument a service so failures are visible before users complain

Who it suits

Developers who can build an app and now want to run it reliably.

What you'll work with

Docker
GitHub Actions
Terraform
Cloudflare/AWS free tier
Linux
Prometheus/Grafana

The project briefs

Complete any 2 of these 4to finish the programme. Assessment criteria are published here so you know what “good” means before you start.

Containerise an Application Properly

~8h estimated

Write a Dockerfile you would put in production.

Multi-stage build, non-root user, no secrets baked into layers, a small final image. Then compare your image size to the naive version and explain the difference.

Assessed against

Multi-stage build with a documented size reduction
Runs as a non-root user
No secrets in any layer — prove it with history inspection
A health check that actually reflects readiness

You'll finish with

GitHub repo with Dockerfile
Image size comparison

CI/CD Pipeline That Blocks Bad Merges

~10h estimated

Build a pipeline that catches problems before they ship.

Lint, test, build, deploy. Then open a pull request that deliberately breaks a test and screenshot the pipeline refusing it. A pipeline nobody has seen fail is untested.

Assessed against

Runs on every pull request
Fails the build on lint or test failure
Deploys automatically only from main
Evidence of it catching a deliberate breakage

You'll finish with

GitHub repo with workflows
Screenshot of the blocked merge

Infrastructure as Code

~12h estimated

Define your infrastructure in a file, and rebuild it from nothing.

Terraform against a free tier. The real test is destroying everything and recreating it from the code alone. If that fails, the code is not the source of truth.

Assessed against

All resources defined in code, none clicked in a console
State handled deliberately, and the choice explained
A successful destroy-and-recreate, evidenced
Variables separated from configuration

You'll finish with

GitHub repo
Terminal output of the rebuild

Monitoring and Alerting

~10h estimated

Know your service is broken before a user tells you.

Metrics, a dashboard, and one alert that fires on a condition that actually matters. Then trigger it deliberately. An alert nobody has seen fire is a wish, not a safeguard.

Assessed against

Three or more meaningful metrics, with a reason for each
A dashboard someone else could read
One alert, deliberately triggered and evidenced
A written note on what you chose not to alert on, to avoid fatigue

You'll finish with

GitHub repo with configs
Dashboard screenshot
Alert firing evidence

Free to apply and free to complete. The completion certificate is optional.

Other domains

AI Agents & Automation

Build autonomous agents that use tools, not chatbots that answer questions.

Generative AI & LLMs

Go past prompt tinkering into retrieval, evaluation and cost control.

Machine Learning

Classical ML done properly — including the evaluation everyone skips.

Ready to Transform Your Enterprise with AI?

Book a free 30-minute consultation with our AI architects. Discover how agentic AI can automate your workflows and multiply your team's output.

No commitment required · Free architecture review · NDA protected

Cloud & DevOps Internship

Make deployment boring, repeatable and reversible.

Containers, pipelines, infrastructure as code and observability — built on free tiers so nothing here costs you money. The skill being taught is making a deploy so routine that nobody dreads it.

Intermediate4 weeks · remote4 briefs · complete any 2Free to join

The project briefs

Complete any 2 of these 4to finish the programme. Assessment criteria are published here so you know what “good” means before you start.

Containerise an Application Properly

~8h estimated

Write a Dockerfile you would put in production.

Multi-stage build, non-root user, no secrets baked into layers, a small final image. Then compare your image size to the naive version and explain the difference.

Assessed against

Multi-stage build with a documented size reduction
Runs as a non-root user
No secrets in any layer — prove it with history inspection
A health check that actually reflects readiness

You'll finish with

GitHub repo with Dockerfile
Image size comparison

CI/CD Pipeline That Blocks Bad Merges

~10h estimated

Build a pipeline that catches problems before they ship.

Lint, test, build, deploy. Then open a pull request that deliberately breaks a test and screenshot the pipeline refusing it. A pipeline nobody has seen fail is untested.

Assessed against

Runs on every pull request
Fails the build on lint or test failure
Deploys automatically only from main
Evidence of it catching a deliberate breakage

You'll finish with

GitHub repo with workflows
Screenshot of the blocked merge

Infrastructure as Code

~12h estimated

Define your infrastructure in a file, and rebuild it from nothing.

Terraform against a free tier. The real test is destroying everything and recreating it from the code alone. If that fails, the code is not the source of truth.

Assessed against

All resources defined in code, none clicked in a console
State handled deliberately, and the choice explained
A successful destroy-and-recreate, evidenced
Variables separated from configuration

You'll finish with

GitHub repo
Terminal output of the rebuild

Monitoring and Alerting

~10h estimated

Know your service is broken before a user tells you.

Metrics, a dashboard, and one alert that fires on a condition that actually matters. Then trigger it deliberately. An alert nobody has seen fire is a wish, not a safeguard.

Assessed against

Three or more meaningful metrics, with a reason for each
A dashboard someone else could read
One alert, deliberately triggered and evidenced
A written note on what you chose not to alert on, to avoid fatigue

You'll finish with

GitHub repo with configs
Dashboard screenshot
Alert firing evidence

Free to apply and free to complete. The completion certificate is optional.