/explore
|
You are here 
|
rkoutnik.com | ||
| | | | |
blog.cassidoo.co
Interviews are scary, but they don't have to be. When you're on the spot, it's best to be prepared. Let's prepare you. |
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
www.laac.dev
In the software industry, some argue that technical interviews are broken, and I tend to agree. Instead of going through why they're broken, I'm going to tell you about my favorite technical interview. |
|
| | | | | ||
| | | | |
www.thepolyglotdeveloper.com
Learn how to search for developer positions and better prepare yourself for the technical interview process in this podcast episode with Brenda itReverie. |
|
| | | |||
