Tell me about a time you set a goal for yourself and how you approached achieving it
Asked at:
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess how you create direction for yourself when nobody is handing you a fully defined checklist. They want to understand whether your goals are thoughtful and meaningful, how you translated them into action, and whether you followed through when progress got messy or slow. At higher levels, they also look for whether the goal matched your expected scope and whether your approach improved outcomes beyond just your own work.
“Describe a time you identified something you wanted to accomplish and drove yourself toward it.”
“What's an example of a meaningful goal you set for yourself at work? How did you go about reaching it?”
“Tell me about a self-directed goal you pursued and what you did when progress was not straightforward.”
“Can you walk me through a time you pushed yourself toward a target that was not simply handed to you?”
“Have you ever set a professional goal for yourself because you saw a gap or opportunity? What happened?”
Key Insights
- You do not need a heroic or life-changing goal, but it should be substantive enough to reveal judgment, planning, and follow-through. A trivial personal optimization often makes it hard to show real ownership.
- You should explain why you chose the goal, not just what the goal was. Strong candidates show they noticed a real gap or opportunity and set a goal with intent rather than picking something arbitrary.
- Do not stop at effort. Interviewers are listening for how you tracked progress, adapted when the first plan was insufficient, and what changed afterward.
What interviewers probe atlevel
Top Priority
Show that you broke the goal into manageable steps and adjusted based on what you learned, rather than just hoping repetition would make it happen.
Good examples
🟢I made a simple plan: shadow one debug session, handle one low-risk issue on my own each week, and ask for feedback on how I approached root cause analysis.
🟢When my first approach was too broad, I narrowed the goal to one service area, kept notes on recurring failure patterns, and practiced there until I was consistently faster.
Bad examples
🔴I wanted to get better at debugging, so I kept taking more bug tickets and assumed I would improve over time.
🔴I set the goal at the start of the internship and mostly checked at the end whether I felt more confident.
Strong answers show deliberate sequencing, checkpoints, and adaptation; weak ones mistake repetition or good intentions for a plan.
Choose a goal that is meaningful for your scope: interviewers want to see initiative beyond assigned tasks, not a vague aspiration or something too big to be credible.
Good examples
🟢After struggling to debug issues on my team, I set a goal to become independently effective with our logging and local debugging tools within two months.
🟢I noticed I relied heavily on my mentor for test coverage decisions, so I set a goal to be able to write and justify solid tests for my own features by the end of the project.
Bad examples
🔴I set a goal to become an expert in distributed systems that quarter, so I mostly watched videos and waited for a chance to use it.
🔴I decided my goal was to rewrite part of our deployment flow even though I was still onboarding and did not understand the existing process well.
Strong goals are grounded in an actual gap the candidate can realistically influence at their level; weak goals are either disconnected from real work or too oversized to show sound judgment.
Valuable
A strong answer shows self-awareness: not just that you completed the goal, but what you learned about how you work and grow.
Good examples
🟢I learned that I improve faster when I make the unknowns explicit and ask focused questions instead of waiting until I am completely blocked.
🟢I also learned to define progress in smaller steps because that kept me moving even when I was still far from being fully independent.
Bad examples
🔴I learned that if you work hard enough, you can usually hit your goals.
🔴The main lesson was that I should keep setting ambitious goals for myself.
Strong learning is specific and transferable; weak learning is generic motivation talk.
You do not need perfect metrics, but you should be able to show how you knew you were improving and what was different afterward.
Good examples
🟢By the end, I could debug routine issues in that service without asking for step-by-step help, and my mentor stopped needing to review basic test decisions with me.
🟢I tracked how many issues I could investigate independently and saw that over a month I went from needing heavy guidance to only occasional check-ins.
Bad examples
🔴I could tell I met the goal because I felt a lot more comfortable by the end.
🔴The project shipped, so I assumed the goal was achieved too.
Strong junior answers provide observable evidence of progress; weak ones rely on feelings or unrelated outcomes.
Example answers atlevel
Great answers
One goal I set for myself during my first few months was to become able to debug routine issues in our service without needing someone to sit next to me the whole time. I chose that because I noticed I was finishing assigned tasks, but I was still slow anytime something behaved unexpectedly. I made a simple plan: I asked a teammate to walk me through one real investigation, kept notes on the steps they used, and then took one small bug each week where I had to write down my own hypothesis before asking for help. At first I was still jumping to conclusions too quickly, so I started checking logs and recent changes in the same order every time. After about six weeks, I was able to handle a couple of production-like issues in our test environment mostly on my own, and my mentor's feedback shifted from guiding my process to just sanity-checking my conclusions. The biggest thing I learned was that independence did not come from just seeing more bugs; it came from having a repeatable way to investigate them.
At the start of last year I set a goal to get faster and more consistent at reviewing and merging pull requests because slow reviews were blocking small features and I wanted to help the team ship more reliably. I tracked how long my reviews and responses took for two weeks, then committed to three concrete changes: keep my own PRs smaller, add a short checklist to each PR describing what needs testing, and reserve two 30‑minute windows daily dedicated to review work. I asked a senior teammate to critique one of my reviews so I could learn to spot edge cases I missed. After six weeks my average review turnaround dropped by about 40% and the number of follow-up fixes decreased, which the product manager noticed as smoother releases. I learned that steady, measurable habits beat bursts of effort and that small process changes can have an outsized impact on team velocity.
Poor answers
A goal I set for myself was to get a lot better technically during my internship. I tried to do that by taking on as many tasks as I could and spending extra time reading about our systems after work. I think it went well because by the end I felt much more confident and people trusted me with more tickets. It showed me that if you work hard and stay motivated, you can improve pretty quickly.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Mid September, 2024
Junior
Tell me about a time you set a goal for yourself and how you approached achieving it
Hello Interview Premium
Your account is free and you can post anonymously if you choose.