Handling Someone Taking Credit for Your Work and Juggling Competing Priorities

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? ```hint 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. ``` #### 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? ```hint 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. ``` #### 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 ### What a Strong Answer Covers - A real, specific example for each part in STAR form, with the candidate's own actions clear - Mature conflict handling that assumes good intent first but does not stay silent - Proactive communication rather than heroics or silent overtime - A result and a lesson, including what the candidate would do differently ### 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?