Limitations and pitfalls of the job interview
There&#x27;s a growing rift in software between employers saying &quot;there&#x27;s a talent shortage&quot; and a rapidly growing population of devs who feel like they&#x27;re locked out due to the technical interview process.<p>Many of the engineers not being hired are recent bootcamp grads but there are also tons of CS majors that can&#x27;t seem to &quot;crack&quot; the interview process.<p>Part of my job is helping companies &quot;fix&quot; their hiring and one of the ideas that I&#x27;ve been putting forth for years that&#x27;s slowly gaining steam is developing a &quot;technical apprentice&quot; role. This role would be responsible for tasks that are frequently de-prioritized like documentation, testing, QA, bug fixes, note taking, etc. and would be a foot in the door for entry-level engineers. The role is designed to focus on communication and soft-skills while also giving the person a chance to prove their &quot;grit&quot; on the technical side. Even a few months in an apprenticeship role is generally enough for companies to &quot;take a chance&quot; on someone as an entry-level engineer.<p>This has been a great way to shift interviews away from algorithms and more towards finding people can add immense value to technical teams even without having on-the-job programming experience.<p>I&#x27;m curious what the HN crowd thinks about that role as a way to bridge the hiring gap.