Tell Me About a Time You Took a Risk: How to Answer (With Examples)

"Tell me about a time you took a risk" sounds like an invitation to brag about being bold. It is not. Interviewers use it to learn three things: how you judge uncertainty, how you act when the outcome is unclear, and how you handle the consequences whether the bet pays off or not. Companies that prize ownership and innovation, such as Amazon ("Bias for Action"), Google, Microsoft and most startups, ask it routinely. So do banks and consultancies, where the real question is whether you can take a considered position without being reckless.

The question has a hidden trap. A story about doing something dangerous with no safeguards makes you look careless. A story where the "risk" was trivial makes you look timid or unprepared. The sweet spot is a calculated risk: a decision where you could genuinely have failed, you understood the downside, you took steps to limit it, and you owned the result.

Interviewers usually score your answer against a handful of signals. Knowing them lets you shape the story before you walk in.

Most candidates ramble through a risk story because they have no structure for the judgment part. Use the standard STAR method (Situation, Task, Action, Result) for the overall shape, and organize the Action section with CALM, a four-step way to show the decision was calculated rather than careless. For a refresher on the base method, see our STAR interview technique guide.

• C – Clarify the stakes: State what you stood to gain and what you stood to lose, in concrete terms such as time, budget, reputation or a customer relationship.
• A – Assess the evidence: Describe what data, advice or precedent you looked at. One or two specifics beat a vague "I did my research".
• L – Limit the downside: Explain what you did to make failure survivable: a pilot, a rollback plan, a small first test, a check with your manager, or a deadline for reassessment.
• M – Move and measure: Say how you committed to the decision and how you tracked whether it was working, including the point at which you would have stopped.

Notice that CALM is mostly about the steps before the outcome. This is deliberate. Interviewers know that results depend partly on luck; what they can evaluate is your process. A good process story still impresses when the result was mixed.

How the framework maps onto STAR

Before drafting anything, list three or four candidate stories and test each against the criteria below. Most people default to the first dramatic thing that comes to mind; the best story is usually a less dramatic one that is well documented and clearly yours.

Match the story to the employer. A technology company will usually respond to a story about shipping something imperfect and iterating. A bank or professional services firm will respond better to a story that shows a considered recommendation backed by analysis. If you are applying for a role like a software engineer, a risk involving a technical decision (choosing an unfamiliar tool, refactoring a fragile system) is more convincing than a generic leadership story.

Finally, avoid stories involving ethics shortcuts, legal or safety violations, or anything that makes a past employer look bad. A risk that involved breaking a rule is almost never worth telling, even if it worked.

The examples below are written to be spoken in roughly 90 seconds to two minutes. They use invented details for illustration, so build yours from your own experience rather than reusing them. Each is labeled with the CALM steps so you can see the structure.

Example 1: Recent graduate (campus project)

Situation and Task: "I was treasurer of a 60-member finance society. Our annual careers event had always been a panel talk, and attendance had dropped each year. I was responsible for the budget and proposed replacing it with a case-competition format, which nobody on the committee had run before. If it failed, we would have spent about a third of our annual budget on an event few people attended."

Action: "I clarified the stakes with the committee: the downside was the money and our relationship with two sponsors. I assessed the evidence by speaking to three other societies that had run case competitions and by surveying members, where 70 percent said they wanted something more hands-on. To limit the downside, I ran a small pilot with 12 members first and got sponsors to commit to prizes only after seeing the pilot feedback. I set a rule that if registrations were under 40 two weeks before the event, we would revert to the panel."

Result: "We reached 78 registrations, and both sponsors renewed for the following year. The main thing I learned was to build in a decision checkpoint. I now do that on any project where the format is new."

Example 2: Early-career professional (stretch assignment)

"In my second year as an analyst, our team lead went on leave just before a client reporting deadline, and I asked to take over the forecasting model even though I had only used a small part of it. The risk was an error going to a client under my name. I spent two evenings mapping the model with the departing lead, built a checklist of the 15 inputs that drive the output, and asked a senior colleague to review my first pass before it went out. The report went out on time, and the reviewer found one formula issue that I fixed beforehand. That made me realize the value of asking for a review before something is final, not after."

Example 3: Mid-career (challenging a process)

"Our customer support team required every refund over $50 to go through manager approval, which was adding two days to resolution times. I proposed raising the threshold to $150 for agents with a high quality score. The risk was higher refund losses, and I would have been accountable for that. I pulled six months of data showing that fewer than 2 percent of refunds in that range were later reversed, proposed a 60-day trial with one team, and agreed that I would report the loss rate weekly. Average resolution time fell by 30 percent and refund losses stayed within the range we expected, so the policy was adopted across the department."

Example 4: Career changer (personal and professional)

"After four years in retail management, I decided to move into data analysis. The risk was leaving a stable role and a salary I would not match for at least a year. I limited it by studying part-time for eight months, completing three portfolio projects using public data, and saving six months of expenses before resigning. I took a junior analyst role at a lower salary, and within 18 months I was promoted. What I took from it is that I am comfortable with risk when I can break it into stages and test each one."

Candidates who have solid experience still lose points on this question through avoidable errors. The most frequent ones appear in the table below.

If your risk did not work out, you can still use the story. In fact, a story that ended in partial failure is often more credible. Explain what you did when the signs turned negative, how quickly you cut your losses and what you now do differently. Our guides on how to answer questions about failure and making a difficult decision show how to handle the aftermath well.

The risk question rarely appears in exactly the same words. Interviewers rephrase it, and your prepared story needs to bend to fit. The table lists the common variants and the emphasis to shift for each.

One well-prepared story can usually be adapted to three or four of these. In your preparation, write down a single master version using the CALM structure, then practice emphasizing different parts depending on the question. This is far more efficient than memorizing separate answers. Related prompts include showing initiative and dealing with ambiguity, and it is worth building stories for each.

Strong delivery comes from deliberate preparation, not memorization. Follow this process in the days before your interview.

• Brainstorm three stories. Write a few bullet points for each: the situation, what was at stake, what you did and the result.
• Quantify. Add numbers wherever you can honestly do so: money, time, percentages, people affected. If you do not have exact figures, use careful estimates and say so.
• Draft the CALM section first. This is the heart of the answer. Make sure each of the four steps is in there.
• Time yourself. Aim for about two minutes. Anything much shorter lacks detail; anything longer loses people.
• Practice out loud. Record yourself or practice with a friend. Listen for filler words and moments where you skip your own reasoning.
• Prepare for follow-ups. Write down three tough follow-up questions and rehearse short, honest answers.

On the day, speak at a measured pace and start with one sentence of context before diving into the story. If the interview is virtual, keep your notes minimal so you can maintain eye contact with the camera. Our video interview tips cover the technical and presentation basics. For a broader view of the behavioral round, see our behavioral interview questions guide.