"personally edited and compiled a Unix Kernel"
No. I've edited and built an operating system, written in assembler, however my experience of Unix is having it run in embedded devices where it's not my problem. The reason why I'm writing this reply is that "compiling a kernel" isn't really something I would hold as a requirement of technical competence. Sure, great if (s)he can, but the vast majority of people can't, don't, and would never need to.
"installed and removed actual software and hardware"
I'm old enough to have had to deal with IRQ conflicts in the hardware, and all sorts of nonsense from the drivers. These days, installing and removing hardware could be as simple as plugging in a USB socket...
"done network diagnostics"
The DNS is misconfigured. I know this, because it's always DNS.
"and got the sodding printer to work again after numerous Microsoft OS upgrades"
I'm old enough to remember a time before that. A time when a software company would write a few drivers for the popular printers, and everything else would pretend to be one such printer. Of course, there were varying degrees of competence in this charade, which tended to mean that anything that wasn't a genuine such and such would need some driver hacks to get it working properly and outputting all the expected characters. There was a time when I used to be able to speak ESC/P and PCL.
But, personally, I'd settle for a judge that is open minded enough to find out about things (s)he doesn't fully understand.