Your Dashboard
Interview Coaching
Learn
System Design
ML System Design
Code
Behavioral
Salary Negotiation
Interview Guides
What project are you most proud of?
Asked at:
Meta
Uber
Amazon
Datadog
What is this question about
Interviewers want to see what you value, how you choose problems, and whether your pride aligns with meaningful outcomes rather than shiny tech. They’re probing for ownership, decision quality under ambiguity, and the learning loop you ran. At seniority, they also expect signs that you elevated others and created durable, repeatable impact. Your story is a proxy for how you’ll pick and drive work here.
Key Insights
- Anchor your pride to outcomes, not outputs. Say what changed for users, the business, or the system, and how you know.
- Make your role unmistakably clear. Use crisp role language (I owned…, I decided…, I delegated…) and quantify scope proportional to your level.
- Close the loop. Name trade-offs, risks, and what you institutionalized afterward so the win wasn’t a one-off.
What interviewers probe atlevel
Top Priority
Show you explored options, asked for feedback, and validated with small tests.
Good examples
🟢I compared two libraries for auth, prototyped both, and picked the simpler one for faster rollout after a quick security review.
🟢Unsure about the query cost, I added an index on staging and measured a 70% improvement before proposing the change.
Bad examples
🔴I chose the library everyone uses—it’s popular so it must be good.
🔴We followed the existing pattern without checking if the constraints changed.
Strong answers show deliberate evaluation and validation, not defaulting to popularity or precedent.
Be precise about what you owned and where you needed guidance.
Good examples
🟢I owned server-side validation and the DB migration, pairing with my mentor on the migration plan and doing the rollout myself.
🟢I added retry logic for our webhook consumer, wrote tests, and handled the on-call for the first week post-launch.
Bad examples
🔴We built a payments integration—I helped with stuff around the edges.
🔴I owned the whole backend, but my tech lead handled the tricky parts and design.
Strong answers specify concrete responsibilities and boundaries rather than vague team-wide claims.
Valuable
Show curiosity, feedback-seeking, and one concrete improvement you institutionalized.
Good examples
🟢An incident exposed a missing null check; I added tests, updated our template repo, and verified no similar issues.
🟢Beta users were confused by copy; I partnered with design to A/B test new text that reduced drop-off by 9%.
Bad examples
🔴Everything went smoothly; I wouldn’t change anything.
🔴My mentor fixed a bug post-launch; I didn’t really follow up.
Strong answers demonstrate active learning and a change that outlives the project.
Show you collaborated, asked for help well, and shared what you learned.
Good examples
🟢I paired with a senior to learn the logging stack, then wrote a short doc that helped two peers debug similar issues.
🟢When specs changed, I set up a 20-min sync to clarify priorities and avoided building a soon-to-be-cut feature.
Bad examples
🔴I stayed late and finished it all myself to avoid blocking others.
🔴Design changed specs mid-way; I was frustrated but just built what I had.
Strong answers show proactive communication and knowledge sharing that helps the team.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Mid November, 2025
Meta
Staff
Early November, 2025
Senior
Early November, 2025
Meta
Mid-level
Comments
Hello Interview Premium
Your account is free and you can post anonymously if you choose.