Product Manager Interviews Module 6 – Behavioural rounds, take-homes and full mocks
Take-home assignments for product managers
Plan a product manager take-home: the five common types, what readers look for first, a four-hour plan with stated assumptions, and the rules on AI use.
What you will learn
- Recognise the common take-home types and what each is judged on
- Plan a time-boxed take-home with stated assumptions
- Follow each employer's rules on AI use and honesty in take-home work
Before you start
What you’ll learn · Before you start
What you will learn
- Recognise the common take-home types and what each is judged on
- Plan a time-boxed take-home with stated assumptions
- Follow each employer's rules on AI use and honesty in take-home work
Before you start
On this page
Amazon’s product manager page lists a writing assessment two days before the interview loop, and Google says some roles complete a small project before their interviews, from preparing a case study to providing writing samples. That work is done alone, on your own time, and read without you in the room.
Below: the five kinds of take-home, what a reader looks for first, a four-hour plan that scales to any brief, and the rules on AI tools.
Five kinds of take-home, each read for the decision first
A take-home assignment: Work a candidate does alone, in a stated time, outside the interviews, such as a written spec, a case-study deck, a data analysis or a ranked list of priorities. It is read and scored, and often discussed in a later round. is written or analysed work done in a stated time. Employers name theirs differently: Amazon’s writing assessment, Google’s small project, the written follow-ups GitLab describes after its deep dive interview, and the work samples Microsoft’s hiring tips mention for some roles.
Not affiliated
Based on public information about Amazon, Google, GitLab and Microsoft. MySmartCoPilot is not affiliated with Amazon, Google, GitLab and Microsoft, and Amazon, Google, GitLab and Microsoft’s real hiring practices may differ from what this lesson describes.
MySmartCoPilot groups what product managers are asked for into five kinds:
| Kind | What you hand in | Read first for |
|---|---|---|
| A product spec or one-pager | One or two pages | The problem, the user and the decision |
| A case-study deck | About ten slides | The recommendation, on the first slide |
| A data analysis | A sheet or notebook and a short memo | The question, and the answer the data gives |
| A prioritisation exercise | A ranked list with reasons | The criteria, stated before the ranking |
| A written narrative | Two to six pages of prose | An argument a reader can follow alone |
Every kind in the table is read for its decision first, in its own form, and for the same reason:
-
Fresher to mid · Warm-up
What does a reader usually look for first in a product take-home?
The decision. A reader opens it to find what you recommend, for whom and why, so put that in the first two lines, then the assumptions behind it, then the evidence. A submission that saves its recommendation for the last page makes the reader hunt for it, and every page before it is read without knowing what it supports.
A four-hour plan that protects the time to cut and check
MySmartCoPilot’s plan gives each phase a share of the time, and the last two phases are never squeezed:
- Minutes 0 to 20
Read the brief, write the decision
Read the brief twice and write, in one line, the decision it asks you to make and for whom. Note what it leaves unclear.
- Minutes 20 to 40
Assumptions and the rules
Write each assumption with the reason you chose it. Read the rules on length, format, tools and AI, and send the recruiter one message if a rule is unclear.
- Minutes 40 to 130
The analysis
The work behind the decision, such as users, evidence, options and the measure of success. Stop adding evidence once the decision stops changing.
- Minutes 130 to 200
The draft
The recommendation first, then the evidence, the plan and the metric with its target, written for a reader in a hurry.
- Minutes 200 to 225
Cut to length protected
Cut to the stated length. Detail moves to an appendix only if the brief allows one.
- Minutes 225 to 240
Check and submit protected
Check every number against its source, the names and the file format asked for, then submit on time.
The timeline has 6 events, from Minutes 0 to 20 to Minutes 225 to 240.
The same shares fit any brief. This program scales them to two, three, four and six hours; put your brief’s hours in
HOURS:
# Scales MySmartCoPilot's four-hour take-home plan to the time a brief allows. Each phase keeps its share of the four
# hours, rounded to 5 minutes, and the analysis takes up what the rounding leaves, so the phases always add up to the
# time allowed. Put the hours your own brief allows in HOURS and run it again.
PLAN = [ # (phase, minutes in the four-hour plan)
("Read the brief, write the decision", 20),
("Assumptions and the rules", 20),
("The analysis", 90),
("The draft", 70),
("Cut to length", 25),
("Check and submit", 15),
]
HOURS = [2, 3, 4, 6]
def scaled(total):
"""Minutes for each phase of a take-home of `total` minutes."""
four_hours = sum(minutes for _, minutes in PLAN)
out = [5 * int(minutes * total / four_hours / 5 + 0.5) for _, minutes in PLAN]
out[2] += total - sum(out) # the analysis takes up the rounding
return out
for hours in HOURS:
total = hours * 60
minutes = scaled(total)
print(f"{hours} hours ({total} minutes)")
start = 0
for (phase, _), m in zip(PLAN, minutes):
print(f" minute {start:3d} to {start + m:3d} {phase} ({m})")
start += m
cut_and_check = minutes[4] + minutes[5]
print(f" cutting and checking: {cut_and_check} minutes, {100 * cut_and_check / total:.0f} % of the time")Output
2 hours (120 minutes) minute 0 to 10 Read the brief, write the decision (10) minute 10 to 20 Assumptions and the rules (10) minute 20 to 60 The analysis (40) minute 60 to 95 The draft (35) minute 95 to 110 Cut to length (15) minute 110 to 120 Check and submit (10) cutting and checking: 25 minutes, 21 % of the time 3 hours (180 minutes) minute 0 to 15 Read the brief, write the decision (15) minute 15 to 30 Assumptions and the rules (15) minute 30 to 95 The analysis (65) minute 95 to 150 The draft (55) minute 150 to 170 Cut to length (20) minute 170 to 180 Check and submit (10) cutting and checking: 30 minutes, 17 % of the time 4 hours (240 minutes) minute 0 to 20 Read the brief, write the decision (20) minute 20 to 40 Assumptions and the rules (20) minute 40 to 130 The analysis (90) minute 130 to 200 The draft (70) minute 200 to 225 Cut to length (25) minute 225 to 240 Check and submit (15) cutting and checking: 40 minutes, 17 % of the time 6 hours (360 minutes) minute 0 to 30 Read the brief, write the decision (30) minute 30 to 60 Assumptions and the rules (30) minute 60 to 190 The analysis (130) minute 190 to 295 The draft (105) minute 295 to 335 Cut to length (40) minute 335 to 360 Check and submit (25) cutting and checking: 65 minutes, 18 % of the time
Recorded with Python 3.14.8 on macOS 26 arm64. To run it yourself: mise exec python@3.14.8 -- python3 time_box.py
Runs on this device, in your browser. The first run downloads Python (about 13.5 MB), which is kept for the next runs.
Your run, in this browser
A three-hour brief keeps 30 minutes for cutting and checking. Write your assumptions in the second phase, each with the reason you chose it, because a reader judges an assumption only if it is written down.
Each employer’s rules on AI come before the work
Rules on AI tools differ by employer and by stage, so read them before you start:
| Where the rule is | What it says |
|---|---|
| Microsoft’s hiring tips | Welcomes AI tools when you prepare; in assessments and interviews it expects your own work, with outside help only where it is explicitly permitted |
| Google’s interview tips | Search and AI may not be used during its interviews |
| Your brief | Its own rule comes first; when you are unsure what it means, ask the recruiter in writing |
Whatever the rule, never present a tool’s work as your own where the rules forbid it.
Checkpoint
Check: The five kinds of take-home and what is read first · A time-boxed plan with stated assumptions · Following each employer's rules on AI
Flashcards · 5 cards
Recall it, then check
Say the answer to yourself before you look: recalling it is what makes it stick.
-
What is a take-home assignment in a product manager process?
Written or analysed work done alone, within a stated time and on your own time, and read without you in the room, such as a writing assessment or a small project before the interviews.
-
Which five kinds of take-home do product managers get?
A product spec or one-pager, a case-study deck of about ten slides, a data analysis with a short memo, a prioritisation exercise, and a written narrative of two to six pages.
-
What does a reader look for first in any take-home?
The decision, in the take-home's own form: the recommendation on a deck's first slide, the problem, user and decision of a spec, the answer the data gives in an analysis, and the criteria stated before a ranking.
-
Which phases of a time-boxed take-home are never squeezed?
The last two, cutting and checking: even a three-hour brief keeps 30 minutes for them. Write each assumption down with its reason in the second phase, since a reader can judge only what is on the page.
-
What should you do about AI tools before starting a take-home?
Read the rules before you begin, because they differ by employer and by stage, and the brief's own rule comes first; if it is unclear, ask the recruiter in writing. Where the rules forbid it, never hand in a tool's output as if you wrote it.
Terms in this lesson
- take-home assignment
- Work a candidate does alone, in a stated time, outside the interviews, such as a written spec, a case-study deck, a data analysis or a ranked list of priorities. It is read and scored, and often discussed in a later round.
Two sample take-homes, scored against one guide Pro: opens with a Pro, Premium or Ultimate pass
In this part:
- A one-page proposal for a marketplace’s new sellers
- A ten-slide case study for a city bike-share
- Five mistakes that sink a take-home, and the fix for each
- A practice brief to time-box in four hours
- Practise: the decision first, within the time
- Interview questions
- Your take-home brief is vague about the target users and how long to spend. What do you do before you start?
- The take-home brief does not mention AI tools. How do you decide whether to use them, and what do you disclose?
- You have spent six hours on a take-home meant to take three and you are not done. What do you submit?
- Key takeaways
3 interview answers · about 26 minutes
Opening this part with your pass…
This part opens with any MySmartCoPilot pass.
- Pro pass · 1 week₹79$2.99
- 30 days₹179$5.99
- 1 year₹1,699$45
One payment; a pass never renews. The price shown is the total you pay: no fees or charges are added at checkout.
Passes can’t be bought right now, so this part can’t be opened at the moment. The free part above stands on its own. If you have a pass, enter your licence key.
It also opens every other in-depth part in Learn and every Pro tool. Sales are final, except where the law gives you a right to withdraw, for example in the EU and the UK (refund policy).
References
- Product Manager Interview Prep (Amazon Jobs)
- How we hire (Google Careers)
- Interviewing at Google: interview tips (Google Careers)
- Product Manager (job family) (GitLab Handbook)
- Hiring tips (Microsoft Careers)
Related tools
Report a problem with this lesson
Kept only in this browser. Your Learn progress