A practice prompt we wrote. No company or candidate report names it, so it carries no company tag.
How to answer
The question has two halves, and the second is where the answer is won. The outcome has to be the customer’s, measured the way they measure it. An April 2019 Palantir blog post says its Deltas, engineers on a team supporting one customer, measure success by impact on the customer’s goal. Source 1Dev versus Delta: Demystifying engineering roles at PalantirPublisherPalantir BlogSource typecompany blog
- Pick the outcome by what changed for the customer, not by what you built. A modest result whose cause you can point to beats a flagship launch where your part is a blur.
- State the outcome in one sentence, in the customer’s unit (hours, money, errors), and say who measured it.
- Draw the line out loud. Credit the others by role and by what each did (“the data engineer built the ingestion; their ops lead ran the rollout”), then one or two contributions of your own, at least one a call you made, not only code you wrote: the problem you reframed, the scope you cut, the person at the customer you got to say yes. For example: “The team shipped the new dispatch board. What was mine: I sat with the dispatchers through a shift, saw they re-keyed every change by hand, and argued to cut the mobile app from the first release so we fixed that first.”
- Link your part to the result. For each contribution, what would have shipped, or failed, without it: the metric moved when your piece went live, or the rollout could not start until it existed.
- Say why this one, tied to the customer, not the stack. Have ready the part you would do differently; the interviewer will ask.
The trap is pride in the wrong thing. “I’m proudest of the architecture” answers a different question, and “it was a real team effort” leaves nothing to credit to you. The ownership audit lesson shows how to sort your calls beforehand.
Follow-ups
What the interviewer may ask next, once your first answer is on the table.
- Who measured that result, and would the customer describe it the same way you just did?
- Take your part out. What would the outcome have been without it?
- Which part of that project are you least proud of?
Where answers go wrong
- Tells the team’s success in “we” from start to finish, so the “specifically you” half of the question goes unanswered.
- Picks the most impressive technology instead of the result the customer felt, so the outcome has no number and no customer in it.
- Claims the whole outcome. The follow-up that asks what would have happened without their part takes the claim apart.
Answer this in two minutes
Write the answer you would say out loud. The clock starts with your first word.
Illustrative answer about a fictional project
The outcome I’m proudest of is from a freight brokerage we deployed our document-processing platform to. The time from delivery to paying the carrier fell from 19 days to six, measured by their controller over the first full quarter, against the quarter before.