Placement Prep · Lesson 5 of 10

The technical interview: what freshers are asked

A checklist of core subjects and how to answer when you don't know something.

Fresher technical interviews mostly check fundamentals and whether you really did your projects. Expect questions from these areas:

  • Your main language — data types, loops, functions, strings, collections, exceptions. Be ready to write small programs on paper or a shared editor.
  • OOP — class vs object, encapsulation, inheritance, polymorphism, abstraction, with a small example of each.
  • DBMS & SQL — keys, normalisation, joins, GROUP BY, and writing simple queries. See the SQL track.
  • Operating systems — process vs thread, deadlock, memory basics.
  • Networks — what happens when you type a URL, HTTP vs HTTPS, IP and DNS basics.
  • Data structures — arrays, strings, stacks, queues, linked lists, hash maps; time complexity in big-O.
  • Your projects — the deepest questions come from here.

When you don't know

Say so honestly, then reason aloud: "I haven't used that, but I think it works like ... because ...". Interviewers value clear thinking and honesty more than a bluff they will detect immediately.

Thinking aloud while coding

Repeat the problem in your words, ask about edge cases, describe your approach before typing, then test your code with a small example.

Worked example

Adapt it to your situation
Interviewer: "What's the difference between an abstract class and an interface in Java?"

Candidate:
"Both define behaviour that other classes implement. An abstract class can hold state — fields — and constructors, and a class can extend only one. An interface mainly defines a contract; a class can implement many interfaces. In my project I used an interface, PaymentMethod, so that UPI and card payments could be swapped without changing the checkout code."

What to notice

• Starts with what they have in common, then the differences.
• Gives the key practical rule (single vs multiple inheritance).
• Ends with a real example from the candidate's own project — this is what turns a textbook answer into a strong one.

Names, companies and numbers are fictional examples. Always confirm details on the employer's official site.

Key points

  • Revise OOP, DBMS, OS, networks and DS basics.
  • Expect deep questions on your own projects.
  • Say 'I don't know' honestly, then reason aloud.
  • Explain your approach before you code.

Quick check

You're asked about a concept you've never used. What's the best response?

Practice task

For each topic in the list, write a one-paragraph answer in your own words with an example from your projects or daily life. Explain two of them aloud to a friend.

Interview corner

What happens when you type a URL in the browser?

DNS lookup to find the IP, a TCP (and TLS for HTTPS) connection, an HTTP request, the server's response, and the browser parsing HTML and loading CSS/JS. Go deeper only where asked.

Explain time complexity with an example.

It describes how running time grows with input size. Searching an unsorted array is O(n); binary search on a sorted array is O(log n) because it halves the range each step.

Original lesson written by the InfoparkDaily team · © 2026 InfoparkDaily · Free to learn — no paid course or subscription.