One-Way Video Screen: Why Whatnot, Product Critique and Going Above and Beyond

This is a one-way recorded video screen for a software engineering candidate at Whatnot. There is no live interviewer: five questions appear one at a time, the whole screen takes about 10 minutes, and each question allows roughly 30 seconds of preparation before recording starts. The questions assume a candidate who is still studying or has recently graduated. Four of the five questions are below. The fifth collects logistics (where you live, when you graduate, and whether you need visa sponsorship) and only needs short, factual answers. Answer each question as you would on camera. ### Constraints and Clarifications - Five questions in about 10 minutes, so each answer has roughly a minute and a half. - About 30 seconds to prepare before each recording. - No follow-up questions: every answer has to stand on its own. ### Clarifying Questions - Does the platform offer a practice question or allow re-recording, or is the first take of each answer final? - Is there a hard cutoff for each answer, and does a timer show how much time is left? - Should the product question be answered only from your own use of the product, or may you also draw on what you have read about it? ### Part 1 — Motivation What motivated you to apply to Whatnot? ```hint Make it specific to this company An answer that would work unchanged for any other company is too generic. Connect one real reason to the product and one to the kind of engineering work you want to do. ``` #### What This Part Should Cover - A specific, credible reason tied to this company and its product. - A link between that reason and your own skills or goals as an engineer. - Delivery within about a minute and a half. ### Part 2 — Using the product Have you used Whatnot? What do you like about it? Where do you think it needs to improve? ```hint Tie each point to a user For both the strength and the weakness, name who experiences it and in what situation, so the critique reads as product thinking rather than personal taste. ``` #### What This Part Should Cover - An honest statement of how much you have used the product. - One concrete strength, and why it works for the people who use it. - One concrete, constructive improvement, with a sense of how you would validate it or what building it would involve. ### Part 3 — Experience and a favorite Do you have any internship experience or work history? What was your favorite experience? ```hint Overview first, then one story Spend a sentence or two on the overview and the rest of the time on the single experience you chose, including why it was your favorite. ``` #### What This Part Should Cover - A brief, ordered overview of your internships or jobs. - One favorite experience, with your own contribution and its result. - Why it was your favorite, and what that says about the work you want next. ### Part 4 — Going above and beyond Tell me about a time when you went above and beyond to solve a problem at work. ```hint Define the baseline Make the expected scope explicit before describing what you did beyond it; otherwise the listener cannot tell which part was extra. ``` #### What This Part Should Cover - The problem and what was expected of you. - What you did beyond that expectation, and why. - A measurable result, told in the first person. ### What a Strong Answer Covers - Specific, honest answers that would not fit any other company or any other candidate. - A compact structure for each answer (point, evidence, result) that finishes before the time runs out. - Product-minded framing: praise and critique grounded in real use, with the critique kept constructive. - Calm on-camera delivery: looking at the lens, speaking clearly, and not reading from a script. ### Follow-up Questions - If you had not used the product before the screen, how would you prepare so that your answer to the product question is still honest and useful? - How would your motivation answer change in a live interview with an engineering manager, where follow-up questions are possible? - For the improvement you proposed, how would you measure whether it worked after launch? - If your only work history is one internship, how would you avoid telling the same story for the favorite-experience and above-and-beyond questions?