TechCrunch found Vocci's $249 ring records well and its software disappoints. The question that asks for that review of you.
On September 20, 2026, TechCrunch's Ivan Mehta published a hands-on review of the Vocci ring, a meeting note-taker built into a piece of jewellery and priced at $249. The verdict is split, and the split is instructive. On the hardware, Mehta wrote that "The device captures meetings very well": in conversations spanning more than an hour in loud cafes, the ring converted most of the chat into accurate transcripts. It weighs under 6 grams, and the company claims it can record for 8 hours on a single charge. Then the review turns. "The software is the disappointing part of the Vocci ring," Mehta wrote. He found the app "a bit confusing", added that "The feature rollout for its software is also slow", and judged the platform "not fully built out" for the automation other notetakers are building. He also wrote that the form factor "could create some privacy issues". The ring has a recording indicator, "but it faces the user". According to TechCrunch, the company said it encourages people to disclose that they are recording, "but that may not be enough." It is one reviewer's assessment, and he presents it as that.
Set the product aside and look at what the review does. It does not call the ring good or bad. It separates the part that worked from the part that did not and says exactly where the shortfall is. Then it judges the remedy as well as the problem. An indicator light exists, but it points the wrong way. A policy of encouragement exists, but in the reviewer's judgment it does not change what happens. That is a complete post-mortem written by an outsider. An interviewer who asks "Tell me about a time you failed. What would you have done differently?" wants to know whether the candidate can write the same review of their own work when no reviewer forces them to.
Why they ask it
Nobody asks an experienced manager this to find out whether they have failed. Everyone in the room has. The question samples how accurately a person sees their own work when the result was bad, because a manager needs that accuracy every week. The person hired will run post-incident reviews, give performance feedback, and report slipped dates upward. A manager who cannot find their own contribution to a failure is unlikely to find it in their team's work either. They tend to blame conditions.
The second sentence of the question does more work than the first. "What would you have done differently" tests whether the lesson became a practice the candidate actually follows. Interviewers listen for what the candidate now does that they did not do before.
The trap
The best-known failure mode is the disguised success: the candidate cared too much, or took on too much, and everything turned out fine. Most experienced candidates know to avoid it. A more common version at senior levels is the diffuse failure. The project slipped, the reorganization hurt, the timeline was unrealistic, and the candidate's own decisions never appear in the story. The candidate is describing conditions and owning nothing.
The subtlest trap sits in the second half. A candidate names a real failure with a real cost, then says they would communicate earlier, push back harder, or be more careful next time. This is the interview equivalent of an indicator light that faces the wearer. It reassures the person telling the story and changes nothing for anyone else in the room. When the lesson is stated as an intention, the interviewer cannot tell it apart from no lesson. Many otherwise credible answers are lost here.
Applying STAR-T
Situation. Keep it short and make the stakes legible. Our platform team had committed to moving the billing service to the new event pipeline before the finance team's reporting deadline, and another team's launch depended on that date. A sentence or so of context is enough. The interviewer needs to know what was at risk, not the architecture.
Task. State what was yours. I owned the plan and the date. I had told both teams it would hold. This sentence stops the answer from turning into a story about circumstances.
Action. This is where a failure answer differs from every other STAR answer, because the action that matters is the decision that went wrong. Name it as a decision, with the reasoning that made it look sensible then. We were behind, and my most senior engineer was confident he knew every consumer of the old service. I chose to skip the dependency audit to buy back time. I did not tell either team that I had removed that check. The specific choice, the reason for it, and the fact that it stayed invisible to others are the material the interviewer is looking for.
Result. Give the cost plainly, and include the cost to other people. An undocumented consumer surfaced during cutover. We rolled back, the date slipped, and the dependent team lost their launch window. Their manager heard about it from the incident channel before hearing it from me. Then say what was recovered, briefly. Do not let the recovery become the point.
Trade-off. A strong answer admits that the fix costs something. I now treat the audit as something I cannot cut for schedule. If I drop any safeguard, the people exposed to the risk hear it from me the same day. That has cost us time on later projects, and I have had to defend it in planning. If the lesson sounds free, the candidate has probably never applied it.
The follow-up that breaks weak answers
The follow-up is nearly always some form of: when did that last come up, and what did you do? It pushes the lesson out of the hypothetical. A candidate whose answer ended on an intention has nothing to say. They restate the intention with more feeling. A candidate who changed a practice has a second, smaller story ready. It is a later project where the same pressure appeared, the same shortcut was available, and they did something observably different. The variant is sharper: what would the other team's manager say about how you handled it? An honest answer includes the part where that manager was right to be annoyed.
Prepare both stories before the interview. The failure is the first, and the later time the lesson held is the second. Interviewers often find the second more persuasive.
Score your answer against the director’s bar
Q: Tell me about a time you failed. What would you have done differently?
Bank one failure story with a named decision and a changed practice, then rehearse it aloud until the follow-up has an answer. Try it free →