Update opening paragraph, split recommendations (#468)

Closes #465

CRITERIA.md

@@ -2,16 +2,7 @@
 
 In order to be accepted into this list, the company's interview process **must not** do the following in **any** step of the interview process:
 
-- Use CS/algorithmic questions/brainteasers/riddles/puzzles/etc that DO NOT relate to the job the candidate is applying for
+- Ask CS trivia/brainteasers/riddles/puzzles/etc that DO NOT relate to the job the candidate is applying for
 - Use live-coding sites like HackerRank or LeetCode
 
-The only exceptions to the above is where CS knowledge is a **requirement** of the role.
+The only exceptions to the above is where CS knowledge is a **requirement** of the role. For example, if you are being hired to write a package manager, you probably need to understand DAGs.
-
-## Recommendations for companies that do "whiteboard" interviews
-
-- Instead of using questions that bear no resemblance to the role, adapt the question so that it does. A screening question can be easily adapted so that it applies a "real world" requirement
-- Take-home exercises can be good. Please try to:
-  - time-box them (e.g. under 4 hours)
-  - only allow use of stdlib
-  - pay the candidate for their time
-- Give the candidate options: Some candidates might not have the time necessary to complete a take-home exercise. In those scenarios, allow the candidate to take their laptop in to perform a shorter exercise (e.g. pair program on a small issue)

README.md

@@ -1,17 +1,20 @@
 # Hiring Without Whiteboards
-A listing of companies (or teams within companies) that don't do typical, CS based "whiteboard" interviews. Using sites like [HackerRank](https://www.hackerrank.com) _probably_ fall into that category and won't be accepted. The companies and teams listed here instead use interview techniques and questions that resemble day-to-day work – for example pairing on a real world problem, or a paid/unpaid take home exercise.
+
+A listing of companies (or teams) that don't do "whiteboard" interviews. "Whiteboards" is used as a metaphor, and is a _symbol_ for the kinds of CS trivia questions that are associated with bad interview practices. Whiteboards are not bad – CS trivia questions are. Using sites like HackerRank/LeetCode _probably_ fall into a similar category.
+
+The companies and teams listed here use interview techniques and questions that resemble day-to-day work – for example pairing on a real world problem, or a paid/unpaid take home exercise. Read (and contribute to) [our recommendations](RECOMMENDATIONS.md) for ways to conduct better interviews.
 
 ### tl;dr
-- Discussing a real world problem with the help of a whiteboard is 👍
+- Discussing a real world problem (with or without whiteboard) is 👍
-- Solving basic CS questions, technical puzzles, riddles, brainteasers (with or without whiteboard) is 👎
+- Solving CS trivia, technical puzzles, riddles, brainteasers (with or without whiteboard) is 👎
 
-<a href="https://twitter.com/dhh/status/834146806594433025?lang=en"><img src="https://i.imgur.com/xJV6cF4.png" width=500 /></a>
+<a href="https://twitter.com/dhh/status/834146806594433025?lang=en"><img src="https://i.imgur.com/xJV6cF4.png" width="500" /></a>
 
-Please open a PR to be added.
+Please open a [PR](https://github.com/poteto/hiring-without-whiteboards/pull/new/master) to be added.
 
 ### Duds
 
-If you've been through an interview with one of these companies recently, and your experience suggests otherwise from their description, please open a PR to remove them from this list.
+If you've been through an interview with one of these companies recently, and your experience suggests otherwise from their description, please open a [PR](https://github.com/poteto/hiring-without-whiteboards/pull/new/master) to remove them from this list.
 
 ### I want to sort/filter/group by X!
 

RECOMMENDATIONS.md

@@ -0,0 +1,12 @@
+# Recommendations for companies that do "whiteboard" interviews
+
+Have a suggestion? Please contribute to this doc!
+
+- Instead of using questions that bear no resemblance to the role, adapt the question so that it does. A screening question can be easily adapted so that it applies a "real world" requirement
+- Take-home exercises can be good. Please try to:
+  - time-box them (e.g. under 4 hours)
+  - only allow use of stdlib
+  - pay the candidate for their time
+- Give the candidate options:
+  - Some candidates might not have the time necessary to complete a take-home exercise. In those scenarios, allow the candidate to take their laptop in to perform a shorter exercise (e.g. pair program on a small issue)
+  - Some candidates prefer the whiteboard when discussing a problem, let them