- Understand the basics, and then set up mocks
- You need to mock interview early on so you can fuck up and understand where you need the most work
- Doing these out loud is the best way to practice as it's most similar to the way you'll be interviewed in real life
- Practice, Practice Practice
- At the end of the day the interviewers are trying to determine whether you’re able to use frameworks and logic in order to break down complex problems—if you practice these enough you should be able to answer interview questions about anything, not just software applications (ex. “How would you improve airports?”)
- I believe friendliness and willingness to learn goes a long way
- In my opinion, the best PM’s I’ve worked with are open minded and friendly, if you think this describes you, make sure it comes across in your interviews
- Smile, ask how they’re doing, crack a joke, don’t take yourself too seriously. Whether or not they realize it, interviewers are trying to determine two things in the interview: 1) can you do the job and 2) are you the kind of person they’d want to work with.
Interview Basics:
Copy these docs into your own version so you can take notes in them and add areas of opportunity at the bottom—revisit these every time you mock and try to adapt them to what works best for you. These frameworks are a combination of multiple and I adapted them to the point where they worked well for me, but they won’t work well for everyone—feel free to make them your own!
Product Sense Best PracticesExecution Best PracticesLeadership & Drive Best Practices