A Better Technical Interview (Sam Jones) @TestDouble
A Better Technical Interview (Sam Jones)  @TestDouble
Uploaded March 2020 | Updated November 2026, 2 days ago
It’s easy to find fault in the way we interview in tech. Often, there are unclear goals, trivia questions, and unrealistic coding environments. Let’s analyze the things we don’t like, and design a better process. Let’s make a better technical interview with honesty, transparency, and a more realistic experience.

More here: blog.testdouble.com/talks/2017-01-27-a-better-technical-interview
A Better Technical Interview (Sam Jones)3 Stages to evaluate codeSometimes a Controller is just a Controller (Justin Searls)How to tell if AI threatens your jobThe Social Coding Contract (Justin Searls)Diagnosing vibe coding with code smells: superpower or illusion?Unpopular opinions on vibe coding from senior developersThe Tale of the Hidden Consultant: a scary software storyLegacy modernization: What happens when seams are at cross purposes?Ratcheting to zero: How incremental constraints eliminate technical debtDiagnosing vibe coding with code smells: superpower or illusion?The Rails of JavaScript wont be a Framework (Justin Searls)
Test Double |

A Better Technical Interview (Sam Jones)

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER