IT interview preparation for freshers
Your first technical interview is the first time anyone asks you to explain what you know out loud, with follow-up questions, against a clock. Most interview preparation for freshers is reading. This page is about the part reading does not train: what each round looks for, and how to answer so the follow-up works for you.
For final-year students, recent graduates and anyone in their first year of work — campus placements or off-campus. Already working? IT interview preparation for developers.
What a fresher IT interview looks like
Most companies hiring freshers, from large service firms running campus drives to product startups, use some version of three stages.
Online assessment
Aptitude, reasoning and one or two coding problems against a timer. It filters on volume, so the bar is clearing it rather than topping it.
Technical interview
Questions from your resume and the core subjects — a language, OOP, DBMS, data structures — then a project discussion and often a problem solved live. This is where most freshers are decided.
HR interview
Fit, communication, relocation and shifts, and whether what you say matches your resume. Shorter, but a vague or inconsistent answer here can undo a good technical round.
What happens in a technical interview, minute by minute
Technical interview questions for freshers, by subject
Fresher technical rounds draw on a small set of subjects. The questions are rarely hard on their own; the follow-up is where an answer you memorised comes apart.
Data structures and algorithms
Arrays, strings, hashing, recursion and trees, solved out loud with the complexity stated.
Your programming language
Java, Python, C++ or JavaScript — the basics, and the follow-up that checks you understand them rather than remember them.
OOP, DBMS and SQL
The viva subjects, asked as "why", not "define": why normalise, when an index hurts, what inheritance costs.
Web development
If your projects are web apps: how the page renders, where state lives, and how a request reaches the database.
Self introduction: a template for freshers
Nearly every interview opens with “tell me about yourself”. Your answer picks the next ten minutes of questions, so build it around the project you can talk about best. Aim for sixty to ninety seconds, in four parts:
- Who you are, in one line: degree, college, year.
- What you have built: one project, named, with your part in it.
- One specific proof: a problem you solved in it, a number, an internship.
- Why this role: the link between what you did and what they do.
I am Riya, a final-year computer science student at a college in Pune. Over the last year I have mostly built web applications — the one I am proudest of is a hostel complaint tracker that about two hundred students in my hostel used. I built the backend in Node.js and MySQL, and the hardest part was stopping duplicate complaints when the same issue was reported several times a minute. That is why this backend role interests me: it is the kind of problem I want to spend more time on.
Leave out your percentage, your family and a list of hobbies. Every skill you name is a skill you can be asked about.
How to explain your college project
For most freshers the project discussion is the longest part of the technical round, and the part you control most. The interviewer is checking whether you built it and whether you understand why it was built that way.
- Lead with the problem it solved, not the tech stack.
- Say exactly which part you built, especially in a team project.
- Have one decision ready to defend: why that database, why that structure.
- Know what broke and what you would change now. "Nothing" is the wrong answer.
HR and behavioural questions
The HR round checks that the person in the room matches the resume: why this company, whether you can relocate or work shifts, what you would do in a conflict. Answer honestly and specifically; for “tell me about a time…” questions, use the STAR structure — situation, task, action, result.
Say it out loud before it counts
A round with Sia, at Beginner difficulty
Three, five or eight questions, one at a time, with follow-ups on what you actually said. Scored the moment you finish, with a written breakdown of where each answer fell short. Repeat it as often as you like.
A live interview with an engineer
Forty minutes over Zoom with someone who interviews for a living. They score five criteria, write up what to fix, and you keep a numbered certificate for the session.
Every round is scored the same way — see how scoring works. Pay per session, no subscription.
Questions freshers ask
When should a fresher start preparing for interviews?
Ideally two to three months before placements or applications open, so the core subjects and a few scored interviews fit around college. If you only have two weeks, prioritise your own projects, one language and the most common data structures.
Do freshers get asked system design?
Rarely as a full round. Some product companies ask a small design question, scoped to a feature rather than a whole system. Data structures, a language, DBMS and your projects come up far more often.
I am from a non-CS branch. Will that count against me?
Less than you might think, if your projects and fundamentals are solid. Expect to be asked why you moved to software; a specific, honest answer works better than a general one.
Is an interview with Sia useful if I have never had a real one?
That is when it helps most. The first time you explain an answer out loud under follow-up questions should not be the interview that counts. A round with Sia can be set to Beginner difficulty for exactly that.
Read next
- What Happens in a Technical Interview: A Minute-by-Minute Breakdown for Freshers
- Behavioral Interviews for Freshers: The STAR Method, Done Properly
- How to Prepare for a Technical Interview in 2 Weeks (Fresher's Day-by-Day Plan)
- AI Mock Interviews vs Human Mock Interviews: Which Should a Fresher Choose?