Your Definition of Accountability
How do you define personal accountability? Give an example of a time you were held accountable or held others accountable for an outcome.
Why Interviewers Ask This
Interviewers at Adobe ask this to assess your alignment with their 'No Asshole' culture and creative collaboration values. They need to verify if you own your mistakes without defensiveness, as accountability is vital for maintaining psychological safety in cross-functional design and engineering teams.
How to Answer This Question
1. Define Accountability: Start by framing it not just as admitting errors, but as proactive ownership of outcomes and a commitment to solutions. 2. Select Your Story: Choose a specific scenario where a project missed a target or a mistake occurred, ensuring it involves clear consequences. 3. Apply STAR Method: Structure your narrative clearly. In the Situation, set the context. In the Task, state your specific responsibility. 4. Detail the Action: Describe exactly how you identified the issue, took full ownership without blaming tools or teammates, and implemented a fix. 5. Highlight the Result: Conclude with the positive outcome, emphasizing what you learned and how you changed your process to prevent recurrence. This structure mirrors Adobe's focus on growth mindset and transparent communication.
Key Points to Cover
- Demonstrating a growth mindset where failure is viewed as a learning opportunity
- Avoiding blame-shifting or making excuses when things go wrong
- Showing proactive communication by addressing issues before they escalate
- Highlighting concrete steps taken to rectify the situation and prevent recurrence
- Aligning personal behavior with collaborative and transparent company values
Sample Answer
I define personal accountability as the unwavering commitment to owning both successes and failures, focusing immediately on solutions rather than excuses. It means recognizing that my actions directly impact our collective goals.
In my previous role as a Product Designer, we were launching a new feature for a client deadline. I realized two days before launch that my initial user flow had a critical accessibility flaw that would block users with screen readers. Instead of hiding the issue or hoping it wouldn't be caught, I immediately informed the engineering lead and product manager. I acknowledged that I had rushed the QA phase due to time pressure.
I took full ownership by staying late to redesign the flow overnight and coordinating closely with developers to ensure the fix was implemented correctly. We launched the feature one day late, which was a significant hit, but because I communicated early and owned the error, the team maintained trust. The post-mortem led to a new mandatory accessibility checklist for all future sprints. This experience reinforced that true accountability builds stronger teams and prevents small errors from becoming major crises, aligning perfectly with Adobe's value of creating an environment where everyone feels safe to speak up and grow.
Common Mistakes to Avoid
- Blaming external factors like tight deadlines or unhelpful colleagues instead of owning your part
- Providing a vague answer that lacks specific metrics or a clear timeline of events
- Focusing too much on the problem rather than the solution and the lesson learned
- Claiming you have never made a mistake, which suggests a lack of self-awareness
Practice This Question with AI
Answer this question orally or via text and get instant AI-powered feedback on your response quality, structure, and delivery.