For a fresher, the strongest answers turn real learning into evidence. You do not need to claim a full-time job you have not held. A course project, internship, volunteer task, part-time role or independent build can show how you work. This guide selects recurring question types found in university career guidance; it is not a measured ranking of what every employer asks.

“Tell me about a project you are proud of”

Pick a project whose decisions you can explain. State the problem, your contribution, one difficult choice and the result. If it was a team project, separate “we built” from “I implemented.” An illustrative answer might explain that you designed a small API, wrote tests for invalid inputs, and learned from a failed first deployment. Replace that example with your own facts.

“What did you do when you did not know something?”

Employers can evaluate learning even without long work history. Describe a specific gap, where you looked, how you checked your understanding and what changed in your work. “I watched tutorials” is a start; “I built a small test, compared it with documentation and corrected my assumption” shows a method.

“Describe a disagreement in a team”

Use a manageable example, not a story that exposes classmates or colleagues. Explain what each person cared about, what evidence you brought, how a decision was made and what you learned. A good answer does not require you to have “won.” It shows listening and a constructive result.

“Why this role?”

Connect a requirement in the posting to a real interest and an example of preparation. “I want to learn” is honest but incomplete. Name what you can contribute now, what you want to develop and why this team is a sensible place to do that work. Research the employer; do not copy a generic mission statement into your response.

“What is one weakness you are working on?”

Choose a real, non-disqualifying development area and show a concrete action. For example, you may have learned to ask for an interface agreement earlier in a team project instead of discovering integration mismatches at the end. Avoid presenting a strength as a fake weakness. The action and learning are more important than a polished label.

A project evidence worksheet

  1. Name one project and the problem it served.
  2. List what you personally decided or built.
  3. Record one obstacle and how you checked a possible fix.
  4. Describe the outcome without invented percentages.
  5. Prepare a follow-up: what would you improve now?

Use the same project for different questions only when each answer highlights a genuinely different decision. If every answer sounds identical, gather another example. The common-question guide provides the broader selection method; Interview Challenge helps you rehearse published questions.

Sources: Harvard FAS interviewing and Penn interview guidance. The examples are illustrative, not claims about any real applicant.