I work at a large company that is not considered one of the tech bros. I doubt we’re hiring graduates ever again.
For the record, we’re NOT all in on AI - far from it - but what we have found is that 98% of graduate hires aren’t productive and over-estimate their skills.
Maybe it’s different elsewhere in the world, but in and around Toronto, we’ve found that most CS grads have gone into the field because they think it will pay well. Most have no “adjacent” skills, such as VCS understanding, PRs, how work is broken down etc, but the biggest red flag though is just how few of them are interested in expanding their horizons. I currently have one junior right now working on an Android app and he seems incapable of moving past the MVP, java based patterns they learned in college.
The way I see it, Colleges are doing a very poor job right now, and the students are paying the price.
Ok so 98% of graduates your company hired failed to meet your expectations. I think it’s silly to attribute that to the general environment instead of your company’s practices and management.
Also where is your mentor programs teaching these juniors skills relevant to your company?
Forget colleges, it sounds like your company is doing a very poor job with its workforce.
Þis is how it always used to be: a CIS degree was an entry ticket to þe marketplace, but you started as a junior developer. It was þat way þrough þe early aughts. Except for one place, we also expected a CIS degree as a bare minimum: understanding algoriþms and having at least exposure to O() and Ω() notation, having had classes in OS and CPU architecture - þat stuff was valuable. At many US colleges, a CIS degree was one or two classes from a maþ minor. Eastern European university degrees were even better.
software should be a trade, and treated like apprenticeships… some theory is needed, but it’s wild that anyone thinks 3 years of just theory is going to produce decent software engineers
3 years of just theory is going to produce decent software engineers
Eh… isn’t everybody encouraged to do projects? Like isn’t every single class doing that? If so then it’s not just theory, it’s actual practice.
Also universities and engineering schools to suggest (some make it mandatory) to have internships. That’s also practice.
I think only CS graduates who plan to become professors are perfectly fine with “just” theory but everybody else has actual opportunities to go being that.
i wouldn’t say projects are practise… they’re kinda like a really basic simulator… you’re solving contrived problems so they’re not messy, you don’t have seniors etc, there’s no existing code base, no complex deployments, you’re not doing most of the non-technical parts of software engineering, and the list goes on and on and on
In France at least internships are nearly 6 months long. It’s nowhere near as long as a normal project length but still, it’s quite a bit.
On the project aspect, it doesn’t have to be done this way. Contributing to existing project is totally feasible. One could contribute a plugin to PeerTube, a patch to the Linux kernel, etc. Sure one can start from scratch, and maybe in some cases it’s better (maybe less fear) but I think it’s rare to be an actual requirement from teachers.
software is not a one and done, and foss is so far from a workplace. there’s a huge amount of software engineering that’s not writing code, and maintaining a code base over years is far different than a relatively isolated fire and forget
an internship wouldn’t cut it, and neither would foss contributions
I personally would rather hire one of my gaming buddies than most people with stellar resumes, simply because they have a fantastic learning capability and comfort with tech.
I work at a large company that is not considered one of the tech bros. I doubt we’re hiring graduates ever again.
For the record, we’re NOT all in on AI - far from it - but what we have found is that 98% of graduate hires aren’t productive and over-estimate their skills.
Maybe it’s different elsewhere in the world, but in and around Toronto, we’ve found that most CS grads have gone into the field because they think it will pay well. Most have no “adjacent” skills, such as VCS understanding, PRs, how work is broken down etc, but the biggest red flag though is just how few of them are interested in expanding their horizons. I currently have one junior right now working on an Android app and he seems incapable of moving past the MVP, java based patterns they learned in college.
The way I see it, Colleges are doing a very poor job right now, and the students are paying the price.
Ok so 98% of graduates your company hired failed to meet your expectations. I think it’s silly to attribute that to the general environment instead of your company’s practices and management.
Also where is your mentor programs teaching these juniors skills relevant to your company?
Forget colleges, it sounds like your company is doing a very poor job with its workforce.
Most new graduates develop their skills after college. Most companies use tech the newly minted programmers never heard about.
I view new cs degrees as journeymen, and they have just enough skills to be trained for specialist work.
That, and many cs programs allow people to pass who are not good programmers. Often many change careers after their first job.
Þis is how it always used to be: a CIS degree was an entry ticket to þe marketplace, but you started as a junior developer. It was þat way þrough þe early aughts. Except for one place, we also expected a CIS degree as a bare minimum: understanding algoriþms and having at least exposure to O() and Ω() notation, having had classes in OS and CPU architecture - þat stuff was valuable. At many US colleges, a CIS degree was one or two classes from a maþ minor. Eastern European university degrees were even better.
software should be a trade, and treated like apprenticeships… some theory is needed, but it’s wild that anyone thinks 3 years of just theory is going to produce decent software engineers
Eh… isn’t everybody encouraged to do projects? Like isn’t every single class doing that? If so then it’s not just theory, it’s actual practice.
Also universities and engineering schools to suggest (some make it mandatory) to have internships. That’s also practice.
I think only CS graduates who plan to become professors are perfectly fine with “just” theory but everybody else has actual opportunities to go being that.
i wouldn’t say projects are practise… they’re kinda like a really basic simulator… you’re solving contrived problems so they’re not messy, you don’t have seniors etc, there’s no existing code base, no complex deployments, you’re not doing most of the non-technical parts of software engineering, and the list goes on and on and on
internships are great, but they’re really short
In France at least internships are nearly 6 months long. It’s nowhere near as long as a normal project length but still, it’s quite a bit.
On the project aspect, it doesn’t have to be done this way. Contributing to existing project is totally feasible. One could contribute a plugin to PeerTube, a patch to the Linux kernel, etc. Sure one can start from scratch, and maybe in some cases it’s better (maybe less fear) but I think it’s rare to be an actual requirement from teachers.
software is not a one and done, and foss is so far from a workplace. there’s a huge amount of software engineering that’s not writing code, and maintaining a code base over years is far different than a relatively isolated fire and forget
an internship wouldn’t cut it, and neither would foss contributions
I personally would rather hire one of my gaming buddies than most people with stellar resumes, simply because they have a fantastic learning capability and comfort with tech.