18 Mar 2025

TCS ILP Training after Completing

My 6-Week ILP Training Journey πŸš€

Hey everyone! πŸ‘‹

Earlier, I shared my Week 1 experience of ILP training. Now that I’ve completed all 6 weeks, I thought it’d be fun to take you through my journey—the ups, the downs, and everything in between! πŸ˜ƒ


🏷️ Domain Allocation – Where Did I Land?

I was assigned to the Java domain (woohoo! πŸŽ‰). That meant I got a full 6-week training in Java, Servlets, JSP, and JDBC. Others who joined with me in ILP (called associates) got placed in different domains like ITIS, ITIS with CSP, and more.

πŸ’‘ How do they assign domains?
They map you based on your IPA score (Initial Proficiency Assessment) and the business requirements. So, it's not in your hands—just luck and scores. πŸ€


πŸ“… Week 1: The "Chill" Start 😎

The first week was pretty relaxed. We mostly:
✅ Sat through BizSkill (Business Skills) sessions πŸ§‘‍πŸ’Ό
✅ Attended some mandatory courses πŸ–₯️
✅ Tried to make new friends (because networking is key! 🀝)

Nothing too technical yet, just getting settled in.


πŸ“… Week 2: Technical Training Begins πŸ’»

The second week started to pick up the pace.

πŸ’Ό Still had BizSkill sessions, but now with technical training.
πŸ–₯️ UNIX/Linux was taught in just ONE session (yes, one! 😱).
Each session lasted around 45 minutes to 1 hour—super fast-paced!

πŸ”Ή They only covered the most important commands, which was great for absolute beginners.
πŸ”Ή But if you wanted to clear the PRA, you had to study separately using YouTube or other online resources. πŸ“š

For me, it felt like a waste of time because I already knew UNIX, and sometimes:
πŸ“Œ They either taught too slowly 😴
πŸ“Œ OR rushed through topics at lightning speed

πŸ’‘ By the end of the week, they had already completed:
UNIX/Linux
SQL
HTML & CSS
JavaScript
Agile Methodologies

ALL in just one week! 🀯


πŸ“… Week 3: Java Begins – My Comfort Zone 😏

Finally, my favorite—Java training! ☕

πŸ”Ή Since I already knew Java, I used this time to explore advanced concepts.
πŸ”Ή They gave us our first project—a console-based Vehicle Insurance System. πŸš—πŸ“œ

Project Requirements:
πŸ’» Complete CRUD operations (Create, Read, Update, Delete).
πŸ“ Submit the project on time (deadlines matter!).
✅ Pass PRA 1—which I successfully did! πŸŽ‰

This week was smooth sailing for me. 😎


πŸ“… Week 4: Java Backend – The Real Challenge 😡

This is where things got hard. 😨

πŸ”Ή We moved on to Servlets, JSP, and JDBC.
πŸ”Ή I had zero experience in these and found the training material insufficient. πŸ“–
πŸ”Ή Even YouTube tutorials were limited.

So, what did I do? πŸ€”
✔️ Learned through online websites πŸ’»
✔️ Used ChatGPT for doubts πŸ€–
✔️ Watched multiple YouTube videos πŸŽ₯

At first, it felt like reading an alien language πŸ›ΈπŸ‘½, but slowly, I started understanding it.


πŸ“… Week 5: PRA 2 & The Group Project—The Most Intense Week! πŸ”₯

😨 PRA 2 was extremely difficult—totally different from what I expected. I failed! πŸ’€

And just when I thought it couldn't get worse...
πŸ’₯ They announced a Group Project, which was mandatory to clear ILP and get the release letter.

Project Details: πŸ—️

We had to build a full-stack application using:
🎨 Frontend: HTML, CSS, JS
⚙️ Backend: Servlets, JSP, JDBC
πŸ—„️ Database: MySQL


😬 My Role in the Project – A Tough Ride!

I wasn't confident in backend development, so I requested my team’s Scrum Master (Team Lead) to assign me:
✔️ Registration Page πŸ“
✔️ Login Page πŸ”‘
✔️ Dashboard πŸ“Š

At first, I struggled big time! 😡
πŸ”Ή Backend connections were tricky.
πŸ”Ή Debugging took forever.
πŸ”Ή My brain was fried from constant trial and error. 🧠πŸ”₯

But, after multiple sleepless nights, I:
✔️ Successfully built the full login, register, and dashboard functionality! πŸš€
✔️ Helped debug other teammates’ code too.
✔️ Worked till 8 PM daily and even on Saturdays.

The biggest issue? Integrating everyone’s code into one project! πŸ˜–


πŸ“… Week 6: Final Review – Stress Level πŸ’―

After much effort, we finally integrated everything and got it running.

πŸ” Internal Review:

πŸ‘¨‍🏫 They found some bugs, asked us to fix them, and improve our code.

πŸ’£ External Review – A Nightmare!

😑 The external reviewer was super strict.
🚨 Some teams were told to redo their entire project!
πŸ“’ He was frustrated because many projects had missing functionalities and major bugs.

Final Results: 🎯

✅ Those who cleared PRA 1 or PRA 2 were declared as passed.
⚠️ Others were sent to Technical LAP (extended training).
πŸ•’ The release letter was delayed until the last minute!


πŸ† Final Thoughts on ILP – Was It Worth It?

Despite all the stress, pressure, and last-minute rush, ILP was an amazing experience! πŸŽ‰

Key Takeaways:

✔️ You grow a lot—both technically and personally.
✔️ You make valuable connections with teammates.
✔️ You get to experience the real pressure of IT projects.

πŸ’‘ My Advice:
πŸ‘‰ Don’t stress too much—learning takes time! 🧘‍♂️
πŸ‘‰ If you end up in LAP, don’t panic! It can actually give you more time to improve.
πŸ‘‰ Enjoy the experience and make friends! The people you meet here might help you in your career later. 🀝

All the best for your ILP journey! πŸš€

No comments:

Post a Comment