How interview loops differ

Every PM loop tests the same core skills: product judgment, analytical thinking, execution, communication and how you work with people. What changes from company to company is the order, the format, how much each skill counts and how the decision gets made. If you prepare the same way for every company, you will over-prepare for rounds you will never face and walk into the round that matters most without practice.

This module teaches one habit you will use in every lesson: build a loop map before you prepare. A loop map is a one-page table showing what you know about each stage of a company's process, where that knowledge came from, and which of your answers and stories you will use there.

#The five ways loops differ

#1. What happens before the loop

Most processes open with a recruiter conversation. After that, companies vary a lot. Some send an online assessment. Some ask for a writing sample, a case study or a take-home exercise. Some add a phone or video screen with a PM or hiring manager before the main loop. Each of these is a filter, and each needs its own preparation. A written exercise, for example, rewards clear structure and tight prose far more than a spoken answer does.

#2. What the loop weights

Many large tech companies spread their interviews across product sense, analytical or execution questions, and behavioral questions. The mix differs. Some lean heavily on past behavior and stated values, and almost every question starts with "Tell me about a time." Others spend most of the loop on open-ended product and metrics cases. Early-stage startups often care most about whether you can ship with very little support.

#3. The format of each round

Two rounds can test the same skill in very different ways. Product sense might be a design prompt ("Design a product for…"), a critique of the company's own product, or a detailed walk-through of a product you built. Execution might be a metric-drop case, a prioritization exercise, or a written plan. Knowing the format tells you what to rehearse.

#4. Who interviews you

You might meet only PMs, or a mix of PMs, engineers, designers, data scientists and leaders. A common pattern at larger companies is to include at least one interviewer from outside the hiring team, to keep the hiring bar consistent across teams. Who is in the room shapes how technical, visual or numbers-heavy your answers should be.

#5. How the decision is made

Some companies score every candidate against the same written rubric and then review the full packet together. Others leave more of the decision to the hiring manager. Some hire for a specific team; others hire into a general pool and match you to a team afterward. Timelines range from days to a couple of months. None of this changes how you answer a question, but it changes how you plan your search and when you can expect news.

Key idea The skills are the same everywhere. The weights, formats and order are not. Find out which ones apply before you spend a single hour practicing.

#What four large companies publish

Several large companies describe their process on their own careers pages. Everything in this table comes from the pages listed under Sources. Processes change, so read the current page before you rely on any of it.

Even among four very large companies, these differ: one publishes a writing assessment, one adds "Reflection" to the usual answer structure, and one gives a range of interview counts instead of a fixed number. You would prepare differently for each.

Also notice what is missing. None of these pages hands you a question list or tells you how answers are scored line by line. Anyone who claims to know a company's secret rubric is guessing. Don't build your prep on it.

#Build your loop map

A loop map has one row per stage. Fill the columns from the most reliable source you have, and write down where each fact came from so you know how far to trust it.

Rank your sources like this:

1. What your recruiter tells you about your specific process. This beats everything else, because it is about your role and your level, this month.
2. The company's own careers and interview-prep pages. Accurate in general, but often written for many roles at once.
3. The job description. The best guide to which skills this team wants most.
4. Second-hand reports from friends or forums. Useful for color, but often out of date or about a different team. Treat them as hints to verify, never as fact.

#A worked example

Suppose you are interviewing for a product manager role at Larkspur, a fictional mid-size company that makes scheduling software for clinics. The recruiter call has just ended. Here is the loop map you might write that evening:

Three things make this map useful. It separates what you were told from what you guessed. It turns every row into a concrete preparation task. And it shows you exactly which question to ask next ("Can you tell me more about the engineering conversation?").

Try it Pick one company you want to interview with. Spend fifteen minutes on its careers site and the job description, then draft its loop map. Mark every cell where your only source is a forum post or a guess. Those cells become your questions for the recruiter.

#What weak preparation looks like

A weak candidate memorizes a forum list of supposedly common questions for the company and practices only those. When the loop turns out to be organized differently, they have nothing systematic to fall back on.

A strong candidate builds core skills first with the earlier modules of this kit, then builds a loop map from the recruiter and the company's own pages, and shifts the last week or two of practice toward the formats it says matter most.

Next, Patterns at large tech companies turns the published information above into specific preparation moves. For a refresher on the round types themselves, see The round types and how they differ.

#Sources

• Google, "Our hiring process": https://www.google.com/about/careers/applications/how-we-hire/
• Amazon, "Product Manager Interview Prep": https://amazon.jobs/content/en/how-we-hire/product-manager-interview-prep
• Meta, "Meta Jobs Hiring Process": https://www.metacareers.com/hiring-process/
• Meta, "Preparing for Your Product Management Interview": https://www.metacareers.com/PM-prep-onsite/
• Meta, "Preparing for Your Full Loop Interview at Meta": https://www.metacareers.com/pm-l-prep-onsite/
• Microsoft, "How we hire": https://careers.microsoft.com/v2/global/en/hiring-tips.html
• Microsoft, "Interview tips": https://careers.microsoft.com/v2/global/en/hiring-tips/interview-tips.html

#Recap

• PM loops test the same core skills everywhere, but differ in what happens before the loop, what gets weighted, the format of each round, who interviews and how the decision is made.
• Build a loop map for every company: one row per stage, with the source and your confidence for each fact.
• Trust your recruiter first, the company's own pages second, the job description third, and second-hand reports least.
• No company publishes its full rubric or question list. Prepare skills, not rumors.
• Use the map to shift your last week or two of practice toward the formats that company actually uses.