Tell me about a project you worked on and what your role was
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this open-ended prompt to see how you choose to frame your work, how well you understand the project beyond your task list, and whether your role matches the level you're interviewing for. They are listening for scope, ownership, judgment, and clarity: what problem mattered, what you personally drove, how you handled uncertainty, and what changed because of your work. Because you get to pick the story, your answer also signals what you think is impressive.
Key Insights
- You are not being asked for a job description. Pick one concrete project and tell a story: what problem existed, why it mattered, what your role actually was, and what happened as a result.
- Be very crisp about the boundary between team effort and your own contribution. Strong candidates give generous credit to others while still making their personal decisions and ownership unmistakable.
- Choose a project whose scope fits your level. A junior candidate does not need to sound like a tech lead, and a staff candidate hurts themselves if they only describe being assigned a narrow implementation task.
What interviewers probe atlevel
Top Priority
At junior level, a strong answer is a well-understood small project where you can clearly explain the problem, your tasks, and what changed because of your work.
Good examples
🟢I worked on improving our account recovery flow. It was a small part of a larger customer support initiative, and my role was to implement the backend validation and add tests so users got clearer errors instead of generic failures.
🟢One project I owned as a new grad was adding internal analytics for a report generation feature. It wasn't a huge system, but it touched production code and helped the team understand where users were dropping off.
Bad examples
🔴I worked on rebuilding our whole payments system. I mostly took tickets from the board and implemented whatever was assigned, so I can't really speak to the larger decisions, but it was a major company project.
🔴The main project I want to talk about is a hackathon app I built alone over a weekend. It was fun and I used a lot of technologies, so I think it shows what I can do better than my actual team work.
Weak answers either hide behind a giant project the candidate barely understood or pick something too detached from real collaborative engineering; strong answers pick a manageable slice they genuinely understood and can discuss end to end.
Valuable
Example answers atlevel
Great answers
One project I worked on was improving our password reset flow, because users were sometimes getting all the way to the end and then seeing a generic failure. I joined after the general approach had already been discussed, and my role was to update the backend validation, add test coverage for the edge cases we were missing, and help verify the behavior in staging. Early on I found that one error path behaved differently for older accounts, so I checked a few real examples with my mentor before finishing the implementation. We released it behind a flag, turned it on gradually, and support tickets for that flow dropped afterward. It was a good project for me because it was small enough that I could own a real piece of it, but it still affected production users.
One project I worked on was helping the operations team track incoming shipments in a small internal dashboard. I was on a rotation with one senior engineer, and my role was to build the part that showed shipment status and highlighted anything that was delayed so the team could spot problems quickly. Most of my work was in the front end, but I also fixed a couple of simple API issues when the data coming back from the service did not match what the page expected. I spent a lot of time checking the workflow with the operations staff, because I wanted to make sure the labels and filters matched how they actually talked about the shipments. We launched it to one warehouse first, and after that they told us it saved them time every morning. I liked this project because it was practical and customer-facing, and I could see the result of my work very clearly.
Poor answers
A project I worked on was our platform migration, which was one of the biggest things happening on the team. I helped with backend work and fixed several tickets related to the migration, so I was pretty involved in it. There were a lot of moving pieces and different services, so it would be hard to explain all of it, but the project was important and I learned a lot from being part of it. Overall it went well because we finished the migration work for our team.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late July, 2026
Mid July, 2026
Early July, 2026
Hello Interview Premium
Your account is free and you can post anonymously if you choose.