The stuff you need to know for most jobs can be learned through books (DS&A); everyone, including grads, learn to actually code on the job. Systemic thinking and breaking problems down into manageable chunks is harder to train for; this is where I think something that's akin to apprenticeship could really help. At least the way I view it, and maybe I'm wrong, is that in the early 2000's, much less the 90's, there weren't many CS or CE schools - much less accredited ones that followed CAC standards. If your company is doing this then they're just getting back to the roots of what a computer programmer used to be.
1. In weekly one on ones we may discuss a topic. I ask them to apply that topic.
2. They pick up sprint tasks and look to apply the knowledge they've gained.
3. They may ask some questions along the way; it's important that other engineers are also available for question asking - the same way peers may depend on each others knowledge.
4. You peer review the outcome in a PR.
Rinse and repeat.
I'll add I end up having to do this with everyone if they're fresh to industry or came from a place with poor standards for code writing and/or problem solving.
German here. The secret sauce behind the Duales System is that it's, as the name suggests, a split system - one part of the training is at government-run schools ("Berufsschule"), and the other part at the company that trains and pays you. And since the curricula are virtually the same across the schools, even if they're a bit outdated, they still produce decent graduates.
Our pride as a nation, our role models, is not a few people who struck it right to become multi-billionaires, our pride is the millions of people working for the Mittelstand and the consistently high quality of the stuff they produce. Boring, but wildly profitable and very, very resilient.
PS: You actually might know some of these things our tradespeople built. BMW/Audi/Mercedes/Volkswagen cars, MAN trucks, Rheinmetall, KMW and ThyssenKrupp military hardware from tanks to the massive Panzerhaubitze 2000, Diehl's IRIS-T anti-air defense, Heckler & Koch/Walther guns, anything with "Siemens" on it built before Siemens fell to MBA shenanigans, all developed and prior to globalization also built in Germany. And a lot of it, especially the military tech, is up to par with what the US military builds - for IRIS-T SLM and PzH 2000, the Ukraine war shows that they are even better to some experts.
One thing we sadly lost was pharmaceuticals - up until the 60s-70s, Germany used to be the "apothecary of the world" [3], but we lost that to India and China.
[1] https://en.wikipedia.org/wiki/Hidden_champions
[2] https://hbr.org/1992/03/lessons-from-germanys-midsize-giants
[3] https://www.deutsche-apotheker-zeitung.de/daz-az/2018/daz-44...
Remember that they're not just mashing code straight to the main branch; they're apprentices, so other engineers paired with them, others read their pull requests, etc. It wasn't a free-for-all, nor should it be.
This sounds like the kind of situation he'd excel with - is your company currently hiring U.S. based folks?
The part-time work is like doing the labs part.
Also at the end of it, you can still go to the university if feeling like it. I did so.
Going through technical school was a secure way to have a job, in case the university exams weren't good enough for the engineering degree, which by the way is mostly state sponsored on this side of the Atlantic.
It's an interesting model, I remember folks on HN calling for more companies to try it since it seems to have had some success in Germany, but I predict a lot more security bugs and unmaintainable code in the near future.