Tell me about a project of your choice and its challenges
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
This is an open-ended project showcase question, so interviewers are evaluating both the substance of the project and your judgment in choosing it. They want to see what level of complexity you naturally operate at, how you personally contributed, how you handled obstacles, and whether you can explain the work in a clear, structured way. For more senior candidates, the project itself is often less important than what it reveals about scope, leadership, and decision-making under uncertainty.
Key Insights
- You are being judged partly on project selection. If you choose something low-stakes, overly routine, or hard to attribute to your own work, you make the interviewer work harder to see your level.
- Don't just narrate what the team built. Make your personal role, key decisions, and the hardest tradeoffs unmistakably clear, especially if the project involved many people.
- Challenges are where the signal lives. A polished success story without real obstacles, changed assumptions, or hard decisions often sounds shallow rather than impressive.
What interviewers probe atlevel
Top Priority
Name a real obstacle and walk through how you investigated it instead of just saying it was hard.
Good examples
🟢The hardest part was inconsistent data from an older system, so I reproduced the issue locally, traced where assumptions broke, and added validation before rollout.
🟢I underestimated how one dependency behaved in production, so I compared logs from test and production and changed the implementation after confirming the mismatch.
Bad examples
🔴The biggest challenge was that the codebase was complicated, so I spent extra time figuring it out and eventually finished.
🔴We hit some bugs during testing, but we fixed them one by one and got the feature out.
Strong answers reveal a thinking process under difficulty; weak ones label something as challenging without showing diagnosis or adaptation.
Valuable
Example answers atlevel
Great answers
One project I like to talk about was adding a bulk upload feature for a small internal tool my team used. I owned the backend validation and the upload status page, with my mentor helping on the initial design. The hardest part was that the input files looked consistent in test data, but in real usage there were a lot of missing or malformed fields, so my first version failed too often. I reproduced a few real examples, added stricter validation and clearer error messages, and changed the processing flow so one bad row didn't fail the whole upload. We shipped it to a pilot group first, and support requests dropped because users could fix issues themselves. The biggest thing I learned was to validate assumptions with real data earlier, and I've used that on later tasks.
A project I enjoyed was simplifying our mobile web checkout flow and adding a lightweight progress indicator; I owned the front-end implementation and the integration tests while a designer handled the visuals and a backend engineer supported payment edge cases. The main challenge was that the third-party payment widget behaved inconsistently on slow connections, which made the page appear stuck and caused users to abandon their carts. I addressed it by reducing the number of visible steps, adding clear loading states and timeouts, wrapping the payment widget with a safe retry/fallback, and rolling the change out behind a feature flag so we could watch metrics. In the first month we saw a noticeable drop in cart abandonment, and I learned how small UX and reliability fixes directly affect business outcomes as well as the value of close coordination with design and backend teammates.
Poor answers
A project I worked on was part of our migration to a new platform, which was a really big effort for the company. I helped by taking the tickets assigned to me and implementing the front-end changes. The main challenge was just learning the codebase because there was a lot going on, but I picked it up and finished everything on time. The project launched successfully, so overall it showed I can contribute well on important work.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late March, 2026
Early February, 2026
Late January, 2026
Project Deep Dive
Hello Interview Premium
Your account is free and you can post anonymously if you choose.