- exponent, free peer to peer mock interview service
- leetcode, coding question with varying difficultly and built in ide, testing, and automated grading
- hackerrank similar to leetcode
- coding
- algorithm design and analysis
- system design
- once you get past entry level positions and gain some experience you start to face system design interviews
- books
- System Design Interview book 1, 2 by Alex Xu
- open-ended discussion (behavioral)
- professional background and history
- projects you've contributed to, the impact they had, the technologies you used/leveraged
- challenging situations in team settings
- technical interests and passions
- technologies you would like to work on/with
- skills and expertise you are looking to develop
- preference in backend, front-end, full-stack roles
- interest in machine learning, security, distributed systems, and/or cloud infrastructure
- company fit
- professional background and history
- communication
- ask clarifying questions
- discuss design decisions and implementation trade-offs
- speed
- practice coding quickly
- get a working solution first
- quality
- write clean/bug free code
- iteratively fix bugs and optimize the solution
- linkedin
- have an up to date profile on linkedin
- recruiters regular run keyword searches looking for candidates and will even reach out
- internship
- full time
- picking a language to interview in
- spend a couple of hours research company culture, industry, and product
- company's website, company's wikipedia article, glassdoor reviews
- spend a couple days (2-3) studying the subject matter and CS fundamentals
- data structures, object-oriented design, and algorithms
- ex: arrays, (O)n, binary trees, link list, integers, hash map, traversals, recursions, etc.
- go back to your college textbooks
- pick your favorite data structure and implement it
- spend a week or 2 practicing problems and practicing mock interviews
- line up interviews in rounds so you can pace yourself and improve
- line up easier or companies your less interested in earlier so you can build momentum and confidence for the interviews you really care about
- practice while applying then set interviews 2-3 weeks out to study and get in the zone
- checklist right before the interview
- explore roles adjacent to software engineering
- www.stackoverflow.com
- http://bigocheatsheet.com/
- http://www.geeksforgeeks.org/
- http://www.coderust.com/
- https://gist.github.com/TSiege/cbb0507082bb18ff7e4b
- http://codingforinterviews.com/practice
- https://www.topcoder.com/
- https://www.programcreek.com/2012/11/top-10-algorithms-for-coding-interview/
- computer science review