Maya applied for a senior lifecycle marketing role on Tuesday.
On Wednesday morning, before a recruiter call, before salary range confirmation, before anyone had explained the actual problem, she got the sacred modern hiring ritual:
“Thanks for your interest! As the next step, please complete this brief exercise. It should take 60–90 minutes. We’d love to see how you’d improve our trial-to-paid conversion flow. Please include segmentation, email copy, experiment ideas, and a measurement plan.”
A “brief exercise,” apparently, now means: diagnose our funnel, write campaign copy, build an experiment roadmap, and do unpaid product marketing archaeology in your pajamas.
The company had not confirmed the role was funded. The recruiter had not spoken to her. The job post listed “competitive salary,” which is recruiter-speak for “we have chosen fog.” The deadline was Monday.
Maya almost did it. Strong candidates do this all the time because the hiring machine trains you to treat every hoop like a compliment. “They’re interested!” Maybe. Or maybe their candidate screening process has become a vending machine where your weekend goes in and a vague rejection comes out.
Here’s the playbook: before you touch the assignment, build a Pre-Take-Home Gate.
Not a tantrum. Not a manifesto. A gate.
A professional checkpoint that says: my time is real, my work is not confetti, and if you want job-relevant proof, you can provide job-relevant context.
Diagnosis: the pre-screen assignment is where dignity quietly leaves the room
A take-home after a real conversation can be reasonable.
A scoped, paid work trial with clear work trial evaluation criteria? Great. Adults evaluating adults. Put it on the calendar and let everyone keep their soul.
But the pre-screen unpaid take-home assignment is a different animal. It shows up before the company has earned any trust, then asks you to act like an internal consultant with no access, no context, and no guarantee a human will read the thing.
That’s not rigor. That’s a free consulting interview task wearing a little “we value your time” sticker.
The biggest red flags are usually small and polite:
- The assignment arrives before any human conversation.
- There is no salary range, level, timeline, or hiring process map.
- The prompt uses real company problems: “audit our funnel,” “improve our onboarding,” “prioritize our roadmap,” “analyze this live customer segment.”
- The time estimate is fictional. “60 minutes” somehow includes research, strategy, writing, design, analysis, and a presentation deck. Sure. And I am a regional llama judge.
- There is no hidden interview scorecard disclosure — just “show us how you think.”
- They ask for editable files, raw analysis, or a recorded walkthrough they can circulate forever.
- The assignment is followed by “one quick revision,” which is hiring’s version of “just the tip.”
The humiliation isn’t only the unpaid work. It’s the asymmetry.
They get evidence. You get mystery.
They get your candidate work product. You get “we went with someone more aligned.”
They get to decide whether the role is real later. You have to pretend the job is real now.
So don’t start by asking, “Should I do the assignment?”
Ask: “Has this company earned an assignment yet?”
The Pre-Take-Home Gate: five things to get before you open the doc
Your goal is not to be difficult. Your goal is to turn a vague hoop into a fair evaluation.
Before doing the work, ask for these five items.
1. Process clarity
You need to know where this assignment sits in the loop.
Ask:
“Happy to consider the exercise. Before I begin, could you share the full interview process from here, including number of rounds, who reviews the assignment, and expected timeline?”
You are listening for whether the assignment replaces an interview step or merely unlocks the door to endless interview rounds.
Bad answer:
“We’re still figuring it out, but this is the first step.”
Translation: welcome to the ritual fog machine.
Better answer:
“After this, selected candidates meet the hiring manager, then a panel, then final. We review against a rubric and respond within five business days.”
Not perfect. At least oxygen exists.
2. Compensation and level confirmation
No salary, no homework.
Not because you are greedy. Because doing unpaid work for a role that might be $40K below your range is not ambition. It is calendar vandalism.
Ask:
“Before I invest time in the assignment, can you confirm the compensation range and level for this role?”
If they dodge, you have learned something useful before donating a Saturday.
3. Evaluation criteria
“Show us how you think” is not criteria. It is mist.
Ask:
“Could you share the 3–5 criteria reviewers will use to evaluate the assignment? I want to make sure I’m aiming at the actual scorecard rather than guessing.”
This forces the hidden interview scorecard into the daylight.
Look for concrete criteria like:
- prioritization logic
- customer insight
- tradeoff reasoning
- measurement plan
- communication clarity
- technical feasibility
- stakeholder management interview signals
If they cannot name the criteria, the assignment may be less about skill and more about vibes with a deadline.
4. Scope cap
Never accept “brief” as a unit of measurement.
Ask:
“The prompt could be answered at multiple depths. Is the expectation a 60-minute outline, a polished deck, or a detailed plan? I can cap the work at 90 minutes and note assumptions where deeper access would be needed.”
This does two things:
- It sets take-home assignment boundaries.
- It prevents them from grading your 90-minute outline against someone else’s 12-hour unpaid thesis.
5. Work product boundaries
If the prompt touches real company strategy, protect the output.
Ask:
“Since this uses your current business context, can you confirm the submission is for evaluation only and won’t be used operationally without a paid engagement or written agreement?”
This is not dramatic. This is normal adult language.
Companies use contracts, NDAs, IP assignments, and compliance policies every day. Candidates are the only people expected to hand over thinking with a smiley face and a Google Drive link.
The prep workflow: turn the assignment into a controlled evaluation
If the company gives reasonable answers, you may still choose to do the take-home. Fine. The play is not “never do homework.” The play is “never become unpaid staff.”
Use this workflow.
Step 1: Build a role-evidence map before creating anything new
Open a blank doc with two columns:
| Role need | Existing proof |
|---|---|
| Improve lifecycle conversion | Increased activation email CTR 22% by segmenting onboarding paths |
| Experiment design | Ran 14 A/B tests with documented hypothesis, sample size limits, and rollout rules |
| Cross-functional work | Coordinated PM, data, and CS to reduce churn-risk handoff time by 30% |
| Measurement | Built dashboard tying trial behavior to paid conversion and expansion |
This keeps you from overbuilding. You are not trying to solve their company. You are trying to demonstrate job-fit evidence.
Step 2: Decide what belongs in the assignment versus the interview
A good take-home should show judgment, not donate the roadmap.
Put in the assignment:
- assumptions
- prioritization framework
- sample approach
- sanitized examples from past work
- risks and tradeoffs
- measurement logic
Hold for the interview:
- detailed campaign copy libraries
- step-by-step implementation plans
- exact segmentation schemas
- vendor-specific configurations
- internal-style roadmaps they could ship next week
Your assignment can say:
“I’d validate this segment with event-level data before recommending exact campaign logic. Below is the framework I’d use and a sample first experiment.”
That sentence is doing push-ups. It proves judgment and sets a boundary.
Step 3: Use proof blocks instead of building a shrine
Every section should include one compact proof block:
Similar work I’ve done: At a B2B SaaS company, I rebuilt trial onboarding around activation behavior instead of signup date. The highest-intent segment saw a 19% lift in demo requests over six weeks, while low-activation users were routed into education instead of sales pressure.
Proof blocks make the evaluator connect your recommendation to your actual experience. They also help if the assignment gets summarized later by an AI interview transcript, recruiter notes, or some debrief bot turning your work into beige soup.
If the process moves into an AI interview screen or one-way video interview after the assignment, tools like NoSweatKing can help decode the question and keep your answers in your own voice instead of letting the bot flatten your proof.
Step 4: Put assumptions on the page
Do not pretend you have internal context you don’t have.
Use an assumptions box:
Assumptions:
- Trial-to-paid conversion is currently constrained more by activation than pricing.
- Product usage events are available by account and user.
- Sales touches higher-intent trials within 48 hours.
- The goal is paid conversion quality, not just volume.
This protects you from the classic reviewer complaint:
“They didn’t account for our enterprise sales motion.”
Correct, Chad. You hid it behind the curtain.
Step 5: Timebox and label the version
Put this at the top:
Scope note: This is a 90-minute evaluation response based on public information and the provided prompt. I’ve focused on approach, prioritization, and measurement rather than a production-ready plan.
That one note prevents a lot of nonsense. It tells sane reviewers how to judge it and tells unserious reviewers you are not here to renovate their basement for exposure.
Three examples: how to respond without sounding combative
You don’t need a courtroom tone. You need calm leverage.
Example 1: The assignment arrives before the recruiter call
Send:
Thanks for sending this over. I’m interested in the role, and the exercise looks relevant. Before I invest time, could we confirm a few basics: compensation range, level, interview process, who reviews the assignment, and the evaluation criteria? Once I have that, I can decide whether to complete it or suggest a smaller proof sample.
Why it works:
- Positive tone.
- Clear ask.
- No apology for having a life.
Example 2: The prompt asks for real strategy
Send:
This appears to touch current business strategy, so I’d like to keep the submission at framework/sample level rather than a production-ready plan. I can outline how I’d diagnose the issue, prioritize opportunities, and measure success within a 90-minute cap. If you need a deeper operational audit, I’d be happy to discuss a paid work trial.
Why it works:
- Names the boundary.
- Offers useful proof.
- Introduces paid work trial without sounding like you invoice people for breathing.
Example 3: They refuse criteria and say “just be creative”
Send:
I can work with an open-ended prompt, but to make the exercise useful for both sides, I’d need at least the review criteria. Otherwise it becomes more of a guessing exercise than a job-relevant assessment. Could you share what strong submissions typically demonstrate?
Why it works:
- Calls out the flaw without insulting anyone.
- Forces them to admit whether a real rubric exists.
Mistakes to avoid when you’re trying to protect your time
Boundaries are a skill. The trick is to avoid turning them into either surrender or a hostage note.
Mistake 1: Doing the assignment immediately because you’re flattered
An assignment is not validation. It is a request for labor.
Treat it like a business decision.
Ask: What do I know about the role, compensation, process, and likelihood of human review?
If the answer is “nothing,” you are not being strategic. You are feeding the void with nicer formatting.
Mistake 2: Overdelivering to prove seriousness
The broken hiring system loves candidates who overdeliver before anyone has committed to anything.
Do not turn a 90-minute prompt into:
- a 17-slide deck
- a complete campaign calendar
- a redesign prototype
- a SQL analysis pack
- a 90-day plan with budget assumptions
That is not seriousness. That is pre-employment Stockholm syndrome.
Mistake 3: Sending raw, reusable work product
Avoid editable decks, spreadsheets with formulas, production-ready copy libraries, and detailed implementation roadmaps unless there is a paid agreement.
PDF is your friend. Watermarked samples are your friend. Sanitized proof is your friend.
Your candidate work product should prove competence, not become their Q4 plan.
Mistake 4: Accepting revision loops without a decision point
If they ask for revisions, ask what decision the revision unlocks.
Send:
Happy to clarify one section. Before I revise, can you share what concern this revision is intended to address and whether this is the final assessment step before a decision?
If they cannot answer, you are not revising. You are entering the unpaid fog sauna.
Mistake 5: Confusing “nice recruiter” with “fair process”
A recruiter can be kind and still work inside a candidate screening process that wastes people’s time.
Be pleasant. Still ask for the process map.
The system is not improved by your silent suffering.
The short checklist: before you say yes to the take-home
Use this before opening the assignment doc.
- Have I spoken to a human?
- Is the compensation range acceptable?
- Is the role level clear?
- Do I know the full interview process after this step?
- Do I know who reviews the work?
- Do I have work trial evaluation criteria?
- Is the time cap realistic and written down?
- Does the prompt avoid real company strategy, or have I set boundaries?
- Am I submitting framework-level proof instead of production-ready work?
- Have I labeled assumptions and scope?
- Is there a clear decision point after submission?
- Would I still feel okay if this produced no response?
That last one matters.
If you would feel robbed, shrink the scope, ask for payment, propose a live working session, offer past proof, or decline.
The line that keeps your dignity intact
Here is the core sentence:
“I’m happy to demonstrate relevant skill, but I’d like to align on scope, criteria, and process before creating new work.”
That’s it.
Not “I refuse.”
Not “how dare you.”
Not “attached please find my 42-page unpaid strategy thesis, please love me.”
Just: skill, scope, criteria, process.
The modern hiring machine will keep asking candidates to prove everything before companies prove anything. You don’t have to fix the whole machine today. You just have to stop handing it your weekends without a receipt.
No salary, no human, no homework.
Put that on a mug. Then put it in your calendar as a boundary.
