See "Interview Guide > Practice" on my GitBook

I hate programming interviews.

• Interviews reward people who are good at interviewing
• Interviews have no direct correlation with a person's ability to do their job.
• They usually require a special "trick" to solve.
• You are at the mercy of the interviewer.
  • If your interviewer sucks, so will your interview.
• The system is a black box.
• Computer science questions suck, they don't always directly represent what you may be doing on a day to day basis.

Special Tricks To Solve Programming Questions

• Binary Search
• Exponential Growth
• Recursion
• Using maps or hashes
• Using a combination of data structures (for example: LRU Cache that uses Maps and a Doubly Linked List)

O Notation

Best to Worse:

• O(1)
• O(log N)
• O(N)
• O(N log N)
• O(N^2)
• O(2^N)
• O(N!)

Sites

• https://github.com/trekhleb/javascript-algorithms
• https://github.com/basarat/algorithms
• http://bigocheatsheet.com/
• http://hackerrank.com/
• https://techdifferences.com/difference-between-quick-sort-and-merge-sort.html
• https://www.interviewbit.com/google-interview-questions/
• https://github.com/amejiarosario/dsa.js-data-structures-algorithms-javascript