You know your project. Then someone asks, “What did you personally change?” and your answer turns into a tour of the tech stack.
Try preparing one episode instead of the whole repository.
Write down the original problem, the decision you made, and the evidence you can actually show. A bug report, a test or a before-and-after trace can explain more than “I improved performance.” If you did not measure the result, say what you verified instead.
Here is a fictional example: “The search page showed stale results when responses arrived out of order. I cancelled the previous request and added a test that resolves the second request first.” You can explain the mechanism, your contribution and the check without inventing a percentage.
Now practise the follow-up: why this approach, which alternative did you reject, and what would you change with more time? Record a two-minute answer. Listen for the point where you switch from your actions to vague team language.
Disclosure: This article was prepared with AI assistance and reviewed against the linked sources and implementation. Examples explicitly marked fictional are illustrative.
Top comments (0)