Interview questions
Software engineer interview questions for freshers
Fresher software interviews are more predictable than the horror stories suggest. Most run the same arc: your projects, some computer-science fundamentals, a problem or two, and questions that check whether you can talk about code — not just write it.
That last part is the silent filter. Plenty of students can solve the problem but can't explain their approach out loud, and the interview only measures what you can say. These are the questions to practice speaking, not just solving.
Question 1
Walk me through your best project.
The most important answer of the interview — it's where follow-ups come from. Cover what it does, your specific part, the hardest problem you hit, and one thing you'd do differently. If you can't go three levels deep on it, pick a different project.
Question 2
What happens when you type a URL into a browser?
A layered classic: DNS, TCP/TLS, the HTTP request, the server, rendering. Go as deep as you genuinely know and say where your knowledge ends — that honesty reads far better than a memorized script that collapses at the first follow-up.
Question 3
Explain the four pillars of OOP with real examples.
Encapsulation, abstraction, inheritance, polymorphism — everyone can recite them. You stand out by pointing at where each one lives in your own project instead of the textbook's Animal/Dog example.
Question 4
What's the difference between an array and a linked list?
They're checking whether you think in trade-offs: contiguous memory and O(1) index access versus O(1) insertion and no resize cost. Bonus points for saying when you'd actually pick each.
Question 5
How would you find a bug in code that worked yesterday?
A process question wearing a technical mask. Say the steps: reproduce it, check what changed (git log, dependencies, data), isolate with logs or a debugger, fix, and add a test. "I'd Google it" is only step four.
Question 6
Explain a REST API to someone non-technical.
Communication check. A waiter analogy or a form-and-response analogy in two or three sentences is perfect. If you reach for "stateless" and "idempotent" with a non-technical audience, you've failed the actual test.
Question 7
What is the time complexity of your solution — can you do better?
Expected after any coding problem. State the complexity and why, then think out loud about improvement honestly. Interviewers routinely ask "can you do better?" even when you can't — it's a composure check.
Question 8
SQL: write a query to find the second-highest salary.
The single most common fresher SQL question. Know two approaches (a subquery with MAX, and LIMIT/OFFSET or a window function) and mention how yours behaves with duplicates — that's the follow-up.
Question 9
What is the difference between a process and a thread?
Core OS fundamental: processes own isolated memory, threads share it within a process. Follow-ups usually probe why shared memory is both the benefit and the danger — mention race conditions before they ask.
Question 10
Why do you want to be a software engineer?
The HR round doesn't disappear for technical roles. Something specific you built and the moment it worked beats "I'm passionate about coding" — passion is claimed, moments are evidence.
Common questions
Do fresher software interviews always include DSA?
At large companies and campus placements, almost always — usually arrays, strings, and one or two standard problems, not competitive-programming puzzles. Smaller companies and startups often weight your projects more heavily than algorithms.
How deeply will they ask about my projects?
Deep enough to detect a tutorial clone: why this stack, what broke, how you fixed it, what you'd change. If you built it yourself, this is the easiest part of the interview. If you didn't, it's the round that catches it.
Can I practice a mock software interview by voice?
Yes — Opiliant runs a voice interview for software roles with follow-up questions on your answers, then scores your content, structure, and communication. Your first interview is free when you sign up.