Tell me about a time a colleague took credit for your work.
answer
- name the work and your exact share
- the moment credit went elsewhere
- check the record before assuming intent
- one private, low-heat conversation first
- record corrected, relationship kept
basics
~10 sTests whether you can defend your contribution without starting a feud. Answer with one concrete instance, facts checked before motive assumed, a private correction first, and a working relationship that survived it.
how to answer
6 beats- the work and your specific share of itName the piece of work in one or two sentences and be precise about which parts were yours. Keep this beat and the setup together to roughly a fifth of your airtime; the interviewer does not need the architecture, only enough to judge the claim.
- the moment you found the credit had gone elsewhereGive the specific moment: a readout, a summary, a demo, a promotion packet. State it flatly and without adjectives about the other person, because the restraint here is itself part of the signal.
- what you checked before you reactedSay what you looked at and what it showed, including any part of the work that was genuinely shared. Conceding the shared edge makes everything you claim afterwards more believable, not less.
- the conversation you had with them firstQuote roughly what you said. The strongest version is short, private, non-accusatory and asks for something specific rather than an apology, such as presenting your own work next time.
- how the record actually got correctedThis beat and the previous one should carry the bulk of your airtime, around sixty percent together. Describe the mechanism, not the feeling: a contributors line, a written summary, a re-run demo, a name added to a change log.
- result, the relationship, and what you kept doingClose in the last fifth with what changed and where the relationship landed, then the habit you kept so the same ambiguity does not recur. End on the habit rather than on vindication.
your answer
5 story prompts- Pick work you can prove was yours: a document history, a ticket trail, a commit, a design review.
- Choose an instance where you actually spoke to the person, not one you only resented quietly.
- Have one number ready for what the work achieved, not just proof that you did it.
- Be honest about any part that was genuinely shared and say so in the story.
- This can be the same story as your feedback-conversation answer, re-angled onto attribution.
draft and rehearse your own answer in a learn session
go deeper
The axis is conflict resolution under a personal grievance: whether you can separate the record from the resentment. Interviewers watch for facts checked before motive is assigned, a direct and private raise rather than an escalation, and evidence instead of accusation. A strong answer proves you can defend your contribution without turning a team into a scoreboard.
I was about six months into my first role at an infrastructure consultancy, embedded with a client's platform team. Their storage cluster paged constantly and nobody trusted the alerts any more, so I spent a couple of sprints re-scoping one alert and writing a runbook for it. Mean time to restore for that alert class dropped from 47 minutes to 16 over the following month. At the fortnightly client readout, a consultant on our side walked the client through the change and answered every question as though he had written it. My name never came up. I was annoyed, so before I said anything I went and looked: the document history showed I had written it, but he had reviewed it and suggested one of the thresholds. Mostly mine, not entirely. I asked him for ten minutes the next morning. I did not accuse him of anything. I said the runbook was the first thing I had owned end to end, that I wanted to present my own work, and asked whether he had meant to leave me out. He said he had been driving the deck and had not thought about it. At the next readout he introduced me and I talked the client through the alert work myself. That is still how the account runs. He and I stayed on good terms, and he put me on the failover work a quarter later, which I do not think I would have got if I had gone around him.
The signal sits in the checking beat: the record gets verified before motive is assigned, and the shared edge is conceded out loud. The private, specific ask carries the resolution. Assigning him a motive, or going to a manager first, would downlevel this instantly.
I was technical lead on an engagement where two client squads shared one on-call rota that neither of them really owned. I redesigned the routing: ownership tags per service, a single escalation path, and a change log the client could read. Database failover restore time came down from 38 minutes to 14 across three release cycles. The steering readout that quarter had a slide crediting all of it to one of their managers, who had chaired the meetings and written none of it. Two of my engineers had done most of the tagging work, and they noticed before I did, which was the part that actually mattered to me. I did not raise it in the room. Afterwards I sent him the change log and asked whether we could add a contributors line to the readout template, framed as something my engineers needed for their own performance reviews rather than as a correction of his slide. He agreed, and opened the next readout by naming both of them. I also started sending a short written summary after each milestone with names attached, to his director and to mine, so the record existed before anyone had to argue about it. He stayed a good partner for the rest of the engagement. The attribution line is still in that template, and I care about that more than the slide, because it means my people get credited when I am not in the room.
Middle-scope signal: the credit being protected belongs to the team, and the fix is a change to how the record is kept rather than a one-off correction. Framing the ask around performance reviews lets the other side agree without losing face. Calling him a credit thief would downlevel it.
Own-task scope is fine: one piece of work you did, one correction you made. What is being scored is that you checked the record before assigning motive and spoke to the person before anyone else heard about it.
Expect feature and peer scope. Show the mechanics: which artefact proved the contribution, how you asked for the record to be fixed, and how you kept crediting the people who genuinely helped while correcting the account of your own part.
You are judged on team scope and prevention. Talk about protecting your engineers' credit rather than only your own, and about the attribution habit you left behind: who presents what, where contributions get written down.
Scope is organisational and about incentives. Show a repeatable mechanism for how work gets attributed in readouts, reviews and promotion cases across teams, and be ready to describe a time you gave credit away on purpose to buy trust.
saying these in an interview costs you the question
- Relitigating who was right instead of what changed afterwards
- Escalating to a manager before any direct conversation happened
- Painting the colleague as a glory hunter or a credit thief
- No artefact or record backing your claim beyond your own say-so
- Silent resentment presented as being the bigger person
- Claiming shared work as entirely yours while complaining about exactly that
- Did you take it to your manager?Say what you actually did, and show the ordering rather than defending it. Direct conversation first, manager second, and normally only when the pattern repeats or the person disputes the record. If you did escalate, describe what you brought with you: the artefact trail and what you wanted to happen next, not how it made you feel. If you did not escalate, say what would have made you.
- What if they had flatly denied it?Do not promise a confrontation you have never had. The honest answer is that you stop arguing about intent, because that is unwinnable, and move to the record: ask for the written artefact or the contributors line to reflect who did what. If it still does not change, you raise a pattern with your manager rather than a single incident, and you make your own work legible going forward.
- How is that working relationship now?Interviewers ask this to see whether you left wreckage. A good answer is unglamorous: you still work together, or you parted on neutral terms. Give one small piece of evidence rather than an assertion, such as a later piece of work you did together. Do not use the follow-up to reopen the case or add a fresh grievance you left out the first time.
- How do you make your contributions visible now without self-promoting?Talk about habits, not about marketing yourself. Written summaries with names attached, contributors lines in shared documents, demoing your own work rather than having it demoed for you, and crediting other people generously enough that credit-giving is normal on your team. One or two concrete practices beats a philosophy of personal branding.
## What is actually being measured This prompt is a trap dressed as sympathy. The interviewer sounds like they are inviting you to complain, and a surprising number of candidates accept the invitation. What is actually being measured is whether you can hold two things at once: a **legitimate interest in your own record**, and a **working relationship** you did not burn to protect it. ## Common wordings The same family shows up as: - *tell me about a time someone took credit for your work* - *how do you handle it when your contribution is not recognised* - *tell me about a time you did not get credit you deserved* - and the softer *how do you make sure your work is visible?* Treat them as one story with different entry points. The last variant lets you skip the grievance entirely and lead with the habit, which is often the stronger opening if your story is thin. ## Weak versus strong The **weak answer** spends its airtime establishing that the work was yours and that the other person was dishonest. It has no verification beat, no direct conversation, and its result is either silent suffering or a manager riding in. The **strong answer** does something the weak one never does: it checks. It says what the document history or ticket trail actually showed, and it usually concedes a shared edge, because real collaborations rarely have clean boundaries. That concession is what makes the rest of the answer credible. From there the strong answer: - has one low-heat conversation, - asks for something small and specific, - and reports a result about the record rather than a verdict about the person. ## Evidence types that carry weight In descending order: 1. an artefact with your name on it and a timestamp; 2. a person who can corroborate; 3. a public correction that actually happened; 4. and, weakest, your recollection. Notice that the first three exist only if you built them before you needed them, which is why the **visibility habit** belongs in your answer as a consequence, not as a slogan. ## How the bar moves - **Early in a career** this is entirely about self-management: did you react to the story in your head or to the record in front of you. - **In the middle band**, interviewers want the mechanics of the fix and evidence that you were as careful with other people's credit as with your own. - **At senior level** the question quietly changes subject: the credit at stake is usually your team's, and the answer that lands is one where you noticed on their behalf and changed how attribution gets recorded on your surface. - **At principal level** it becomes incentive design, and the most convincing material is a case where you deliberately let credit go somewhere else because the trust was worth more than the line item. ## Two failure modes worth naming 1. The first is the **scoreboard**: an answer that reads as though you track contribution ratios. 2. The second is the **martyr**: 'I let it go, the work speaks for itself.' Both fail for the same reason. Neither one shows you saying the hard, small sentence to the person's face, which is the only part of the story the interviewer cannot get anywhere else.