[notafraudster]

I did a CS degree 20 years ago. Databases, concurrent programming, and network programming were all 4th year electives (I took network, AI, and image processing personally). But something not being included in a core curriculum doesn't mean someone can't learn it.

My curriculum was: Year 1: Intro Comp Sci / Year 2: 2 courses in Logic, 2 courses in data structures and algorithms / Year 3: 2 courses in processor design, 1 course in finite state automata, 1 course in parsers / Year 4: a course in ethics, a course in team programming (which covered UML and version control), and two electives.

I believe a major was 14 courses so I'm missing one, or it may have been it was three electives. I didn't take databases because I was already a paid sysadmin before I started college and mostly at the time database courses were just ten tedious weeks of normalization crap.

Also, treat your interns better. The reason to hire interns is because you plan to devote some of your resources to help them in their professional development. Stop asking what you can get out of your interns and start asking how you can best give something to them.

[onezeronine]

I once hired two interns from an old startup of mine in 2017 who were on the verge of quitting CS because they found out that maybe it is not the course for them. I told them that CS teaches fundamentals, but real life programming work teaches you how to write good code.

I got them to work on an internal tool using Node and Vue.js for 2 months. They were good programmers overall.

After their internship ended and completed the requirements for college, I received a personal letter from them thanking me for the knowledge and support they got from me. Apparently, I lost the letter after closing our startup after a year. But I vividly remember the gratitude I got from them.

What I learn is that internship is a two-way street. You learn how to communicate with them effectively at their level and they learn from you in writing software.