* you aren't looking (seems unlikely)

* there's something toxic about your team that means they'd never work for you and you should fix that (hopefully unlikely)

* you aren't paying enough to make the move worthwhile for them (seems likely as people never want to pay the going rate)

That's why I presumed salary. Double your salary and you may suddenly find you're being flooded with contacts from the compiler engineers at places like Google. If that's the case then your only problem was the compensation you were offering and not a problem with education.

Until reading this, it would never have occurred to me that a compiler tech at Nvidia would get anything remotely like that figure.

To be honest, as someone interested in compiler tech roles, it never occurred to me to even consider Nvidia until reading this discussion.

That's... an impressive number.

> Why would you presume anything about salary?

Because that's usually the reason, especially when speaking of what universities teach. "We can't find people who know $TECH" is, under those circumstances, almost always corp-speak for "We can't find new grads who already know $TECH to fill our entry level positions for what we're willing to pay in order to replace the employees that learned it on the job and then leave when we don't give them raises after a couple of years."

Have you posted the positions you're trying to fill here on the monthly "Who is Hiring?" thread?

As an out of the box suggestion, consider sponsoring the creation of an online course (like a Udacity nanodegree, perhaps) that covers the curriculum material you consider missing. A comprehensive set of 'build your own programming language and tooling' courses would probably be quite popular.