To answer “tell me about a time you set a goal and achieved it”, describe one goal you chose yourself, state it as a measurable target with a deadline, walk through the milestones you set and the setback you hit along the way, and finish with the result compared to the target. The interviewer is checking whether you are self-motivated and whether you plan, not whether the goal was impressive. A modest goal with a clear number and a real obstacle beats a grand goal described vaguely.
What is the interviewer really testing with this question?
This question is about drive and planning. Interviewers commonly listen for:
- Ownership of the goal. You set it, or you raised the bar on one you were given. A quota your manager assigned is weaker unless you explain how you shaped it.
- Measurability. There is a number and a date, so “achieved” means something.
- Planning. You broke the goal into milestones and tracked them.
- Persistence. Something went wrong and you adjusted instead of giving up.
- Relevance. The skills behind the goal matter for the job you want.
This is a past-tense question. If the interviewer asks where you are headed next, that is a different prompt; see how to answer “what are your career goals?”. Here they want proof you have already done it once.
How to make your goal sound measurable
Many candidates describe goals like “get better at public speaking.” That is a direction, not a goal. Rewrite your story’s goal using the widely used SMART checklist: specific, measurable, achievable, relevant and time-bound. If your team uses OKRs (objectives and key results), you can describe the goal that way instead.
| Vague goal | Measurable version you can say in an interview |
|---|---|
| “Improve customer satisfaction” | “Raise our team’s CSAT from 82% to 90% within two quarters” |
| “Learn SQL” | “Write the weekly retention report myself in SQL within six weeks, instead of waiting on the data team” |
| “Speed up our releases” | “Cut average deploy time from 45 minutes to under 15 by the end of the quarter” |
| “Grow my network” | “Book 20 informational calls with product managers in three months” |
| “Get promoted” | “Lead one cross-team project end to end this year, which my manager said was the gap for the next level” |
Then add milestones. A three-month goal usually has two or three checkpoints. Mentioning them shows the interviewer you manage yourself rather than hoping it works out.
How do you answer “tell me about a time you set a goal and achieved it”?
Use the STAR method, with the goal stated precisely in the Task:
- Situation: the context and why the goal mattered, in two sentences.
- Task: the goal itself, with the number and the deadline, and whether you chose it.
- Action: the plan, the milestones, the setback and how you adjusted. This is most of the answer.
- Result: the outcome against the target, plus what it led to.
Three example answers we wrote
These are example answers we wrote to show three kinds of goals: a work target, a learning goal and a team goal. Use your own details and real numbers.
Example answer we wrote: work goal, customer support lead
Situation: I led a support team of six at an online retailer. Our first-response time on email tickets averaged 19 hours, and our satisfaction survey comments kept mentioning slow replies.
Task: I set myself a goal to get the average first-response time under 8 hours by the end of the quarter, without adding headcount. My manager agreed it was ambitious.
Action: I broke it into three monthly milestones: 14 hours, 10 hours, then under 8. In month one I tagged two weeks of tickets and found that about a third were order-status questions. I wrote five saved replies for those and shifted one person’s schedule to cover the morning peak. We hit 13 hours. In month two progress stalled at 11 hours because a product recall doubled volume for a week. Rather than drop the target, I set up a temporary recall form on the help page that answered the most common question before customers emailed, and reviewed the queue daily with the team.
Result: We finished the quarter at 7.5 hours, and satisfaction scores on email rose from 81% to 88%. The saved-reply library became part of onboarding for new hires.
Example answer we wrote: learning goal, marketing analyst
Situation: I was a marketing analyst who relied on the data team for every SQL query, which meant a three-day wait for most campaign reports.
Task: I set a goal to write the weekly campaign performance report myself, in SQL, within eight weeks.
Action: I set milestones: basic queries by week two, joins and aggregations by week four, and a full draft report by week six that a data engineer would review. I studied 45 minutes before work each day and practiced on real tables in our sandbox. In week three I fell behind because a campaign launch ate my mornings, so I moved my study block to lunch and dropped one milestone exercise rather than the deadline. I asked a data engineer for a 30-minute review every Friday.
Result: I shipped my first self-written report in week seven. It cut turnaround on campaign reports from about three days to same-day, and the data team reclaimed roughly four hours a week. Six months later I was writing queries for two other marketers.
Example answer we wrote: team goal, engineering lead
Situation: As tech lead for a team of five engineers, I noticed releases were happening only every two weeks because each deploy took about 45 minutes and often failed.
Task: I proposed a quarterly team goal: cut average deploy time to under 15 minutes and release at least twice a week.
Action: I split the work so each engineer owned one bottleneck: test parallelization, build caching, and a flaky integration suite. We reviewed a deploy-time chart in every Monday standup. Halfway through, the flaky-test work stalled because it needed changes from another team. I met their lead, agreed to quarantine the six worst tests behind a nightly run, and kept our goal intact.
Result: By quarter end, deploys averaged 12 minutes and we released three times a week. Failed deploys fell from about one in four to roughly one in fifteen, and the approach was copied by two neighboring teams.
Weak vs strong answers
| Element | Weak answer | Strong answer |
|---|---|---|
| The goal | “I wanted to get better at my job.” | A number, a deadline and why it mattered |
| Who set it | A quota you were handed | A goal you chose or raised yourself |
| Plan | “I worked really hard.” | Milestones and how you tracked them |
| Obstacle | Everything went smoothly | A real setback and the adjustment you made |
| Result | “It went well.” | Outcome against the target, plus what it led to |
Follow-up questions to expect, and mistakes to avoid
Common follow-ups:
- Why did you choose that goal over others?
- How did you track progress week to week?
- What would you have done if you had missed the target?
- Have you ever set a goal and not achieved it?
- What goal are you working on right now?
Mistakes that weaken the answer:
- A goal with no number. If you cannot say how you measured it, the interviewer cannot tell whether you achieved it.
- A goal that was easy. If you would have hit it anyway, it does not show drive.
- A personal goal with no link to the job. A marathon can work for entry-level candidates, but connect the planning habits to work.
- Taking credit for a team result. On team goals, say clearly what you did and what others did.
- Skipping the setback. It makes the story sound rehearsed and the goal sound too safe.
A goal story often overlaps with initiative and self-directed learning, so prepare different stories for the initiative question and the learning-something-quickly question. Our full list of “tell me about a time” questions helps you map one story to each prompt.
Practice it
Numbers are easy to forget under pressure, so rehearse until the target and the result come out without notes. You can run a free AI mock interview built from your résumé and job description: CoPilot Interview reads each question aloud, listens to your answer and scores it out of 10 with what to fix, for example a goal that was not measurable or a result with no comparison to the target. It is free for 15 minutes a day, with no account. If your stories are still rough, draft them first in the free STAR story builder.
Turn your goal story into a two-minute answer
Practice behavioral questions out loud, get a score out of 10 with specific feedback, and tighten the numbers before your interview.
Try a free AI mock interviewFAQ
What is a good example of a goal you set and achieved?
A good example is a goal you chose yourself, with a measurable target and a deadline, such as cutting a response time, learning a tool well enough to use it at work, or improving a team metric. It should include milestones, a setback and a result compared to the target.
Can I use a personal goal instead of a work goal?
Yes, especially if you are early in your career. Choose one that shows planning and persistence, such as a certification or a fitness goal with milestones, and connect those habits to the job. Experienced candidates should usually pick a work goal.
Does the goal have to be big?
No. A modest goal with a clear number, a real obstacle and a measurable result is stronger than a large goal described vaguely. Match the scope to the level of the role.
What if I exceeded the goal?
Say so, with the numbers, but keep the focus on how you planned and adjusted. Exceeding the target is a good result, not the whole story.
What if the interviewer asks about a goal I did not achieve?
Have a second story ready. Explain the goal, what you learned from missing it and what you changed. Our guide to answering the failure question shows how to structure that.
How long should my answer be?
Around two minutes. State the goal with its number and deadline early, spend most of the answer on milestones and the setback, and finish with the result against the target.