diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 2b9cdfc..a00365a 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -7,7 +7,7 @@ Please send a pull request if you have any [additions, updates](#additions-or-up
 ## Additions or updates
 1. The pull request adheres to the repository's
     [Code of Conduct](/CODE_OF_CONDUCT.md)
-1. The company fits the criteria
+1. The company fits the [criteria](/CRITERIA.md)
 1. You add the company in alphabetical order in the list
 1. You submit the company with a website
 1. You submit the company with a location
@@ -16,9 +16,7 @@ Please send a pull request if you have any [additions, updates](#additions-or-up
 ## Removals
 1. The pull request adheres to the repository's
     [Code of Conduct](/CODE_OF_CONDUCT.md)
-1. Read the following:
-    - The use of the term "whiteboards" is metaphorical - if the interview calls for CS knowledge as a **requirement** (i.e. you require the knowledge to do your job), then it is OK
-    - Screening questions that involve a CS question/brainteaser/puzzle are considered to be disqualifiers from being included in this list
+1. The company **DOES NOT** fit the [criteria](/CRITERIA.md)
 1. Explain why the company does not fit the criteria
 1. The PR will be merged assuming the guidelines are followed
 1. The person who added the company will be given a chance to respond and add the company back if it does indeed **require** CS knowledge
diff --git a/CRITERIA.md b/CRITERIA.md
new file mode 100644
index 0000000..6052c2f
--- /dev/null
+++ b/CRITERIA.md
@@ -0,0 +1,17 @@
+# Criteria
+
+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
+- Use live-coding sites like HackerRank or LeetCode
+
+The only exceptions to the above is where CS knowledge is a **requirement** of the role.
+
+## 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)
\ No newline at end of file