Earlier quoted context omitted.
"kernel"? For WHAT operating system(s)? Or do you just expect them, naturally, to be expert in all of them, so little their efforts are worth, so great your cash is worth? Then for WHAT work? Writing device drivers? Tweaking the TCP/IP stack? New, tricky things in video? For WHAT? Here is the general situation: A successful information technology startup is a RARE thing, among entrepreneurs, businesses, and even info…
For your "cooperative and preemptive multitasking" - it's not my question - see the link on the article: http://www.rethinkdb.com/blog/2010/06/will-the-real-programm... They asked this on RethinkDB interview. I found a similarity and just mentioned it. FYI its a pretty common terminology. I also don't care what you think about my ego. I made a candid post for a problem I am facing. If you criticize that's very welcom…
Broadly you seem to be recruiting a bit too close to the ground, to be straining over gnats and forgetting elephants. E.g., my best work in concurrency was at the Watson lab in Yorktown Heights. We had NO trouble hiring people with lots of smarts, knowledge, talents, and determination. When I interviewed people, I asked more general questions. So for concurrency, ask about some really solid topics in the field.
You gave a URL on your terminology: I still don't think that the terminology is both solid and common enough to use in an interview. Indeed, I would guess that a real expert in concurrency, e.g., a recent CS Ph.D. who did their research in the field, would not use such terminology. What a Dijkstra semaphore is is solid. So, might ask about that. I don't think your terminology is good for recruiting real expertise.