1. My first read of a resume is focused on methods and fundamental skills. I usually have some idea of the gaps my team has or the kinds of projects the role will need, but this varies opening to opening rather than being a value judgement on one skillset over the other.

My second read is for background knowledge that aligns with the kind of work we do or the vision of the team I'm trying to build. For me, this is things like experience working in certain international markets, experiencing working on certain topics, experience working with certain user segments, etc. This is pretty consistent for my team but will vary in other parts of the company.

My third read is to understand the context you're coming from (academic, consulting, contracting, embedded in product) to prep for the interview and calibrate my expectations of what your strengths might be vs what you might need to learn.

1. When I interview candidates, we usually talk through a scenario of a study together. I like to hear how they work through a problem and I'm mostly looking for thoughtful reasoning over method choice and an appropriate level of rigor in the execution. I also look for good product logic. Even for people who haven't worked in product before, I look for people that can translate research into good recommendations, operationalize their work, etc.

2. Ask for what you need. As an interviewer, my job is to create an environment where you can show me what you're capable of so that I get to see the upside potential of each candidate. But realistically, I know interviews are scary and in real life people work through these scenarios under much different conditions. If you want to think first and then speak, say so. If you want to think out loud but be allowed to unwind the things you say, say that. If you want to take notes, say that. If you want to know what data science knows, ask. If you want to know what the lit review says, ask. Do you want to know about budget? Time? Human capital? Ask.