I really don't care whether one knows Angular or CPU schedulers on day one. What I care is whether one has done programming and can listen. Knowing and doing ar

I really don't care whether one knows Angular or CPU schedulers on day one. What I care is whether one has done programming and can listen. Knowing and doing are two different things and I found knowledge a poor predictor of ability to do - plenty of threads here on challenges of IT interviews. Knowledge gaps are relatively easy to fix but ability to analyze complex issues and then create solutions always felt to me a more innate capability. CS degrees are proof of ability to execute a longer project and having analytical skills. That is worth something but does not proof ability to craft new stuff or work in a team which are also vital. Hiring is taking risks and hiring from boot-camps is likely riskier. Cost is lower and depending on the job, project, business and hiring managers risk profile one or the other decision makes sense.