4 ms·
I've been in the industry since the mid-90s, and employed doing full-time software dev since 2000 (before that was sysadmin and scripting and the like). I have
by cmrdporcupine 11y ago
I've been in the industry since the mid-90s, and employed doing full-time software dev since 2000 (before that was sysadmin and scripting and the like). I have no degree; my undergrad was a BA in philosophy, but I never finished it. I dropped out to join the .com boom and do what I really wanted to do. (I never had the math grades to get into a CS program). There was never a good time for me to go back and get a degree, I was always either employed or broke, or had responsibilities (home, kids, etc.) that prevented me from dropping out of the workforce to do it.
So as to your question; Yes, it happens routinely, in my Canadian job market. At both the junior and senior level. Many positions won't even reply if they don't see the degree on your resume. I make it explicit in interviews just to get it out there because I have had too many unpleasant situations where the degree was at first assumed and then revealed to not be there. Reactions vary.
In the end I've had a successful career, but with some struggle. I work at Google now. But mostly only because I came through acquisition. I would not even be considered for an interview otherwise. I have faced some small internal attitude over not having a degree, tho only a little bit.
There are other things that result; grads from CS programs spend a lot of time in algorithms course studying the kinds of things that get asked as skill testers in job interviews but then almost never used in the real world again. (Not to say I haven't studied these algorithms, but studying them in school I think helps respond in the way an interview expects.) That also affects employability. And more and more because this is the direction more and more interviews are taking.
- jasonjei 11y agoI think interviews are also a whole another can of worms for recruiting. Hiring a programmer isn't the same as hiring in many other professions; you're actually quizzed (university style) on textbook algorithms. Granted, there needs to be a filter. However, how many algorithms does one need to memorize to be a good programmer? Is knowing how red-black trees work going to make one successful? Or is knowing how hash tables work Under the surface going to make one successful? Or is just being able to use the Hash data structure provided in Ruby good enough?
- cmrdporcupine 11y agoSo has something changed or was I just 'lucky' before, because for the first 10 years of my career I almost never ran into these whiteboard/skillz-tester type of interviews. And never into a "we take your life for the day and drill you with multiple teams for hours on end, oh and also you have to point us to a very illustrious github and stackoverflow portfolio." It was usually just a phone screen, an in person, a few questions to see if you were full of shit, and then call references. Ta da!