What are the proudest things you have achieved in the past couple of years, either professionally or personally
Asked at:
Spotify
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to see what you value, how you define meaningful achievement, and whether the scale of your examples matches your level. They are also looking for evidence of ownership: not just that something good happened around you, but that you drove something difficult to a real outcome. Because the prompt is open-ended, your story selection itself is part of the evaluation.
“What's an accomplishment from the last few years that you're especially proud of, and why?”
“Tell me about a recent achievement that best represents the kind of impact you like to have.”
“If you had to pick one thing you've done in the last couple of years that you're most proud of, what would it be?”
“What project or personal milestone from the last few years stands out most to you?”
“Looking back over the past couple of years, what feels like your most meaningful accomplishment?”
Key Insights
- You are being judged not just on the achievement, but on your taste in choosing it. Pick something that is genuinely consequential for your level, not merely memorable or personally enjoyable.
- Do not stop at the win. Strong answers explain why the problem mattered, what made it hard, what you specifically did, and how you know it had impact.
- If you include a personal example, make sure it still reveals transferable traits like discipline, resilience, leadership, or learning; otherwise it can feel safer but less job-relevant than a professional example.
What interviewers probe atlevel
Top Priority
You do not need to claim solo ownership, but you do need to clearly separate your work from what your mentor or team handled.
Good examples
🟢The project was team-owned, but my part was investigating the failure pattern, proposing the fix, and implementing the first version with review from a more senior engineer.
🟢I didn't define the whole roadmap, but I took responsibility for one user flow end to end, including the implementation, testing plan, and follow-up after release.
Bad examples
🔴We improved the deployment process and it went really well; I was part of the team so I'm proud of that whole effort.
🔴My team launched a new feature and it was very successful, and I contributed across different parts as needed.
Weak answers hide behind team language; strong answers are honest about support while making the candidate's own decisions and effort easy to see.
At junior level, interviewers want to hear that you made a real contribution to something that mattered, even if the scope was bounded and you were guided.
Good examples
🟢I'm proud of owning a small but important reliability fix in our checkout flow; with help from my mentor I traced intermittent failures, implemented a safer retry path, and support tickets dropped afterward.
🟢One achievement I'm proud of was taking a rough internal tool and turning it into something my team could actually use every day, which cut repetitive setup work for new tasks.
Bad examples
🔴I'm most proud of fixing a typo in our onboarding flow because people had mentioned it for a while and I finally got it done.
🔴I built a small script for myself to rename files faster, and that was a big achievement for me because it saved me a few minutes each week.
Weak answers confuse convenience or neatness with impact; strong answers show bounded but real business or team value appropriate for an early-career engineer.
Valuable
Even a small project becomes compelling if you can explain the real challenge and the steps you took to work through it.
Good examples
🟢The hard part was that the bug was intermittent, so I added logging, reproduced it in a smaller setup, and used that to narrow the cause.
🟢What made it difficult was balancing speed with not breaking an older workflow, so I shipped a limited version first and expanded it after feedback.
Bad examples
🔴It was challenging because I hadn't done it before, but I kept working and eventually got it done.
🔴The main difficulty was that it took a lot of effort and there were a lot of details to handle.
Weak answers label something as hard without showing problem-solving; strong answers reveal how the candidate thought through the difficulty.
Pick something that reflects good instincts: solving a real problem, helping users or teammates, or growing in a meaningful way.
Good examples
🟢I'm proud of taking a vague assignment and turning it into something useful for the team because it taught me how to ask better questions and own the result.
🟢What I'm proud of most is a project where the work reduced a recurring frustration for users, because it felt tied to a real need rather than just completing tickets.
Bad examples
🔴I'm proudest of finishing a task much faster than expected because I like moving quickly when the work is straightforward.
🔴One of my proudest moments was getting praise for a polished demo, which showed I can present things well.
Weak answers emphasize vanity wins or convenience; strong answers reveal mature instincts about impact, learning, and usefulness.
Example answers atlevel
Great answers
One thing I'm really proud of from the last year was improving a flaky part of our checkout test flow during my first full-time role. It wasn't a huge project, but it was causing repeated failed deployments and people had started to work around it instead of fixing it. I took ownership of investigating it, added some targeted logging, and with guidance from a senior engineer I narrowed it down to a timing issue in one service call. I implemented the fix, added coverage so we could catch it earlier, and stayed with it after release to make sure the failure rate actually dropped. Over the next few weeks that alert basically disappeared, and the team stopped having to rerun those deployments. I was proud of it because it was the first time I took a fuzzy, annoying problem and drove it all the way to a real outcome.
I'm proud that I took the lead on creating an interactive onboarding guide for new engineers at my small company. New hires were spending most of their first week wrestling with environment setup and hunting for the right docs, so I put together a repo with one-click setup scripts, sample data, and a clear step-by-step checklist, and worked with HR and two senior engineers to capture tribal knowledge. I ran a short pilot with the next two hires and iterated based on their feedback. After that, setup time dropped from about five days of back-and-forth to a single day, and I saw far fewer "how do I..." messages in Slack. I felt proud because it was a small project that combined coding, communication, and empathy, and it made new teammates' lives noticeably easier.
Poor answers
I'm probably most proud of a script I wrote to clean up some file names for my own workflow. It wasn't assigned to me, so I liked that I found something on my own and solved it. It made my work faster and the code was much cleaner than what I had before. A few teammates said it was neat, so that felt like a strong achievement. I think it shows I pay attention to efficiency.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Mid January, 2025
Spotify
Mid-level
Hello Interview Premium
Your account is free and you can post anonymously if you choose.