Six-week vacation training
A six-week training block built around one technology: three weeks of taught fundamentals, three weeks of supervised building, and a certificate that names what you actually shipped.
Admissions open
Free demo class & counselling
Batch slots
Course overview
Six weeks of hands-on classroom training in one technology at our Ludhiana centre, ending with a mini project, training report and certificate your college accepts.
Six weeks is what is actually free once exams end, and this is a full track built for that window rather than a longer course cut down. You pick one technology from the techcadd course list, learn it from setup and core concepts, and spend the last fortnight building something small enough to finish and real enough to defend.
Everything runs offline at the Ludhiana centre, in a morning or evening batch chosen at admission. No prior experience is assumed — the first two weeks exist precisely to remove that gap. You leave with one mini project and its source files, a written case study, and the training certificate, college-format training report and attendance record your university asks for.
Curriculum
6 modules and 24 topics across 6 weeks, in the order they are taught. Each one closes with something that works before the next one opens.
Syntax, structure and the tooling around your chosen track. By Friday you are writing small programs without looking at the slides.
Topics covered
Tools & libraries
You finish with
Five working programs and a repository you push to daily.
Functions, data structures and error handling — the pieces every real program is assembled from, taught through problems rather than definitions.
Topics covered
Tools & libraries
You finish with
A small tool that reads, transforms and writes real data.
The framework, library or platform your track is known for. This is the week that turns a student into someone who can be given a task.
Topics covered
Tools & libraries
You finish with
A running application skeleton with your own data in it.
Connect to the outside world — APIs, authentication, third-party services — and prove it works instead of assuming it does.
Topics covered
Tools & libraries
You finish with
A feature that talks to a live service and has tests to prove it.
Your own project, built in supervised sessions with a daily standup and a code review at the end of each day.
Topics covered
Tools & libraries
You finish with
A deployed capstone with a public link.
Documentation, the training report, a presentation and a mock viva — plus resume and portfolio work so the six weeks stay useful after submission.
Topics covered
Tools & libraries
You finish with
A submitted report, a rehearsed viva and an updated resume.
Module by module
Four modules. Your module list comes from the technology you choose, and the counsellor shares the full syllabus before you enrol — but the shape below is the same whichever track you pick.
Core concepts of the chosen technology, taught from zero. Software installation and environment setup happen on your own lab machine rather than being demonstrated on somebody else’s, and every concept is practised the same day it is taught under supervision.
The essential toolset of your chosen technology, through guided builds that repeat each concept until you can do it unaided. Every class is trainer demonstration in the first half and lab work in the second — watching is not the same as doing.
Guided exercises that combine the earlier modules, then your first independent build without step-by-step instruction. A doubt window before every class closes means nothing carries over into the next day.
One project scoped small enough to finish and real enough to defend, with its documentation and a short written case study. The week ends in a presentation, viva preparation and a final review.
Saturdays are kept free for revision and project work.
Find your pace
The 6 Weeks Training syllabus in the order you meet it, and what you are able to do by the end of each stretch of it. Every row is a capability, not a topic you sat through.
| Capability | Foundations | Applied | Professional |
|---|---|---|---|
| Core syntaxFoundations | Covered in Foundations | Covered in Applied | Covered in Professional |
| Data typesFoundations | Covered in Foundations | Covered in Applied | Covered in Professional |
| Control flowFoundations | Covered in Foundations | Covered in Applied | Covered in Professional |
| Editor & terminalFoundations | Covered in Foundations | Covered in Applied | Covered in Professional |
| Functions & modulesBuilding blocks | Covered in Foundations | Covered in Applied | Covered in Professional |
| CollectionsBuilding blocks | Covered in Foundations | Covered in Applied | Covered in Professional |
| File handlingBuilding blocks | Covered in Foundations | Covered in Applied | Covered in Professional |
| Error handlingBuilding blocks | Covered in Foundations | Covered in Applied | Covered in Professional |
| Framework structureThe applied layer | Not yet covered in Foundations | Covered in Applied | Covered in Professional |
| Routing or pipelinesThe applied layer | Not yet covered in Foundations | Covered in Applied | Covered in Professional |
| Data layerThe applied layer | Not yet covered in Foundations | Covered in Applied | Covered in Professional |
| ConfigurationThe applied layer | Not yet covered in Foundations | Covered in Applied | Covered in Professional |
| REST APIsIntegration & testing | Not yet covered in Foundations | Covered in Applied | Covered in Professional |
| AuthenticationIntegration & testing | Not yet covered in Foundations | Covered in Applied | Covered in Professional |
| Testing basicsIntegration & testing | Not yet covered in Foundations | Covered in Applied | Covered in Professional |
| DebuggingIntegration & testing | Not yet covered in Foundations | Covered in Applied | Covered in Professional |
| PlanningCapstone build | Not yet covered in Foundations | Not yet covered in Applied | Covered in Professional |
| Incremental deliveryCapstone build | Not yet covered in Foundations | Not yet covered in Applied | Covered in Professional |
| Code reviewCapstone build | Not yet covered in Foundations | Not yet covered in Applied | Covered in Professional |
| DeploymentCapstone build | Not yet covered in Foundations | Not yet covered in Applied | Covered in Professional |
| Report writingReport & presentation | Not yet covered in Foundations | Not yet covered in Applied | Covered in Professional |
| DocumentationReport & presentation | Not yet covered in Foundations | Not yet covered in Applied | Covered in Professional |
| PresentingReport & presentation | Not yet covered in Foundations | Not yet covered in Applied | Covered in Professional |
| Resume & portfolioReport & presentation | Not yet covered in Foundations | Not yet covered in Applied | Covered in Professional |
The full programme runs 6 weeks. Where you finish is a question of pace rather than of syllabus — everyone covers all of it.
The case for it
A course is worth the time you give it only if you finish with work you can show and skills you can defend. That is the standard this programme is designed against.
You learn industrial training the way it is used in production, with the workflow, tooling and standards a working team expects. Nothing in the syllabus exists only to fill hours.
Sessions are hands-on. You do every example, break it, and fix it. Each module closes with a lab task that has to work before you move on.
One major, two minor finished projects — the kind of work an interviewer can open, click through and question you on.
A structured final phase: portfolio review, profile cleanup, aptitude and role-specific practice, mock interviews and placement support.
Why this course
Six things we hold ourselves to for every 6 Weeks Training batch that starts in Ludhiana.
Fewer topics, covered until they stick. We do not stretch a six-month syllabus thin and call it a course.
You leave with working familiarity in one thing instead of vocabulary in five.
The trainer walks the lab while you build. Watching is not the same as doing, and the timetable is written around that.
Nothing carries over to the next day, which is the single reason six weeks is enough time to reach a working level at all.
Certificate, training report and attendance record, formatted for submission and backed by viva preparation.
Continue into a 4 or 6 month track and the topics you have already covered are not restarted from zero.
Eligibility
Nobody on this list needs prior knowledge of the technology they choose.
Your college specifies the duration and the paperwork format. Bring the guidelines to the counsellor and the certificate, report and attendance record are issued to match.
Meets the requirementSix weeks is what is actually free once exams end. This is a full track built for that window, not a longer course cut down to fit it.
Fits the breakYou want to know whether coding, design or data suits you before committing four or six months. Six weeks answers that with a finished project rather than a guess.
Try before you commitOne fixed daily slot, morning or evening, chosen at admission. The schedule is compact on purpose so travel days stay predictable.
Predictable timingsEvening batches run the same syllabus and the same project requirement as the morning batch. Nothing is trimmed because you came after class.
Evening batchA certificate, a project and a case study you can put on a resume, produced in six weeks rather than promised in six months.
Documented quicklyNot sure which of these you are, or whether the timing works around what you already do? That is exactly what the call is for. Ask about 6 Weeks Training
Technology ecosystem
6 Weeks Training is the centre. These are the tools you use around it in a working team.
Hands-on projects
Each one lands in your portfolio with the working files, the process and something a reviewer can open.
Week 5 deliverable
One application, built in the open across the fifth week: planned on Monday, reviewed every evening, deployed by Friday. You choose the domain, we hold the standard — it has to run, it has to handle bad input, and you have to be able to explain every file in it.
Certification
Finish the 6 Weeks Training programme at techcadd Ludhiana and you leave with more than a line on a CV — a verifiable certificate, and the project work that makes it mean something in an interview.
Issued in your name on completion of the 6 Weeks Training syllabus, with a reference number an employer can verify with us.
A separate certificate for the capstone you submit, naming the project so the work is attached to the credential.
Students who complete the live-project phase receive an internship letter covering the duration and the work delivered.
Every file, repository and deployed link stays yours — the part of the credential a reviewer can actually open.
techcadd has been training in Ludhiana since 2007. The certificate carries that record; the industrial training work you did carries the rest.
This is to certify that
has successfully completed the 6 Weeks Training programme
6 Weeks Industrial Training
This is to certify that
for project work delivered under supervision in Ludhiana
6 Weeks Training capstone
Where it takes you
The route from your first module to the roles 6 Weeks Training opens — and the work that has to exist at each step.
The vacation training your semester requires, documented properly.
Working knowledge of one stack, deep enough to be given real tasks.
A capstone plus two smaller projects, all deployed and linkable.
On the data track, the querying and charting a first analyst role needs.
Scripts that remove repetitive work — the fastest way to be useful on a team.
Credit towards the four- and six-month tracks if you continue.
Salary outlook
Indicative ranges for the roles this course opens — what a fresher out of Ludhiana is offered, what the metro and remote markets pay for the same skills, and how that moves with two or three years of work behind you.
| Role | Ludhiana & Punjab | Delhi NCR & Bengaluru | Remote & freelance |
|---|---|---|---|
| Six-week training creditEntry | ₹2.4–4.2 LPA | ₹4–8 LPA | ₹20k–45k / project |
| Trainee developerEntry to mid | ₹3.6–6.5 LPA | ₹6.5–14 LPA | ₹35k–90k / project |
| Portfolio starterEntry to mid | ₹3.6–6.5 LPA | ₹6.5–14 LPA | ₹35k–90k / project |
| Analyst traineeMid | ₹3.6–6.5 LPA | ₹6.5–14 LPA | ₹35k–90k / project |
Ranges are indicative, drawn from what our own students report and from openings we see through the placement cell. Actual offers depend on your portfolio, the interview and the company — nobody can promise you a number, and we do not.
Six-week training credit, Trainee developer, Portfolio starter, Analyst trainee and related positions, depending on which part of the syllabus you go deepest on.
The first jump usually comes at 18–24 months, once you have shipped work you can point to. Depth in one area moves it faster than breadth across many.
Yes, and a good number of our students do. Remote and contract work is the reason Ludhiana candidates now compete for the same briefs as metro ones — the portfolio travels, the address does not matter.
IT services, manufacturing and export units running automation, e-commerce and D2C brands, healthcare, education, and the agencies serving all of them. Punjab hiring is broader than it looks from a job board.
It helps with the practical half. The projects and tooling carry into an M.Tech, MCA or a specialisation abroad, and the portfolio is often what separates two applicants with the same marks.
Being straight with you
Six weeks will not make you job ready, and we would rather say that upfront than have you find out in an interview.
Working familiarity with one technology, a completed project you can open and explain, and the documents your college asks for.
A decision. You find out whether this field suits you after six weeks and one fee, rather than after six months and a much larger one.
As a starting point. They finish the six weeks, confirm the field suits them, and continue into a longer track from where this one ended.
Future scope
The value of a six-week block is not the certificate at the end of it. It is that you leave knowing one stack well enough to keep going on your own — and that is the point at which self-study starts working instead of stalling.
Training letter, project certificate, report and a capstone on a public URL. The submission is done and the project outlives it.
Six taught weeks with a weekly assessment gets you past the stage where every new problem needs someone in the room. From here, documentation and practice carry you.
One stack, understood properly, is what junior job posts actually ask for. Students who continue into the longer programmes convert this into placements considerably faster.
Job descriptions name a framework, not a syllabus. Six weeks is exactly enough for one of them if the time is not scattered across four.
Using an assistant is now table stakes. Knowing when its answer is wrong is the skill, and that only comes from having written the thing yourself first.
More companies test with a small build than with a written round. The weekly assessments here are deliberately shaped like those tasks.
Junior roles that would once have required relocating are now open to anyone who can demonstrate the work. That cuts both ways — the bar on demonstration went up.
Where six-week students go next
The comparison
Every institute in Ludhiana claims industry training and placement support. These are the differences you can actually check on a demo visit — ask any of them of anyone, including us.
| What to ask about | techcadd | Typical institute |
|---|---|---|
| Who teaches | Trainers who still do industrial training work outside the classroom | Full-time faculty teaching from a fixed deck |
| 1-on-1 classes | One-to-one teaching available on every course — the pace is yours, and your work is looked at by name | One group class moving at one pace, whoever that pace happens to suit |
| Project work | 5 real projects plus a capstone you deploy and defend | Guided exercises copied from the board |
| Curriculum | Reviewed every batch against what working teams ship | Updated when the printed syllabus is reprinted |
| How a module ends | A lab task that has to run before you move on | Notes to revise before an exam |
| Doubt support | Trainer sits with your code; open lab hours between classes | Ask at the end of class if there is time left |
| What you leave with | Completion certificate, project certificate, internship letter — all verifiable | One printed certificate |
| After the course | Portfolio review, mock interviews, referrals, continued doubt support | The course ends and so does the contact |
Written about the market, not about any particular institute in it. Visit two or three, sit through a demo class at each, and ask all eight of these questions — that is the only version of this table worth trusting.
Student Voices
Feedback from students who completed the 6 Weeks Training programme at techcadd Ludhiana.
Simranjeet Kaur
6 Weeks Training / B.Sc. IT graduate
I joined with no background in this. By the third month I was building industrial training work on my own, and the project reviews are where I actually learnt to do it properly.
Harman Sethi
6 Weeks Training / Now working as an intern in the field
The classes are practical. Every session ends with a task that has to work, so you cannot fake understanding. That habit helped me most in interviews.
Ankit Verma
6 Weeks Training / BCA final year
Doubt support was the difference for me. My trainer sat with my work, found the mistake and made me fix it myself instead of handing over the answer.
Navjot Singh
6 Weeks Training / Career switch from operations
I came for the skill and left with a portfolio — projects I could actually demo on a call, not a certificate I had to explain.
Simranjeet Kaur
6 Weeks Training / B.Sc. IT graduate
I joined with no background in this. By the third month I was building industrial training work on my own, and the project reviews are where I actually learnt to do it properly.
Harman Sethi
6 Weeks Training / Now working as an intern in the field
The classes are practical. Every session ends with a task that has to work, so you cannot fake understanding. That habit helped me most in interviews.
Ankit Verma
6 Weeks Training / BCA final year
Doubt support was the difference for me. My trainer sat with my work, found the mistake and made me fix it myself instead of handing over the answer.
Navjot Singh
6 Weeks Training / Career switch from operations
I came for the skill and left with a portfolio — projects I could actually demo on a call, not a certificate I had to explain.
Simranjeet Kaur
6 Weeks Training / B.Sc. IT graduate
I joined with no background in this. By the third month I was building industrial training work on my own, and the project reviews are where I actually learnt to do it properly.
Harman Sethi
6 Weeks Training / Now working as an intern in the field
The classes are practical. Every session ends with a task that has to work, so you cannot fake understanding. That habit helped me most in interviews.
Ankit Verma
6 Weeks Training / BCA final year
Doubt support was the difference for me. My trainer sat with my work, found the mistake and made me fix it myself instead of handing over the answer.
Navjot Singh
6 Weeks Training / Career switch from operations
I came for the skill and left with a portfolio — projects I could actually demo on a call, not a certificate I had to explain.
Real, unedited feedback from techcadd learners on Google.
Frequently asked questions
The 8 things people ask most often about the 6 Weeks Training course at techcadd Ludhiana.
It is the shortest structured training we run — one technology, taught hands-on for six weeks, finishing with a mini project. You receive a certificate, a college-format training report and an attendance record.
45 days gives you about two extra weeks, spent on deeper application work and a larger mini project. Choose 6 weeks if your university specifies that duration or your break is short.
It counts where your university specifies a six-week duration. Bring your college guidelines to the counsellor before enrolling so the certificate, report and attendance format match exactly.
Yes, through the evening batch. It runs the same syllabus and the same project requirement as the morning batch.
No. Every 6 week batch starts from setup and core concepts, and the first two weeks assume no prior experience with the technology.
Yes, and students regularly do. Topics already covered are not restarted, so you continue from where the six weeks ended.
The syllabus overlaps, but six weeks is delivered as six taught weeks with a weekly assessment, while the 45-day programme front-loads the teaching and gives you a longer stretch of project time. Pick the one your university has specified; if it accepts either, choose six weeks for more structure and 45 days for more building.
Batches run in the morning, afternoon and evening, five days a week. You can switch batch timing once during the programme if your college schedule changes.
Next batch
Send this form and a counsellor calls you back about this course specifically — batch dates, fees and whether it fits what you already know.
Would rather talk now? +91 98881 22667
Ready to get started?
Talk to a counsellor today. One call is usually enough to know which track fits your degree, your schedule and the job you want.
Call now+91 98881 22667