Tell Me About a Time You Worked Independently: How to Answer

Short answer: interviewers ask "tell me about a time you worked independently" to find out whether you can be trusted with a task and left to deliver it. A strong answer shows that you clarified the goal, built your own plan, solved problems without waiting to be told, checked in at sensible moments and delivered a result someone could measure.

Every manager has a limited amount of attention. A new hire who needs step-by-step instructions, or who stalls the moment they hit an obstacle, costs that manager hours every week. A new hire who can take a brief and run with it frees them up. That is why this question appears in interviews for almost every kind of role, from analyst programs and software engineering to retail, logistics and healthcare jobs where you may be the only person on shift.

The question has become more common as remote and hybrid work has spread. When your manager cannot see you at your desk, they need confidence that you will manage your own time, unblock yourself and flag problems early. Interviewers for fully remote roles often ask a version of this question in the first round for exactly that reason.

Large employers that run structured behavioral interviews usually map this question to named competencies such as "drive," "ownership," "self-management" or "delivering results." Amazon, for example, publishes its Leadership Principles, and "Ownership" and "Bias for Action" are the ones a working-independently story naturally supports. If the company you are applying to publishes its values or competencies, read them and use the same vocabulary when you describe your actions.

The most common misunderstanding about this question is thinking it rewards doing everything alone. It does not. Employers want people who can work without supervision, not people who refuse to collaborate or disappear for two weeks and return with the wrong deliverable. The best answers show calibrated independence: you made the decisions that were yours to make, asked the questions that genuinely needed an answer and kept people informed without needing them to manage you.

A useful way to think about it is as a spectrum. At one end, a person needs to be told what to do at every step. At the other, a person goes completely dark and makes decisions far beyond their authority. Interviewers are looking for someone in the middle-right of that spectrum, and the right position shifts with seniority.

Why the balance matters

If your answer leans too far toward asking permission, it sounds like you lacked confidence. If it leans too far toward going it alone, it raises a different concern: will this person fit into a team? Some candidates also accidentally signal that they dislike working with others by saying things like "I do my best work when nobody is around." Even if that is true, it is not the message to lead with. Frame independence as something that helps the team, for example by taking work off a busy colleague's plate or covering a gap so others could focus.

It also helps to know that teamwork and independence are usually assessed side by side. Many interviewers will ask this question in the same session as "tell me about a time you worked in a team". Prepare both stories so they complement each other rather than contradict each other.

The best stories have four ingredients: you were the clear owner of a piece of work, the path to the result was not fully mapped out for you, you hit at least one obstacle you had to solve yourself, and there is a concrete outcome. If any one of those is missing, the answer tends to sound thin.

Good sources of stories

• A research, analysis or reporting task you were handed with a short brief
• A project you ran while your manager was on leave, traveling or busy with something else
• A process, document or tool you built from scratch because nothing existed
• A shift, site visit or client meeting where you were the only person from your team present
• Remote work where you were in a different time zone from the rest of the team
• A senior thesis, capstone, independent study or personal project with a real deliverable
• Teaching yourself a new tool or skill to complete a task on time

Stories to avoid

Avoid examples where working alone was simply the default and nothing required judgment, such as "I studied for my exams on my own." Avoid stories where you worked independently because you did not trust your teammates, or where you made a decision that clearly should have been escalated, such as committing budget or changing a client agreement without approval. Also avoid any story where the result was a missed deadline caused by not asking for help early enough, unless you are deliberately using it as a lesson-learned example and can show what you now do differently.

If your work history is short, an academic project is perfectly acceptable. Interviewers for graduate schemes and internships expect it. What matters is that you set your own milestones and pushed through a problem, not that a company paid you to do it. Our first job interview questions guide has more ideas for finding examples when you have limited experience.

The STAR method (Situation, Task, Action, Result) gives your answer its overall shape. For independence questions, though, the Action step is where most candidates go vague: "I just got on with it." The SOLO framework fills that step with the four behaviors interviewers are listening for.

Time allocation

Aim for 90 to 120 seconds. A good split is about 15 to 20 seconds of context, 60 seconds of action (spread across the Scope, Organize and Loop-in steps) and 20 to 30 seconds on the result and what you learned. The most common error is spending a full minute describing the project, which leaves no time for the decisions that prove you can work independently.

Include one obstacle

An independence story without a problem is just a description of someone doing their job. Include one specific obstacle, such as missing data, a tool you had never used, a stakeholder who was unavailable or a requirement that changed, and explain how you got past it. The obstacle is where the interviewer sees your problem-solving and your judgment about when to ask for help.

Each example below follows STAR with the SOLO steps inside the Action. Use them to see the structure, then replace every detail with your own experience. Interviewers hear published sample answers often, and a borrowed story usually falls apart under follow-up questions.

Example 1: Ambiguous analysis task (analyst or graduate role)

Situation: "Three months into my role as a junior business analyst, my manager asked me to find out why customer churn in our Midwest region had risen over the previous two quarters. She was leading a system migration and told me she would have very little time for the next three weeks."

Task: "I had a one-line brief and a deadline: a recommendation for the regional leadership meeting in three weeks."

Action: "First, I scoped it. I asked her one question by email: was the goal to explain the churn or to recommend fixes? She said both, with fixes as the priority. I then planned the work in three phases with a checkpoint at the end of each week. In week one I pulled account data and found I didn't have access to the support-ticket system. Rather than wait, I asked the support team lead for a read-only export, which arrived in two days. In week two I found that most of the churned customers had opened two or more billing tickets in the 60 days before canceling. Every Friday I sent my manager a three-bullet update with what I had found and what I planned next, so she could redirect me if needed."

Result: "I presented two days before the deadline. The region introduced a billing check-in call for any account with a second billing ticket, and churn in the next quarter fell back toward the company average. My manager later gave me ownership of the monthly churn report. The lesson I took was that one clarifying question at the start saved me from building the wrong analysis."

Example 2: Remote, different time zone (tech or operations role)

Situation: "I was the only member of a product support team based on the West Coast; everyone else was in New York. A customer escalation came in at 4 p.m. my time, after the rest of the team had logged off."

Task: "The customer's integration was failing, and they had a launch the next morning. I needed to resolve it or hand it over in a state the East Coast team could pick up immediately."

Action: "I reproduced the error in our test environment and traced it to an expired API credential on the customer's side. That was within my authority to fix with the customer, so I walked them through regenerating it on a call. One part of the issue, a rate limit that needed raising, required engineering approval, which I didn't have. I documented the exact request, posted it in the engineering channel with the customer's launch time and set up a temporary workaround the customer agreed to. Before logging off I wrote a handover note so the morning team knew precisely what was done and what was outstanding."

Result: "The customer launched on time. Engineering approved the rate-limit change by 10 a.m. Eastern without needing to ask me anything, because the note answered their questions. My team lead later adopted my handover format as the standard for after-hours escalations."

Example 3: Solo shift (frontline or hourly role)

Situation: "At a pharmacy where I worked as a technician, I was regularly the only technician on the evening shift, with one pharmacist who was focused on consultations and checking prescriptions."

Task: "One evening our automated refill queue showed more than 60 prescriptions due for pickup the next day, which was about twice the normal volume because of a system outage earlier in the week."

Action: "I sorted the queue by pickup time and by whether a prescription needed a call to an insurer or a prescriber, because those take longest. I handled the calls first while offices were still open, then filled the straightforward refills. I told the pharmacist my plan in one sentence so she could prioritize her checks in the same order, and I flagged two prescriptions that needed her clinical judgment rather than guessing. I left a note for the morning team listing the eight prescriptions still waiting on a callback."

Result: "All but those eight were ready by opening, and the morning team closed out the rest before noon. My manager asked me to write up the triage order as a checklist for other evening staff."

Example 4: Senior thesis (no work experience)

Situation: "For my senior thesis in economics, I chose to study the effect of state minimum-wage changes on teen employment. My advisor met with me once a month, so most of the work was self-directed."

Action: "I wrote my own timeline with a milestone every two weeks and shared it with my advisor so she could hold me to it. Halfway through, I realized I needed a statistical method we hadn't covered in class. I worked through an online course and two textbook chapters over a week, then booked office hours with a teaching assistant to check that I had applied it correctly rather than waiting for my next advisor meeting."

Result: "I submitted a week early, received honors, and presented the paper at our department's undergraduate research day. More importantly, I learned to set my own deadlines well ahead of the real ones."

The difference between an average and an excellent answer is rarely the story itself. It is the level of detail in the decisions you made and whether the interviewer can see how you managed yourself. Compare two versions of the same situation.

Common mistakes

The self-check

Before your interview, test your answer against five questions. Is it clear what you were asked to do and how vague the brief was? Can the interviewer see your plan? Is there one obstacle you solved yourself? Did you keep anyone informed, and did you escalate anything appropriately? Is there a number or concrete change in the result? If any answer is no, that is the part to rework. Then say it out loud and time it; most first drafts run long because of background detail, and that is the part to cut.

Structured interviewers often follow the main question with probes designed to test whether the story is real and how deep the skill goes. Prepare a short answer to each of the following from the same story.

How to answer "Do you prefer to work alone or in a team?"

This question often comes straight after the independence question, and it is a trap only if you pick one extreme. The strongest answers say you are comfortable with both, explain what each is good for and connect the answer to how the role actually works. For example: "I like a mix. I do my best deep work, like analysis or writing, with a block of uninterrupted time on my own, but I find the best ideas come from testing that work with other people. From what I understand, this role is about 70 percent independent analysis and 30 percent working with the sales team, which suits me well."

Questions that use the same answer

• "Tell me about a time you worked with minimal supervision."
• "Describe a project you managed on your own from start to finish."
• "Give an example of when you were a self-starter."
• "Tell me about a time you had to make a decision without your manager."
• "How do you manage your work when working remotely?"

Several related questions can share material with this story, including showing initiative, dealing with ambiguity and taking ownership. Keep one backup example in a different setting so that if the interviewer asks for "another time," you are not forced to reuse the same project.