TCS interview process and practice questions

Behavioral questions

1. Tell me about a time you had to learn a new tool or language quickly.

   A good answer covers

   • Why you needed it and how little time you had
   • How you learned it: documentation, small experiments, asking someone
   • What you delivered with it and what you'd do faster next time

2. Tell me about a disagreement in a team project and how it was resolved.

   A good answer covers

   • What the disagreement was about, described fairly from both sides
   • What you said or did to move it forward, such as testing both ideas
   • How it ended and how the team worked together afterwards

3. Tell me about a time you balanced your studies with another big responsibility.

   A good answer covers

   • The two commitments, such as a club, sport, part-time work or family duty
   • How you planned your time and what you gave up
   • The result for both, and what it taught you about deadlines

4. What is one weakness you're working on, and what are you doing about it?

   A good answer covers

   • A real weakness that matters at work, not a disguised strength
   • A specific example of when it caused a problem
   • The steps you're taking and the progress you can show

Role and technical questions

1. Explain your final-year project and your part in it.

   A good answer covers

   • The problem it solved and who would use it
   • How it works in plain words: front end, back end, database, any outside services
   • What you built yourself, one difficulty you hit and how you solved it

2. What is the difference between an abstract class and an interface?

   A good answer covers

   • An abstract class can hold state and some implemented methods; an interface mainly defines a contract
   • A class extends one class but can implement many interfaces (in Java or C#), and how default methods blur the line
   • When you'd choose each, with a small example such as shapes or payment methods

3. What is the difference between a primary key, a unique key and a foreign key?

   A good answer covers

   • Primary key: identifies each row, no nulls, one per table
   • Unique key: no duplicates but can usually allow a null; a table can have several
   • Foreign key: links to another table's key, with an example such as orders and customers

4. What happens, step by step, when you type a website address into a browser and press Enter?

   A good answer covers

   • DNS lookup to find the server's IP address
   • Opening a connection (TCP, and TLS for HTTPS), then the HTTP request and response
   • The browser rendering HTML, CSS and JavaScript and fetching other files

5. A client's banking application becomes slow every month-end. How would you start finding the cause?

   A good answer covers

   • Asking what 'slow' means: which screens, which users, since when
   • Checking what is different at month-end: batch jobs, report queries, traffic
   • Looking at logs and database query times before guessing, then a fix and a check

6. For experienced candidates: tell me about a production issue on your project and how your team handled it.

   A good answer covers

   • What broke, who was affected and how it was noticed
   • Your part in finding the cause and fixing it
   • What changed afterwards to stop it recurring, such as a test, alert or process

Why TCS? Fit and HR questions

1. Tell me about yourself.

   A good answer covers

   • Your degree, college and the one or two skills you're strongest in
   • Your best project or internship in two sentences, with your own part in it
   • Why you're applying for this role, all in under two minutes

2. Are you willing to relocate and work in any shift?

   A good answer covers

   • A clear, honest answer: yes, or yes with a real constraint stated politely
   • That you understand client work can follow other time zones
   • Something that shows you adapt well, such as studying or working away from home

3. Why do you want to join TCS?

   A good answer covers

   • One or two specific reasons: training for new joiners, the range of industries it serves, moving across technologies
   • How that fits what you want to learn in your first few years
   • Something you've read about its work, not general praise for its size

4. Do you have any questions for us?

   A good answer covers

   • One or two thoughtful questions about the training, the first project or the team
   • Nothing you could easily find on the careers site
   • A short thank-you and a line on why you're still keen

Tips

• Know your project inside out: they'll ask what you built yourself.
• Revise OOP, DBMS and SQL basics; expect one or two simple coding questions.
• Answer HR questions honestly and briefly; relocation and bond questions are common.
• Read the current NQT pattern on the official registration page before you prepare; sections and timings can change between cycles.
• Draw your project's flow on paper beforehand: modules, database tables, and who did what.
• In the managerial round, expect a 'what would you do' scenario; reason aloud and say how you'd keep the client informed.
• If you don't know an answer, say so and explain how you'd find out; guessing on a basic concept costs more.