Behavioral: the technical work you personally did on a project and what it changed

Pick a project you worked on and walk me through your technical contributions to it. What exactly did you do, and what changed because of it? ```hint Separate your part Before you answer, sort out which pieces of the work were yours, which were your teammates', and what would have gone differently without you. ``` ### Clarifying Questions - Does a technical contribution have to be code, or do design reviews, data analysis and API or data-contract decisions count? - Should I go deep on one contribution, or walk through several from the same project? - Can the example come from an earlier engineering role, or should it be from product work? ### What a Strong Answer Covers - A contribution with real technical substance, explained at a depth the interviewer can probe - Clear ownership: what the candidate did personally versus what teammates did - How the candidate worked with others on the technical choices: raising concerns, weighing options, reaching agreement - A concrete effect on the product, the system or the team, measured where possible - The link from the technical work to what it meant for users or the business ### Follow-up Questions - Which alternative did others on the team favor, and why did your approach win or lose? - What would the project look like today without your contribution? - Tell me about a time your technical opinion turned out to be wrong. How did you find out?