# Tell me about a time you disagreed with a team member. | Aced

Aced (formerly Exponent) publishes a public search API over its indexed pages; the guide is at https://www.aced.io/agents/agent-access.

Source: https://www.aced.io/questions/6521/describe-team-disagreement-experience
Source observed: 2026-11-04T23:28:15.641Z
Last checked: 2026-11-04T23:28:15.641+00:00
Indexed: 2026-11-06T15:57:26.037+00:00

---

# Tell me about a time you disagreed with a team member.

We provide interview-preparation resources through Aced (formerly Exponent). This behavioral, cross-functional interview-question page helps candidates review reported interview experiences, compare roles and companies, explore related questions and courses, and practice an answer.

## Question details

- **Reported interviews:** 5 shared experiences
- **Categories:** [Behavioral](https://www.aced.io/questions?type=behavioral), [Cross-Functional](https://www.aced.io/questions?type=cross-functional)
- **Roles represented:** [Software Engineer](https://www.aced.io/questions?role=swe) (2), [Engineering Manager](https://www.aced.io/questions?role=em), [Business Analyst](https://www.aced.io/questions?role=business-analyst), [Product Manager](https://www.aced.io/questions?role=pm)
- **Companies represented:** [Amazon](https://www.aced.io/questions?company=amazon) (3), [Google](https://www.aced.io/questions?company=google) (2)

Detailed company statistics for this question require an upgrade: [Upgrade](https://www.aced.io/upgrade?src=questions).

## Interview experiences

Five community-shared experiences are associated with this question. The dates below are relative labels preserved from the source; the page was observed on 2026-11-04.

### Google · 2 months ago

**Role:** Software Engineer · Mid Level / L4

> “The process was straight-forward, I also felt sick the day before the phone interview and they rescheduled it without any problem. The phone interview was quite “flat”, I talked almost the whole time both at the technical and behavioural round and the interviewers basically always only agreed with what I was saying. The on-site was really cool, offices are great and my 2 interviewers were really kind persons that made me feel very comfortable.”

[Read the Google Software Engineer interview experience](https://www.aced.io/experiences/google-software-engineer-interview-db29a7)

### Amazon · 5 months ago

**Role:** Software Engineer · Intern

> “Overall, the process was pretty smooth: application, online assessment, then two virtual interviews. The OA and coding rounds went well because the questions were standard DSA and I was comfortable explaining my approach and complexity. The behavioral portions also felt solid once I got into my STAR examples. The hardest part was handling follow-up questions and changing constraints in real time, especially when I had to rethink an approach while still communicating clearly.”

[Read the Amazon Software Engineer Intern interview experience](https://www.aced.io/experiences/amazon-software-engineer-intern-interview-26d676)

### Amazon · 6 months ago

**Role:** Engineering Manager · Staff / L6

> “The overall interview process consisted of a recruiter screen, a technical call with the hiring manager, a written narrative exercise, and a 5-round virtual loop focusing on System Design, People Management, Operational Excellence, Cross-Functional Leadership, and a Bar Raiser round, with each module heavily testing Amazon’s Leadership Principles using the STAR method. What went well was my ability to deliver structured, data-driven answers that dedicated most of the time to my direct actions as a leader while anchoring results in concrete business metrics. I successfully demonstrated core Leadership Principles like Customer Obsession and Hire and Develop the Best through explicit examples of team growth, performance management, and architecture trade-offs, effectively balancing high-level business strategy with technical depth during system design discussions. What didn’t go as well was my initial tendency to credit the team using “we” instead of “I,” which required interviewers to interrupt and probe for my specific individual contributions. Additionally, I mismanaged pacing in one round by spending too much backstory time setting up an operational failure scenario, which left little time for long-term preventative fixes, and I initially got bogged down optimizing a single database schema during system design rather than outlining the full end-to-end architecture first”

[Read the Amazon Staff Engineering Manager interview experience](https://www.aced.io/experiences/amazon-staff-engineering-manager-interview-556a8d)

### Amazon · 10 months ago

**Role:** Business Analyst · Intern

> “Exactly what people say the behaviorals are. 5 behaviorals across 2 interviews. In the first techncial one, I got asked 9 SQL and 1 Python. Messed up the python”

[Read the Amazon Business Analyst Intern interview experience](https://www.aced.io/experiences/amazon-business-analyst-intern-interview-94e5d7)

### Google · 2 years ago

**Role:** Product Manager · Mid Level / L4

> “I went through 5 rounds for a Senior PM role: a recruiter screen, a hiring manager call, then three virtual on-sites covering Product Sense, Analytical/Metrics, and Googleyness/Leadership, followed by a cross-functional interview with an engineering partner. The whole process took about 5 weeks from initial outreach to offer. What went well: The recruiter was communicative throughout and gave clear prep guidance before each round, which helped me calibrate expectations. The Product Sense interview felt collaborative — the interviewer built on my ideas rather than just grading me, and I appreciated that the analytical round used a real, de-identified product problem rather than an abstract puzzle. What didn’t go well: Scheduling took longer than expected between the hiring manager call and the on-site loop (about 10 days), which created some uncertainty. I also found the case interview time pressure tight — 45 minutes wasn’t quite enough to fully structure and solve the prompt, so I’d have appreciated a few extra minutes to synthesize a recommendation at the end.”

[Read the Google Product Manager interview experience](https://www.aced.io/experiences/google-product-manager-interview-b70ab2)

## Community answers

No answers have been contributed by the community yet. You can log in or sign up to answer the question.

## Related questions

- [Tell me about a time when you disagreed with Engineering.](https://www.aced.io/questions/263/engineering-disagreement)
- [Tell me about a time you worked with another team.](https://www.aced.io/questions/5826/working-with-another-team)
- [Tell me about a time when you had a disagreement with your manager.](https://www.aced.io/questions/241/disagreement-manager)

## Related courses

### Engineering Management Interview Prep

![Engineering Management Interview Prep](https://images.ctfassets.net/x78yjrjc11pq/5AqarwlCDWmr0W7AbMJFwp/16862dab13471f5eb8728b27eb2fbc07/engineering_management_track_compressed_bbabaec4a6__281_29_9a9687c1fb.jpeg?w=800&h=800&fm=webp&q=75)

[Explore Engineering Management Interview Prep](https://www.aced.io/courses/engineering-management)

Land an engineering manager role at Meta, Google, Amazon, Microsoft, Stripe, and other top companies with mock interviews, frameworks, and advice from senior candidates. Topics include system design, people management, project retrospectives, behavioral interviews, and more.

### System Design Interviews

![System Design Interviews](https://images.ctfassets.net/x78yjrjc11pq/78x7miFZFjBCrM5GqftrMJ/2f6d26e632c4e7265c49f6a180227edb/system_design_track_compressed_26ac98a46e__281_29_5be2280f31.jpeg?w=800&h=800&fm=webp&q=75)

[Explore System Design Interviews](https://www.aced.io/courses/system-design-interviews)

Learn to answer current system-design questions across product, infrastructure, and AI domains through in-depth video examples, written breakdowns, reference patterns, and mock-interview answers from senior engineers and managers.

## Practice your answer

Submitting an answer marks this question complete. Use [Practice with AI](https://www.aced.io/practice/ai/new?type=Behavioral&question=describe-team-disagreement-experience&src=questions) to practice this Behavioral question with AI.

## Aced interview-preparation areas

We offer courses and practice resources for Product Management, Forward Deployed Engineering, Engineering Management, Software Engineering, System Design, Data Science, Machine Learning, Data Engineering, AI Engineering, Investment Banking, Generative AI, Security Engineering, TPM, Solutions Architecture, UX / Product Design, and BizOps & Strategy. We also offer interview experiences, questions, coaching, resume review, salary negotiation, job referrals, resources, and related programs through our public site.

---

[Read this page’s summary](https://www.aced.io/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fquestions%2F6521%2Fdescribe-team-disagreement-experience&trace=t_679ff9ab98f3)

## Ask a follow-up about this page

Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Aced (formerly Exponent)’s knowledge base. No account or API key required.

Open this URL with your own question, URL-encoded. Include your question in q. All research inputs are optional; no account or setup.

`GET https://www.aced.io/agents/agent/faq?q={question}&trace=t_679ff9ab98f3`

[Tool guide and examples](https://www.aced.io/agents/agent-access) · [OpenAPI](https://www.aced.io/agents/api/public/v1/openapi.json) · [Page TLDR form](https://www.aced.io/agents/agent-tools/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fquestions%2F6521%2Fdescribe-team-disagreement-experience). Opening a form does not execute a tool.