Tell me about a specific project or experience from your resume
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
This is an open-ended calibration question disguised as a simple resume walkthrough. Interviewers are using your choice of project, the way you frame it, and the depth of your explanation to infer your actual scope, ownership, judgment, and communication skill. They're also checking whether your resume bullets correspond to work you truly understand rather than work you merely participated in.
Key Insights
- You are being evaluated as much on project selection as on storytelling. Pick an example that is representative of your target level, not just the flashiest technology or the most recent thing on your resume.
- Don't give a resume recap. Quickly establish the problem, why it mattered, what specifically you owned, what tradeoffs you navigated, and what changed because of your work.
- Be precise about your contribution when the project involved other people. Strong candidates naturally separate team achievement from their personal role without minimizing either.
What interviewers probe atlevel
Top Priority
Choose a project where you had real hands-on ownership of a small but meaningful piece, and explain it clearly.
Good examples
🟢I picked a bug-heavy onboarding flow I was assigned to improve. It was a small project, but I owned the investigation, the code change, and the follow-up checks after release.
🟢I chose a feature from my internship where I implemented one reporting page end to end with guidance from my mentor. It was narrow enough that I can explain the decisions I personally made.
Bad examples
🔴I worked on migrating our whole platform to a new architecture. I mostly listened in meetings and picked up tickets, but it was a huge company effort and looked great on my resume.
🔴The best example is a class project where we built a social app over a weekend. It was fun and used a lot of tools, so I usually talk about that even though nobody really used it.
Weak answers either borrow scope from the team or pick something flashy but shallow; strong answers pick manageable work the candidate genuinely understands and owned.
Valuable
Example answers atlevel
Great answers
One project on my resume that I like to talk about was improving our user signup form during my internship. We were seeing failed submissions for a small but noticeable group of users, and I was asked to investigate with support from my mentor. I traced the issue to how we were validating phone numbers, found that the logic handled only one format correctly, and implemented a fix with tests for the edge cases I found. I also added a simple check in staging using sample data so we could verify the behavior before release. After we shipped it, the support requests tied to that issue dropped, and the project taught me to spend more time validating assumptions about input data before I start coding.
One project I often mention was building an internal tracker for equipment checkout at the nonprofit where I interned. Before that, the team was using a shared spreadsheet, and it was easy for items to get marked incorrectly or forgotten when volunteers were busy. I worked with one staff member to understand the daily process, then built a simple web form and a dashboard that showed what was available, what was checked out, and what was overdue. My main job was handling the front-end and basic data entry flow, while my supervisor reviewed the requirements and helped me test it with a few real cases. After we launched it, the staff said it saved them time and made it easier to keep track of supplies, and I liked that the project had a very direct impact on people doing hands-on work. It also taught me that asking non-technical users about their routine is often the best way to find the real problem to solve.
Poor answers
A project from my resume is a major platform migration my team worked on last summer. It was a really big effort and I was involved throughout, mostly by taking tickets and helping where needed. The main thing was that we all worked hard and got it done on schedule. I think it's a good example because it was high impact and used a modern stack.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Mid June, 2026
Mid November, 2025
Hello Interview Premium
Your account is free and you can post anonymously if you choose.