The latest articles on Forem by ankitjc (@ankitjc). https://forem.com/ankitjc https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1977607%2F065e206c-5730-48dd-a4aa-1fb952244c39.jpeg https://forem.com/ankitjc en ankitjc Sun, 25 Aug 2024 20:01:14 +0000 https://forem.com/ankitjc/do-we-need-a-new-technical-interview-process-f0i https://forem.com/ankitjc/do-we-need-a-new-technical-interview-process-f0i <p>Question: Hows the current technical interview process for a software engineer look like right now? </p> <p>Answer: Generally - <br> Step 1 - 30 mins call with recruiter to assess match. <br> Step 2 - 1 hour technical assessment (coding interview).<br> Step 3 - 4 to 8 hours of final round with multiple interviews. </p> <p>Sounds about right, yes? </p> <p>Whats the problem with this? <br> Well, lets do some math. </p> <p>There are ~4 million software engineers in just North America. <br> Lets consider 1% switch jobs each year. </p> <p>40k engineers ready for interview. <br> Each engineer on an average applies to 25+ jobs (sometimes 100+).<br> Communicates with 10+ recruiters.<br> Gives 5+ technical assessments. <br> Final rounds 2+? </p> <p>Lets do a back of the napkin calculation -- </p> <p>5 mins for job application = 40k * 25 * 5 mins = <strong>80k hours</strong>. <br> 30 mins for recruiter talk = (40k + 40k) * 10 * 30mins = <strong>400k hours</strong>. <br> 60 mins of assessment = (40k + 40k) * 5 * 60mins = <strong>400k hours</strong>. <br> 6 hours of assessment = (40k + 40k) * 2 * 360mins = <strong>960k hours</strong>. </p> <p>Total = <strong>~2 million hours</strong> of engineering time per year! </p> <p>Is there a way to get back <strong>some</strong> (if not all) <strong>of this time</strong>? </p> career