Tell me about a time you received critical feedback from your manager. How did you respond to it, and what did you learn?

In my first year on a backend team, my manager told me that I was waiting too long before asking for help when I got stuck. I thought I was showing independence, but they pointed out that I was sometimes burning half a day on the wrong path and then creating a last-minute rush for review. I asked them for a couple of specific examples so I could understand the pattern, and I realized I hesitated whenever I felt I should already know the answer. After that, I set a rule for myself that if I was blocked for more than an hour, I would either ask a focused question or share two options I was considering. On my next project, I also sent brief updates when something might affect another person. A few weeks later my manager told me my updates were much more useful and that I was unblocking myself faster without disappearing for long stretches. The big thing I learned was that asking early is not a sign of weakness if you do the preparation first.

Early on as a junior frontend engineer on a small, fully remote product team, my manager pulled me aside and said my pull requests were too large and mixed visual changes with unrelated refactors, which made reviewers miss visual regressions and slowed down delivery. I asked for concrete PRs they found hard to review and realized I was trying to bundle everything into one ‘complete’ change rather than shipping in reviewable pieces. After that I started breaking work into small, single-purpose PRs, attaching before-and-after screenshots and a short checklist of what to look at, and I offered a quick screen-share walkthrough for anything with subtle UI behavior. Reviews became faster, fewer issues reached QA, and I got direct praise for making reviewers’ lives easier. The lesson I took away was to respect other people’s time by making changes easy to review — that discipline actually helped me iterate faster and build better user-facing features.