# Behavioral interview question: disagreeing with someone and resolving it 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/1350/time-disagreed-someone-resolved Source observed: 2026-11-04T21:35:01.372Z Last checked: 2026-11-04T21:35:01.372+00:00 Indexed: 2026-11-05T00:46:18.03+00:00 --- # Tell me about a time you disagreed with someone and how you resolved it. We provide this behavioral interview question with interview context, shared interview experiences, community answers, related questions, and preparation courses. The question has **24 interviews**, was reported last asked **a month ago** at the time shown on the page, and is associated with Software Engineer, Product Manager, Technical Program Manager, BizOps & Strategy, Backend Engineer, Security Analyst, Security Engineer, Data Engineer, Customer Success Manager, and Solutions Architect roles. The page notes that questions like this are often asked at **Amazon** to assess fit with Amazon’s Leadership Principles. ## Member access Membership includes: - 100+ expert answer videos - Access to all courses - Peer-to-peer practice - Private Discord community - Full question database [Upgrade](https://www.aced.io/upgrade?src=questions) · [Upgrade now](https://www.aced.io/upgrade?src=questions) ## Interview experiences Ten shared experiences are listed: - [Microsoft · a month ago](https://www.aced.io/experiences/microsoft-product-manager-intern-interview-afa269) — Intern Product Manager. A quick, personable interview lasted about 25–30 minutes and included information about next steps. - [Justworks · 2 months ago](https://www.aced.io/experiences/justworks-product-manager-interview-bd27e8) — Mid Level / L4 Product Manager. The hiring-manager screen was mainly behavioral and assessed product style and fit. - [Amazon · 5 months ago](https://www.aced.io/experiences/amazon-senior-product-manager-interview-48b127) — Senior / L5 Product Manager. The process matched the described format; the candidate recommended preparing stories that fit the questions. - [Apple · 5 months ago](https://www.aced.io/experiences/apple-software-engineer-interview-4f063d) — Mid Level / L4 Software Engineer. The process included a hiring-manager chat, practical live technical screen, and six-interview onsite. The technical screen involved parsing and filtering JSON and discussing scale; onsite rounds included Go-by-hand coding and AI system design. - [eBay · 5 months ago](https://www.aced.io/experiences/ebay-product-manager-interview-803fed) — Mid Level / L4 Product Manager. The process was structured and straightforward, and the recruiter was informative. - [Sierra AI · 5 months ago](https://www.aced.io/experiences/sierra-ai-bizops-strategy-interview-c2893e) — BizOps & Strategy. The process was good, with friendly, smart interviewers and a straightforward first screen. - [SeeScan · 7 months ago](https://www.aced.io/experiences/see-scan-senior-backend-engineer-interview-0fa208) — Senior / L5 Backend Engineer. Behavioral and technical rounds were friendly and relaxed; the final round was an intense technical deep dive into design patterns and code-quality evaluation. - [Amazon · 9 months ago](https://www.aced.io/experiences/amazon-software-engineer-interview-39a0db) — Mid Level / L4 Software Engineer. The process included an online assessment and three 40-minute interviews. Technical questions were classic problems, while behavioral follow-ups examined detailed work rather than stopping at a polished STAR response. - [Meta · 10 months ago](https://www.aced.io/experiences/meta-facebook-software-engineer-interview-f72c39) — Entry Level / L3 Software Engineer. The final loop had three technical interviews and one behavioral round. Candidates were expected to explain brute force before optimization, defend their approach, and manually trace code because it could not be run. Team matching could take a long time after clearing the loop. - [Microsoft · 3 years ago](https://www.aced.io/experiences/microsoft-technical-program-manager-interview-bf0c74) — Entry Level / L3 Technical Program Manager. The candidate said the interview went well but wished they had asked more clarifying questions. ## Community answers The page lists **53 community answers**. ### Dhruv M. — June 16, 2025 During an internship at Datacore Insights, Dhruv and a teammate disagreed about which KPIs to highlight in a supply-chain-optimization presentation. The teammate wanted delivery time only; Dhruv also wanted inventory turnover and order accuracy. Dhruv first sought to understand the teammate’s reasoning and explained how the broader set aligned with client goals. They each created a mock-up slide and presented the alternatives to a supervisor. They agreed to prioritize delivery time while placing the other two KPIs in a supporting section. The supervisor approved the result, and the client responded positively to the balanced view. [View Dhruv M.’s profile](https://www.aced.io/users/387d2fd6-f147-4a06-9b53-70af2e93139a) · 2,048 karma ### Ross B. — April 15, 2024 Ross frames conflict resolution around **mutual respect, results orientation, and focus on the user**. The example concerns a product-design refresh intended to increase daily retention by **30%** and referral-based acquisition by **20%** over six months. Although user testing looked positive, the deployed design performed worse. Engagement dropped after several minutes, and users reported that the app was slow. Ross believed performance caused the problem; an infrastructure leader believed automated tests showed the app worked correctly. Ross paused the technical dispute to acknowledge the infrastructure leader’s competence and their two years of effective collaboration. They then tested the app as real users would. It became laggy after about **5 minutes**. Users were force-quitting, and the system lost approximately the **30 seconds** before quitting, leaving the worst sessions unmeasured. The blind spot explained lower retention and referrals. Ross’s stated principles are: 1. **Mutual respect:** State respect explicitly and explain why it exists. 2. **Focus on results:** Assess performance against growth objectives rather than arguing abstractly about whether the app is “fast enough.” 3. **User focus:** Treat user experience as essential context because available data is incomplete. [View Ross B.’s profile](https://www.aced.io/users/161dc9c2-c7c4-440f-95eb-722047d0f24c) · Member · 562 karma ### Stephen B. — June 11, 2023 Stephen describes disagreeing with another manager, Alex, about advertising for a restaurant. Alex preferred a cautious approach; Stephen preferred an innovative one. They used active listening, open communication, compromise, and consensus-building to create a hybrid solution. They documented an action plan and established ongoing evaluation and feedback. [View Stephen B.’s profile](https://www.aced.io/users/756e7b4c-48c2-4ee4-94ed-625f556a0b10) · 90 karma ### Tony M. — updated May 15, 2022 Tony selected an experimentation tool that met testing requirements, but teammates preferred another tool because it was more accessible. To gain support, Tony consulted a manager, gathered metrics, forecast future data volume, and explained that the selected tool was stronger on pricing and scalability. Tony reports convincing the team that the alternatives would struggle as the organization grew. [View Tony M.’s profile](https://www.aced.io/users/469afe44-30fe-4f1c-9bc0-c29b53bc618a) · 593 karma ### Madina A. — February 10, 2026 Madina describes disagreement with product managers over a proposed **3x GMV increase for 2024** at a grocery-delivery service. Historical patterns suggested the prior growth rate was maturing and that the target might be too aggressive. Madina aligned the group around ambitious but defensible goals, proposed a formal forecasting exercise, explained risks, listened to product expectations, validated ambition, and involved product managers in reviewing assumptions and model inputs. Madina built a GMV forecast using **Facebook Prophet**, reporting an error rate of approximately **4%**. Multiple scenarios led to realistic but challenging targets, strengthened trust, and resulted in earlier involvement in strategic discussions. [View Madina A.’s profile](https://www.aced.io/users/6a2b44d8-f030-4a77-b7be-449e3c545011) · 102 karma ## Related questions - [Tell me about a time you had a conflict with someone. How did you resolve it and what did you learn?](https://www.aced.io/questions/140/conflict-resolution-learning) - [Tell me about a time you disagreed with a team member.](https://www.aced.io/questions/6521/describe-team-disagreement-experience) - [Tell me about a time you dealt with something unexpected, and how did you respond?](https://www.aced.io/questions/6843/describe-response-unexpected-situation) ## Related courses ### [Product Strategy Questions](https://www.aced.io/courses/product-strategy) We teach approaches for product-strategy interview rounds in the AI era. ![Product Strategy Questions](https://images.ctfassets.net/x78yjrjc11pq/5hHtTyOypgyKA7R3fxMlyl/dde193ecc09baabd8304c3aec25483f2/product_strategy_course_ab4d3cf294.jpeg?w=800&h=800&fm=webp&q=75) ### [Data Engineering Interview Prep](https://www.aced.io/courses/data-engineering) We cover data modeling, pipeline design, SQL, coding, and behavioral interviews through mock interviews, frameworks, and advice from senior candidates for roles at Meta, Google, Amazon, Microsoft, Walmart, DoorDash, and other companies. ![Data Engineering Interview Prep](https://images.ctfassets.net/x78yjrjc11pq/5XoOCgXlGqN2fa1zaroNWd/9a2e23df48a212bc00d352873feb2d6a/Data_Engineer_Interview_Prep_Hero_Image.jpg?w=800&h=800&fm=webp&q=75) ## Practice You can submit an answer to mark the question complete or [Practice with AI](https://www.aced.io/practice/ai/new?type=Behavioral&question=time-disagreed-someone-resolved&src=questions). --- [Read this page’s summary](https://www.aced.io/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fquestions%2F1350%2Ftime-disagreed-someone-resolved&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%2F1350%2Ftime-disagreed-someone-resolved). Opening a form does not execute a tool.