JuniorBehavioural

Tell me about a time you had more work assigned than you could realistically finish. What did you do?

What they are really testing: They want to see whether you go quiet and hope, or surface the problem early with a plan. Junior candidates who raise a flag early are far cheaper to manage than ones who miss a date silently.

A real interview question

Tell me about a time you had more work assigned than you could realistically finish. What did you do?

What most people say

drag me

I just worked late and pushed through until everything was done. I do not like letting the team down, so I made it work.

It rewards heroics over planning, hides the trade off from the manager, and gives no evidence you can rank work or communicate risk. It also quietly signals you will burn out and then surprise everyone.

The follow-ups they ask next

  • What if your manager had said no, everything still has to ship?

    Do not fold and do not fight. Ask which of the items they want first if only half lands, and confirm that ranking in writing so the trade off is shared, not hidden.

  • How did you estimate how long each ticket would take?

    Be honest that early estimates are rough. Say what you anchored on, a similar past task, and that you tracked the gap so your next estimates got better.

  • Has your flag ever turned out to be a false alarm?

    Yes, and that is fine. Say that an early flag you can withdraw costs the team nothing, a late surprise costs them a release.

What the interviewer is listening for

  • Raised the risk early and with a concrete list rather than a vague sorry
  • Ranked work by who is blocked downstream, not by what was most fun
  • Came with a proposed plan and let the manager correct it

What sinks the answer

  • Silent overtime as the only strategy, with the surprise landing on the deadline
  • No sense of which task actually mattered to anyone else
  • Blames the manager for over assigning without ever having said anything

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 have not managed a huge backlog yet, but here is how I would reason about it. I would list everything, mark who is blocked if each item is late, and take that list to my lead the same day with a proposed cut rather than waiting.

Keep going with behavioural

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