If you study at a college affiliated to Bihar Engineering University, you have probably heard some version of this sentence from a senior: internship is compulsory after certain semesters, and without the certificate your file is incomplete. The broad shape of that advice is right, but the details vary from college to college, so treat everything below as the common norm — and confirm the exact version with your own Training & Placement cell and Head of Department before you plan anything.
Which semesters, and why those
The widely followed pattern under BEU-affiliated colleges is internship exposure around the 3rd, 5th and 7th semesters: early exposure, then deeper project work, then a final pre-placement stint. The logic is straightforward. The first round teaches you how an engineering task is documented, the middle round expects a genuine build, and the final round should look like something you can defend in a viva or an interview. Some departments compress or shift this schedule, and some add a mini-project or seminar alongside it. That is exactly why your HoD’s word overrides any blog post, including this one.
The other thing that varies is nomenclature. Your department may call it industrial training, summer internship, field work, or simply practical training. Different names, same expectation: a bounded piece of engineering work, done by you, with evidence. When a senior says "internship is mandatory," they usually mean the department will ask for a completion record plus a report at the start of the following semester — ask your T&P desk what your department asks for, in writing, before you commit to any program.
The 120-hour, 4–6 week norm
The figure you will hear most often is around 120 hours spread over four to six weeks — roughly twenty focused hours a week. That arithmetic matters more than it looks. Twenty hours a week is a real part-time job: it means a training that asks for two hours of video-watching a day cannot honestly fill the norm, and a two-day workshop with a certificate cannot either. When you evaluate any internship, divide the promised effort by the promised weeks and ask whether the weekly deliverables could plausibly fill that time.
Hours alone, of course, prove nothing without output. Colleges that take the requirement seriously look for a dated trail: what you submitted each week, what feedback you received, and what changed in response. A program that publishes its week-by-week syllabus and reviews every submission against a stated rubric fits this expectation naturally; a program that issues the certificate on payment or attendance alone does not. Whether the work is online or in person is a separate question — some departments accept online-first training, others insist on field or lab hours, and only your T&P cell can tell you which category your department falls in.
Individual work, and the credit question
One point deserves emphasis because students get tripped by it every year: the work is expected to be individual. Group certificates where five names share one project report are the single most common reason departments reject a submission. Even when you learn alongside a cohort, your submissions, your report, and your viva answers must be your own. Keep your own copies of everything — weekly submissions, reviewer comments, the final evaluation — because that file is what you will defend if questions arise.
Finally, the credit question. No training provider — CannyIntern included — can grant academic credit or promise that any college will accept its certificate. Credit is decided entirely by your college, through its T&P cell, HoD, and university norms. Any provider that claims otherwise, or that claims university approval or affiliation, is misleading you. The honest transaction is this: the provider supplies structured work, reviewed submissions, and instantly verifiable records; your department judges whether that satisfies its requirement. Ask your TPO to verify a sample certificate before you enroll — a serious provider will welcome the scrutiny.
