I know from experience that a B.Sc. in Computer Science at the Technical University of Munich (considered a very good school) was harder to get before 2008 than it is now.
In the killer-subjects like discrete mathematics, theoretical computer science and algorithms we had failing-rates of 80%.
I can image the German government asked for "more CS grads" and after this the professors started to introduce one problem in each exam that anyone could pass who practised a bit and / or wasn't entirely stupid. The other two to three problems were still on a high level, and if you wanted a top-grade, you still had to solve those. As a result the failing-rate for the mentioned killer-subjects dropped from 80% to 20-30%.
Do you have any links to back that up?
I'm not studying at TUM but I'd be really surprised if there's a 80% pass rate for those subjects.
What is considered a passing grade at one of these schools?
At my private liberal arts college in the US it was usually (but ultimately up to professor discretion):
00-59% - Fail (0.0 for GPA)
60-67% - D (1.0)
68-69% - D+ (1.3)
70-72% - C- (1.7)
73-77% - C (2.0)
78-79% - C+ (2.3)
80-82% - B- (2.7)
83-87% - B (3.0)
88-89% - B+ (3.3)
90-92% - A- (3.7)
93+ - A (4.0)
You could count any class with a D or better toward graduation, but to actually graduate you needed a 2.0 or better GPA. If you did not have it you could take additional courses to bring your GPA up, but adding on 3-credit courses when you've got 120 credits built up with a sub-2.0 GPA is typically a losing proposition. Most transferred if they were sub-2.0 by the end of their Sophomore year.I've seen other grading scales with E's in addition to/instead of F, or minor variations on the percentages. It seems popular to give Honors courses an extra point (e.g. an A- is 4.7 instead of 3.7), particularly in US High Schools.
See https://en.wikipedia.org/wiki/Academic_grading_in_Germany
FWIW I did my masters there and in my opinion the way they evaluate students is suboptimal anyway - but I don't know if that's a TUM thing or a German thing.
yeah, my uni was pretty bad, all the useful stuff I learned and use daily came from my own learning, none from university. campus was a fun place and great experience though :)
It's the recruiting equivalent of buying IBM (or Microsoft I guess).
If the applicant pool is large enough any quick way to discriminate that skews positively for applicant capability is going to be used. It is also much easier to see if someone has a degree than to actually test if they have the required skills.
I think a lot of self-taught developers (myself too earlier in my career) fail to realize this.
If you've got 1,000 applicants and your job is to schedule 10 interviews from that pool, you will do anything that won't absolutely destroy candidate quality. It's not about the finding the best, it's about finding someone who wants the job and will be able to do it. The name of the game is not minimizing false negatives (disregarding good people), but minimizing false positives (interviewing shitbirds).
So if you work for BigCo you say the person need three years of corporate experience. You're down to 800 applicants. One year of experience in the JavaScripts. 750 applicants. Maybe the phrase "SQL Server" has to be on their resume. 400 applicants. College degree. 320 applicants. Computer Science degree. 120 applicants. Maybe you want to filter by your preferred recruiter, because they only charge you 11% of base salary instead of 18% like that other firm. 22 applicants. Now you can actually read the resumes and pick the top half to interview. Anyone who actually wrote a cover letter and is in this pile is pretty much guaranteed an interview.
It's true that it's costly and hard to test one's skills. The trouble with grades though is some people cheat brilliantly on their tests and others, some of them really good, test badly (if they're bored they don't prep, screw the grade average, etc) and some of the latter are actually extremely pragmatic on the job. I don't quite understand it but it's there.