Tell me about a time you disagreed with the priority of an assigned task
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
This question assesses how you handle disagreement when you do not fully control the work, especially when priorities are set by someone else. Interviewers want to see whether you can challenge direction thoughtfully, understand the broader context, and stay constructive even if the final decision is not yours. It is less about whether you were right and more about how you reasoned, communicated, and followed through.
Key Insights
- Disagreement over priority is usually about tradeoffs, not stubbornness. You should show that you tried to understand the other person’s constraints before arguing for your own view.
- A strong answer does not end at 'I raised my concern.' You should show what you did to clarify the impact, propose alternatives, and support the final path once a decision was made.
- Do not pick a trivial example where the stakes were tiny or an example where you simply ignored the assignment. Interviewers are looking for judgment under tension, not reflexive resistance.
What interviewers probe atlevel
Top Priority
At junior level, strong communication means raising concerns respectfully, not making priority disagreements feel personal or oppositional.
Good examples
🟢I raised my concern directly with the person assigning the work and explained it as a question, not a challenge to their authority.
🟢I kept the discussion focused on impact and asked whether there was room to revisit the order of work after we compared the risks.
Bad examples
🔴I told my lead the task did not make sense and that we were wasting time.
🔴I kept debating the priority in the team chat because I wanted everyone to see that I was right.
Weak answers create friction or embarrassment; strong answers show tact, directness, and a focus on solving the problem.
Valuable
Example answers atlevel
Great answers
In my first year, I was assigned a UI cleanup task right before a release, and I thought a data validation bug I had noticed was more urgent. Instead of assuming the cleanup task was a mistake, I asked my lead what was driving it and learned that a customer demo depended on that workflow looking polished and stable that week. I still wanted to make sure the bug was understood, so I checked recent support tickets and found a few cases where users had hit it under a specific condition. I brought that back with a suggestion: I would finish the assigned cleanup, then spend a short block of time adding a guard for the bug if we had room. My lead agreed, and that ended up being the plan. What I think went well is that I raised the concern without treating my lead like they were wrong, and we covered both the immediate commitment and the risk I had noticed.
At my last job, I was helping a small internal tools team, and I was asked to update a report template that the team used every day. I thought it should wait because another request had come in from customer support about a broken export, and I felt like that was more visible to the business. I asked my manager how they were thinking about the two tasks, and she explained that the report was tied to a monthly leadership review happening that afternoon, so it had a hard deadline even though it seemed less urgent to me. Once I understood that, I finished the report first and then helped triage the export issue with support so we could at least tell customers what was happening. That experience taught me to look beyond what seems loudest and ask what deadline or dependency I might be missing. I still speak up when something looks risky, but I try to do it by asking questions and offering options instead of pushing back on the assignment itself.
Poor answers
I was assigned to update some internal tooling, but I thought another bug was more important because it was more interesting and probably affected more people. I told my lead that I really did not think the assigned task should be first, but they wanted me to do it anyway. I went ahead and finished it, and later the other bug still came up, which kind of proved my point. For me, that was a good example of speaking up when a priority does not seem right.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late April, 2026
Tell me about a time you disagreed with the priority of an assigned task
Hello Interview Premium
Your account is free and you can post anonymously if you choose.