It is when the job market is overcrowded as shit. I don't think I've been in a single interview where the guy didn't ask me about my GPA (usually they just bring it up casually). And not listing it here is pretty much an auto-ding unless you have very impress work experience.
GPA + Career
>I know some people say there is no minimum GPA requirement, but surely tech giants do? Or other companies at least?
The big boys like perfect students, though you can get by with a good resume.
Basically, excellent marks are a substitute for a certain amount of experience and get you into graduate recruitment programs right out of the door, actually six months to a year before you graduate usually.
Most other companies won't care quite as much, practical coding tests are way more important. They might break some ties in an hiring committee though and/or get you into a short list for interviews.
>Matters somewhat for first job, depends on the company and what they're looking. Doesn't matter at all afterwards unless the company is stuck up as hell.
this.
I had dodgy marks in some areas, the only person who ever looked at it was the recruitment agent and he decided he could sell me regardless so he pitched me to his client and they never saw my results.
After that, it was always my resume, experience and references that got me my next job.
>MUST HAVE 5-10 YEARS OF WORK EXPERIENCE WITH AN EXCELLENT ACADEMIC RECORD
>all these idiots with no idea what they are talking about
If you didn't go to Stanford or MIT you better hope that your GPA is at least 3.8 or you're be working for some literally who startup for 6 years before breaking 100k.
if you know your shit you'll be alright. I graduated with a 2.7something GPA from a big but not super well know state school. My major was EE, but I hated that shit and started learning how to program at the start of my junior year. I was able to secure a FAANG/Big4/whatever internship for the next summer and from that got a full-time offer. Been working at the company for almost 4 years and have had really healthy career growth.
I did spend most of my free time learning how to program, but it was worth it IMO. A couple of things you should focus on:
1) practice leetcode/ctci. as dumb as it is, its how tech recruiting works. game the system and memory the dumb mind puzzles. this is something I didnt personally do and it fucked me over in a couple of interviews.
2) make sure you actually understand the basics of CS. these will also be part of the dumb tech interviews and will be somewhat useful throughout your career (you'd be surprised how many high-paid SDEs fuck these up)
3) spend some time building software (make sure to think about system architecture) and learning the tooling (git + some build system). a ton of CS grads will never have built a real piece of software and it will show once they are actually doing an internship. you'll have a huge head start if you dont need hand holding with this kind of stuff (especially the tooling)
Anyone else hate people who went to """""""top"""""" schools?
protip: no one knows what they're talking about unless they're a believable person with 3 successes in the given area but you can't tell that from here
I fucking hate those brainteaser questions.
>Design an algorithm that simulates a dice with coin flips
...
This. Once your foot is in the door it’s much easier to get momentum going.