Handling Someone Taking Credit for Your Work and Juggling Competing Priorities
GoogleSoftware Engineer · OnsiteLast updated
A two-part behavioral interview asking how you would handle a colleague taking credit for your work, and how you manage your time and coordinate with others when juggling several tasks with different priorities. It evaluates conflict resolution, communication and prioritization judgment.
This is a behavioral ("Googlyness") round for a software engineering role. The interviewer asked two questions.
Clarifying Questions
- Should each answer use a real past situation, or is a hypothetical acceptable if this has not happened to me?
- Is the person taking credit a peer, someone more senior, or someone on another team? The right first step differs.
- For the prioritization question, is the interviewer interested in personal time management, coordination with teammates and stakeholders, or both?
Part 1 — Someone takes credit for your work
How would you handle a conflict in which someone else took credit for your work?
What This Part Should Cover
- Checking the facts and the other person's view before escalating
- A private, direct conversation focused on the record and on future attribution, not on blame
- When and how to involve a manager, and how the visibility of your work is protected from then on
- Keeping the working relationship and the team's goals intact
Part 2 — Many tasks with different priorities
When you face several tasks with different priorities, how do you manage your time and coordinate with others day to day?
What This Part Should Cover
- A concrete way of ranking work (impact, urgency, dependencies, deadlines)
- How the ranking is communicated and renegotiated with the manager and stakeholders
- Daily mechanics: planning, protecting focus time, handling interruptions
- What happens when something has to slip
Hints
Hint 1
Separate the facts from the motive: Think about what you would verify, and whom you would talk to first, before assuming the credit was taken on purpose.
Hint 2
Make the trade-offs visible: Think about how the people waiting on you learn that their request is not first, and who decides when two "top priorities" collide.
Follow-up questions
- What if you raised the credit issue privately and the person kept doing it?
- Tell me about a time you had to tell a stakeholder that their request would not be done on time.
- How do you decide when an interruption is worth dropping your planned work for?
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.