I have a special kind of shame reserved for the hiring process we once called “async-friendly.”
We were a small team hiring a customer operations lead. Everyone was busy, calendars were a crime scene, and we wanted to avoid dragging candidates through endless interview rounds. Noble goal. Gold star. Put it on the fridge.
So we built what we thought was a humane alternative: an async collaboration exercise.
One shared doc. One realistic scenario. A few comments from the team. Candidates could respond “on their own schedule.”
Except “on their own schedule” quietly turned into: please be available at 9:42 p.m. on Thursday, 7:18 a.m. Friday, and once more on Saturday because our head of product had a follow-up thought while making pancakes.
We told ourselves we were testing collaboration.
We were testing whether a candidate would behave like they already worked here, without pay, context, authority, or health insurance.
That is not a candidate screening process. That is unpaid onboarding wearing startup cologne.
The exercise looked reasonable until the calendar started leaking
The original task was simple:
“Review this mock customer escalation and propose a response plan. Please spend no more than 90 minutes.”
Not terrible. A customer ops lead should be able to show judgment under ambiguity. A realistic work sample can beat a fake culture fit interview where everyone pretends “tell me about yourself” is a diagnostic instrument.
The problem was what happened after the task landed.
Our support manager added: “How would you revise the macro library?”
Our product lead added: “What would you change in onboarding to prevent this?”
I added: “Can you think about how this scales with enterprise customers?”
Suddenly the 90-minute exercise had become:
- incident response
- support operations design
- product feedback triage
- customer segmentation
- change management
- executive communication
- maybe light therapy for founders who can’t write requirements
The candidate, Maya, answered everything. Calmly. Specifically. Better than we deserved.
Then we dinged her internally for being “a little slow to engage in the doc.”
She had responded within 18 hours.
We had not told her there was a response-time score.
That is how a hidden interview scorecard becomes a tiny machine for humiliating normal adults with jobs, kids, parents, commutes, sleep needs, and the tragic defect of not refreshing a Google Doc like it owes them money.
Takeaway: cap the task before the task grows legs
When you get an “async” unpaid take-home assignment, reply with a polite boundary before you start:
“Happy to complete this. To keep the work sample focused, I’ll spend up to 90 minutes and will note assumptions where more context would be needed. If the team wants deeper follow-up or live iteration beyond that, I’m happy to discuss a paid work trial or a scheduled live working session.”
This does three things:
- It confirms you are cooperative.
- It makes scope creep visible.
- It prevents the company from pretending your weekend was implied.
The boundary is not rude. The boundary is a fence around your dignity.
“Async” became recruiter-speak for “always available”
Here is the dirty little hiring trick: words like “async,” “ownership,” “high agency,” and “strong culture fit” can mean reasonable things.
They can also mean: we want someone who absorbs organizational chaos without asking what time it is.
In our case, “async” meant different things to different people:
- The recruiter meant: “No need to schedule another call.”
- The hiring manager meant: “Show how you think in writing.”
- The product lead meant: “Let me test a real backlog issue for free.”
- The founder, unfortunately me, meant: “Let’s see if they keep momentum without hand-holding.”
Maya heard: “Complete a contained exercise.”
She was the only one behaving like the written instructions mattered.
That is the candidate’s daily problem in modern hiring. The stated process is one thing. The ritual underneath is another. Then the rejection email says “not enough signal,” as if the company didn’t bury the signal under twelve unspoken expectations and a Slack-shaped fog machine.
If a company wants responsiveness, it should define responsiveness.
If it wants strategic thinking, it should ask a strategic question.
If it wants free consulting, it should at least have the courage to invoice itself for the embarrassment.
Takeaway: ask what “good” looks like before you perform it
Before starting an async exercise, ask for the scorecard in plain language:
“To make sure I aim at the right target, what will the team be evaluating most: quality of recommendation, written communication, speed of response, stakeholder thinking, or technical depth?”
If they say “all of the above,” congratulations, you have found the buffet of ambiguity.
Follow up with:
“Helpful. Since the recommended timebox is 90 minutes, I’ll prioritize the first two and briefly flag the others as assumptions or next steps.”
That sentence is magic because it forces tradeoffs back where they belong: on the employer.
You are not refusing to be excellent. You are refusing to be infinite.
The strongest candidate did not write the longest answer
One candidate before Maya submitted eight pages.
Eight pages for a “90-minute” exercise.
The doc had diagrams. Escalation tiers. A customer-health scoring model. A sample dashboard. Probably a small municipal charter somewhere in the appendix.
The team loved it.
Of course we did. Someone had delivered a free consulting interview task with better formatting than our internal operating plan.
But when we actually compared the work to the role, Maya’s shorter answer was stronger.
She did something subtle: she separated immediate action from system repair.
Her response looked like this:
- First 24 hours: stabilize the customer, assign owner, confirm facts, stop duplicate replies.
- Next 7 days: identify pattern, update macros, add escalation trigger.
- Next 30 days: measure recurrence, review onboarding gap, assign cross-functional owner.
- Risks: overpromising, blaming support, solving product gaps with apology theater.
That was the job.
Not making the prettiest artifact. Not donating a full operating model. Not proving she would bleed in brand colors.
The issue was our team had not agreed on the difference between “good work sample” and “large work sample.” Hiring teams confuse those constantly. They call it rigor. Sometimes it is just appetite.
Takeaway: submit proof blocks, not a hostage note from your weekend
A good take-home should show judgment, not word count.
Use proof blocks inside the assignment:
“In a prior escalation queue, I reduced repeat contacts by 18% by separating urgent customer recovery from root-cause fixes. I’m applying the same pattern here: stabilize first, then prevent recurrence.”
That one paragraph does more than three pages of generic frameworks.
A proof block connects:
- the problem they gave you
- the action you recommend
- the result you have produced before
- the judgment behind your tradeoff
If you already built a role-evidence map for the job, pull from it. Match your examples to the work they actually need done. If an automated hiring screen or one-way video interview comes before the take-home, tools like NoSweatKing can help decode questions and shape answers in your own voice, but the same principle applies here: your real experience needs subtitles the system can read.
We accidentally punished the candidate who respected the timebox
Here is where the founder confession gets extra crispy.
When we reviewed the submissions, someone said:
“Maya’s answer is clean, but it feels less invested.”
Less invested.
Because she followed the 90-minute instruction.
Because she did not turn a hiring exercise into a weekend residency.
Because she did not confuse unpaid labor with enthusiasm.
This is one of the most insulting little moves in modern hiring: companies set a limit, then emotionally reward the people who exceed it.
“Please spend no more than two hours.”
Then they hire the person who spent nine.
That does not identify the best candidate. It identifies the candidate with the most available unpaid time, the least current leverage, or the strongest fear that boundaries will be misread as attitude.
And yes, sometimes people overdeliver because they want the job. That is human. The villain is not the candidate who writes the eight-page deck. The villain is the process that turns desperation into a scoring advantage.
Takeaway: make the timebox visible in the submission
At the top or bottom of your take-home, write:
“Completed within the requested 90-minute timebox. I focused on the highest-leverage decisions and noted where I’d go deeper with internal data or a live stakeholder discussion.”
This protects you in two ways.
First, it tells a sane hiring team you can prioritize.
Second, it tells an insane hiring team you are not the right free-labor appliance for their kitchen. That is useful information.
If they penalize you for respecting their own instructions, they were not evaluating skill. They were evaluating compliance under fog.
The follow-up comments were the real interview — and nobody admitted it
After Maya submitted, the team left comments in the doc.
Some were fair:
“What would you do if product disagreed with your root cause?”
Some were vague:
“Can you make this more strategic?”
Some were basically unpaid roadmap extraction:
“What are the top five lifecycle changes you’d recommend based on this?”
Maya replied to a few. Then she stopped.
At debrief, someone asked whether that showed “limited ownership.”
No. It showed she had a spine and possibly dinner plans.
The moment a company starts asking layered follow-up questions inside an async doc, the process has changed. It is no longer just a take-home. It is an interview round. Maybe several. Just with worse boundaries and no calendar invite.
If the team wants back-and-forth, schedule it. If the team wants deeper work, pay for it. If the team wants to test collaboration, put the candidate in a defined live working session with a clear start, stop, and evaluation criteria.
A comment thread is not a culture. It is a hallway with no exits.
Takeaway: convert comment creep into a scheduled conversation
When follow-ups start multiplying, use this script:
“These are useful questions. To keep the async exercise from expanding beyond the original scope, I’m happy to discuss them in a 30-minute follow-up and walk through how I’d approach the tradeoffs live.”
If they push for written answers anyway:
“I can answer one additional priority question in writing. For the broader set, I’d recommend a live discussion or paid extension since they move into deeper operating recommendations.”
You are not being difficult. You are converting shadow labor into a visible process.
What I would build now if I could redo that hiring process
If I were designing that exercise today, I would make five changes.
First, I would give a real timebox and honor it.
Not “90 minutes” while secretly loving the person who builds NATO for Zendesk. Actually 90 minutes.
Second, I would define the scorecard:
- diagnosis quality
- prioritization
- customer judgment
- communication clarity
- awareness of cross-functional dependencies
Third, I would ban extra team comments until after scoring.
No drive-by “quick questions” from people who forgot they were participating in a hiring process and not browsing a snack table.
Fourth, I would offer a live alternative.
Some excellent candidates think better in conversation than in polished documents. Others are great async. The job probably needs both, but the interview should not pretend one format equals truth.
Fifth, I would pay for anything that touches real company strategy.
If the work can be used, sold, shipped, prioritized, copied into a roadmap, or forwarded to the board with “interesting thoughts,” it is work. Pay for work. Revolutionary stuff. Alert the business schools.
Takeaway: use the “could they use this?” test
Before doing any take-home, ask yourself:
“Could this company use my output even if they do not hire me?”
If yes, protect it.
Options:
- Use a fictionalized version.
- Blur exact recommendations and focus on process.
- Include assumptions instead of proprietary details.
- Offer a paid work trial for deeper analysis.
- Suggest a live working session using a mock scenario.
A legitimate skills assessment does not require you to hand over a finished operating plan.
Your boundary is part of your signal
Candidates worry that boundaries make them look uncommitted.
Bad companies will absolutely read them that way.
Good.
A company that treats a basic time boundary as a character flaw is not hiring a teammate. It is shopping for an endlessly refillable human battery.
The point is not to refuse every unpaid take-home assignment. Sometimes a contained work sample is the cleanest way to show what a resume cannot. Especially if resume filter bots already flattened your career into keyword soup and an AI recruiter decided your last title was not spiritually aligned with the job post.
The point is to stop letting the exercise mutate while you are inside it.
Here is your simple rule:
Do the test they described, not the job they failed to staff.
And if the test changes, name the change.
Not with rage. Not with a 1,400-word manifesto in the comment thread. Save that for me; I have a blog and unresolved feelings.
Use calm, adult language:
“This seems to be expanding beyond the original exercise. I’m still interested, and I’d be glad to continue in a scoped live session or paid trial.”
That sentence will not save every opportunity.
It will save your calendar from companies that confuse hiring with harvesting.
The final field note
We did not hire Maya.
We should have.
A month later, the person we hired burned out trying to solve the exact cross-functional mess Maya had identified in 90 minutes. The eight-page deck had looked more impressive. Maya’s answer had been more correct.
That is the absurdity of modern hiring in miniature: the system asks for judgment, then rewards overproduction. It asks for collaboration, then hides the rules. It asks for culture fit, then defines culture as tolerating confusion with a smile.
If you are facing one of these async exercises today, remember this:
You are allowed to be generous without being exploitable.
You are allowed to show skill without donating strategy.
You are allowed to want the job and still protect the person who has to live your life if you do not get it.
The hiring ritual may not come with dignity included.
Bring your own.
