The method

How an RKR internship actually runs.

Lab-first, mentored, evidence-driven. Every week you build something real, get it reviewed, and add it to a portfolio — finishing with a defended capstone and a credit-mappable certificate.

What makes it work

Four things a real internship needs.

Lab-first, from Week 1

No watch-only videos. You work inside a live topology on real network operating systems in a cloud pod you open from a browser — configuring, breaking and fixing the actual technology.

A deliverable every week

Each week ends in a concrete artifact — a config, a capture, a report, a script — that your mentor reviews. Progress is visible and evidence accumulates into a portfolio.

Mentored by working engineers

Weekly live reviews plus an async help channel with a one-business-day response. Your mentor does this work for a living and teaches you to talk about it like an engineer.

A defended capstone

You finish by designing, building and defending a real project against a written brief and injected faults — the closest thing to an engineering interview, graded on a published rubric.

Your path

From picking a track to a defended capstone.

01

Pick a track from your branch

Choose the internship that extends the courses you've studied — Networks, Security, Wireless, Cloud/Automation or Observability.

02

Choose your format

4-week winter sprint, 8-week summer internship, or a 6-month semester capstone — matched to your academic calendar and credit needs.

03

Build in the lab, weekly

Work through a week-by-week plan on real gear in cloud pods, with weekly mentor reviews of your configs and evidence.

04

Defend a capstone, earn the certificate

Finish with a graded, defended capstone, a portfolio and a credit-mappable RKR certificate — and, for the strongest, a hiring-pipeline referral.

Three formats

Matched to your academic calendar.

Winter

4 weeks · ~20 hrs/wk

A fast, intense first exposure for pre-final year students during the winter break.

Summer

8 weeks · ~25 hrs/wk

The core track — the standard AICTE summer internship, with the full week-by-week arc.

Semester capstone

24 weeks · ~18 hrs/wk

A full final-semester internship-in-lieu-of-project, mapped to NEP 2020 credits.

Assessment & certificate

Graded on evidence, certificated for credit.

Continuous assessment (60%)
Weekly deliverables reviewed by your mentor — configs, captures, reports and scripts.
Defended capstone (40%)
A real build defended live against a rubric and injected faults.
Credit-mappable certificate
Verifiable certificate with graded outcome and logged hours, formatted for AICTE/NEP submission.
Hiring bridge for distinction
Top interns are referred into the RKR hiring pipeline and fast-tracked into the certification ladder.
Mandatory
internships are now an AICTE/NEP 2020 degree requirement — most students still can't find a technical one that builds real skills
AICTE internship policy · NEP 2020
Lab-first
every internship is done on real network operating systems and cloud pods, not slideware
3 formats
4-week winter · 8-week summer · 6-month semester capstone — mapped to the Indian academic calendar
Portfolio
interns leave with configs, verification evidence, a GitHub repo and a defended capstone

Ready to build something real?

Pick a track that extends your syllabus and start on real gear.