/explore
|
You are here 
|
www.hillelwayne.com | ||
| | | | |
yolken.net
|
|
| | | | | In a previous post, I discussed preparing for coding interviews as a candidate. In this post, I want to flip to the other side of the table and talk about conducting better interviews from the interviewer perspective. | |
| | | | |
www.danhacks.com
|
|
| | | | | [AI summary] A comprehensive guide listing resources and techniques to help software engineers prepare for coding interviews, covering data structures, algorithms, and practical practice tools. | |
| | | | |
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.susanjfowler.com
|
|
| | | In today's post, I want to share some of the things I've learned about how to structure and run these types of interviews. If you're here because you want to know how to ace the architecture interview, you should keep reading, because I think the best ways to prepare for these things is know how interviewers think about them. | ||
