TopGit
GitHub Repo Review

Hiring Without Whiteboards: skip the whiteboard interview

poteto/hiring-without-whiteboards
HTopGit review image for poteto/hiring-without-whiteboards
Review by Topgit.dev for poteto/hiring-without-whiteboards, with GitHub repository stats and README context.
Quick verdict

Hiring Without Whiteboards is worth a scan before you accept any onsite loop, but it's a crowdsourced pointer list, not a vetted directory. Reach for it when you want candidate company names to research before applying; skip it if you need a guarantee that an entry's process is still accurate today, since anyone can add an entry and nobody re-verifies old ones automatically.

Stars
★ 53.2k
Forks
⑂ 4.0k
Language
JavaScript
License
MIT
Topic
—
Updated
Sep 2026
Homepage
—
GitHub

Why whiteboard interviews frustrate developers

Whiteboard interviews get blamed for a lot, but the real complaint is narrower: timed algorithm puzzles and riddle-style trivia don't predict whether someone can do the actual job, whiteboard or laptop. This repo's own framing draws that line explicitly — a real-world problem walkthrough is fine with or without a marker in hand, while brainteaser-style trivia is the actual red flag, marker or not. The harder problem for a job seeker is finding out which category a company falls into before you've already booked the interview loop.

What Hiring Without Whiteboards is and how it works

Hiring Without Whiteboards is a GitHub-hosted, alphabetically organized list of companies and teams that use interview formats other than whiteboard algorithm puzzles — think take-home projects, paid trial days, or pairing on a real problem. Each entry names the company, its location or remote status, and a short note on what the actual interview steps look like, added and edited by anyone via pull request.

What hiring formats these companies use instead

  • ✓Alphabetical sections (0-9, A-C, and onward) group company entries so you can scan a letter range instead of one long scroll.
  • ✓Each listing typically pairs the company name and location with a short description of the actual interview stages — phone screen, take-home, onsite pairing, and who you meet.
  • ✓Take-home projects and paid or unpaid trial work show up repeatedly as the stand-in for whiteboard rounds, sometimes followed by a walkthrough discussion of the code.
  • ✓Pair-programming sessions on a realistic problem appear as another common substitute, done either remotely or on-site with an engineer.
  • ✓A 'Duds' section exists specifically for flagging companies whose process has reportedly reverted to old-style trivia interviews.
  • ✓A linked RECOMMENDATIONS.md file collects the maintainers' suggestions for running a better interview process, separate from the company list itself.
How this repository's GitHub stars have grown over time. Source: star-history.com.View the star history ↗

How developers use this list in their job search

  • •Skim the list before submitting an application to see whether a target company already appears with a description of its process.
  • •Search by letter section or use browser find (Ctrl/Cmd+F) for a specific company name rather than scrolling read-only through hundreds of entries.
  • •Cross-reference an offer or a scheduled onsite loop against the listed steps to gauge whether the day matches what's described here.
  • •Open a pull request to add a company after a good interview experience, or to flag one in the 'Duds' section after a bad one.

Strengths

  • ✓Entries go beyond a company name — most include location/remote status and a real description of the interview steps, not just a link.
  • ✓The alphabetical, section-by-section structure makes a list with hundreds of companies genuinely browsable instead of one giant unsorted table.
  • ✓It's actively open to correction: the 'Duds' section gives anyone a direct path to flag an entry that no longer matches reality.
  • ✓MIT-licensed and hosted on GitHub, so the raw list is easy to fork, search locally, or repurpose in your own job-search tooling.

Limitations to keep in mind when browsing the list

  • △Entries have no timestamp or 'last verified' date, so there's no way to tell from the list itself whether a company's process described here is from last month or several years ago.
  • △Coverage is whatever contributors happened to submit — well-known companies that never got a pull request simply aren't listed, and there's no guarantee the list is complete for any industry or region.
  • △It's a flat markdown list with alphabetical headers. There's no search, no filter, and no tagging by interview format, so finding 'companies that do pair programming' means reading entries one by one.
  • △The 'Duds' section relies on someone noticing a company's process regressed and opening a PR about it — a stale, no-longer-accurate positive entry can sit uncorrected for a long time.

Other resources for finding alternative hiring processes

Glassdoor interview reviews — search a specific company directly for recent, dated candidate accounts of what its interview loop actually involves, something this list's entries don't timestamp.Blind (teamblind.com) — an anonymous community where candidates and employees discuss current interview processes and compensation, useful for cross-checking whether an entry here is still accurate.

Frequently asked questions

What is the Hiring Without Whiteboards list?

Hiring Without Whiteboards is a GitHub-hosted, community-edited list of companies and teams whose interview process uses take-home projects, pairing sessions, or work samples instead of whiteboard algorithm puzzles, with a location and short process description for each entry.

How many companies are listed in Hiring Without Whiteboards?

Hiring Without Whiteboards doesn't publish a running total — the list has grown into a large, alphabetically organized collection spanning many countries and company sizes, and it keeps expanding as contributors submit pull requests.

What types of interviews do these companies use instead of whiteboards?

Listed companies favor formats like paid or unpaid take-home projects, pair programming on a realistic problem, work-sample reviews, and system-design discussions, usually paired with a behavioral or culture-fit conversation — the exact mix is written into each company's own entry.

Can I contribute a company to the Hiring Without Whiteboards list?

Hiring Without Whiteboards accepts new entries through a GitHub pull request — the README asks contributors to add the company's name, location, and a short description of its actual interview steps.

Are all companies on the list still using non-whiteboard hiring?

Not necessarily — Hiring Without Whiteboards is community-maintained with no verification pass or update date on entries, so a company's process may have changed since it was added; the README's own 'Duds' section exists for reporting entries that no longer hold up.

Is the Hiring Without Whiteboards list free to use?

Hiring Without Whiteboards is free to browse on GitHub and released under the MIT license, so anyone can read, fork, or reuse the list without payment or a signup.

Who should try it — and who should skip

Try this if you're actively job-hunting as a developer and want a head start on which companies to research before you apply, or if you're building your own short list of realistic interview-style employers. Skip it if you need current, verified data on a specific company's process right now — cross-check any entry against Glassdoor or a direct question to your recruiter before assuming it still holds, since nothing here is dated or re-confirmed automatically.

Related repositories

Source & attribution

Based on the poteto/hiring-without-whiteboards GitHub repository (github.com/poteto/hiring-without-whiteboards) and its README.

GitHub data · last synced Aug 14, 2026Reviewed by Henry
← Back to TopGit

Want a second opinion on hiring-without-whiteboards?

Ask an AI that can read this page — one click and you get its take on hiring-without-whiteboards.

GitHub