/explore
|
You are here 
|
martinjeeblog.com | ||
| | | | |
preemchro.me
Some thoughts on how I would go about fixing the dreaded tech coding interview. |
|
| | | | | ||
| | | | |
adambennett.dev
Android Bennett's blog :: android, kotlin, thoughts, opinions, occasional rants |
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
simpleprogrammer.com
So... Do you wanna know more about coding interview preparation and how to prepare for a coding interview? |
|
| | | |||
