poteto/hiring-without-whiteboards

What this is

A curated list of companies and teams that avoid "whiteboard" interviews in the CS-trivia sense. The README treats the whiteboard as a symbol for puzzle- and trivia-based screening, including platforms such as HackerRank and LeetCode, rather than the physical board itself. Listed employers describe interview processes built around day-to-day work: pairing on a real problem, a take-home exercise, a paid trial, or a discussion of a candidate's code README lines 1–6.

The list is organized alphabetically by company name (0–9, A–C, D–F, and so on) and each entry carries the company's office locations and, where provided, a short description of its interview loop. It serves job seekers evaluating employers and teams that want examples of alternative hiring practices.

Browse and contribute

Open the company list and find the alphabetical section for a company you are interested in. Each line follows the form: company link, locations, then a short note on the process. For example, one entry describes a take-home assignment followed by a design discussion based on it. Entries are descriptive, not ranked, so read the process note rather than the position in the list.

To add a company, open a pull request against the repository PR entry point. If your recent interview with a listed company contradicts its description, the README asks for a pull request to remove it Duds section. The repository also links a set of interview recommendations for teams designing better loops.

Practical constraints

• The list is community-maintained and descriptive. A company's inclusion reflects a contributor's account of its process, not an audit or a guarantee that every team or role follows the same loop.
• Process descriptions vary in detail. Company links can change or go stale, so verify the current role and process on the employer's careers page.
• The project is a static Markdown list and does not run as an application; it is read on GitHub and edited through pull requests.
• Released under the MIT license.

HotRepo's take

The repository shows sustained interest on Hacker News across several years: 2020 discussion drew 481 points and 450 comments Hacker News 2020, and the 2017 thread drew 423 points and 363 comments Hacker News 2017. That is a substantial, recurring conversation around one list, which fits the project's role as a shared reference rather than a software product.

Comments in the 2020 thread, however, show that the underlying category is contested. Readers debated whether take-home projects are fairer than whiteboards or merely shift the time cost onto candidates, and one commenter described a bad experience with a listed company in which the first round used a timed HackerRank-style question take-home debate. These are individual opinions, not verified findings. They do support reading each company's entry as a starting point for checking the actual loop, not as a certification. The single HotRepo daily snapshot on 2026-11-01 recorded a JavaScript-language rank of 7 and 38 new stars snapshot; one daily record is not enough to describe a trend.