Summer Internship
Why colleges run this
Most summer internships end with a certificate and nothing to show. This one ends with a repository, a demo and a report the student can open in an interview.
Course outcomes
CO1
Operate a version-controlled project repository using branches, commits and issues
K3CO2
Apply the core techniques of the chosen technical track to a defined problem
K3CO3
Write a specification that states scope, data and interface before building
K3CO4
Build and test a working mini project against that specification
K3CO5
Demonstrate the finished project and defend its design decisions
K4Modules tap a module for its theory & lab
Hours shown are the recommended 20-day format — module time scales to the duration you pick (≈ shown for your 3-day selection).
01Orientation and toolchain≈ 2 h
Theory
Version control, branching, issue tracking, working agreements
Lab
Set up the project repository and board
Output
Repository with a written README
02The technical block≈ 4 h
Theory
Core stack for the chosen track, taught against the project brief
Lab
Daily guided exercises building toward the project
Output
Exercise set, reviewed
03Requirement and design≈ 2 h
Theory
Scoping, user stories, data model, interface sketch
Lab
Write the specification the build follows
Output
One-page specification
04Build and review≈ 2 h
Theory
Implementation, code review, testing basics
Lab
Two review checkpoints with a mentor
Output
Working mini project
05Demonstrate and document≈ 1 h
Theory
Writing a project report, preparing a demonstration
Lab
Present to the cohort
Output
Project report and recorded demo
Every participant receives
Certificate of completion Course material LMS access Interview question bank Mock interview & viva practice