FoundationNew Grad

Tell me about a time you faced a difficult problem or got stuck. What did you do?

What they are really testing: A behavioral question testing how you handle being stuck, which is most of real engineering. They want resilience and a problem-solving process, not a hero story. With no job, a project, coursework, or group assignment is completely valid material.

A real interview question

Tell me about a time you faced a difficult problem or got stuck. What did you do?

What most people say

drag me

I do not really get stuck, I just keep working until I figure it out, I am pretty good at solving problems on my own.

"I never get stuck" is a red flag, everyone gets stuck, so it reads as either dishonest or inexperienced, and refusing to ask for help is a negative, not a strength. It also dodges the question by giving no actual example.

The follow-ups they ask next

  • What if your only examples are from school or personal projects?

    That is completely fine for an entry-level interview, the interviewer expects it. A debugging story, a hard assignment, or a group-project conflict all work. They are evaluating your process and resilience, not where it happened.

  • When is it right to ask for help versus pushing through?

    Try to localize the problem first so your question is specific, then ask, struggling alone for days is not a virtue. Good answer: I narrow it down, search and read docs, and if still stuck after a reasonable effort I ask with a clear, specific question.

What the interviewer is listening for

  • Uses STAR with a real example
  • Shows a problem-solving process
  • Honest about asking for help + a genuine lesson

What sinks the answer

  • "I never get stuck"
  • Refuses to ask for help as a "strength"
  • No concrete example

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.

Situation: [a real problem, e.g. my app failed only after deploy]. Task: [what I had to solve]. Action: [how I worked it, layer by layer, what I tried, where I looked, narrowing it down]. Result: [it resolved, and the lesson was X]. And [when genuinely stuck I ask for help, after narrowing it so my question is specific].

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