DevOps Intern
e& Egypt split an 11-person cohort into two teams operating as competing companies. My five-person team built a Django employee database application, containerized it, automated its delivery pipeline, and presented the live deployment to e& Egypt's supervisors.

End-of-program cohort photo
Build Scope
Application development
- CRUD operations, authentication, and session management for the employee database app, built in Django
- Integration with an AWS RDS database instance
- Feature branches in GitHub to manage merge conflicts across the five-person team
DevOps practices
- Linux systems administration: file permissions, configuration files, terminal workflows
- Docker and Kubernetes containerization of the application
- Docker Hub image management and GitHub Actions CI/CD pipelines
- Production deployment and daily KPI tracking
Completed Work
Employee database application
A Django application for managing employee records, with authentication, session management, and full CRUD operations against an AWS RDS-backed database.
- Built with
- Django, AWS RDS, GitHub
- Contribution
- Built core CRUD and auth flows as part of a five-person build team.
- Outcome
- Taken through the full pipeline to a live, presented deployment.
CI/CD pipeline
Containerized the application with Docker and Kubernetes, published images to Docker Hub, and wired up GitHub Actions to automate builds and deployment.
- Built with
- Docker, Kubernetes, Docker Hub, GitHub Actions
- Contribution
- Set up and maintained the pipeline stages that carried the app from commit to production.
- Outcome
- A working, automated path from code change to live deployment, presented to e&'s supervisors.
Technical Stack
Technical skills
Django, Linux administration, Docker, Kubernetes, CI/CD
Tools and platforms
AWS RDS, Docker Hub, GitHub Actions, GitHub
Working style
Team-based delivery, Client-style presentation, KPI tracking
Delivery Pipeline
Linux and Docker fundamentals
Cohort-wide training on Linux administration and containerization established the foundation before team delivery began.
Building the application
Our five-person team implemented the Django employee database app against shared requirements, using feature branches to keep everyone's work isolated.
Containerizing and automating
The app was wrapped in Docker, orchestrated with Kubernetes, and published to Docker Hub.
Shipping through CI/CD
GitHub Actions handled builds and deployment on merge, with daily KPI tracking against the running deployment.
Presenting the result
The finished, live deployment was presented to e&'s supervisors in a simulated client meeting.
Problems & Handling
With five people working in the same Django codebase at once, merge conflicts were the main thing slowing us down.
Multiple people touching overlapping models and views meant conflicts were common without a clear branching discipline.
We moved to feature branches per contributor with smaller, more frequent merges instead of long-lived branches.
Conflicts became routine and quick to resolve, rather than large, blocking events late in the sprint.
Summary
- Cohort size
- 11, split into two competing teams
- Build team size
- 5
- Pipeline stages automated
- Build, containerize, deploy
- The deployment was live and stable enough to present directly to e&'s supervisors in a simulated client meeting, rather than presenting slides about it.