Behavioral: aligning engineering, design and other functions on one project

In a product manager interview, you are asked to tell the story of a project you worked on with people from several functions, such as engineering, design, data, marketing or legal. Answer with one real project from your own experience. Explain what the project needed, which functions were involved and what each cared about, what you personally did to keep the group moving in one direction, and how it turned out. ```hint Pick a project with friction Choose a project where the functions wanted different things or worked on different timelines, so the story shows how you brought them together rather than just listing who was in the meetings. ``` ### Clarifying Questions - Should it be a project I led as the product manager, or is one where I was a contributor alongside other functions acceptable? - Are you most interested in how I handled a disagreement between functions, or in how I organized the day-to-day work across them? - Does the project need to have shipped, or is one that was stopped partway acceptable if the collaboration story is strong? ### What a Strong Answer Covers - A project with real stakes in which the functions involved had distinct goals, constraints or incentives - The candidate's specific part in creating a shared goal, clear decision owners and a working rhythm across functions - At least one concrete tension between functions, how it was surfaced and how it was settled, with the trade-off made explicit - An outcome for users or the business, plus a lasting lesson about working across functions - A concise STAR structure that spends most of its time on the candidate's own actions ### Follow-up Questions - Which function was hardest to work with, and what did you do to understand their priorities? - When two functions disagreed and both had a fair point, who made the final call, and how did the side that lost respond? - What would you set up differently at the start of your next cross-functional project?