The best way to answer an interview question is to use the STAR method, with one change: start with a two-sentence summary. It is the step most answers are missing, and it turns a rambling reply into a clear one.
Most interview advice stops at Situation, Task, Action, Result. That structure works, but it asks the hiring manager to follow your story without knowing where it is going. A short summary up front gives them the map, and it is the one change I would make to almost every candidate's answers.
In this post you will see how to open an answer with that summary, a full worked example for a customer success manager, and examples for other EdTech roles.
What interviewers are really asking
When an interviewer says "tell me about a time when", they are checking whether you have already done the thing the role needs. Your past behaviour is the best evidence they can get, so they ask for a real example.
The STAR method gives that example a shape:
- Situation: the context. Where you worked and what was happening.
- Task: your responsibility. What needed to be achieved, and by when.
- Action: what you personally did, step by step.
- Result: the outcome, with numbers where you have them, and what you took from it.
You will hear these questions in every EdTech function, from a sales manager asked about a deal that was lost to an instructional designer asked about a course that was not working.
Where STAR answers go wrong
Most people start with the Situation and spend the first minute on background. The interviewer is listening, but they do not yet know what the story is about, why it matters or where it ends.
Three things tend to follow:
- The interviewer cannot tell whether your story answers the question until you reach the Result.
- The set-up uses up the time you need for the Action and the Result, which are the parts they are actually assessing.
- You lose your own thread, because you have not said where you are heading.
None of this is a problem with STAR itself. It is a problem with starting in the middle of the story.
The fix: start with a two-sentence summary
Before you go into the detail, say in two sentences what happened across the whole story. Then move into STAR and fill in the how.
- Sentence one: your role and the situation. "While working as a [role], I [noticed / was asked to / faced] [the problem or goal]."
- Sentence two: what you did and how it ended. "I [your main actions], and [the result]."
Then add a bridge such as "Let me take you through how that went", and begin the Situation.
Keep it to two sentences. If you need a third, you have started telling the story instead of summarising it.
This works for three reasons. The hiring manager knows straight away what you did and how it turned out, so they listen for the detail instead of waiting for the point. You show you can communicate clearly and briefly, which matters in any client-facing EdTech role. And you keep yourself on track, because you have already said where the story is going.
Worked example: a customer success manager and a churning account
The question: "Tell me about a time you saved an at-risk customer."
Start with the two-sentence summary:
While working as a Customer Success Manager, I spotted from our usage data that one of my accounts was at risk of churning, because they had stopped using the platform. I brought in the account manager to plan a reactivation, ran training for their team, and not only saved the account but secured an upsell.
Then add "Let me take you through how that went" and give the detail in STAR order:
- Situation: Our usage reports showed that one of my accounts had gone quiet. Logins had dropped by [X]%, renewal was [X] months away, and nobody on their side had raised a problem.
- Task: My job was to find out why usage had fallen and to get the account back to healthy use before the renewal conversation.
- Action: I looked at the data to see which teams had stopped and when. I contacted the account manager so that our reactivation plan and the commercial conversation lined up. I then set up training sessions for the team, and followed up with regular usage check-ins.
- Result: The account renewed, usage recovered to [X]% of licences, and the customer expanded with [the upsell]. I now check for usage drops across all my accounts every [week / fortnight].
The summary tells the hiring manager what happened. The STAR detail then shows how you did it, which is where they see your judgement. Swap anything in [brackets] for your own details, and keep the numbers real.
Two-sentence summaries for other EdTech roles
The same pattern works in every function. Each summary below names the role, the situation, what the person did and how it ended.
- Account Executive. Question: "Tell me about a deal you almost lost." Summary: "While working as an Account Executive, I was selling to a university where the deal stalled after their IT team raised security concerns. I brought our security lead into the process, rebuilt the proposal around their requirements, and closed the deal [X] weeks later for [£X]."
- Instructional Designer. Question: "Tell me about a course that was not working." Summary: "While working as an Instructional Designer, I found that learners were dropping out of one of our main courses after the second module. I reviewed the learner data and redesigned that module with shorter activities and clearer assessment, and completion rose from [X]% to [X]%."
- Implementation or Project Manager. Question: "Tell me about a project that was going off track." Summary: "While working as an Implementation Manager, I took over a school rollout that was [X] weeks behind plan. I reset the timeline with the customer and cleared the data migration blocker, and we launched on the new date with [X] schools live."
- Marketing Manager. Question: "Tell me about a campaign that did not perform." Summary: "While working as a Marketing Manager, I ran a webinar campaign that brought plenty of registrations but very few qualified leads. I reworked the targeting and the follow-up with the sales team, and the next campaign produced [X] times as many qualified opportunities."
- Head of Customer Success. Question: "Tell me about a time you led a team through change." Summary: "While working as Head of Customer Success, I inherited a team whose renewal rate had fallen after a restructure. I redefined account ownership and introduced a monthly health review, and renewals rose from [X]% to [X]%."
After each summary, you would go into the full STAR detail exactly as in the customer success example.
How to prepare: build a story bank
You do not need a new story for every question. Five or six strong stories will cover most of what you are asked, and the summary is what lets you reuse them.
- Pick your stories. Choose moments such as a clear win, a setback you recovered from, a difficult stakeholder, a time you led without authority, and a time you used data to make a decision.
- Write the two-sentence summary for each. Then jot the STAR detail as short bullet points, not a script, so you sound natural.
- Add the numbers. Renewal rate, revenue, completion rate, time saved, schools or learners reached. Only use figures you can back up.
- Match them to the role. Choose examples that look like the job you are applying for, whether that is school-facing customer success, university sales or corporate learning design.
- Practise out loud. Say the summary first, then the full answer, and time it. The summary should take around fifteen seconds, and the whole answer around two minutes.
One story can also answer different questions. A single customer rescue can be "a time you used data", "a time you worked across teams" or "a time you grew an account", if you change the two-sentence summary to put the right part first.
Common mistakes to avoid
Even with a good summary, a few habits can weaken an answer.
- A long set-up. If the Situation and Task take more than a few sentences, cut them back. The detail the interviewer wants is in the Action and the Result.
- Saying "we" all the time. The interviewer is assessing you. Say what you did, and credit the team where it is fair to.
- A summary with no outcome. "I worked on a retention project" says nothing. "I saved the account and secured an upsell" tells them what happened.
- A vague result. "It went well" is not a result. Give a number, or a clear before and after.
- Using the same story for every question. Interviewers notice. Vary your examples across the interview.
- Stretching the truth. Follow-up questions will test every claim, so only tell the story as it happened.
What to do next
Preparing your stories on your own will take you a long way. The harder part is knowing which of them is strongest for the roles you are going for, and how they sound to someone sitting across the table.
If you are preparing for a specific interview and want answers built around your own career, a one-to-one session is the next step. We can work through your real interview questions, tighten your two-sentence summaries and practise with feedback that is tailored to you.
Book a one-hour 1:1 career strategy session to work on your positioning, your search and your interview preparation. Book your session
