FoundationNew Grad

Walk me through a project you built.

What they are really testing: For a candidate with no job history this is the single most important question. They are checking whether your project is real and yours, whether you understand it deeply or just followed a tutorial, and whether you can communicate technically. Depth of decisions matters more than the project being impressive.

A real interview question

Walk me through a project you built.

What most people say

drag me

I built a web app using React and Node and a database, and it has login and a dashboard, and it works.

This is a feature list, not an engineering story. It shows no decisions, no problems solved, and no understanding of why anything was done. It reads exactly like a tutorial follow-along, which is what the interviewer is screening for.

The follow-ups they ask next

  • What would you do differently if you rebuilt it?

    Have a real answer ready, this is almost always asked. Pick something genuine (do CI/CD earlier, choose a managed database, write tests first). It shows reflection and growth, "nothing" signals you have not thought critically about your own work.

  • Did you build this yourself or follow a tutorial?

    Be honest. Following a tutorial to start is fine, the question is what you understood and changed. Say what you added, broke, fixed, or decided on your own. Owning the decisions is what makes it yours.

What the interviewer is listening for

  • Explains decisions and trade-offs
  • Describes a real problem they debugged
  • Reflects on what they would change

What sinks the answer

  • Just lists technologies/features
  • No decisions or problems
  • Cannot answer "what would you change"

If you genuinely do not know

Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.

I built [a real app] because [a genuine reason]. The interesting part is the decisions: [I chose X over Y because Z]. The hardest problem was [something that broke], and I [debugged it down to the cause and fixed it]. If I rebuilt it I would [one honest improvement]. I can go deeper on [any part].

Keep going with new grad

All 336 cloud engineer questions

Knowing the answer is not the same as recalling it under pressure

Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.

Start free