Written By Ankush Gupta, Fractional CMO, Fameninja ORM Management Company
The scheduling thread was longer than the interview would have been. We were trying to put a first call in the diary with someone whose written submission was the strongest thing in the pipeline, and the only slot that worked on both sides was late enough on theirs that they joined with the lights off behind them. The call was flat. We moved on. Weeks later I opened that submission again, because we were writing a brief and I wanted the phrasing they had used. It was still better than what we were getting. Nothing said on the call had contradicted it. We had trusted the live signal because it was live.
That is not really a story about one candidate. It is about the order we had put things in. At FameNinja almost none of the actual job happens in a shared hour, and yet the shared hour was the first thing we asked anyone to produce.
The calendar was our first real screen, and nobody had designed it
Job posts get audited and interview questions get argued over. Scorecards get rewritten every time a hire goes wrong. The scheduling link never gets looked at, and it is usually the first hard gate a candidate has to clear. To pass it they need an hour that overlaps with yours, a room quiet enough to think in, a connection that holds video, and a day that can absorb being interrupted in the middle. Read that back as a list of things people have unequal access to. Then ask how much of it the work actually requires.
For us, the answer was almost none of it. Search cleanup, review handling, PR production, the automation pipelines we build in n8n, the ongoing care of a large publishing network. That work is written down, queued, picked up and handed over. Someone being awake at the same time as me is convenient. It is not the skill.
We changed the order before we changed anything else
The written work now comes first. A candidate gets a small piece of real work lifted from our SOPs, stripped of client detail, and they send it back on their own clock. We score it against what we would expect from someone already on the team. The call comes after that, and it is a conversation about the thing they have already made rather than a performance in front of strangers.
What this surfaced is people the old order lost quietly. The qualities our work pays for are patience with a long document and a habit of noticing the detail that does not fit. Saying plainly which step of a process will fail, before anyone runs it, is worth more to us than saying anything quickly. That shows up on paper. On a video call it reads as slowness, and slowness in a live room gets punished by everyone in it, including the person doing it.
An asynchronous interview only works if the job is asynchronous too
There is a way to get this wrong and we found it. You can run a carefully written hiring process and then make every real decision on a call, in which case the exclusion has not gone anywhere. It has moved into the job. The person you hired on the strength of their writing discovers that decisions happen in a window they cannot reach, and that what appears in writing afterward is somebody’s summary of a room they were not in.
The correction was not a policy document. It was a rule about where a decision becomes real. A decision that exists only in a call has not happened yet. It goes into the task, with a named owner and a written next step, or it does not count, and we put the chasing and escalation for that into n8n because a rule nobody follows up on is a preference. This is the part HR tends to treat as an operations problem and operations tends to treat as an HR problem.
The tradeoff
Written-first hiring is slower at the front and heavier on the people running it. Someone has to build the tasks, keep them current as the work changes, and actually read what comes back, which is effort the old process skipped by putting a face in front of us for an hour and calling that evidence. It also carries a bias of its own. It rewards people who write clearly, and clear writing is taught very unevenly. We have not solved that one. What we do is read a submission for what the person noticed rather than how gracefully they said it, which helps and does not fix it.
Some roles really are live. Crisis work is one. So is a founder who has just found something about themselves on the first page of Google and wants to talk about it now. For those, the live round is the work itself, so we kept it, and we kept it nowhere else.
None of this began as an inclusion initiative, and I would be overclaiming if I dressed it up as one. It began because we kept losing good people to a diary. Once you write down what a scheduled interview quietly demands, and next to it what the work demands, the gap between the two lists is hard to stop seeing. Fix the order first. The policy can catch up.
About the Author
Ankush Gupta is a Fractional CMO at FameNinja, where he works on online reputation management, digital PR and marketing automation.
