Remote Job Application Form Template
An async-first remote hiring application — time zone overlap with a conditional "make it work" prompt, a writing sample link, and a remote setup check.
We work remote and mostly async, so this application is a preview of the job: clear questions, written answers, no surprise video calls.
A doc, blog post, README, or memo — async teams run on writing.
Remote hiring keeps borrowing office-era screening — the phone screen, the culture chat — and then wondering why hires who interviewed brilliantly disappear between standups. This application screens for the actual job: working alone, writing clearly, and overlapping enough hours to hand work across time zones.
Why these fields. The writing sample link is the interview. Async teams live in documents, and one link to a README, memo, or post tells you more about a candidate's daily output than an hour of video charisma. Time zone comes in two layers — the band they sit in, and the overlap hours with your anchor (9–5 New York here; change it to yours) — because overlap, not geography, is the real constraint. The conditional prompt is this form's best idea: instead of auto-rejecting under-2-hours candidates, it reveals a question asking how they would make low overlap work. Candidates with a real handoff rhythm — written standups, recorded walkthroughs, clean end-of-day notes — turn a disqualifier into their strongest answer, and those candidates are often your best async operators. The setup question surfaces practical readiness (connection, workspace, focus habits) that office hiring never had to check, and the intro's promise of no surprise video calls attracts exactly the temperament the role demands.
What we left out. Video introductions — they tax bandwidth, penalize non-native speakers, and reintroduce the charisma bias async work is supposed to escape. Street addresses — country-level location is enough until a payroll conversation. Personality assessments — the writing sample and the low-overlap answer are behavioral evidence, not self-description.
Who uses this. Distributed startups hiring across continents, agencies staffing global client coverage, open-source companies whose culture already lives in writing, and support teams building follow-the-sun rotations where the overlap question inverts: they want less.
Make it yours. Set the anchor time zone in the overlap question to your team's center of gravity, and adjust the threshold in the Logic panel if your rhythm needs more or fewer shared hours. A webhook can push each application into your tracking stack. Review applications in writing, as the ending promises — many teams paste the writing-sample links into a shared doc and read before looking at any resume.
Consistency is the pitch. Every element here — written answers, honest constraints, no calls until they're earned — previews how your team works. Candidates who find the form refreshing are the ones who will thrive; candidates who find it cold have told you something useful too.
Frequently asked questions
Why is the writing sample required?
Async teams communicate in writing, so one real document is the highest-signal artifact a candidate can provide — far more predictive than an interview performance.
What happens when someone has under 2 hours of overlap?
A logic rule reveals a question asking how they would make it work. Great answers about handoffs and written communication regularly rescue candidates a hard cutoff would have lost.
Can we change the anchor time zone?
Yes — edit the overlap question label to your team’s anchor city and adjust the logic threshold in the Logic panel. The time zone bands are editable options too.
Does the application data reach our ATS?
Add a webhook and every submission POSTs to your endpoint in real time — signed, with retries — or export the pool as CSV whenever review begins.