Use the company list to choose whom to contact
Before agreeing to a take-home assignment, ask whether you'll discuss your solution with the people you'd work alongside. Hiring Without Whiteboards helps you find employers whose reported interviews include practical work and conversations about it. The English README organizes company links alphabetically, with locations and brief process descriptions. That makes it useful when irrelevant algorithm puzzles are a reason you'd decline an interview. Treat each description as a lead to confirm with the recruiter. The list's introduction explicitly asks candidates to report mismatches.
The checkout in our sandbox was just 0.2 MB across 15 files. Reading the directory needs no local runtime, so you can browse it before deciding whether to contribute. Its admission criteria reject unrelated computer-science puzzles and screening through sites such as HackerRank or LeetCode. They allow exceptions when the knowledge belongs to the role, using package-manager work as an example. That's a sensible distinction: a discussion of a dependency graph can be relevant engineering work. The presence of a board or a coding editor doesn't settle the question.
What happened when we ran it
Our run installed commit 9b60360 with Yarn in 5 seconds, adding 243 packages and leaving 25 MB on disk. We cloned it on October 2, 2026, in a fresh Debian sandbox with 3 CPUs and 8 GB of RAM, using the lab-node:22 image. The container was unprivileged and had no secrets. Installation succeeded. This measures the repository's local setup under those conditions, without establishing anything about an employer's interview experience.
The test step succeeded in 1 second. Our harness skipped the build because it found no build script or target, so there is no successful build to report. The checkout contained approximately 1 line of source, and the scan found 1 CI workflow file, no Dockerfile, and no tests directory. Those findings describe a repository centered on documents. The supplied measurements give no test count or evidence that individual company descriptions were checked against current recruiting practices.
Admission allows take-home work without requiring payment
The recommendations for employers ask them to compensate candidates and limit take-home work. They also suggest offering a shorter pairing exercise to someone who can't spare the time. These are recommendations, however. The admission criteria don't require payment or a fixed time limit. If unpaid work is your reason for avoiding a hiring process, membership here won't answer that concern. Ask what the exercise involves, whether you can stop at the agreed limit, and whether the employer pays for your time before accepting it.
Installing the contributor environment consumed 25 MB in our sandbox, a modest local cost compared with the commitment a candidate may make to an assignment. Keeping the list easy to maintain doesn't make its listed processes equally manageable. The README includes both pairing and take-home exercises, and practical live coding remains possible. Developers who freeze when someone watches them code should confirm whether they can work asynchronously. Someone caring for a family may prefer a scheduled conversation over an open-ended project, even if both employers satisfy the directory's criteria.
Corrections show why you must confirm the exact role
The last repository push was September 24, 2026. The Betterment correction, closed in August, came from a candidate describing a lengthy process and heavily scripted behavioral questions. The September link cleanup addressed rebrands and removed a defunct company. These are useful signs of maintenance, and concrete reasons to distrust an entry as a permanent promise. They also show what volunteer editing can repair: a candidate reports a discrepancy, or a contributor notices that a link no longer leads where it should.
Our scan found 1 CI workflow file, but corrections to interview descriptions still need people with recent experience. The contribution format requires a website, location, and brief account of the process, without a required verification date. GitHub reported 52,558 stars and 10 open issues and PRs in our October check. The latest-release endpoint returned no release, which is unsurprising for an edited directory. Recent pushes and substantive corrections support continued maintenance. Neither a small queue nor a passing check proves that the company you're considering follows its entry today.
Choose a different resource when interview style isn't your filter
Remote In Tech is a better starting point when working location decides whether you'd apply: its repository backs a directory of remote-friendly tech companies. Awesome Remote Job suits someone looking for job boards and broader remote-work resources. Reverse Interview helps you prepare questions about the role and engineering team once a conversation is booked. None promises the same interview-style filter. Choose the resource that answers the decision immediately in front of you, rather than assuming a company directory also evaluates the job itself.
Our 5-second install makes contributing easy to consider, while ordinary readers can go straight to the documents. I'd use Hiring Without Whiteboards to build a shortlist, then spend my attention on the exact vacancy. When an entry is wrong, the removal guidelines give you a way to explain the mismatch and let the original contributor respond. Before reserving time for an interview, send the recruiter the entry and ask: does this description apply to this role, and what work will you expect me to do before we meet?