Tell me about a time when your manager set reasonable demands. Follow up asked for a situation with unreasonable demands.

For reasonable demands: How did you meet or exceed those expectations?

For unreasonable demands: What steps did you take to address the misalignment?

What communication approach did you use in each case?

• What was the impact of fulfilling reasonable expectations?
• How did addressing unreasonable demands affect the working relationship?
• What did you learn about managing expectations?

Sample Answer (Junior / New Grad) Situation: During my first year as a software engineer, I had two very different experiences with quarterly goals. In Q2, my manager asked me to complete two feature implementations and improve our test coverage by 10%. In Q3, they asked me to rebuild an entire microservice architecture, lead a cross-functional project, and mentor three interns—all while maintaining my regular feature work.

Task: For Q2, I was responsible for delivering solid individual contributor work with clear scope. For Q3, the expectation was that I would simultaneously handle senior-level architecture work, leadership responsibilities, and my normal workload. The reasonable demands aligned with my experience level, while the unreasonable ones didn't account for my actual capacity or skillset at that stage.

Action: For the reasonable Q2 goals, I broke down each feature into weekly milestones, communicated progress in our 1:1s, and proactively asked for code review feedback. I finished both features on time and actually hit 12% test coverage improvement. For the unreasonable Q3 demands, I scheduled a dedicated conversation with my manager to walk through the scope. I created a document showing time estimates for each responsibility and explained that the architecture work alone was typically a senior engineer's full quarter. I proposed focusing on one feature and mentoring one intern instead, offering to take on more complex work gradually.

Result: My Q2 work earned positive peer feedback and led to my manager trusting me with slightly more complex projects. For Q3, my manager appreciated my candid analysis and we agreed on a more realistic scope—I successfully delivered one well-architected feature and mentored one intern who later joined our team full-time. This experience taught me the importance of proactive communication and setting boundaries early. I learned that good managers appreciate honest capacity discussions rather than silent struggles or burnout.

Sample Answer (Mid-Level) Situation: As a mid-level product designer, I experienced two contrasting situations with the same manager within six months. First, they asked me to redesign our onboarding flow to improve conversion by 15%, conduct user research with 20 participants, and partner with engineering on implementation—all over an 8-week sprint. Later, they simultaneously assigned me to lead the complete redesign of three major product surfaces, present at an executive review, join a separate team's project as design lead, and continue my existing commitments, expecting everything delivered in the same 8-week timeframe.

Task: The first request was challenging but achievable—it represented a single focused initiative where I owned the design process end-to-end. The second situation spread me across multiple high-stakes projects requiring deep focus and different stakeholder groups. I needed to either figure out how to do the impossible or reset expectations with my manager while maintaining our working relationship.

Action: For the reasonable onboarding project, I created a detailed project plan, scheduled weekly syncs with stakeholders, recruited research participants within the first week, and iterated based on feedback. I delivered the new flow with clear documentation and saw it through implementation, even staying late a few nights before launch. For the unreasonable demands, I requested an urgent 1:1 and came prepared with a priority matrix showing the resource requirements for each project. I explained that each initiative needed focused attention to meet quality standards and proposed we prioritize based on business impact. I suggested bringing in another designer for one project and pushing one timeline by a quarter, presenting data on our team's historical throughput to support my case.

Result: The onboarding redesign increased conversion by 18% and became a case study I presented at our design all-hands. For the unreasonable situation, my manager initially pushed back, but after I involved our design director for perspective, they agreed to adjust. We postponed one project, and I successfully led the other two initiatives to completion with much higher quality outcomes. The executive presentation went well and led to $2M in additional design budget. I learned that even reasonable managers can lose sight of realistic capacity during high-pressure periods, and that advocating for sustainable workloads actually leads to better results than attempting the impossible.

Sample Answer (Senior) Situation: As a senior engineering manager leading a team of 12, I had two distinct experiences with my director's expectations. In the first half of the year, they asked me to improve our team's delivery velocity by 20%, reduce incident rate by half, and develop two engineers into tech leads—ambitious but grounded in our team's capabilities and historical performance. Six months later, following a reorganization, they expected my team to simultaneously own three critical product launches across different business units, absorb five engineers from a dissolved team without onboarding time, maintain our existing 99.9% uptime SLA, and continue all professional development initiatives, all within a single quarter during a hiring freeze.

Task: The initial expectations challenged me to level up our team's operational excellence and leadership pipeline, which fit my role as a senior manager building a high-performing team. The later demands required me to essentially triple our output while integrating new team members and maintaining quality, without additional resources or timeline flexibility. I needed to protect my team from burnout while delivering maximum business value and maintaining my relationship with my director.

Action: For the reasonable goals, I implemented a metrics-driven approach: established weekly velocity tracking, conducted retrospectives to identify process bottlenecks, created a tech lead development program with my two high-potential engineers, and paired them with staff engineers for mentorship. I ran monthly check-ins with my director to show progress and adjust tactics. When faced with the unreasonable demands, I prepared a comprehensive analysis including team capacity models, risk assessments for each launch, and onboarding timelines based on our historical data. I scheduled a meeting with my director and their skip-level, presented three scenarios with trade-offs clearly outlined, and recommended we fully commit to two launches while transitioning the third to another team. I was firm but solutions-oriented, emphasizing that this approach would better serve the company's goals.

Result: Under the reasonable expectations, we increased velocity by 24%, reduced incidents by 55%, and both engineers successfully transitioned to tech lead roles, later becoming core contributors to major initiatives. Regarding the unreasonable situation, after seeing my data-driven analysis, leadership agreed to redistribute the workload. My team successfully delivered two launches that generated $8M in first-quarter revenue, and the absorbed engineers were properly onboarded over six weeks rather than thrown into crisis mode. One difficult outcome was that my relationship with my director became strained temporarily, but my skip-level appreciated my strategic thinking and protective leadership. Within two quarters, my director acknowledged that my pushback had prevented what would have been a disastrous quarter. This reinforced my belief that senior leaders must sometimes absorb organizational pressure to create sustainable outcomes, even when it creates short-term friction.

Sample Answer (Staff+) Situation: As a Staff Product Manager leading platform strategy, I navigated two very different expectation-setting experiences with our VP of Product. In the first scenario, they challenged me to define a three-year platform vision, align five cross-functional teams around shared technical investments, and demonstrate a path to $50M in enabled revenue—a substantial but achievable mandate given the organizational readiness and my scope. A year later, following an executive mandate to accelerate AI adoption, they expected me to simultaneously drive enterprise AI platform adoption across 12 business units, re-architect our data infrastructure, build consensus among VPs with competing priorities, deliver a board-ready strategy in six weeks, and maintain my existing platform commitments, all while navigating a 20% budget cut and unclear executive alignment.

Task: The first challenge aligned with my staff-level mandate to drive cross-organizational strategy and required me to leverage my influence and technical judgment to create transformational impact. The second situation asked me to solve a board-level strategic problem with executive-level authority but without executive resources, timeline, or political capital. I needed to either deliver impossible results or recalibrate expectations at the VP and C-suite level while maintaining my credibility as a strategic leader who delivers under pressure.

Action:

Common Mistakes

• Only presenting one perspective -- This question asks for contrast, so shortchanging either the reasonable or unreasonable situation weakens your answer
• Making it personal -- Focus on the mismatch between expectations and reality rather than criticizing your manager's character or competence
• Accepting unreasonable demands silently -- Interviewers want to see that you can professionally advocate for realistic scope and protect team capacity
• Being defensive or entitled -- Frame your response around impact and feasibility, not personal convenience or effort level
• No learning or growth -- Show how these contrasting experiences improved your judgment about managing expectations going forward

Result: Under the reasonable expectations, we increased velocity by 24%, reduced incidents by 55%, and both engineers successfully transitioned to tech lead roles, later becoming core contributors to major initiatives. Regarding the unreasonable situation, after seeing my data-driven analysis, leadership agreed to redistribute the workload. My team successfully delivered two launches that generated $8M in first-quarter revenue, and the absorbed engineers were properly onboarded over six weeks rather than thrown into crisis mode. One difficult outcome was that my relationship with my director became strained temporarily, but my skip-level appreciated my strategic thinking and protective leadership. Within two quarters, my director acknowledged that my pushback had prevented what would have been a disastrous quarter. This reinforced my belief that senior leaders must sometimes absorb organizational pressure to create sustainable outcomes, even when it creates short-term friction.