What gets asked in a fresher technical round, why your own projects are the most dangerous part of it, and what to do when you genuinely do not know.
Quick answer
What technical questions are freshers asked in interviews?
Fresher technical rounds cover four areas: your own projects in depth, core computer science subjects (OOP, DBMS, operating systems, networks), data structures and algorithms with a coding or pseudocode question, and fundamentals of the language on your resume. Projects are usually the largest share, because they are the only place an interviewer can test whether you actually understand what you claim to have built.
A fresher technical round is not trying to find out whether you know everything. It is trying to find out whether what you claim to know is real, and whether you can think when you are stuck.
That distinction changes how you prepare. Depth in the few things on your resume beats shallow coverage of a syllabus, and a structured "I do not know, but here is how I would work it out" scores better than a confident wrong answer.
| Area | Share of a typical round | What is being tested |
|---|---|---|
| Your projects | 30–40% | Whether you did the work and understood your own decisions |
| Core CS subjects | 25–30% | Whether the fundamentals are usable, not just memorised |
| DSA / coding | 20–30% | Problem-solving approach, not just a correct answer |
| Language fundamentals | 10–15% | That you know the language you listed well enough to use it |
The follow-up is the real question
Anyone can recite the definition of normalisation. The question that separates candidates is "when would you not normalise?" — prepare the second-level answer for every fundamental you revise.
The interviewer has your resume and roughly ten minutes. Projects are the cheapest way for them to find out whether you are genuine, so expect the deepest questioning here.
For every project on your resume, be ready with
If a project cannot survive that list, either learn it properly or take it off the resume. See common resume mistakes.
Most fresher coding questions are easy-to-medium: string manipulation, array traversal, a hash map, occasionally a two-pointer or basic recursion. The evaluation is mostly about method.
For what to practise beforehand, follow the DSA roadmap.
You will be asked something you cannot answer. This is deliberate, and it is not automatically a rejection — how you handle it is part of the test.
| Days | Focus |
|---|---|
| 1–3 | Your own projects — write out the seven answers above for each one |
| 4–7 | OOP and DBMS, with a second-level "when would you not" answer for each concept |
| 8–10 | OS and networks fundamentals |
| 11–13 | Daily coding practice, out loud, on paper or a whiteboard rather than an IDE |
| 14 | One full mock technical interview with someone who will push back |
For most campus roles: arrays, strings, hash maps, stacks, queues, recursion basics, sorting and searching, and simple trees. Advanced graph and dynamic programming problems appear mainly at product companies with harder hiring bars.
You will be asked about your own core subjects with the same depth, plus whatever technology your projects use. The structure of the round does not change — the syllabus does.
Yes, when it is true, and then show how you would approach finding out. Bluffing is caught almost immediately and costs far more than the missed question.
Usually yes, unless the role specifies one. Use the language you are fastest in — see which language to pick for placements.
Get pushed on your own projects by someone who will actually challenge the answers.
Book a live mock interview →What a coding interview actually evaluates beyond "did you get the right answer", and how to approach a problem out loud, under pressure.
Coding & TechnicalA structured order to learn DSA in — from arrays and strings through to graphs and dynamic programming — instead of random, unordered problem-solving.
Coding & TechnicalC++, Java or Python? The honest answer is that the choice matters less than the commitment — but the trade-offs are real, and worth knowing before you pick.
Interview PreparationThe questions that come up in almost every fresher interview — what each one is actually testing, and how to build an answer that sounds like you rather than a script.