Q1: “Tell me about yourself”

Why they ask: The #1 most asked question in any interview, anywhere. It tests your communication skills and whether you can structure your thoughts. The interviewer forms 50% of their impression in the first 90 seconds — this question IS those 90 seconds.

What most freshers say (wrong): “My name is [Name], I am from [City], I did my schooling at [School], I scored 85% in 10th and 78% in 12th, then I joined [College] for B.Tech in Computer Science...” — a chronological biography that puts the interviewer to sleep.

What to say instead (right): “I am [Name], a final year [Branch] student at [College]. My strongest technical skills are [2–3 skills]. During college, I [one achievement — project, internship, or competition]. I am looking for a role where I can apply these skills and grow as a professional.”

Tip: 90 seconds max. Education → Skills → One achievement → What you want. Do not start from 10th class. Do not list hobbies unless they are relevant.

Q2: “What are your strengths and weaknesses?”

Why they ask: Tests self-awareness. Every fresher gets this question. The interviewer is not looking for perfection — they are looking for honesty and maturity.

What most freshers say (wrong): “My strength is I am a hard worker. My weakness is I am a perfectionist.” — generic, rehearsed, and the interviewer has heard it 500 times today.

What to say instead (right): Strength — pick one with proof: “I am good at breaking down complex problems — in my final year project, I divided a 6-month project into 2-week sprints and we delivered on time while other teams missed their deadlines.”

Weakness — pick a real one with a fix: “I tend to spend too much time on research before starting a task. I have been working on this by setting time limits for research and forcing myself to start building sooner.”

Q3: “Why should we hire you?”

Why they ask: Tests whether you can sell yourself in 60 seconds. Most freshers freeze here because they feel they have nothing to offer.

What most freshers say (wrong): “Because I am hard-working and a quick learner.” — every candidate says this. It means nothing.

What to say instead (right): “I have strong fundamentals in [skill], I built [project] which shows I can apply what I learn, and I am genuinely interested in [company's domain]. I may not have industry experience yet, but I learn fast and I am willing to put in the work.”

Q4: “Where do you see yourself in 5 years?”

Why they ask: Tests ambition and whether you will stay with the company long enough to justify training you.

What most freshers say (wrong): “I want to be a manager.” (Too generic — every candidate says this.) Or worse: “I want to start my own company.” (Red flag — they think you will leave as soon as you learn enough.)

What to say instead (right): “In 5 years, I want to be a strong technical professional who can lead small teams and mentor newer engineers. I want to grow within a company that invests in my development.”

Q5: “Why do you want to join our company?”

Why they ask: Tests whether you researched the company or are just applying everywhere on Naukri and hoping something sticks.

What most freshers say (wrong): “Because it is a reputed company with good growth opportunities.” — this answer works for literally any company. The interviewer knows you did zero research.

What to say instead (right): Mention ONE specific thing — their training program, a product they built, a client they work with, or their technology stack. Example: “I want to join [Company] because your ILP training program is one of the best in the industry, and I want to build a strong foundation before specializing.” Ten minutes of research on the company website separates you from 80% of candidates.

Q6: “Tell me about your final year project”

Why they ask: This is the only “experience” a fresher has. It tests your communication skills and whether you actually built something or just copied code from GitHub.

Structure your answer: What problem it solves → What technology you used → What your specific contribution was (if team project) → What you learned.

Tip: Practice this until you can explain it in 3 minutes to someone who is not in your field. If your non-technical friend understands your project explanation, you are ready.

Q7: “Are you willing to relocate?”

Why they ask: Deal-breaker for service companies that post employees across India — Chennai, Bangalore, Hyderabad, Pune, Mumbai, Kolkata, and smaller cities.

The only correct answer: “Yes.” Always yes. Even if you have a preference, say yes first. Hesitation or conditions on this question gets freshers rejected more than any technical question ever will.

Q8: “Do you have any questions for us?”

Why they ask: Tests genuine interest. Saying “no” is a red flag — it signals you do not care enough to be curious.

Good questions to ask: “What does the first 6 months look like for a new hire?” / “What technologies will I be working with?” / “How is performance evaluated for freshers?”

Bad questions to ask: “What is the salary?” (too early in the process) / “How many leaves do I get?” (sends the wrong signal about your priorities)

Q1: “Explain OOP concepts”

Why they ask: The universal technical question. If you are a CS, IT, or ECE student, you will get this. It appears in campus placements at TCS, Infosys, Wipro, Cognizant — everywhere.

What the interviewer evaluates: Not whether you can list the four pillars — every candidate does that. They want examples. If you say “polymorphism means many forms” and stop, you fail. If you say “polymorphism means I can call the same method draw() on a Circle object and a Rectangle object and each one behaves differently — that is runtime polymorphism through method overriding,” you pass.

Cover these four with simple examples: Inheritance (a Car class extending a Vehicle class), Polymorphism (method overloading vs overriding), Abstraction (hiding complex logic behind a simple interface), Encapsulation (private variables with public getters/setters).

Q2: “What is the difference between an array and a linked list?”

Why they ask: Tests data structure basics. This is the most common data structure question for freshers because it tests whether you understand memory allocation and access patterns.

What the interviewer evaluates: Can you explain when to use which? Not just definitions — practical trade-offs.

Key points: Arrays have fixed size and O(1) random access but expensive insertion/deletion. Linked lists have dynamic size and O(1) insertion/deletion at known positions but O(n) access. Arrays use contiguous memory; linked lists use scattered nodes connected by pointers. In practice, arrays are used more often because CPU cache performance favors contiguous memory.

Q3: “Write a program to reverse a string”

Why they ask: The most common coding question for freshers. It tests whether you can write working code under pressure — not whether you can solve complex algorithms.

public static String reverse(String s) {
    char[] chars = s.toCharArray();
    int left = 0, right = chars.length - 1;
    while (left < right) {
        char temp = chars[left];
        chars[left] = chars[right];
        chars[right] = temp;
        left++;
        right--;
    }
    return new String(chars);
}

What the interviewer evaluates: Can you write syntactically correct code? Do you handle edge cases (empty string, single character)? Can you explain your approach before writing? The solution does not need to be clever — it needs to be correct and clear.

Q4: “What is DBMS normalization?”

Why they ask: Tested at every service company interview. Most TCS, Infosys, and Wipro projects involve databases, so they want freshers who understand the basics.

What the interviewer evaluates: Can you explain normalization with a simple example — not just recite definitions?

Key points: Normalization reduces data redundancy. 1NF: atomic values, no repeating groups. 2NF: 1NF + no partial dependencies. 3NF: 2NF + no transitive dependencies. Use a student-course table example: show the redundancy, then normalize it step by step. Interviewers love candidates who can walk through a concrete example instead of reciting textbook rules.

Q5: “Explain your favorite programming language's key features”

Why they ask: They want to see passion and depth in at least one language. If you list Java on your resume, they expect you to explain why you like it and what makes it different.

What the interviewer evaluates: Do you actually use this language or did you just list it on your resume? Can you go beyond surface-level features?

Tip: Pick the language you are most comfortable with. Know 3–4 features deeply — for Java: platform independence (JVM), garbage collection, multithreading, strong OOP support. For Python: dynamic typing, extensive libraries, readability, versatility across domains. Do not list 10 features superficially — explain 3–4 with conviction.

Q1: “Tell me about a time you worked in a team”

Why they ask: Every job involves teamwork. They want to know if you can collaborate or if you are the person who does the entire group project alone and resents everyone.

What most freshers say (wrong): “I worked in a team for my final year project. We divided the work and completed it.” — too vague, tells the interviewer nothing.

What to say instead (right): Use a college project, event organization, or competition as your example. Structure: What was the goal → What was your role → What challenge did the team face → How did you contribute to solving it → What was the result. Example: “During our college tech fest, I led a 4-person team to build the event website. Two days before launch, our backend developer fell sick. I picked up his pending API work even though I was focused on frontend, and we launched on time. I learned that flexibility matters more than role definitions in a small team.”

Q2: “How do you handle pressure?”

Why they ask: IT jobs involve deadlines, client escalations, and production issues. They want to know you will not crumble under stress.

What most freshers say (wrong): “I work well under pressure.” — empty claim with no evidence.

What to say instead (right): Give a specific example from exams, deadlines, or competitions. Example: “During my semester exams, I had three exams in three consecutive days. I created a priority-based study plan — focused on high-weightage topics first, used past papers to predict questions, and managed to score above 75% in all three. I handle pressure by breaking the problem into smaller, manageable tasks instead of panicking about the whole thing.”

Q3: “What will you do if you are assigned a technology you do not know?”

Why they ask: In service companies, you rarely get to choose your technology stack. They need freshers who can adapt, not complain.

What most freshers say (wrong): “I will learn it.” — correct but too vague. Every candidate says this.

What to say instead (right): “I will learn it — and here is proof I can. For my final year project, I had to learn React in two weeks because our team decided to switch from plain HTML. I used YouTube tutorials, the official documentation, and built a small practice project before touching the main codebase. Within two weeks, I was contributing production-ready components. I am comfortable learning new technologies because I have done it before.”

Q4: “If you do not get this job, what will you do?”

Why they ask: Tests resilience and whether you have a plan beyond this one interview. They also want to see if you will say something desperate or negative.

What most freshers say (wrong): “I will be very disappointed.” or “I really need this job.” — desperation is not a selling point.

What to say instead (right): “I will keep improving my skills and applying. One rejection does not define my career. I will analyze what I could have done better in this interview, work on those areas, and come back stronger for the next opportunity. But I genuinely hope to be selected here because [specific reason about the company].”