How would you handle a teammate taking all the credit for a team project during a presentation everyone contributed to?

Who else did you involve, if anyone?

• How was the situation resolved?
• What was the impact on team dynamics?
• What did you learn about handling attribution issues?

Sample Answer (Junior / New Grad) Situation: During my internship at a fintech startup, our team of three interns spent six weeks building a customer onboarding dashboard. One of my teammates presented our work at the end-of-summer showcase and repeatedly used "I" instead of "we" when describing features I had primarily built, including the data visualization components that took me two weeks to develop.

Task: I had been responsible for the entire frontend data visualization layer and had collaborated closely with another intern on the API integration. I needed to ensure that my contributions were recognized by the team leads and executives in attendance, as this presentation would influence internship return offers and my professional reputation.

Action: After the presentation, I privately approached my teammate in a conference room and calmly explained that I noticed the language used made it sound like a solo project. I shared specific examples of where "we" would have been more accurate and explained how it made me feel. I also sent a follow-up email to our manager thanking the whole team and clearly outlining each person's contributions to the project. Additionally, I scheduled a brief one-on-one with my manager to discuss my specific work on the visualization components.

Result: My teammate apologized and admitted they were nervous during the presentation and hadn't realized how their word choice came across. They sent a message to the leadership team clarifying that it was a collaborative effort and highlighting my visualization work specifically. My manager appreciated my professional approach and made sure my contributions were noted in my final evaluation. I learned the importance of documenting contributions throughout a project and speaking up constructively when credit isn't fairly distributed.

Sample Answer (Mid-Level) Situation: As a software engineer at a mid-sized SaaS company, I led the technical implementation of a new payment processing system that reduced transaction failures by 40%. The project involved collaboration between engineering, product, and finance teams over four months. During our quarterly all-hands meeting, the product manager presented the success as their individual achievement, barely mentioning the engineering team's role and not acknowledging me or my two engineers by name despite us building the entire technical solution.

Task: I had architected the system, written the majority of the critical code, and mentored two junior engineers through their first major project. Beyond my own recognition, I felt responsible for ensuring my team members received proper credit for their growth and contributions, as this visibility was important for their career development and upcoming performance reviews.

Action: I scheduled a meeting with the product manager within 24 hours and brought specific examples of the presentation language that misrepresented the effort. I explained that while I appreciated their excitement about the results, the lack of team recognition was demotivating and inaccurate. I proposed that we co-present a technical deep-dive at the next engineering all-hands. I also documented each team member's contributions in our project retrospective and shared it with engineering leadership. Finally, I brought up the concern in my one-on-one with my engineering manager, focusing on establishing better norms for cross-functional credit.

Result: The product manager acknowledged they had gotten caught up in the excitement and agreed to the joint presentation, which successfully highlighted the engineering work. They also sent a company-wide Slack message crediting the engineering team by name. My manager worked with the product organization to create clearer guidelines about attribution in cross-functional presentations. Both junior engineers received strong performance reviews with explicit mentions of this project. I learned to proactively establish credit-sharing norms at the start of cross-functional projects rather than waiting for issues to arise.

Sample Answer (Senior) Situation: As a senior engineering manager at a healthcare technology company, my team of eight engineers spent nine months building a HIPAA-compliant data pipeline that enabled real-time patient monitoring across our platform. The initiative was highly visible to executives and board members. During a board presentation, the VP of Product presented the capability as primarily a product innovation, minimizing the complex engineering challenges we had solved and not mentioning my team's work or the technical leadership I provided in navigating regulatory requirements and architectural decisions.

Task: I was responsible not only for ensuring my own contributions were recognized but also for advocating for my team's visibility at the executive level, which directly impacted their career trajectories and our ability to attract top engineering talent. Additionally, I needed to address a pattern I had noticed of engineering contributions being downplayed in executive communications, which was affecting morale across the engineering organization.

Action: I first gathered data by reviewing the past six months of executive presentations and documenting similar patterns. I then scheduled a private conversation with the VP of Product, approaching it as a partnership opportunity rather than a confrontation. I shared specific feedback about the board presentation and explained the broader impact on engineering morale and retention. I proposed we create a shared slide deck template for cross-functional initiatives that explicitly included contribution sections. I also worked with the CTO to present the technical achievement at the next board meeting, bringing two of my senior engineers to share their work directly. Finally, I established a monthly "engineering wins" communication that went to all executives, ensuring consistent visibility for technical achievements.

Result: The VP of Product became a strong ally and we co-created attribution guidelines that were adopted company-wide for executive presentations. My team's work was properly recognized in subsequent board materials, and the CTO cited our project as a model for engineering excellence. Engineering retention improved by 15% over the following year, and in anonymous surveys, engineers specifically mentioned feeling more valued by product leadership. Three team members were promoted within the next cycle, with board-level visibility of their work cited as a factor. I learned that addressing credit issues requires both immediate resolution and systemic change to prevent recurrence, and that approaching these conversations as opportunities for improved collaboration rather than blame leads to more sustainable outcomes.

Sample Answer (Staff+) Situation: As a Staff Engineer at a large cloud infrastructure company, I led a cross-organizational initiative spanning 12 teams to redesign our global load balancing system, which reduced latency by 35% and saved $8M annually in infrastructure costs. The 18-month effort involved complex technical tradeoffs, extensive consensus building, and significant architectural innovation. At our annual engineering conference, a director from another organization presented the work as their team's achievement in a keynote speech, omitting the broader collaboration and specifically not mentioning the core architectural framework I had designed and evangelized across the organization.

Task: Beyond personal recognition, I needed to address a systemic issue where distributed, cross-functional technical leadership was being misattributed to individual teams or leaders, which was undermining the collaborative culture we were trying to build at scale. I also had a responsibility to the dozens of engineers across multiple organizations who had contributed to this effort to ensure their work was visible to senior leadership, as this project was meant to serve as a model for future cross-org initiatives.

Action: I approached this at multiple levels simultaneously. First, I had a direct conversation with the director who gave the presentation, seeking to understand their perspective before sharing mine. I learned they were under pressure to demonstrate their org's impact and hadn't fully understood the cross-org nature of the project. Rather than escalating, I proposed we co-author a detailed technical blog post and co-present at the next conference, highlighting the collaborative model. I then worked with my VP and the CTO to establish an "Architecture Excellence" award program that specifically recognized cross-organizational technical leadership and contribution. I created a detailed project retrospective document that mapped contributions across all teams and shared it with senior leadership, turning it into a case study for effective cross-org collaboration. Finally, I initiated a working group of Staff+ engineers to develop guidelines for attribution in large-scale technical initiatives.

Result:

Common Mistakes

• Being passive-aggressive -- Address the issue directly and professionally rather than complaining to others or making subtle comments
• Focusing only on yourself -- Advocate for the entire team's contributions, not just your own recognition
• Waiting too long -- Address credit issues promptly before the narrative becomes established as fact
• No concrete evidence -- Be prepared with specific examples of contributions and misrepresentations rather than speaking in generalities
• Making it personal -- Frame the conversation around accurate representation and team morale rather than attacking someone's character
• Skipping the direct conversation -- Always talk to the person involved before escalating to management
• Not proposing solutions -- Come with ideas for how to correct the record and prevent future issues

Result: The VP of Product became a strong ally and we co-created attribution guidelines that were adopted company-wide for executive presentations. My team's work was properly recognized in subsequent board materials, and the CTO cited our project as a model for engineering excellence. Engineering retention improved by 15% over the following year, and in anonymous surveys, engineers specifically mentioned feeling more valued by product leadership. Three team members were promoted within the next cycle, with board-level visibility of their work cited as a factor. I learned that addressing credit issues requires both immediate resolution and systemic change to prevent recurrence, and that approaching these conversations as opportunities for improved collaboration rather than blame leads to more sustainable outcomes.