Career Program, next batch starts 14 Oct 2026 · Limited seats+91 9544 95 7747
Career Program · Phase 2 projects

What students actually built.

The Career Program ends with six production projects mentored by experienced working engineers. Below is each one: what gets built, the stack and the weeks it takes. Each project is mentor-reviewed and goes into the student's portfolio, and student work appears here only once the student agrees to publish it.

Note: the curriculum view for these six projects lives on the Career Program page. This page is the project-by-project view.
Six project blocks

Six projects. Six things on a resume.

Each block below is one of the six projects, listing what is built, the stack and the weeks it takes.

01
Production Linux Infrastructure.
Multi-server Linux · Apache/Nginx · MySQL · hardened SSH & firewall
Weeks 1–4

A multi-server Linux infrastructure hosting a real web application. Students set up the OS, configured services, hardened SSH and the firewall, set up user management and log monitoring, and ran the box like a real production system would be run.

02
Containerised Application Stack.
Docker · Docker Compose · private registry · health checks & logging
Weeks 5–8

The Project 1 stack, fully containerised. Multi-container architecture managed with Docker Compose, pushed through a private registry, with health checks, structured logging, and the operational practices that make containers behave in production.

03
End-to-end CI/CD Pipeline.
Git workflows · Jenkins / GitHub Actions · automated test & deploy
Weeks 9–12

A real CI/CD pipeline built around the Project 2 stack. Code commit triggers automated tests, a build, and a deployment, with strategies for rollback, environments, and branch protection.

04
AWS Cloud Migration.
EC2 · VPC · RDS · S3 · IAM · CloudWatch · ALB
Weeks 13–16

The Project 3 stack is moved to AWS. Students design the VPC, set up EC2 and RDS, configure IAM properly, hook up CloudWatch, and put a load balancer in front. Cost awareness is part of the brief, not just "make it run".

05
Kubernetes on AWS EKS.
EKS · Helm · ingress · secrets · HPA · monitoring
Weeks 17–21

The application is deployed on AWS EKS. Helm charts package the workloads, ingress handles routing, secrets are managed properly, autoscaling responds to load, and basic observability is wired in. This is the project that turns "I know K8s" into "I've deployed something on K8s".

06
Infrastructure as Code + Observability.
Terraform · Ansible · Prometheus · Grafana · alerting
Weeks 22–25

The Project 5 deployment is refactored end-to-end as Terraform. On top, students build the observability stack, Prometheus and Grafana for metrics, log aggregation, and alerting that actually fires on the things that matter. This is the project that turns the resume from "trained" to "shipped".

A note on this page

Why this page exists separate from the Career Program page.

The Career Program page explains the curriculum. This page exists for the people who want to see the projects, recruiters, employers, parents, and students comparing programmes.

01

Curriculum vs proof of work

Most institute websites stop at "what you'll learn". Two different jobs, two different pages.

02

Verifiable over time

The more cohorts complete the programme, the more verifiable this page becomes.

03

Built with student consent

We don't publish student work without explicit consent. Until consented artefacts are in, each block shows only the project itself.

04

Mentor-reviewed

Every project is reviewed by experienced working engineers on Techcake premises before it counts as complete. The standard isn't "good for a student", it's the agency review standard, applied to students.

Want projects like these on your resume?

The path runs through the Career Program.

10 months, 4 months of training, then 6 months building the six projects on this page with experienced working engineers. Reserve a seat for the next intake.

Reserve Your Seat

Or call us directly: +91 9544 95 7747

Chat on WhatsApp
CallWhatsAppReserve Now