The PMM take-home assignment. What it tests and how to do it well.

The take-home exists because a resume and a conversation can’t show how you work alone with incomplete information. You get a brief, a deadline, and no one to ask, which is close to what a PMM faces when a launch lands on a Monday and the product manager is out.

Reviewers usually score it against the same handful of things they use in the live rounds. They want a clear recommendation, a defensible reason for it, evidence that you understand the buyer, and writing they could forward to a colleague without editing. On the Mokk rubric that maps to strategic thinking, analytical rigor, market expertise, and communication and storytelling.

Formats vary a lot. Some companies send a prompt and give you several days to produce a memo, and others give a slide template and a two-hour window. Note any rule about length, tools, or using AI, and follow it exactly. If a rule is missing, ask the recruiter early, when the question still reads as judgment.

The example prompts below are illustrative and none comes from a specific company.

Positioning brief

You receive a one-page description of a product, a few customer quotes, and a list of competitors. The ask is to position the product for a segment. A typical version reads, “Here is an analytics tool for small clinics. Recommend how we should position it against the two incumbents.”

A strong answer picks one segment and says why, names what the buyer uses today, states the one claim the product can prove, and lists what you chose to leave out. Reviewers read that last part closely, because cutting is the hard part of positioning.

Launch plan

You get a product, a date, and a budget range, and you are asked for a plan for the first ninety days. The common failure is breadth. A plan that covers every channel reads as an inventory.

Strong answers start with the goal and how you would measure it, choose two or three moves that serve that goal, and sequence them with the dependencies on product, sales, and support spelled out. Include one thing you would stop if the first two weeks go badly.

Messaging teardown

You get a landing page or a sales deck and are asked what is wrong with it. Resist rewriting everything. Pick the two changes with the largest effect on the buyer’s first ten seconds, show the before and after, and say what you would test to learn whether you were right.

The gap between Strong and Exceptional is usually one section. Strong submissions defend their recommendation well. Exceptional ones also say what evidence would prove them wrong and which number they would watch in the first month to find out, which is how the rubric describes top-level analytical rigor.

Cross-functional influence rarely shows up in the document. It shows up on the follow-up call, when you explain who you would need to bring along and how.

Decide your budget before you start, then hold to it. If the company says a few hours, take a few hours. A twenty-hour submission tells the reviewer you can’t scope, in a job where scoping is half the work.

1. Recommendation. One paragraph on page one that says what you would do and why.
2. Context and audience. Who the buyer is, what they use today, and what changed.
3. Evidence. The two or three facts that led you to the recommendation, each with a source or a stated assumption.
4. Options you rejected. One or two alternatives and why you passed on them.
5. Risks and measurement. What could make you wrong and which number would tell you early.
6. Next steps. The first three actions and who owns each.

Putting the recommendation first feels exposed, because it shows your conclusion before you have argued for it. Do it anyway. A reviewer reading several submissions in an evening spends their attention judging your reasoning once they know where it lands. Here is what that first paragraph might look like for the clinic analytics prompt above.

Most take-homes end with a call of thirty to sixty minutes where you walk through the work and take questions. Expect the first challenge to land on your riskiest assumption. The next two are usually “what did you leave out” and “what would change your mind.”

Prepare a two-minute version of your recommendation, a list of the three weakest points in your own work, and an honest answer for each. Then rehearse aloud. Explaining a document is a different skill from writing one, and people who wrote a strong memo often open the call by reading it back slide by slide. The presentation round guide covers running that conversation, and the case study guide covers the live version of the same skill.

• The thirty-slide deck. Reviewers read the first handful of slides closely and skim the rest. Keep the main body short and move research, personas, and channel detail to an appendix you can point to on the call.
• Answering a different question. It is easy to write a sharp market analysis and never make the recommendation the brief asked for. Reread the last sentence of the prompt before you send.
• The answer on slide nine. Background first and conclusion last makes the reader work for it. Move the recommendation to page one and let the rest support it.
• Unsourced numbers. If you estimate, say so and show the arithmetic. A labeled assumption reads as rigor, and a confident number with no source reads as a guess.
• Ignoring the constraints. Budgets, headcount, and dates in the brief are part of the test. A plan that needs a team the company doesn’t have fails, however good it looks.