Explore >> Select a destination
|
You are here 
|
alaiacano.github.io | ||
| | | | |
www.hillelwayne.com
|
|
| | | | | Caveats: Im not an interviewer, Ive never done serious research on interviews, and I havent 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. | |
| | | | |
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. | |
| | | | |
patrickhalina.com
|
|
| | | | | With the right prep and approach, you should be able to ace any big tech coding interview. Here are my tips. | |
| | | | |
enterprisecraftsmanship.com
|
|
| | | My new online training course about Encapsulating EF Core Usagewent live. | ||
