The Beer Test That Almost Cost a Company Its Best Engineer

Two offers sat on Priya's desk. Both candidates were exceptional backend engineers with deep experience in distributed systems. One, based in São Paulo, had been flawless through the process: proactive, great written communication, a sharp problem-solver who documented their take-home exercise thoroughly. The other was a local candidate in the company's home city, a friendly presence in the final video call who seemed like a cultural fit, but whose written artifacts were vague and who had glossed over key details in their code sample.

The team was leaning toward the local candidate. The reason? "He felt like someone you could grab a beer with."

The Bias Hiding in Plain Sight

That phrase — the "beer test" — is one of the oldest and most insidious hiring heuristics. It masquerades as cultural alignment but functions as affinity bias: a preference for people who feel familiar, who share a background or communication style, who won't disrupt the social comfort of the existing team. In an office, the beer test has always been flawed. In a remote-first company, it is actively dangerous.

Priya, the hiring manager, recognized the trap. The environment itself had become a filter. The São Paulo candidate had demonstrated the exact skills that make remote work succeed: self-direction, asynchronous clarity, the discipline to document decisions so others can act on them without a meeting. The local candidate had performed well in a synchronous interview — a format that rewards verbal fluency and social ease — but left a thin paper trail.

Remote hiring isn't about moving your old process to video calls. It's a different discipline. If your process only assesses who performs best in a live conversation, you will hire people who thrive in meetings, not those who thrive in the async, document-heavy, outcome-oriented reality of distributed work.

Redesigning the Signal

Priya pushed back. She made the offer to the candidate in São Paulo. It was the right decision, and it set a precedent: the hiring process would be redesigned to find the skills that actually matter in a distributed environment.

The company began by rewriting its job descriptions. A generic, buzzword-filled ad attracts generic candidates. A remote job description must sell the opportunity while setting clear expectations about how work happens. They started including explicit details: "We are an async-first team; strong written communication is critical." "We have a 4-hour overlap window (10 AM - 2 PM ET) for collaboration, but flexible hours otherwise." "Home office stipend provided."

They replaced phone screens with short, paid work samples. A product manager might analyze a brief scenario and write a one-page recommendation. An engineer reviews a piece of code and suggests improvements in writing. Customer support candidates handle sample tickets in writing. The exercises take one to three hours, are directly relevant to the job, and are compensated. The goal isn't just to evaluate the output — it's to see how the candidate asks clarifying questions, structures their thinking in writing, and meets a deadline.

Structure Over Charisma

Interviews got a rubric. Remote interviews are notoriously prone to bias based on video quality, accent, or comfort level on a one-on-one call. A rubric forces interviewers to score candidates on specific, job-relevant competencies: technical skill, written communication, async collaboration, autonomy and ownership, alignment with values. For async collaboration, the rubric asks: "Demonstrates ability to gather input and make progress without synchronous meetings; writes clear updates and documentation." Interviewers score independently before discussing.

"Using a structured rubric transformed our hiring," an engineering manager at a fully remote fintech later said. "It stopped us from hiring the 'most charismatic' person and helped us find people who were genuinely great at the job. It also made feedback discussions much more objective and fair."

The Cost of Comfort

The beer test feels harmless. It feels like team cohesion. But in a distributed company, cohesion doesn't come from shared drinks — it comes from shared protocols. When a team relies on hallway rapport, remote members become second-class citizens. Decisions happen in the room. Context stays in the room. The people who can't be in the room — whether because of geography, caregiving, disability, or simply a different working style — stop being full participants.

Priya's decision didn't just save one hire. It forced the organization to confront what it was actually optimizing for. The São Paulo engineer went on to become a technical lead, mentoring others across three time zones. The local candidate, hired elsewhere, struggled in a role that demanded the very written discipline he hadn't demonstrated.

The beer test didn't die that day. Biases rarely do. But it got named, documented, and designed against. And that, in a remote-first company, is how you build a team that ships.

This is one episode in a much longer story. For the full account of building high-output remote teams, read “High-Output Remote Teams” by Joshua Snyder on MixCache.com.