DevOps Intern

The Etisalat Egypt cohort had 11 interns. After training on Linux administration and containerisation, we were split into two teams that operated as competing companies. My team of five built a Django employee database application, containerised it, automated its delivery pipeline and presented the live deployment to Etisalat Egypt's supervisors.

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 containerisation 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 the 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

Containerised 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 Etisalat Egypt'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

Problems along the way

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.