Feedback I Didn’t Expect — But Probably Needed

📰 Dev.to · Tapesh Nagarwal

Learn to handle unexpected feedback and use it as an opportunity for growth in your career

intermediate Published 8 May 2026
Action Steps
  1. Reflect on your past experiences and identify areas where you received unexpected feedback
  2. Analyze the feedback and try to understand the perspective of the person providing it
  3. Use the feedback as an opportunity to learn and grow, rather than becoming defensive
  4. Prepare for interviews by practicing your communication skills and being open to feedback
  5. Seek out constructive criticism from colleagues and mentors to help you improve
Who Needs to Know This

Software engineers and developers can benefit from this lesson on handling feedback and using it to improve their skills and confidence

Key Insight

💡 Unexpected feedback can be a valuable learning experience, but it requires an open mind and a willingness to grow

Share This
💡 Don't be afraid of unexpected feedback - use it as a chance to learn and grow!

Key Takeaways

Learn to handle unexpected feedback and use it as an opportunity for growth in your career

Full Article

Title: Feedback I Didn’t Expect — But Probably Needed

URL Source: https://dev.to/tapcodes/feedback-i-didnt-expect-but-probably-needed-50i1

Published Time: 2026-05-08T13:39:11Z

Markdown Content:
# Feedback I Didn’t Expect — But Probably Needed - DEV Community
[Skip to content](https://dev.to/tapcodes/feedback-i-didnt-expect-but-probably-needed-50i1#main-content)

[![Image 1: DEV Community](https://media2.dev.to/dynamic/image/quality=100/https://dev-to-uploads.s3.amazonaws.com/uploads/logos/resized_logo_UQww2soKuUsjaOGNB38o.png)](https://dev.to/)

[Powered by Algolia](https://www.algolia.com/developers/?utm_source=devto&utm_medium=referral)

[Log in](https://dev.to/enter?signup_subforem=1)[Create account](https://dev.to/enter?signup_subforem=1&state=new-user)

## DEV Community

![Image 2](https://assets.dev.to/assets/heart-plus-active-9ea3b22f2bc311281db911d416166c5f430636e76b15cd5df6b3b841d830eefa.svg)0 Add reaction

![Image 3](https://assets.dev.to/assets/sparkle-heart-5f9bee3767e18deb1bb725290cb151c25234768a0e9a2bd39370c382d02920cf.svg)0 Like ![Image 4](https://assets.dev.to/assets/multi-unicorn-b44d6f8c23cdd00964192bedc38af3e82463978aa611b4365bd33a0f1f4f3e97.svg)0 Unicorn ![Image 5](https://assets.dev.to/assets/exploding-head-daceb38d627e6ae9b730f36a1e390fca556a4289d5a41abb2c35068ad3e2c4b5.svg)0 Exploding Head ![Image 6](https://assets.dev.to/assets/raised-hands-74b2099fd66a39f2d7eed9305ee0f4553df0eb7b4f11b01b6b1b499973048fe5.svg)0 Raised Hands ![Image 7](https://assets.dev.to/assets/fire-f60e7a582391810302117f987b22a8ef04a2fe0df7e3258a5f49332df1cec71e.svg)0 Fire

0 Jump to Comments 0 Save Boost

Copy link

Copied to Clipboard

[Share to X](https://twitter.com/intent/tweet?text=%22Feedback%20I%20Didn%E2%80%99t%20Expect%20%E2%80%94%20But%20Probably%20Needed%22%20by%20Tapesh%20Nagarwal%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Ftapcodes%2Ffeedback-i-didnt-expect-but-probably-needed-50i1)[Share to LinkedIn](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Ftapcodes%2Ffeedback-i-didnt-expect-but-probably-needed-50i1&title=Feedback%20I%20Didn%E2%80%99t%20Expect%20%E2%80%94%20But%20Probably%20Needed&summary=Recently%2C%20I%20went%20through%20an%20interview%20process%20that%20challenged%20me%20more%20mentally%20than%20I%20expected.%20%20Not...&source=DEV%20Community)[Share to Facebook](https://www.facebook.com/sharer.php?u=https%3A%2F%2Fdev.to%2Ftapcodes%2Ffeedback-i-didnt-expect-but-probably-needed-50i1)[Share to Mastodon](https://s2f.kytta.dev/?text=https%3A%2F%2Fdev.to%2Ftapcodes%2Ffeedback-i-didnt-expect-but-probably-needed-50i1)

[Share Post via...](https://dev.to/tapcodes/feedback-i-didnt-expect-but-probably-needed-50i1#)[Report Abuse](https://dev.to/report-abuse)

[![Image 8: Tapesh Nagarwal](https://media2.dev.to/dynamic/image/width=50,height=50,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3903425%2F1e880ea3-59d5-4802-9637-e26caac85c81.png)](https://dev.to/tapcodes)

[Tapesh Nagarwal](https://dev.to/tapcodes)
Posted on May 8

# Feedback I Didn’t Expect — But Probably Needed

[#career](https://dev.to/t/career)[#devjournal](https://dev.to/t/devjournal)[#interview](https://dev.to/t/interview)[#softwareengineering](https://dev.to/t/softwareengineering)

Recently, I went through an interview process that challenged me more mentally than I expected.

Not because I failed technical questions or completely bombed conversations.

Actually, walking out of several rounds, I felt confident.

The discussions were engaging, the technical reasoning felt solid, and the architectural conversations felt especially strong. I genuinely believed I had communicated the depth of experience I’ve built working on enterprise ETL systems, distributed event pipelines, and quality engineering initiatives.

So hearing feedback that I came across “slightly junior” in an early round caught me off guard.

Then came another round where I solved the debuggi
Read full article → ← Back to Reads