Tell me about a recent technical project you worked on
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to let you choose the evidence they will judge you on. They are not just evaluating whether the project was technically interesting; they are assessing whether you can explain a meaningful problem, your actual contribution, the decisions you made, and the impact at the scope expected for your level. Strong answers reveal judgment, ownership, and level-appropriate complexity without needing a lot of prompting.
Key Insights
- You are being evaluated on project selection as much as project execution. Pick something recent, consequential, and appropriately scoped for your level rather than the most obscure or flashy technical topic.
- Don't turn this into a feature tour. The strongest answers make the problem, tradeoffs, and your personal role unmistakably clear, so the interviewer can tell how you think, not just what your team built.
- You should calibrate emphasis to your level: junior and mid-level candidates win by showing solid execution and clear ownership of a bounded piece, while senior+ candidates are expected to show prioritization, ambiguity handling, and influence across people or systems.
What interviewers probe atlevel
Top Priority
Be precise about what you personally investigated, built, tested, or decided instead of hiding behind 'we.'
Good examples
đ˘I investigated the failure cases, proposed one fix to my mentor, implemented the retry logic, and added the tests for the edge cases we found.
đ˘The overall project was team-owned, but my piece was the permissions check. I wrote that component, found one missing requirement during testing, and updated the implementation before release.
Bad examples
đ´We redesigned the workflow and then we updated the backend. We also fixed a few bugs during testing.
đ´My team decided on the approach, and then we all worked together to get it shipped.
Weak answers blur the candidate into team activity; strong answers let the interviewer trace exactly what the candidate owned and how they contributed.
Valuable
Example answers atlevel
Great answers
A recent project I worked on was fixing duplicate notification emails in one of our internal workflow tools. Support had a small but steady stream of complaints, and I was asked to investigate with guidance from a senior engineer. I reproduced the issue, found that retries could trigger the send path twice, and implemented an idempotency check along with tests for the retry cases. I considered putting the fix in the client, but we had two clients using the same service, so we kept the logic on the backend to avoid duplicating behavior. After we shipped it, the related support tickets stopped showing up over the next few weeks, and it taught me to look at state transitions early when debugging issues like this.
A recent project I worked on was helping add a lightweight dashboard for tracking inventory counts in our store operations system. I was on a small team, and my part was mostly building the front-end screens and wiring them to an existing API so managers could see low-stock items without calling the warehouse. I worked with a designer to simplify the layout, because the first version had too much information on one page, and we wanted something a busy store manager could use quickly. I also wrote a few basic tests for the form inputs so we wouldnât accept negative quantities or blank item names. The feature went live for a pilot group first, and the feedback was that it saved them time during daily check-ins, which felt good because it was a practical improvement for people using the tool every day. It also showed me how much value there is in asking simple questions early, like who will actually use this and what do they need to finish fast.
Poor answers
The most recent technical project I worked on was a large platform migration my team was doing. It was a great learning experience because I got to touch a lot of different parts of the system and see how senior engineers think. I helped with several tasks, mostly fixing issues as they came up and updating code where needed. It all went well and we were able to complete the migration successfully. I liked it because it exposed me to a lot of technology.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late July, 2026
Hello Interview Premium
Your account is free and you can post anonymously if you choose.