IN THIS LESSON

Prepare for the Company, Not the Prompt

A gardening question at Facebook is still, in an important sense, a Facebook question.

Product Sense prompts are often designed to feel arbitrary. You might be interviewing at Facebook and be asked to build a product for gardeners. You might be interviewing at Airbnb and be asked to improve DoorDash. The interviewer appears to have moved you into a product space that has little to do with the company.

Do not assume that means the company is irrelevant.

The prompt gives you a setting. The company gives you a point of view.

Every company has a small number of needs and product truths that recur across its portfolio: the kinds of value it is especially good at creating, the mechanics that make its products work, the risks that can destroy trust, and the strategic advantages it can bring to a new problem. A strong candidate learns those truths before the interview and looks for them inside unfamiliar prompts.

The most useful way to do this is through analogy:

What familiar problem at this company is structurally similar to the unfamiliar problem in front of me?

Then say the analogy out loud.

This does not mean forcing every answer into an existing company product. It means identifying a useful similarity, explaining why it matters, and using it to make better decisions throughout the case.

The Prompt Is Not the Whole Question

Suppose you are interviewing at Facebook and receive this prompt:

Build a product for gardeners.

You could treat this as a generic gardening exercise. You could list gardeners, brainstorm their frustrations, and invent a plant-care tool. That answer may be reasonable.

But Facebook is not a generic company. Its deepest product strengths concern identity, social interaction, communities, content, and network effects. Gardening is also not merely the private act of keeping plants alive. It is a hobby through which people learn from one another, display expertise, exchange local knowledge, share progress, and build relationships.

That creates a useful analogy:

I am going to think about gardening as a social hobby network. The analogy is Facebook Groups—not because the answer must literally be a Group, but because gardening becomes more valuable when people with a shared identity exchange knowledge and help one another over time.

That one statement gives the interviewer a clear view into your reasoning. It also gives you a lens for the rest of the case.

You may now notice customer groups that a generic answer would miss:

• New homeowners who need local advice and reassurance.
• Experienced gardeners who enjoy teaching and displaying expertise.
• Neighborhood gardeners who can exchange plants, tools, and knowledge.
• People interested in a specific practice, such as native plants or vegetable gardening.

You may identify different pain points:

• Advice is often generic when gardening outcomes depend on local soil, weather, pests, and growing conditions.
• Beginners do not know which sources or people to trust.
• Gardeners have progress, failures, and discoveries to share, but no durable community around them.
• Useful knowledge is scattered across one-off searches instead of accumulating within a network.

You may also prioritize different solutions. A plant-diagnosis tool could still be useful, but the analogy may lead you toward a product in which diagnosis becomes the start of a social interaction: a gardener shares a photo, receives help from credible local gardeners, reports what worked, and leaves behind knowledge that helps the next person.

The analogy has not answered the case for you. It has helped you see the problem more clearly.

Call the Analogy During the Interview

Many candidates use analogies silently. They recognize that one product resembles another, then jump straight to a conclusion. The interviewer is left to reconstruct the logic.

Do not make them do that work.

Name the analogy directly. A good analogy statement has three parts:

1. Name the comparison.
2. Explain the structural similarity.
3. State what the similarity will change in your answer.

For example:

The analogy I am using is Facebook Groups. Gardening is a hobby in which identity, repeated interaction, and accumulated community knowledge can create network effects. I will use that lens as I think about customer groups and engagement, while staying open to needs that are specific to gardening.

This is stronger than saying, “Facebook is social, so I would add community features.” The second version jumps from company identity to solution. The first version explains the mechanism and tells the interviewer how it will inform your decisions.

You can use this sentence stem:

The analogy I am using is [familiar product or problem]. Both situations involve [shared underlying need, mechanic, or risk]. That means I want to pay particular attention to [implication for this case].

The analogy can be introduced near the beginning of the case, often while defining the goal or briefly discussing company strategy. You can then refer back to it when it becomes useful:

Returning to the hobby-network analogy, I think experienced local gardeners are especially important because they create value for everyone else.

The analogy suggests that repeated contribution matters more than one-time consumption, so I would prioritize a solution that turns isolated questions into durable community knowledge.

Making the connection explicit is not showing off. It is part of bringing the interviewer along for the ride.

A Marketplace Example: Airbnb and DoorDash

Now imagine that you are interviewing at Airbnb and are asked:

How would you improve DoorDash?

The products look different. One involves travel and overnight stays; the other involves food delivery. But both are two-sided marketplaces that coordinate a real-world experience among people who do not fully control one another.

That creates several important similarities:

• The product promise is fulfilled offline.
• Quality depends on participants outside the company.
• Matching and logistics matter.
• Trust must be established before the experience occurs.
• A single bad outcome can matter far more than several ordinary good outcomes.
• The platform must create value for both demand and supply.

You might say:

The analogy I am using is Airbnb itself. DoorDash also coordinates an offline service among parties who have incomplete information and limited control over one another. In both cases, reliability and trust are part of the core product, and severe negative outcomes can outweigh a large number of routine successes. I want that to shape how I define the goal and prioritize pain points.

This analogy could change the entire answer.

A generic DoorDash response might focus immediately on selection, speed, or discounts. Those are credible areas. The Airbnb analogy, however, may cause you to examine whether the most important customer problem is uncertainty: Will the order arrive? Will it be correct? Has it been handled safely? What happens when something goes wrong?

It may also affect measurement. Average delivery time matters, but averages can conceal the outcomes that most damage trust. You may want to examine cancellation rates, missing or incorrect orders, severe lateness, support resolution, repeat usage after a failure, and the distribution of outcomes rather than only the mean.

Again, the analogy does not mean copying an Airbnb feature into DoorDash. It means transferring a product insight: in a marketplace that delivers an offline experience, the downside is not symmetrical. Reliability and recovery may deserve more weight than a generic engagement framework would give them.

Prepare a Company's Product DNA

You cannot predict every prompt. You can prepare the lenses through which you will interpret them.

Before an interview, write down the target company's product DNA. You are looking for recurring truths, not a list of products or a repetition of the mission statement.

Consider four areas.

1. Core Human Needs

What enduring need does the company repeatedly serve?

For Facebook, this may include connection, identity, belonging, expression, and social discovery.

For Airbnb, this may include trust, belonging, access to distinctive real-world experiences, and confidence when dealing with unfamiliar people and places.

2. Core Product Mechanics

What mechanisms repeatedly create value?

Examples include social graphs, creator-consumer loops, two-sided marketplaces, local density, reputation systems, personalization, repeated contribution, or cross-side network effects.

3. Distinctive Advantages

What can this company do unusually well?

This might include a large network, rich identity data, a trusted brand, logistics infrastructure, existing supply, distribution, hardware integration, or a particular form of expertise.

4. Characteristic Risks

What failure modes are especially damaging?

Examples include loss of trust, low-quality supply, privacy failures, harmful interactions, marketplace imbalance, unreliable offline fulfillment, or content that drives attention without creating value.

Do not prepare ten pages. Aim for three to five important truths that you can explain in your own words.

Then create prompts that appear unrelated and practice finding the analogy:

• How would Facebook build a product for gardeners?
• How would Airbnb improve food delivery?
• How would Spotify build a fitness product?
• How would Google build a product for home repair?
• How would LinkedIn build a product for volunteers?

The exercise is not to guess the company's secret preferred answer. It is to practice recognizing transferable product structures.

Use the Analogy, Then Test Its Limits

An analogy is useful because two situations are similar. It is dangerous because they are never identical.

A strong candidate explains both.

For the Facebook gardening example, the analogy to a social hobby network may be powerful, but gardening also has physical, seasonal, local, and biological constraints. A community cannot substitute for accurate diagnosis, and network effects may be weak in a location without enough active gardeners.

For the Airbnb and DoorDash example, both products coordinate offline marketplace experiences, but the frequency, price, planning horizon, emotional stakes, and supply model differ. DoorDash orders happen far more often and usually carry less individual consequence than a vacation stay. Speed may matter much more. Some trust mechanisms that work for Airbnb would add too much friction to ordering dinner.

Say where the analogy stops:

I think the Airbnb analogy is useful for understanding trust and asymmetric downside. Where it breaks is frequency and transaction value: DoorDash is a high-frequency, lower-consideration product, so any trust mechanism must preserve speed and convenience.

This makes your reasoning more credible, not less. You are showing that you can use a model without becoming trapped by it.

A good rule is:

Name the analogy. Extract the insight. Test the boundary. Return to the user.

The final step matters most. The analogy is a lens, not the customer. Your answer still needs to be grounded in the actual people, motivations, constraints, and pain points within the prompt.

Do Not Turn the Analogy Into a Feature

The most common mistake is to jump from analogy to imitation.

Facebook is social, so the candidate adds a feed.

Airbnb uses ratings, so the candidate adds more ratings to DoorDash.

Spotify recommends music, so the candidate adds recommendations to a fitness product.

This is superficial transfer. It copies the visible feature rather than the underlying logic.

Instead, move through three levels:

1. Company truth: Facebook creates value through identity, interaction, and networks.
2. Prompt insight: Gardening knowledge is local, social, cumulative, and often exchanged among people with different levels of expertise.
3. Product implication: A solution may become more valuable when it helps credible gardeners answer questions, build reputation, and create reusable local knowledge.

Only then should you define features.

This keeps the answer original and customer-centered. The company context improves your product judgment without dictating the product.

A Simple Preparation Exercise

Choose a target company and complete the following exercise before your next mock interview.

First, write three sentences:

• This company creates value by...
• Its products become stronger when...
• The outcomes it must avoid are...

Second, choose an unrelated prompt.

Third, complete this statement:

The analogy I am using is [company product or familiar problem] because both involve [shared structure]. This suggests that I should pay particular attention to [goal, customer, mechanic, or risk]. The analogy breaks down when [important difference].

Finally, complete the case. Refer back to the analogy only when it genuinely improves a decision.

The Real Skill

Product Sense is not the ability to memorize answers to common prompts. It is the ability to recognize what kind of problem you are facing, transfer relevant judgment into a new setting, and explain that reasoning clearly.

That is why apparently arbitrary prompts are useful. They prevent you from relying entirely on product familiarity while still giving you room to demonstrate that you understand the company.

Prepare for the company, not just the prompt.

And when you see the analogy, call it.