TCS, Infosys, and Cognizant together hire more freshers from Tamil Nadu engineering colleges than almost all other IT companies combined. Their Chennai development centres - spread across Sholinganallur, Siruseri, MEPZ, and Ambattur - process thousands of candidates every hiring season. Despite this volume, the interview questions follow recognisable patterns. Candidates who understand these patterns prepare more effectively than those who try to study "everything."
This guide covers the actual questions that come up most frequently based on feedback from recent candidates, along with structured answers that work for freshers without professional experience.
The Technical Screening Round - What to Expect
All three companies have a technical interview as part of their selection process. For freshers, the technical round focuses less on deep expertise and more on whether you understand fundamental concepts from your degree.
"Explain any one project you worked on during your course." This is the single most important technical question for freshers. They're not evaluating the complexity of your project - they're evaluating whether you understand what you built and can explain it clearly. Use this structure: Problem Statement (what problem were you trying to solve) → Approach (what technology or method did you use) → Your Role (what specifically did you do) → Outcome (what was the result). Keep it under three minutes.
A strong answer: "For my final year project, I built a student attendance tracking system using Python and MySQL. The problem was that manual attendance in my college took 10 minutes per class. I designed the database structure with three tables - students, courses, and attendance records - and wrote the Python interface for teachers to mark attendance. My specific contribution was the database design and the backend logic. The system reduced attendance recording time to under 2 minutes per class. It's a simple project, but I learned database normalization and SQL query optimization through it."
"What is object-oriented programming? Explain with an example." This comes up for virtually every CS, IT, and ECE graduate. They want to see if you understand the concept, not if you can recite a textbook definition. Use a real-world analogy: "OOP organises code around objects that have properties and behaviors. For example, if you're building a banking application, an Account object would have properties like account number, balance, and holder name, and behaviors like deposit, withdraw, and check balance. The four principles - encapsulation, inheritance, polymorphism, and abstraction - help manage complexity as the application grows." Follow with a concrete code snippet if they ask you to elaborate.
"What's the difference between [X] and [Y]?" These comparison questions are favourites: SQL vs NoSQL, Java vs Python, TCP vs UDP, stack vs queue, linked list vs array. The interviewers don't expect you to know all combinations. They're testing whether you can articulate differences clearly. For any comparison question, use a three-point structure: Definition of X → Definition of Y → Key differences (use cases, performance, structure). Don't bluff if you genuinely don't know - say "I'm more familiar with X than Y, so let me share what I know about X" and demonstrate depth in what you do know.
Young professional preparing for an IT company interview with laptop and notes
HR Round Questions That Decide Your Offer
After the technical round, the HR interview determines your final selection and often your compensation tier. The technical round filters for competence; the HR round filters for fit.
"Why [TCS/Infosys/Cognizant]?" Every candidate gets this, and most give generic answers about "market leader" or "good brand name." To stand out, mention something specific: a recent company initiative, a technology focus area, or a specific programme. For TCS: "TCS's focus on contextual masters and the TCS Pace framework for innovation is something I find unique - it suggests the company invests in continuous learning beyond just project delivery." For Infosys: "Infosys's Springboard platform for skill development and the emphasis on digital transformation projects gives freshers exposure to real business problems." These specific references show you researched the company, not just the job listing.
"Where do you see yourself in five years?" Don't say "in a management position" unless you can explain the path. A realistic answer for a fresher: "In five years, I want to be technically strong enough to lead a small module or component within a larger project. That means spending the first two years learning the technology stack deeply, then gradually taking on more responsibility. I'd like to be the person my team comes to when they're stuck on a technical problem." This answer is ambitious without being unrealistic, and it shows you're thinking about skill progression, not just title progression.
"Are you willing to relocate?" For large IT companies, this question has significant weight. If you say no, you limit your hiring options considerably - TCS might need you in Mumbai, Cognizant might assign you to Hyderabad. The honest answer that works best: "Yes, I'm willing to relocate. I understand that project requirements determine location, and I'm flexible about where I start." If you have genuine constraints (family medical situation, for example), mention them briefly - most HR managers are understanding about real constraints versus preference-based reluctance.
Situational Questions and How to Handle Them
"Tell me about a time you faced a challenge and how you overcame it." Freshers panic because they think "challenge" means a professional crisis. It doesn't. College-level challenges work perfectly: a difficult project deadline, a group project where a team member didn't contribute, a subject you struggled with and eventually mastered. Use the STAR format: Situation (what happened) → Task (what was your responsibility) → Action (what did you specifically do) → Result (what was the outcome).
"What would you do if you disagree with your team leader's approach?" This tests your conflict resolution maturity. The wrong answer: "I'd go above them to the manager." The right answer: "I'd first make sure I fully understand their reasoning - maybe there's context I'm missing. If I still disagree after understanding their perspective, I'd share my alternative suggestion privately and respectfully. If they still prefer their approach, I'd execute it fully because team alignment matters more than individual opinions, especially when I'm new."
"How do you handle pressure or tight deadlines?" Avoid the clichéd "I work well under pressure." Instead, give a specific approach: "I break the task into smaller parts, estimate time for each, and start with the most critical component. During my final year project submission, we had a two-week deadline cut to one week. I mapped out each remaining task, worked on the backend while my teammate handled the frontend in parallel, and we submitted on time. The key was prioritisation - knowing what to finish first and what could be simplified if needed."
Company-Specific Question Patterns
TCS typically has an aptitude test (TCS NQT) followed by a technical interview and an HR interview. The technical round often focuses on programming fundamentals - data structures, algorithms, and your strongest programming language. TCS interviewers tend to go deeper on one topic rather than covering many topics superficially. If they ask about arrays, expect follow-up questions that test increasing depth.
Infosys uses the InfyTQ platform for assessment, followed by technical and HR rounds. Infosys interviewers frequently ask about database concepts (SQL queries, normalization), networking basics (OSI model, protocols), and your final year project. They also tend to ask "rate yourself on a scale of 1-10 in [technology]" - always rate yourself 6-7 if you're a fresher. Rating yourself 9-10 invites difficult follow-up questions; rating yourself 3-4 undermines confidence.
Cognizant conducts the GenC assessment followed by technical and HR interviews. Cognizant's technical round is generally considered less intense than TCS or Infosys - they focus more on conceptual understanding than coding on the spot. However, their HR round is more thorough, with detailed questions about your motivations, flexibility, and long-term commitment. Cognizant has higher onsite requirements in recent years, so expect questions about office attendance willingness.
Final Thoughts
Create a personal "interview answer bank" - a document where you write down your prepared answers to these common questions. Not as a script to memorise, but as a reference you review before each interview. Update it after every interview with new questions you encounter and better answers you think of later. After your fifth interview, this document becomes your most valuable preparation tool because it contains real questions from real interviews, not hypothetical ones from the internet.
