Back to the scheduled program of UX Interview Series. In the last episode, you get a sense of the work dynamic between UX and P.M. We should give you some clues on what might go into an interview with P.M. And that is what we're going to look at today. What you can expect from that interview round. What product intuition or management questions can come up. How can you prepare yourself to fluently answer all those product questions? So, grab your favorite drink, which I don't seem to have one with me. And let's get into here. Good morning, everyone. My name is Justinian, a designer working in Silicon Valley. Just to set up expectations and some context, not every UX on-site interview we have around with the P.M. It really depends on the company. I have interviewed these companies that I've got around with product managers. But these companies, I did it. One pattern that I found is that if the rose called product designers is very likely you're going to have a 45-minute interview round with a product manager. If it's a more design driven company or a company does not have a super metric driven company culture, they might not have one round with the P.M. So, if you made it to the on-site, it's what product designer wrote, it's a magic driven company, and you watched my last video. Congratulations, you'll be ready for the new information. Here is the list of 15 P.M. interview questions. These are the questions that I know of that I personally got asked, or I think they are just worth being included. And now let's go over them one by one. Well, first one, what are some design problems that you identify on other apps, other mobile apps, web apps, and what is your approach to solve them? It's more like a live exercise. You just walk through which you have in mind. You can solve what's prepared for it, but there's no guarantee you're going to get this question. Next, how do you measure product success? It's a very classic question. As you remember from my last video, product managers care about metric and money. So, title is in. That's your answer. Next, how do you balance business needs with usually needs? So, in the design world, we have advocating for the users. And in the P.M. world, they are advocating for the business, for the metrics, for the money. So, how do we find that? Finds a bad word to use. How do we balance that? Business needs versus users need. We have solved the user's problem. You should help the business. If the scale is tip-to-heavy on one side, then we have to balance it. Next, how do you use qualitative and quantitative data on metrics to inform your decisions? Again, P.M.s are very qualitative, designers qualitative. So, balance it. Use both to make your design decisions, make your choices. Next, before product is shipped, how do you from an hypothesis of what's working and what's not working? So, before you launch the product, before you ship the product, you actually have no idea how it's going to turn out. You can make some assumptions, you can format hypothesis. So, what is hypothesis based on physics, based on user data, user pattern, pass history, how other apps perform, and what's your projection of the outcome? It's going to increase the revenue producer by 20 bucks. Why 20 bucks? What's your projection? How do you form your hypothesis? And you're likely to get a follow-up question of how do you validate the hypothesis that you have? There are many ways to validate it. One is to just, you know, prototype and test. And second, Ashun is spoiled too much. Let's move on. How did you collaborate with P.M.s at different stages in a product development cycle? So, I've got asked before, this is a really classic one. That basically, what we do a day working with P.M. in your company. If you haven't worked before, that should be pretty straightforward. Just describe how you work with P.M. You do this, they do that, and you go back and forth, you communicate, you collaborate, and you shouldn't design to give you feedback, and then you challenge their assumptions. You see what I'm going right? The next question, which is a little bit more detailed, when you collaborate with different stakeholders, mostly P.M. that they are looking for. How do you decide when to use low fidelity or high fidelity design? And this should be also straightforward. It depends on the stages. And you should know when to use low fidelity, walk-up, wire-free prototype, to a very interactive, realistic prototype, or even almost like production-media prototype. Next, can you tell me a challenging project that I have worked on in the past, and how you worked with P.M. to resolve it? This is a really classic one. I think this is important to understand, and it would be great, and actually straightforward, if you have had this experience before. You have worked with P.M. before, and of course, there's no way that it's 100% smooth. There are always some hiccups here and there. Very exciting stuff. So how do you resolve it? Did you ask for other people's opinion? Did you just talk through it? Did you just prototype more and demo them? Or you find new data or you do testing? There are many ways to resolve it. You just walk through your past experience, but then you should be straightforward. It would be more challenging if you are new grad, and you had no experience with P.M. Then watch my previous video. Next, what's the difference between a design problem and a product problem? This, I think, is important to know, because design problem solves the user's issue, or maybe it just solves a UI issue, in a way that translates into product to business needs. So that's why you need to understand the difference between both, and then locate it from both perspective and make your trade-off strike your balance. Next, imagine you're P.M. And I am a designer, pick a project and walk me through how we will work together. So you're really putting yourself into the shoes of a P.M. This is more or less a live exercise, not really design exercise, but more like a product management exercise. You do on the fly. If you do it well, that means you understand the role of a P.M. That means you basically have no problem with this round. Next, if Uber is free in San Francisco, only San Francisco area, how can Uber generate revenue? Right, because if it's free, then who's going to pay for Uber's operation? If users are not paid for it, we are taking Uber for free. Who is paid for it? It's really picking up your brain how? This is product thinking, product intuition. Next, if you believe your design choice is right, how do you influence P.M. to believe in your idea? Basically, you're just asking, how do you influence how to stay hold this, how do you convince them? The main strategy is tech takes and techniques to go about this. I actually mentioned it five in my previous video. Check them out if you like, kind of corner, just go down below. Next, what is your ideal collaboration between P.M. and design? Again, this should also be easy if you have worked with P.M. before. Since you have worked with them, you know what is it like? You know what could have been changed. You have your ideal, relationship with them. Maybe it's more supportive. Maybe you wanted to challenge you even more. Maybe you want to trust each other more. Whatever that is, and when you have to take on this, you can elaborate on this easy question. Last one, the 15th question. If you have two months to work on a project, where is your timeline like? And who will you live in to work on it? After you answer that, the second part is, what if you only have two weeks for it? Where is your timeline like? Who will you collaborate with? Two months versus two weeks. Same project. How do you do them? How do you approach them? I think it'll be the same. How is it going to be different? How same? How different? Yeah, I got this question before. Those are my 15. I need one more hand actually. P.M. questions. And of course, there's always more to expand to add to the list. If you want a copy of this worksheet, you know the trail, comment down below, email me, and then I'll send you one. Even though I just gave you 15 questions, when you actually get into a 45 minute interview with a P.M., more or less, you're not going to get more than 10 questions. Elaboration, you know, takes time. And in the end, you might not even get more than five questions. Think about it. You have your intro. They have their intro. They have a set of questions. They also have to leave time for you to answer questions. And they want to ask as many questions and get as many detailed answers as possible. So if you think about it, there's not that much time in the session. And hence, there are not that many questions. So don't panic about, you're going to have to answer 15 questions in a 45 minute session. Well, now let's switch perspective. After grilling you with all those questions, the P.M. who's interviewing you, she get a sense of the 405 things. Number one, we let the candidate be able to work efficiently and effectively in a product organization set up. So I think this candidate just can really work with P.M. really well in this set up. Just number two, can you see both the big picture and small critical details? Number three, do they understand leveraging the strength and weaknesses of the platforms that they're designing for? Number four, do they stand strong on their opinions or simply just agree with P.M. If they stand strong, how did they try to influence others? Lastly, can I work with this person? Would I enjoy working with them? Can I learn anything from them? If you can answer all the questions from the P.M. thoughtfully and thoroughly, very likely you're going to get a yes for all those five areas. If you get those yeses, it's very likely the P.M. is going to vote for you in the hiring debrief. Then you should come back to this video, leave a comment and accept it. That's why in conclusively some questions that you might get asked in an on-site interview with your product manager. For you to better understand how to work with product managers and engineers and answer those collaboration questions with concrete examples, I have used my best design thinking and craftsmanship skills to capture those these videos for you. Check them out right there. Like and subscribe to support the channel. Keep designing a better future. See you on the next video. Cheers!