DevOps & Cloud Internship — 2 Months
Learners build an automated CI/CD pipeline for a containerized application with monitoring and documented deployment steps. Paid cloud spend is not promised; safe lab environments and any learner-borne costs will be documented before open enrollment.
- Linux
- Git
- Docker
- CI/CD
- Monitoring basics
- Secrets hygiene
Compensation terms are to be announced. Applications will not open until compensation, supervision, and legal review are approved and disclosed. No internship fee is charged.
Legal review of internship terms is still required before this opportunity can accept applications.
Program facts
- Duration
- 2 months
- Level
- Intermediate
- Weekly commitment
- Approximately 15–20 hours per week (subject to final program schedule)
- Delivery
- Online
- Availability
- Coming soon — interest registration available
- Compensation
- Compensation terms to be announced
- Mentor / supervisor
- Mentoring format is subject to program approval before open enrollment.
- Delivery owner
- Assigned before enrollment opens
- Certificate policy
- Completion recognition is subject to published requirements.
Access to paid cloud resources is not promised. Any expected learner expenses will be published before applications open.
Audience, prerequisites, and selection
Audience
- Developers seeking operational skills
- Learners with Linux and Git basics
Prerequisites
- Basic Linux command-line comfort
- Git fundamentals
- Ability to commit ~15–20 hours per week
Selection criteria
- Basic Linux and Git familiarity
- Capacity for approximately 15–20 hours per week
- Motivation aligned with DevOps practice
- Ability to follow operational documentation
Responsibilities
- Document deployment goals, constraints, and environment assumptions
- Design pipeline stages and containerization approach
- Implement CI/CD with automated checks and secrets hygiene
- Validate failure scenarios and rollback considerations
- Demonstrate the pipeline and hand off runbooks
Topics covered through the project
- Linux fundamentalsfoundational
- Git workflows for deliveryfoundational
- Networking fundamentalsfoundational
- Dockerfoundational
- CI/CD pipelinesadvanced
- Cloud fundamentalsfoundational
- Deployment automationadvanced
- Logging and monitoring basicsadvanced
- Secrets management hygieneadvanced
- Security and reliability practicesadvanced
Learning outcomes
- Containerize an application and document runbooks
- Implement a basic CI/CD pipeline with automated checks
- Describe monitoring, secrets, and rollback considerations
Project specification
Build an automated CI/CD pipeline for a containerized application with monitoring basics and deployment documentation.
- Problem statement · Illustrative
- A sample application needs a repeatable path from source change to a documented deployment with basic health visibility.
- Primary user workflow · Illustrative
- Commit change → pipeline runs checks → image is built → deployment steps are executed or documented → basic monitoring or health check is recorded.
- Functional scope · Illustrative
- Container definition, CI pipeline with automated checks, deployment documentation, secrets hygiene, and a simple monitoring or health-check note.
- Technical components · Illustrative
- Dockerfile or equivalent, CI config, sample app, runbooks, and a secrets-handling checklist.
- Data requirements · Illustrative
- No production datasets. Configuration via environment variables; secrets never committed.
- Testing expectations · Illustrative
- Pipeline fails on a deliberate check failure, succeeds on the happy path, and documents rollback or recovery considerations.
- Known limitations · Illustrative
- Not a full multi-region production platform. Paid cloud spend is not assumed unless disclosed for an open cohort.
- What counts as completion · Illustrative
- Working pipeline against published criteria, deployment docs, security checklist, and a demonstration of the delivery path.
Examples
- Build an automated CI/CD pipeline for deploying a containerized application with monitoring and documented deployment steps
Deliverables
- Working CI/CD pipeline against published criteria
- Deployment documentation and runbooks
- Security checklist completion
- Final demonstration
Example or assigned project work—not a published student achievement or employment guarantee. Student work is not assumed for commercial use without appropriate agreements. Sections marked illustrative are representative examples, not a fixed commercial brief.
Evaluation criteria
How work is reviewed — clarity of decisions matters as much as a working MVP.
- Working pipeline against published criteria
- Deployment documentation
- Security checklist completion
Evaluation focuses on observable engineering evidence. Exact rubrics are published per program when approved.
01
Main workflow correctness
Does the primary user journey work as specified?
02
Code comprehension
Can the participant explain what the code does and why?
03
Architecture explanation
Are component boundaries and trade-offs articulated clearly?
04
Input validation
Are invalid inputs rejected or handled safely?
05
Testing
Are expected behavior and at least one failure mode checked?
06
Edge-case handling
Does the work account for realistic non-happy-path conditions?
07
Documentation
Can another engineer set up, run, and understand the MVP?
08
Demonstration
Is the working result shown with an honest account of limitations?
Frequently asked questions
Ready to build something real?
Choose a pathway, review a program, and register interest when enrollment opens.