
Twenty common interview questions for freshers, grouped into HR, technical and situational, with clear tips and sample answer structures for each.
You cannot predict every question, but many fresher interviews repeat the same themes. Practise these twenty questions out loud, in your own words, and you will feel far more prepared. Do not memorise a script, because it sounds unnatural and breaks when the interviewer changes a word. Instead, remember your key points and a real example for each.
HR and personal questions
1. Tell me about yourself. This is usually the first question. Give a 60-to-90-second summary: your education, your main skill or project, and why you want this role. Do not repeat your whole resume. Example structure: "I completed my BCA this year. During my course I built a student attendance app using Java and MySQL. I enjoy solving problems with code, which is why I am applying for a developer role."
2. Why do you want to work here? Show that you have researched the company. Mention what it does, one product or value that interests you, and how your skills fit. Avoid generic answers like "it is a good company".
3. What are your strengths? Choose two real strengths relevant to the job, and back each with a short example, such as finishing a project on time with a team.
4. What is your weakness? Name a genuine one that you are working on, and explain what you are doing about it. For example: "I used to spend too long on small details, so I now set time limits for each task." Avoid fake weaknesses like "I work too hard".
5. Where do you see yourself in five years? Talk about growing your skills and taking on more responsibility in the same field. Do not say you plan to leave or that you have no plan.
6. Why should we hire you? Connect your skills, projects and attitude to what the role needs. Keep it confident but not boastful.
7. Why is there a gap in your studies or career? Be honest and brief, and focus on what you learned or did during that time, such as a course, a project or family responsibilities.
Technical and role questions
8. Walk me through your best project. This is one of the most important questions. Cover the problem, your role, the tools, one challenge you solved and the result. Be ready for follow-up questions on any part.
9. What is the difference between an array and a linked list? Say that an array stores items in continuous memory and gives fast access by index, while a linked list stores nodes connected by pointers and makes inserting or removing easier. Mention when you would choose each.
10. What is object-oriented programming? Name the four ideas, which are encapsulation, abstraction, inheritance and polymorphism, and give a simple real-life example for each, such as a vehicle class with car and bike subclasses.
11. What is a primary key? Explain that it uniquely identifies each row in a table and cannot be empty or repeated. Mention a foreign key as the link to another table.
12. What happens when you type a web address into a browser? Describe the order: the browser finds the server address through DNS, sends an HTTP request, the server processes it and returns a response, and the browser renders the page.
13. What is the difference between manual and automation testing? For testing roles. Mention that manual testing is done by people, is good for exploring and usability, while automation uses scripts for repeated, stable checks that need speed and consistency.
14. What is the difference between GET and POST? GET reads data and puts parameters in the address, while POST sends data in the body, usually to create or change something.
15. Which tools and technologies are you comfortable with? List only what you can discuss in depth. It is far better to say three things well than ten things weakly.
Situational and behavioural questions
16. Tell me about a time you faced a problem and solved it. Use the STAR method: Situation, Task, Action, Result. Example: your team project had a bug the day before submission; you found the cause using logs, fixed it and added a test.
17. How do you handle pressure or deadlines? Describe how you plan, prioritise and communicate early if something is at risk. Give a real example from exams or projects.
18. How do you work in a team? Share a group project, your role, how you handled a disagreement and what you learned from others.
19. What would you do if you did not know the answer to a problem? Show that you break the problem down, search documentation, try small experiments and ask for help after making an honest attempt.
20. Do you have any questions for us? Always ask one or two. Good examples: "What would the first three months look like for this role?" or "How does the team give feedback to new joiners?" Do not ask about salary first.
General tips for every answer
- Keep answers focused, about one to two minutes each.
- Use real examples from projects, studies and teamwork.
- It is fine to say "I am not sure, but here is how I would find out".
- Be honest; interviewers often test claims with follow-up questions.
- Practise with a friend or record yourself to improve clarity and pace.
Before the interview day
Read the job description, research the company, revise the fundamentals of the skills on your resume, prepare your project walk-through and plan your route or test your internet connection. Dress neatly, arrive early and keep a copy of your resume.
Ready for the next step?
Want a mock interview and honest feedback? If you would like guidance from people who work in the industry, join our free career guidance workshop or request a free career discovery session. We will look at your background and help you plan what to learn and build next.
Need career guidance from industry experts?
Join our free workshop or request a free career discovery session.


