/explore
|
You are here 
|
prashamhtrivedi.in | ||
| | | | |
blog.colinbreck.com
I have been part of the interviewing team for my employer for over a decade. Over this time, I've conducted hundreds of technical interviews for programmers. By far the best advice I've ever read on technical interviewing is Joel Spolsky's The Guerrilla Guide to Interviewing. This is an essay I've |
|
| | | | | ||
| | | | |
trishagee.com
Yesterday dawned, with a sense of foreboding (actually it dawned with me coughing my lungs out, but we've heard enough about the sub-optimal state of my respiratory system this week). On this day, I was giving the talk I was dreading when I got asked to do it. It's the talk I actually put more work into than any of the other sessions I was presenting at this JavaOne. It was the Women In IT talk. |
|
| | | | | ||
| | | | |
compositecode.blog
Discover why traditional coding challenges during interviews might be doing more harm than good. Learn how they create stress, ignore real-world skills, and fail to improve employee retention or performance. Explore data-driven insights on better hiring practices for building stronger, more diverse teams. |
|
| | | | | ||
| | | | |
yolken.net
Having switched jobs a few times over the last few years, I've done a a lot of software engineering interviews. In my most recent job search, for instance, I did around eight phone screens followed by six on-sites. |
|
| | | |||
