At 9:17 p.m., Priya got the email every candidate recognizes by smell.
Great speaking with you! The team has an optional exercise you can complete to strengthen your candidacy. It should take about 90 minutes. Please send back a short launch plan, three campaign ideas, and a competitive teardown by Friday.
She had not met the hiring manager.
She did not have the salary range.
She did not have the work trial evaluation criteria.
She did, however, have a vague promise that “strong submissions may move forward.” Which is corporate for: please insert weekend and receive maybe.
The assignment was “optional” in the same way airport security is optional if you don’t mind not boarding the plane.
This is the new dignity tax: companies ask for unpaid take-home work early, call it candidate-friendly, then act surprised when candidates notice the task looks suspiciously like the work they need done.
Let’s build the playbook for handling it without sounding hostile, desperate, or like you were born yesterday.
Diagnosis: What “Optional” Is Really Doing
An optional take-home can be legitimate. Sometimes a company offers an assignment as one way to show skill, especially for candidates with nonlinear backgrounds, resume gaps, contract work, or portfolios trapped behind NDAs.
That version has clear boundaries.
The broken version has fog, urgency, and a hidden interview scorecard wearing a hoodie.
The real question is not “Is this optional?”
The real question is:
Does declining it remove me from serious consideration?
If yes, it is required. The word “optional” is just there to make the company feel less rude.
The red flags
Watch for these exact patterns:
| What they say | What it may mean |
|---|---|
| “It should only take 60–90 minutes.” | They have not measured the work, or they are measuring only the typing, not the thinking. |
| “Use our real website/data/product.” | This may be a free consulting interview task. |
| “No need to overthink it.” | They will absolutely judge the parts you did not overthink. |
| “We don’t have a rubric, just want to see your approach.” | The hidden interview scorecard is vibes with admin access. |
| “Send editable files.” | Your candidate work product may wander into someone’s roadmap meeting wearing sunglasses. |
| “This is before the hiring manager call.” | You are doing labor before a human has invested in you. |
| “Everyone does it.” | Ah yes, the ancient ethical framework of peer pressure. |
If the assignment asks you to diagnose their actual funnel, rewrite their actual docs, analyze their actual data, fix their actual repo, or build an actual plan they could use Monday morning, you are not just being evaluated.
You are being harvested.
The Prep Workflow: Build an Optional Assignment Gate
Do not answer an unpaid assignment with panic. Answer it with a gate.
A gate is not a tantrum. It is a small professional checkpoint that forces the process to become real before you donate your judgment.
Step 1: Confirm whether “optional” affects the next step
Use a sentence that makes the truth easy to say.
Thanks for sending this over. Before I decide how to approach it, can you confirm whether completing the exercise is required to move forward, or whether prior work samples can be reviewed instead?
This is better than asking, “Is it really optional?” because they can dodge that.
You want the operational truth: what happens if I do not do this?
Step 2: Ask for the scoring criteria
A fair assessment can explain what it measures.
Ask:
Could you share the evaluation criteria for the exercise? I want to make sure I focus on the skills that matter for the role rather than guessing at the format.
If they cannot explain the rubric, that is data.
Not always fatal. Some small teams are messy, not malicious. But a vague rubric plus real company work plus urgency is the Bermuda Triangle of candidate dignity.
Step 3: Cap the scope before opening the file
The scope cap is where your weekend survives.
Try:
I can spend up to 90 minutes on a scoped version and will note assumptions where deeper company context would normally be required.
That one sentence does three things:
- It accepts the premise professionally.
- It limits the unpaid labor.
- It prevents them from judging you for not knowing internal context they refused to provide.
Beautiful. Annoying to exploit. We love it.
Step 4: Offer an evidence swap
Many candidates already have proof blocks: past projects, sanitized screenshots, metrics, before/after examples, decision memos, teardown samples, code snippets, presentations, or short case summaries.
Use a role-evidence map: one column for role requirements, one column for your proof, one column for the artifact you can share.
Then send:
I have a prior work sample that demonstrates the same skills: audience analysis, positioning tradeoffs, campaign prioritization, and performance measurement. If acceptable, I can share that instead of creating new strategy work for your current business.
This is not evasive. It is mature.
A company that actually wants to assess skill should be open to equivalent evidence.
A company that specifically wants free work will suddenly become very spiritual about “our process.”
Step 5: Set a work-product boundary
If you do complete a version, label the boundary directly.
I’m sharing this solely for interview evaluation. Please don’t use, reproduce, or distribute it outside the hiring process without written permission.
Will this magically stop every bad actor? No. Neither does a bike lock against a determined goblin with bolt cutters.
But it creates a clear record. It also signals that you understand the difference between assessment and unpaid deliverable.
Do not send editable decks, raw datasets, full repo access, unwatermarked strategy docs, or implementation-ready work unless there is a paid work trial or signed agreement.
PDF is your friend. Sanitized examples are your friend. Assumptions are your friend. Editable source files are not your friend. Editable source files are a raccoon with your house keys.
Step 6: Prepare the walkthrough, not just the artifact
Most candidates over-invest in the artifact and under-prepare the explanation.
Bad move.
The artifact is only half the evaluation. The walkthrough is where you show judgment: assumptions, tradeoffs, risks, what you would validate, and what you refused to invent.
If there is a recorded take-home presentation, one-way video interview, or AI interview screen after the exercise, make the explanation transcript-safe. Use bot-readable answers: “My assumption was…,” “The tradeoff was…,” “The metric I would watch is…,” “I would not recommend implementation until…”
If you want help decoding the prompt and turning your real reasoning into answers in your own voice, NoSweatKing is built exactly for that kind of bot-shaped nonsense.
Examples: How to Push Back Without Sounding Like a Problem
You are not trying to “win” the email thread. You are trying to protect your time while keeping the process honest.
Here are practical versions.
Example 1: The PMM “quick launch plan”
They ask:
Please create a launch plan for our new feature, including messaging, audiences, channels, and three campaign ideas.
Translation: please do early GTM strategy without access to customer research, product constraints, pricing, sales motion, or the politics hiding in the walls.
Send:
Happy to complete a scoped version. Since I don’t have internal customer data or product constraints, I’ll keep this to a 90-minute directional sample: assumptions, positioning options, risks, and validation questions. I’ll avoid implementation-ready campaign copy unless we move into a paid work trial.
That response shows skill and boundaries.
You are not refusing the assessment. You are refusing to pretend incomplete context produces production-ready strategy.
Example 2: The data analyst “use our real dataset” assignment
They ask you to analyze a company export and “share insights.”
That is not a cute little homework. That is potentially real business intelligence.
Send:
I’m comfortable demonstrating the analysis approach. To keep this appropriate for an interview, could you either provide a synthetic/anonymized dataset with a defined question, or confirm this is a paid work trial if the dataset reflects current business problems?
If they say, “It’s just for evaluation,” ask for the specific question and success criteria.
Without those, you are not being tested on analysis. You are being tested on mind reading with CSV garnish.
Example 3: The engineer “small bug fix” in their repo
They ask for a pull request against a real codebase.
Send:
I’m happy to demonstrate debugging and code review skills. For unpaid interview work, I can walk through my approach, identify likely causes, and propose a patch in pseudocode or a limited diff. If you need production-quality implementation, I’d treat that as a paid trial.
Reasonable companies understand this.
Unreasonable companies will act like you insulted their grandmother by declining to fix their backlog for exposure.
Example 4: The new grad “optional challenge” before any human call
They ask for a video, cover letter, assessment, and case exercise before a recruiter screen.
Send:
I’m excited about the role. Before completing the exercise, could you confirm that submissions are reviewed by the hiring team and share what criteria you use to evaluate them? I’m also happy to provide a class project or internship sample mapped to the role requirements.
This is especially important for entry-level candidates who are already getting chewed up by resume filter bots and automated hiring screen workflows before a human ever looks.
You do not need to perform gratitude for being assigned homework by a portal.
Mistakes to Avoid
Mistake 1: Doing the full assignment to prove you care
This is how candidates accidentally train bad hiring systems.
You care. Great.
But care does not require donating a strategy sprint to a company that has not told you the salary, timeline, rubric, or whether the job is an active funded req.
Care is not the same as compliance.
Mistake 2: Treating “only 90 minutes” as a fact
Companies routinely underestimate candidate labor because they count the visible work, not the setup.
They forget:
- reading the prompt
- researching the company
- choosing assumptions
- formatting the artifact
- editing the narrative
- rehearsing the walkthrough
- worrying whether you sounded too much like yourself, a known hiring crime
A “90-minute” take-home can become five hours with better branding.
Mistake 3: Asking for permission to have boundaries
Do not write:
Is it okay if I don’t spend too long on this?
Write:
I’ll spend up to 90 minutes and focus on the core decision logic.
State the boundary like a professional constraint, not a guilty confession.
Mistake 4: Sending current or confidential employer work
Never trade one company’s secrets to impress another company.
Sanitize. Generalize. Recreate. Redact. Use public data. Use mock examples.
If they pressure you for confidential work, congratulations: the interview has successfully revealed a values problem before payroll did.
Mistake 5: Letting revisions become a second unpaid assignment
The first revision is where the trap often blooms.
They say:
This is great. Could you just add pricing, a rollout calendar, and a second version for enterprise?
That is not feedback. That is scope creep in a blazer.
Reply:
I’m happy to discuss those extensions live. Since that moves beyond the original evaluation scope, I’d prefer to cover the tradeoffs in a working session or as part of a paid trial.
Mistake 6: Ignoring what their response tells you
If a company respects a clear, modest boundary, good signal.
If they become offended, vague, or punitive, also good signal.
Not good about them, obviously. Good for you.
You just learned what working there might feel like when you ask for decision rights, realistic timelines, or basic context.
Short Checklist: Before You Say Yes to the “Optional” Assignment
Use this before you open the doc.
- Have I met a human who can explain the role?
- Do I know the salary range or level?
- Is the job real, active, and moving?
- Did they confirm whether the assignment affects moving forward?
- Do I have the work trial evaluation criteria?
- Is the task based on real company problems, data, backlog, customers, or strategy?
- Can I complete a scoped version in the stated time?
- Can I substitute prior proof blocks or a sanitized sample?
- Have I stated a time cap?
- Have I protected my candidate work product?
- Am I sending PDF/sanitized output instead of editable source files?
- Do I know the next step and decision date after submission?
- Have I set a stop point if they ask for revisions?
If you cannot check most of those boxes, pause.
Not decline automatically. Pause.
Ask better questions. Offer a bounded version. Swap in proof. Request a live working session. Suggest a paid work trial.
The goal is not to become “difficult.” The goal is to stop confusing obedience with opportunity.
A real employer can evaluate your skill without quietly repossessing your weekend.
And if their entire process depends on candidates being too anxious to ask for boundaries, that is not a hiring process.
That is a Roomba with a LinkedIn account.
