Scoring product sense

megaphone

Extra info from Amichay (Monday.com)

בראיונות שאני מוביל ב יש המון דגש על פוקוס ותעדוף. לדוגמא, כשמאפיינים בראיון מוצר אני לא רוצה שהמועמד/ת ״Will list success metrics״ אני רוצה שהם גם יקבעו ​kpi ראשי ​ שבאמת ישקף לי האם משתמשים מקבלים ערך מהמוצר. כנ״ל יוז קייסים (באיזה אחד תתחיל? למה?) כנ״ל פיצ׳רים (מה נכנס לגרסה הראשונה ומה לא? למה?) בעיני זה ההבדל בין מועמדים עם אינטואיציה טובה, ובין כאלו שהשתפשפו עם תעדופים וקבלת החלטות כל יום. דבר שני שאני שם עליו דגש זה שאלות אנליטיקס ותעדוף. בראיונות במנדיי אנחנו בודקים שהמועמדים יודעים לקרוא גרפים, שהם יודעים לתרגם שאלה רכה לשאלה דאטאית קונרקרטית. שהם יודעים להעלות היפוטזה ואז להפריך או לאשש אותה באמצעות דאטא. זה מאוד קשה, ויש מנהלי/ות מוצר עם ניסיון מרשים שלצערי נופלים בשלב הזה, אבל הבדיקה הזו קריטית כי ככה אנחנו באמת מקבלים החלטות ביומיום. הטיפ האחרון שלי למי שמתכוננים לראיונות זה לקרוא את Cracking the PM Interview של (שבעברה היתה head of product ב Asana). עוד לא פגשתי מישהו שמחפש משרת פרודקט שסיים את הספר ולא נפלו לו עשרה אסימונים בראש.

Machine translation

In the interviews I lead at monday.com, there is a lot of emphasis on focus and prioritisation. For example, when describing a product in an interview, I don't want the candidate to "list success metrics". I want them to also determine key KPIs that will really reflect to me whether users are getting value from the product. Same as case studies (which one will you start with? Why?) Same with features (what goes into the first version and what doesn't? Why?)
In my opinion, this is the difference between candidates with good intuition and those who have struggled with priorities and decision-making every day.
The second thing I emphasise is analytics and prioritisation questions. In Monday interviews, we check that candidates know how to read graphs, that they know how to translate a soft question into a concrete data question. That they know how to raise a hypothesis and then refute or confirm it using data. It's very difficult, and there are product managers with impressive experience who unfortunately fail at this stage, but this test is critical because that's how we really make decisions on a daily basis.
My final tip for those preparing for interviews is to read Cracking the PM Interview by Jackie Bavaro (who was previously head of product at Asana). I have yet to meet anyone looking for a product position who finished the book and didn't have ten tokens fall on their heads.
info
Source: Verve-PM’s Product Management Interview Guide for Start-ups
when to hire a PM.pdf
387.4 kB
Problem Definition & Clarity (20%)
Scoring Criteria: Does the candidate demonstrate the ability to clearly understand and articulate the problem? Do they ask clarifying questions or make assumptions thoughtfully?
Score Range:
Excellent (4-5): Clearly defines the problem, asks pertinent questions, and identifies edge cases.
Average (2-3): Somewhat defines the problem but misses key areas or assumptions.
Poor (0-1): Jumps to solutions without clear understanding.
Customer-Centric Thinking (20%)
Scoring Criteria: Does the candidate think from the customer's perspective? Are they able to identify key pain points, motivations, and target customer segments?
Score Range:
Excellent (4-5): Insightfully considers customer needs, prioritises based on customer value, and shows empathy.
Average (2-3): Acknowledges customer needs but lacks depth or prioritisation.
Poor (0-1): Focuses more on product features without considering customer needs.
Analytical and Critical Thinking (20%)
Scoring Criteria: How well does the candidate break down the problem and think through different scenarios? Are they able to prioritise based on trade-offs and data?
Score Range:
Excellent (4-5): Demonstrates strong critical thinking, weighs trade-offs effectively, and uses data-driven approaches.
Average (2-3): Considers trade-offs but lacks depth or justification.
Poor (0-1): Ignores trade-offs or doesn't employ a structured approach.
Creativity & Solution Ideation (20%)
Scoring Criteria: Does the candidate come up with innovative or thoughtful solutions? Can they balance short-term needs with long-term vision?
Score Range:
Excellent (4-5): Proposes innovative solutions that align with business goals and user needs.
Average (2-3): Suggests conventional or basic solutions that may not differentiate the product.
Poor (0-1): Struggles to suggest viable or creative solutions.
Communication & Storytelling (10%)
Scoring Criteria: How clearly can the candidate communicate their thought process and solutions? Are they structured, concise, and persuasive?
Score Range:
Excellent (4-5): Clear, logical communication with strong storytelling ability.
Average (2-3): Communicates effectively but may lack structure or clarity.
Poor (0-1): Disorganised or unclear communication.
Strategic Thinking & Business Acumen (10%)
Scoring Criteria: Can the candidate think about the broader business context, including market trends, competition, and business impact?
Score Range:
Excellent (4-5): Demonstrates strong understanding of business impact and competitive landscape.
Average (2-3): Limited understanding of business implications, with a focus on product features.
Poor (0-1): Fails to consider business context.
Overall Scoring:
Total Score Range: 0 to 25.
You can translate the scores into categories such as:
Outstanding (22-25)
Strong (18-21)
Satisfactory (14-17)
Needs Improvement (10-13)
Poor (Below 10)



Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.