Writing as a Hiring Signal

In an in-person loop, writing is one round. In a remote loop it's the medium, and it's being read the whole way through — often by people who never speak to you.

The take-home README is graded, frequently more carefully than the code. The version that works is short and has four parts: what you built and how to run it, the decisions you made and why, what you deliberately left out and what you'd do with another day, and what you'd change to make it production-ready. That last part is where seniority shows — knowing what's missing is a stronger signal than having built more of it. If the brief was underspecified, put your interpretation of it at the top; scoping is what they're testing.

Application and screening answers. "Why are you interested in us" answered in three specific sentences beats two generic paragraphs. Someone reads these, and at small companies it's often a founder.

Async exercises. Some companies replace or supplement the design round with a written one — a proposal, a review of an existing design, a response to a scenario. Structure carries most of the score: a summary at the top, the recommendation before the analysis, headings that let someone skim, and explicit assumptions. Bury the recommendation in paragraph nine and it doesn't matter that it was right.

The incidental writing counts too. How you reschedule, how you follow up, how you answer a clarifying question in email. Brief, clear, and prompt is the whole standard, and it's a live sample of what working with you async looks like.

The mechanics that make writing land are unglamorous: conclusion first, short paragraphs, no throat-clearing, concrete numbers, and one pass to delete a third of it. And where AI drafted it, edit it into your own voice — reviewers at these companies read a lot of generated text and recognise it instantly.

Remote roles across a US/EU time gap live or die on written communication, so companies screen for it hard and mostly without saying so. It's also asymmetric: strong writing gets you an interview from a cold application, and weak writing quietly loses candidates whose code was fine.

• In a remote loop every written artefact is evidence, including scheduling emails.
• The take-home README is scored: how to run it, decisions, deliberate omissions, what production would need.
• Stating what you left out and why is a stronger senior signal than shipping more features.
• Put your interpretation of an underspecified brief at the top — scoping is the hidden rubric.
• Written exercises are scored on structure: recommendation first, assumptions explicit, skimmable headings.
• Specific short answers to "why us" outperform long generic ones, and a founder is often reading.
• Conclusion first, then delete a third; prompt and brief beats polished and late.
• Rewrite AI-drafted text in your own voice; reviewers at these companies spot the default register.