Explaining Your Coding Skills and Technical Depth in a Product Manager Interview

You are interviewing for a product manager role, and the interviewer asks whether you know how to code. How do you answer? ```hint Answer the question behind the question A plain yes or no tells the interviewer very little. Think about what this team needs its product manager to do technically, and which evidence from your own work would show you can do it. ``` ### Clarifying Questions - Is the product manager in this role expected to write code, or to work closely with engineers on technical decisions such as integrations and data? - Does writing SQL or scripts for my own analysis count, or are you asking about building production software? - Would you like a quick summary of my technical background, or an example of a time I used it? ### What a Strong Answer Covers - A direct, honest statement of the candidate's actual coding level, neither inflated nor apologetic - Concrete evidence such as languages, tools and projects, and what the candidate personally built or analyzed - How the skill makes the candidate more effective in this product role, tied to the kind of product the team builds - Awareness of the limits: respecting engineering ownership and knowing when not to dive into implementation ### Follow-up Questions - Tell me about a time your technical understanding changed a product decision or a scope estimate. - How would you handle an engineering estimate that you believe is too high? - If you have never worked with a system like ours, how would you get up to speed on it?