Tell me about one project you are proud of and how you would do it differently if you could redo it
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to learn both what kind of work you gravitate toward and how you think about your own execution after the fact. The "proud of" part reveals your standards, scope, and ownership; the "what would you do differently" part tests reflection, learning, and whether you can critique something successful without becoming defensive or fake-humble. Strong answers make it clear why the project mattered, what you specifically drove, and what you learned that changed how you operate.
Key Insights
- You do not need to pick a flawless project. In fact, a project with some scar tissue is often better because it lets you show pride and honest reflection at the same time.
- The redo portion is not asking for self-criticism theater. The best answers name a real tradeoff or blind spot, explain why it happened, and show how that lesson would change your approach now.
- Your choice of project is itself signal. Pick something with scope appropriate to your level and be precise about your personal contribution rather than hiding inside "we."
What interviewers probe atlevel
Top Priority
You do not need to exaggerate; you just need to be clear about what you owned, what help you got, and what decisions you personally made.
Good examples
🟢My part was owning the API endpoint and the first version of the UI, and I also set up the validation checks after noticing bad input was causing errors.
🟢I had help from my mentor on the initial design, but I was the one who investigated the bug pattern, proposed the fix, implemented it, and monitored the results after release.
Bad examples
🔴We built a reporting tool and we made a lot of good choices. We worked closely together, so it’s hard to separate what I did from what the team did.
🔴My team improved performance across the app. I was involved in debugging and testing, and overall the project went really well.
Weak answers hide behind collective language; strong answers accurately separate team effort from individual ownership without overstating.
Valuable
Example answers atlevel
Great answers
One project I’m proud of was building an internal tool that let our support team look up order status without asking engineers for help. I was the primary engineer on it, with my mentor helping me review the design, and I owned the API, the basic interface, and the launch fixes after we released it. I’m proud of it because it solved a real day-to-day problem and people started using it almost immediately. If I could redo it, I would talk to two or three support agents earlier before finishing the whole interface, because we ended up changing the layout after they showed us how they actually searched for issues. That taught me to validate assumptions sooner, and on later tasks I started doing short check-ins with the people who would use what I was building.
One project I’m proud of was improving the accessibility of the online donation form for a small non‑profit where I did frontend work. I was the sole developer on the changes and worked with the program manager and a couple of volunteer testers to understand common pain points. I implemented semantic HTML, ARIA attributes, better keyboard focus handling, clearer error announcements for screen readers, and improved color contrast. After we rolled it out we saw a noticeable increase in completed donations from users who use assistive technology and we got direct thanks from a few donors. If I could do it again I’d bring in two or three people who use screen readers for usability testing much earlier and add simple automated accessibility checks to our CI so regressions would be caught sooner. That taught me how valuable early user feedback and lightweight automation are, even on small features.
Poor answers
A project I’m proud of was our company’s migration to a new service architecture. It was a very important initiative and I helped with several parts of it, mostly by picking up tickets and making the requested changes. It went well because I stayed busy and got my work done quickly. If I could redo it, I’d probably just start a little earlier and be even more detail-oriented, but overall I was happy with how it turned out.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late December, 2025
Early December, 2025
Early November, 2025
Tell me about one project you are proud of. If you were to redo this project, how would you do it differently?
Hello Interview Premium
Your account is free and you can post anonymously if you choose.