Explore >> Select a destination
|
You are here 
|
interviewing.io | ||
| | | | |
rkoutnik.com
|
|
| | | | | Technical interviews are terrible because we don't know what we're filtering for. | |
| | | | |
www.hillelwayne.com
|
|
| | | | | Caveats: I'm not an interviewer, I've never done serious research on interviews, and I haven't tested this. I propose this entirely as a thought experiment. Assumptions: We interview at jobs to find ideal candidates. WE are looking for candidates who are Good at programming Good at software engineering Can work in a team A "culture fit" (not an asshole). Technical interviews test the first two. They are primarily whiteboard questions, abstract design questions, or "write this program" questions. | |
| | | | |
alexgolec.dev
|
|
| | | | | A new series series to help you prepare for interviews at big tech companies, drawing from my experience recruiting and interviewing for Google. | |
| | | | |
killalldefects.com
|
|
| | | This post originally appeared at Kill All Defects on February 22nd, 2020. Recently a younger developer I respect expressed a somewhat common concern. In essence, their concern was that they... | ||
