We can argue about "fundamentals", but I'm happy hiring non-CS grads. Because for us, "fundamentals" are things like "can you work in a team?", "can you write/c

We can argue about "fundamentals", but I'm happy hiring non-CS grads. Because for us, "fundamentals" are things like "can you work in a team?", "can you write/communicate well?", "can you grasp real-world workflows/issues/bottlenecks real people have using products?", and "will you try the simplest thing first?". Other degrees offer the same or more opportunities to hone these skills. It's easy for senior engineers on the team to address gaps in CS knowledge, but much harder to address a lack of soft skills, writing, or over-designing/too much abstraction (because you were taught the patterns, but not when to use them). I could go on, but IMO, this is why interviews are still so broken, and why the field of software development still faces the same issues it always has. Granted, I'm not building a DB, but compared to maintenance and over-engineering, performance is rarely an issue, and easily solved via profiling.