Too Long; Didn't Read
Anton Fenske shares the internals of designing a pragmatic coding interview that I got to know after interviewing folks for different tech positions. There are 4 basic rules that go like this: Make sure to create boilerplate for everything that doesn’t test for the skills you’re looking for in your candidates. This will save everyone a lot of time while providing enough signal to make a hiring decision. In the next post, we’ll zoom in each of the rules.