In Defence of the Technical Interview
&gt;How could someone with 10 years experience on their CV be unable to start a new project in their own editor<p>This is something I need to study each time I want to change jobs.  
I suspect that I will have to create a new project somewhere in the interview process but it is just something I very rarely do in my day to day job, if ever. I suspect that it is the same for many engineers.<p>FWIW, at my current company, the interview projects come preconfigured, so you only have to import them and start coding.  
We have also already imported some popular libs.<p>Watching somebody rightfully struggle to do that is :<p>- a pain for the interviewee<p>- awkward and uninteresting for the interviewer .. I don&#x27;t expect many people to have to create new projects often so it is totally ok to have forgotten it<p>- a waste of time for the both of us.<p>We also actually don&#x27;t do algorithms.<p>We have a debugging interview, with a shitty codebase where you have to find the issues and correct them. When you are done with the bugs, you can collect your thoughts on what&#x27;s wrong with that codebase so we can discuss how to do it better.<p>Another interview is to have to design a product similar to ours (a simplified version of course) and you have to come up with API and app technical designs.