What?
Intro Systems: demonstrate working knowledge of Assembly. Write C to exploit spatial and temporal locality. Learn to cope with concurrency.
Operating Systems: write process scheduling, virtual memory management, system calls, and filesystem caching into Pintos [0].
Networks: write an IRC server, user-land TCP implementation, and IP router in C from the relevant RFCs.
Advanced Networks: write Byzantine Generals, Raft, and Paxos from the papers.
Programming Languages: write several interpreters.
Parallel Programming: write efficient concurrent algorithms, implementing concurrency primitives yourself.
Software Construction/Engineering: learn to collaborate with a team. Lose your fear of merge conflicts by immersion therapy. Experience the pain of people not pulling their weight.
Intro Security: given a pseudorandom function, write your way up to a PRNG, stream cipher, RSA, Diffie-Helman, and an authenticated encrypted channel.
Databases: write most of a database engine.
If graduates are passing these classes but can't write code, or find it remotely difficult to get to a passable level on any of the tools you listed in a matter of hours/days, then the CS program at the schools they come from are not nearly rigorous enough and should lose reputation in favor of those that are.
A graduate of a decent CS program should have a decent idea of how to create these tools, and be capable of doing so, though with considerable difficulty. Consuming them should be pretty easy.
[0] http://web.stanford.edu/class/cs140/projects/pintos/pintos_1...