TLDR;
- It is okay to not know the answer. Be honest about it.
- Listen to question and understand what interviewer is trying to understand from you.
- Interview is not a points system.
- Ask for feedback.
I have put together these points from personal experience interviewing freshers and identified real scenarios when candidates missed or forgot answers.
Remember – interview is NOT a question paper, and you aren’t collecting points.
An interview is a conversation. The interviewer is trying to understand what you already know, how you think and communicate, and whether you could be a good fit for the role.
Here is some practical interview advice for freshers on what to do before, during and after the interview.
Before the Interview: Prepare Without Memorizing
A good conversation is easy when you have something to talk about. This is why preparation matters.
Know Your Resume and Projects
Go through your resume before the interview and make sure you can explain everything you have mentioned. This is particularly important for projects.
Be clear about what the project did, what you personally worked on, and what you learned from it.
Lets say you worked as part of a team that developed a grocery app and you have contributed mainly to the frontend. Instead of presenting yourself as someone who built the entire application, you could say:
Candidate: “I worked on the development of a grocery app. I used ReactJS for the UI and contributed to the landing page and checkout page.” – This gave complete picture about tech without going in too much detail.
That tells the interviewer where your actual experience lies.
If the project also used Node.js and MySQL but you did not personally work on those parts, don’t present them as your own experience. This matters because anything on your resume can become a follow-up question.
How to Prepare Your Introduction?
Don’t memorize a long speech that sounds the same every time you say it. Prepare the important points you want to communicate. It can give the interviewer some useful context.
For example:
[Who you are] -> [What you have done] -> [What you want to do]
Candidate: “I am Arun. I’m learning Python and I’ve worked on a couple of data analytics projects using it, and I’m now looking for an opportunity where I can work more deeply in that area.” – This is better because it provides more useful information.
That short intro tells the interviewer about your interest, experience and direction. It also gives them something they can ask about.
You can read our guide on how to introduce yourself in an interview for more detailed advice on preparing your introduction.
Prepare for Questions Based on Your Own Experience
Prepare for questions that are likely to come from your resume, projects and role you are applying.
If you have mentioned ReactJS, Node.js, Python, MySQL or another technology, be prepared to explain how you used it. If you have listed a project, think about the technical parts and problems you faced during project. Its a good discussion subject.
You can also use our common interview questions for freshers article to identify topics you should revise before the interview.
Prepare material, not speech.
During the Interview: Listen to What They Are Looking For
Once the interview starts, don’t think only about giving the “right” answer and waiting for the next question.
Listen carefully and try to understand what the interviewer is trying to learn from your answer. Your answers can also help the interviewer discover something useful about you.
Give the Interviewer Something to Explore
Suppose the interviewer asks:
Interviewer: “Which frontend technology have you used?”
You could simply say:
Candidate 1: “I have used ReactJS in my project.” – This is plain answer. No useful additional information.
That answers the question. But if you genuinely have something useful to add, you could say:
Candidate 2: “I used ReactJS in my project, and because of that our UI development became faster.” – This is better because it opens opportunity for easy follow-up question.
Now you have introduced something the interviewer can explore. They might ask:
Interviewer: “How did React make your UI development faster?” – Easy follow-up that you can prepare for.
You can then explain what you actually did and giving them a genuine information that can lead to a useful discussion.
Your Technical Answers Can Create Talking Points
The same approach works with technical questions.
Suppose the interviewer asks:
Interviewer: “Where did you store the data for your app?”
You could answer:
Candidate 1: “We stored the data using MySQL.” – Very basic answer. Interviewer can get this in resume also.
That’s correct, but it doesn’t tell the interviewer much about how you developed the system.
If it is accurate, you could instead say:
Candidate 2: “We created a backend API that accepts a JSON object with specified parameters and an authentication token. The API call then stored the data in a MySQL database running locally.” – This gave more info about API, authentication along with just DB.
You have answered the question, but you have also introduced several areas the interviewer can explore: the API, JSON parameters, authentication and the database setup.
The interviewer might ask ‘how the API worked’, ‘how authentication was handled’, or ‘why the database was running locally’. You have an opportunity to explain work you have actually done.
Don’t Force Your Talking Points
Not every detail needs to become a discussion.
If you are interviewing for a backend position, for example, mentioning that you worked with ReactJS may not be useful if the interviewer is trying to understand your backend experience.
Use your judgment. Introduce relevant details, then wait.
You don’t need to explain everything you know. Let the interviewer pick up the points they are interested in.
The goal is not to talk more. The goal is to help the interviewer understand you better.
Use Your Introduction to Start the Conversation
The first few minutes it feels very robotic when a fresher gives a heavily practiced introduction which feels like speech. Your introduction should give the interviewer a quick idea of who you are, what you are interested in, what you have worked on, and what you are looking for.
For example:
Candidate: “I’m interested in AI image classification. I’ve worked on a couple of projects around it, and I’m now looking for an opportunity where I can work more deeply in that area.”
That gives the interviewer several things they can ask about. They might want to know what you built, why you became interested in image classification, or what you learned from those projects.
Your introduction need not contain everything about you. It just needs to give the interviewer enough context to start a useful conversation.
For a more detailed guide, see our article on how to introduce yourself in an interview.
When You Don’t Know the Answer: Be Honest
There is nothing wrong with not knowing the answer to a question. What can hurt you is pretending that you know it.
The first rule is simple: don’t tell the interviewer that you have done something when you haven’t.
If you have worked only a little with a technology, be honest about your level of experience and then explain what you genuinely know.
For example, if an interviewer asks about authentication in an API and you only worked on a small part of it, don’t suddenly explain how you supposedly designed the entire authentication system.
You could say:
Candidate: “I worked on this part of the API, but I didn’t implement the authentication myself. I have a basic understanding of how it works, though.” – As a fresher, this is good response.
Then explain what you actually know.
If you don’t know the answer, don’t try to construct something that sounds convincing just to get through the question. An experienced interviewer can often tell when a candidate is making things up.
A simple:
Candidate: “I’m not sure about this. I’ll have to learn more about it.” – This is acceptable answer for a fresher.
is much better than an invented answer.
What If You Misunderstood the Question?
Sometimes the problem is not that you don’t know the answer but you have understood the question differently.
If you realize that happened, acknowledge it and restart.
For example:
Candidate: “I’m sorry, I thought the question was about ____. I understand now that you are asking about ____. I’m not very familiar with that yet.” – Being honest shows you are mature and improve.
If it is something relevant to the job, you can add:
Candidate: “If this is something I need to work with, I’ll be able to learn and implement it.” – Reassuring helps when you are ready to learn new things.
You don’t need to pretend that you already know everything. Be honest about the gap and, where appropriate, show that you are willing to learn.
For more info on talking about your strengths such as being a quick learner, see our article on the best answer for “What Is Your Strength?”.
If You Go Blank, Take a Moment
Going blank during an interview is normal, especially when you are a fresher. You may know the subject but suddenly struggle to recall what you want to say. I have gone blank during my interviews as interviewee and sometimes as an interviewer. Its completely natural.
If repeating the question helps you settle down and focus, you can repeat it once out loud. You don’t need to do this for every question. Once or twice during an interview is perfectly reasonable.
You can also use whatever short phrase feels comfortable to give yourself a moment to think.
But don’t deliberately stall because you are hoping the interviewer will move on to the next question.
If you genuinely don’t know the answer, it is better to say so:
Candidate: “I’m not sure about this. I’ll have to learn more about it.” – This is better and helps keep conversation going instead of creating bad impression about candidate.
Stalling for time when you know you don’t have an answer can be more damaging if the interviewer realizes what you are doing.
Preparation helps too. The more familiar you are with your projects, the technologies on your resume, and the questions commonly asked for the role, the less likely you are to completely blank when something familiar comes up.
Don’t Treat the Interview Like a Points System
Sometimes you give an answer that is wrong. You may get a question you have never seen before. You may even realize halfway through the interview that you gave an incorrect answer. This happens and interviewers understand. Its sometimes hard during stressful meetings.
Don’t assume that one bad answer has ruined the interview.
If you realize that you made a mistake, acknowledge it.
Candidate: “I think I made a mistake in my previous answer.” – Interviewer will appreciate you for realizing error.
The interviewer may give you another opportunity to explain it. If you still don’t know the correct answer, be honest about that too.
What you should not do is spend the rest of the interview thinking about the mistake.
There is NO points table where every correct answer adds and wrong answer removes a fixed number of points. One wrong answer does not automatically cancel everything else you have answered during the interview.
Opposite is true as well. A candidate who has answered all questions correctly can still damage the interview by intentionally making up an answer when they don’t know something.
So stay positive and engaged until the interview is over.
Ask Questions and Get Feedback
Most interviewers will give you an opportunity to ask questions at the end. Don’t automatically say, “No, I don’t have any questions.” – This should be avoided.
If you want to understand the position better, use the opportunity.
You can ask:
Candidate: “Could you tell me a little more about the job role?”
Candidate: “What kind of work would I be doing?”
Candidate: “How large is the team?”
You don’t need a long list of questions. A couple of genuine questions are enough.
If the interviewer hasn’t specifically offered time for questions, you can first ask:
Candidate: “If you have a minute, can I ask a couple of questions about the position?”
or:
Candidate: “I wanted to understand a little more about the job. If you have a few minutes, could you tell me more about it?”
Some companies may not be able to share details about a project or client, and that’s fine. Ask what they can reasonably tell you.
Ask for Feedback
One of the most useful things you can get from an interview is feedback.
If the interviewer is willing to share it, ask:
Candidate: “How did I do and what can I improve on?” – Show them you are a willing to take feedback and improve.
or:
Candidate: “Which topics should I improve on?” – This helps technical improvements.
You can also ask:
Candidate: “Which technologies would you suggest I learn and practice?” – Gives you better practical items to learn instead of just fresher projects.
Keep it short, ask naturally, and respect the interviewer’s time.
After the Interview: Learn From It and Move On
Once the interview is over, don’t spend hours thinking about every answer you gave or regretting the mistakes you made. You can’t change that interview. There will be another one.
Instead, focus on what you can learn from it.
Start With What You Didn’t Know
Think about the questions you couldn’t answer and try to understand why you reached that point.
For example, imagine the interviewer asked:
Interviewer: “What is the difference between Node.js and PHP?”
or:
Interviewer: “What is the difference between MySQL and MongoDB?”
First, identify what you didn’t know. Then think about how the question came up.
- Was the technology mentioned in your resume?
- Was it part of a project you worked on?
- Did you mention it during the interview?
- Was it something another team member worked on but you didn’t?
If it came from your resume, prepare it properly before your next interview. If you didn’t actually work with it, be honest about your level of experience next time.
If the question came up naturally during the conversation, think about whether something similar could happen again and prepare accordingly.
Think About What You Missed
You may also realize that you could have explained something better.
Perhaps you mentioned a project but forgot to explain an important part of your contribution. Maybe the interviewer asked about something related to your experience, but you didn’t recognize the opportunity to talk about what you actually did.
Don’t regret it. Remember it.
The next time a similar opportunity comes up, you will know when to bring that information into the conversation.
Important Points
The best interview advice for a fresher is not to try to appear perfect.
It is okay not to know the answer. Be honest about it.
Listen to the question and understand what the interviewer is trying to learn. When there is an opportunity, introduce genuine talking points from your projects, experience and interests so the interviewer can understand you better.
And remember that the interview is not a points system. One question you couldn’t answer does not decide your entire interview. Stay positive and engaged until the end.
Finally, whenever the interviewer has the time, ask for feedback. A simple question about what you should improve or which technologies you should practise can make your next interview better.
Prepare seriously. Be honest. Listen carefully. And remember that an interview is a conversation, not a viva.