91–100 of 170 posts
Earlier quoted context omitted.
How did you learn stuff for working in such companies? I always assumed you need a lot of math and theory to work in finance.
Math and theory would be more important for a dev job, parent commentor is doing SRE.
Earlier quoted context omitted.
Math and theory would be more important for a dev job, parent commentor is doing SRE.
What exactly does an SRE do (Software Reliability Engineer, right?)? I've heard the title before but don't quite understand it.
Rather than focusing on making the software do X, it makes software that already does X more resilient to failure.
Earlier quoted context omitted.
Math and theory would be more important for a dev job, parent commentor is doing SRE.
What exactly does an SRE do (Software Reliability Engineer, right?)? I've heard the title before but don't quite understand it.
Earlier quoted context omitted.
How did you learn stuff for working in such companies? I always assumed you need a lot of math and theory to work in finance.
Math and theory would be more important for a dev job, parent commentor is doing SRE.
I think it strongly depends on exactly what you end up developing.
Earlier quoted context omitted.
> I remember a time when online certificates was an anti signal. I have never interviewed someone with many certifications and thought the person would be a good addition to a team, and I have never worked with someone who has many online certifications and thought they are good at the things they are certified in.
I have over 100 Coursera/edX/Udacity certificates and work on the bleeding edge of tech (AI). MIT's Underactuated Robotics got me into the first cohort of Udacity's Self-driving Car Nanodegree. I think you are shooting yourself in the feet if you plainly reject people like me who just want to keep learning new things.
1. Collects certifications just to pad their resume, and get there probably by mostly studying brain-dumps and memorizing the answers. Often have little or no actual experience with the technology in question.
2. Gains certifications related to things they have actually done / are actually doing, and use the certification process as a "forcing function" to motivate doing a deeper dive into obscure or less frequently used corners of the technology that they may not currently be strong in. Puts the certification on their resume but only expecting it to be a "weak signal" that complements their actual experience.
I think there may also be a 3rd category which may be relate to (1) but specifically relates to people who are just beginning their careers and seek a few certifications just to give them "something to hang their hat on" as far as getting in the door somewhere.
Anyway, I consider myself a representative of group (2) and as such I tend to default to an assumption that most people are also in that group. As such, I consider certifications a positive (if weak) signal, unless there is some other "red flag" to suggest the person is in "group 1". Like having 100 certifications, but not documented experience actually working with any of those technologies, or something like that.
Earlier quoted context omitted.
Math and theory would be more important for a dev job, parent commentor is doing SRE.
What exactly does an SRE do (Software Reliability Engineer, right?)? I've heard the title before but don't quite understand it.
The goal of the job is keeping large systems online and operational.
Think: systems engineering, DevOps, and sysadmin at scale - leveraging automation.
Lots of other shops still call it DevOps Engineering, Production Engineering, etc.
You can do a master in CS even without a CS bachelor online at the University of Colorado Boulder via Coursera. You just need to take 2 classes and get at least B in each. https://www.colorado.edu/cs/academics/online-programs/mscs-c... But as they say, this will only put you on the radar, but then it's all about LeetCode-Hard and -Medium and system design.
Earlier quoted context omitted.
What exactly does an SRE do (Software Reliability Engineer, right?)? I've heard the title before but don't quite understand it.
Site Reliability Engineer - I’m one too lol. Most of what you do is work with dev teams to make sure their service is reliable, then slap an SLO (service level objective) to make sure their service meets a certain threshold of reliability.
(I've never been in a company big enough to have one of these, so I'm just trying to understand)
Dude I got into a FAANG company with no CS degree (or any other degree). Unless you're going into research, where is PhD is almost required, they'll hire you based on your skills.
Same. Self taught as a child (like OP). Offered a job at a FAANG twice, and took it the second time.