STAR: Task
The Task defines YOUR specific responsibility. This is where interviewers start distinguishing individual contribution from team effort.
What is the Task?
The Task answers one critical question: What was YOUR specific role or responsibility in this situation?
This is not what the team needed to do. It's what you were accountable for.
The "I vs. We" problem
The single most common mistake in behavioral interviews is over-using "we":
| ❌ Team-level Task | ✅ Individual Task |
|---|---|
| "We needed to fix the pipeline before the deadline" | "I was responsible for diagnosing the root cause and designing a fix for the event pipeline" |
| "Our team had to improve customer satisfaction" | "I owned the analysis of our NPS data and was tasked with identifying the top 3 drivers of churn" |
| "We were asked to build a new onboarding flow" | "I was the lead engineer responsible for the frontend architecture and the integration with our auth system" |
Why interviewers care about the Task
The Task tells the interviewer:
- Scope of ownership — Were you a contributor, a lead, or a decision-maker?
- Accountability — What were you personally on the hook for?
- Role clarity — Did you understand what was expected of you?
- Level signal — Does the scope of your task match the level you're interviewing for?
Scaling the Task to the level
The Task should demonstrate scope appropriate to the role:
| Level | Task Signal |
|---|---|
| Individual Contributor | "I was responsible for implementing the caching layer and writing the integration tests" |
| Senior IC | "I owned the technical design, led the code review process, and mentored two junior engineers on the team" |
| Manager | "I was accountable for the team's delivery, managed the cross-team dependencies, and made the prioritization calls" |
| Senior Leader | "I set the strategy for our migration approach, got buy-in from three VP stakeholders, and owned the success metrics" |
Exercise: Extract the individual Task
For each scenario, rewrite the Task to clearly show individual ownership.
1. "We needed to migrate our database from MySQL to PostgreSQL."
→ "I was the engineer responsible for designing the migration strategy, writing the data transformation scripts, and validating data integrity across both systems."
2. "The team had to reduce our API response time."
→ "I owned the performance investigation — my task was to profile our API endpoints, identify the bottlenecks, and propose solutions with estimated impact for each."
3. "We were told to improve our deployment process."
→ "I was tasked with evaluating our CI/CD pipeline, identifying the manual steps causing delays, and building an automated deployment workflow."
Your turn: Take the Situation you wrote in the previous section. Now add a Task: What were you specifically responsible for? Write 1-2 sentences using "I" language.
Why is it important to use 'I' instead of 'we' when describing your Task?
A candidate says: 'Our team was responsible for launching the new product.' What should the interviewer do?
Which Task statement best demonstrates senior-level scope?