Salaries won't race to the bottom, because 1. there is still a demand, and 2. someone from a boot camp doesn't have the knowledge and understanding that a more senior person does. Can they learn that? Of course they can, but then they will become more valuable and expect more money. Companies that hire the cheapest person possible almost always end up at the same conclusion. You pay peanuts, you get monkeys.
Story time. At a previous company I worked with a number of smart people. Education wise, I didn't hold a candle to them. One went to a top engineering school in the U.S., one had a master's degree in CS, and one went to one of the top rated CS programs in the world. (They are all several years my junior.) All of a sudden our boss calls me in a panic, because some update that was done was failing and causing our clients to not submit data. After asking questions about what's happening, level of impact where it was occurring, I briefly look at the error log and say, "There's the problem, and this was the update that caused it." How did I know, because I smarter? No. I had more experience, I've seen more things. I've solved more problems. Their degrees didn't teach them anything about how to handle that situation. This is why not having a CS degree isn't a death knell of a career, and new people entering the field aren't either.
In fact, every once in a while on here you'll see somebody post a sort of ironic list of the things that they don't teach you in a CS curriculum: databases, networks, version control, debugging, command-line terminal usage, web security, usability... in short, all the things that you actually need to know in order to be a proficient software developer.
Still, nearly everything (computer related) that I learned in my CS degree was stuff that I never would have come across on my own, like calculus, linear algebra, statistics, complexity theory, numerical analysis. It sort of "ties together" the practical stuff, but you don't need to know any of it to be effective. I'm glad I did it because it's neat stuff and a different perspective. In a way, the nice thing about having a degree is knowing that you don't know what you might be overlooking in not having one.
That said... why not just go and get one now? You'll feel a little weird being 10 years older than everybody else and it'll look weird at first putting "15 years experience, graduated last year" on your resume, but you're nearly guaranteed a perfect GPA at this point. In a few years, you'll have the "checkmark" you need and you'll know what you were (or weren't) missing.
I tried. CS classes were a total walk in the park. But I simply could not do the math. I hired tutors, I quit my job and studied full time, I've never tried so hard at anything in my entire life. I bashed my head against a wall for almost 2 years trying to pass calculus, and failed it 3 semesters in a row before giving up. It's why I have the utmost respect for people with engineering degrees now.
I know a number of software developers who are sustaining. They aren't going up the ranks or down the tubes. They are happily sustaining. They do good work and are content.
As we are sold that we always need an upward trajectory... it doesn't work out that way. As you get older you find there is no more up. The purpose of always going up runs out of steam.
> It seems like you either hit the startup equity lotto, or burn out by 40.
Is this a SV or startup mentality?
Most successful startups have an average founders age at founding of like 45. It's not the young in age who are more likely to found successful startups.
If you burn out by 40 it may mean you have an unsustainable lifestyle.
And yeah, management track involves a lot more politics and organizational stuff than I really want to take on, at least within Google. I could see going mgmt track at a smaller company, but without recent experience they wouldn't hire me on that path.
Interviews for senior level positions should contain almost no technical questions at all - you can tell pretty quickly if someone knows what they're talking about by digging into their experience with earlier projects. How was a solution architected? What other ways did they consider? Why did they go the route they did? And my favorite, "think about the most complex project that you had a hand in architecting (for architects) or developing (for developers), and teach it to me." You can immediately see where they focus, what things they gloss over, and if you have time and it's an engaging conversation, changing one of the core pieces and asking how they'd change the design can be a lot of fun (for an interview, anyway).
I think of programming as a creative process. And like any creative process, set and setting are extremely important.
If it makes you feel better, I have a CS bachelor's and I still get imposter syndrome on a fairly regular basis
Thing about having no CS degree is, in some ways I really _am_ an impostor here, in a company where masters and phds are commonplace, in a company was founded by two academics who never worked in the industry, etc. When I first joined I was blown away by how much of Google seemed academia-like... internal conferences with poster boards, peer and code review processes like a doctoral thesis committee, campus cafes, academic publishing all over the place, etc. etc. Hell there's even the equivalent of residences (GSuites, Google managed rental properties for traveling googlers)... It's toned down some as Google has ballooned in size, but still.
I hear this a lot. The difference is that I objectively am an impostor. I've worked with plenty of Stanford/Berkeley CS grads and can conclusively say that I am a worse programmer than them and will never be as good. My concern is that eventually the number of those people will be so great that mediocre devs will be pushed out of the market. I'm honestly incapable of passing these Leetcode/Google style algorithm interviews which are skewed towards CS grads, and that's increasingly becoming the standard for every company regardless of size.
CS degrees train people to think that that kind of thing is what programming is ("why else did I pay thousands for this degree?"), and then they go out into the industry and propagate that in interview processes, and believe that failing these tests in an interview is an obvious indicator that someone is "lying" about their programming ability.
The reality is that for many of us programming is a far more experimental and experential process, and I will use all sorts of algorithmic and data structure techniques but will go read or acquire that knowledge in the process of creating. It's not something I feel comfortable doing on a whiteboard in front of a person or group of people.
Imposter how? Did you lie on your resume? To your co-workers?I would assume not. You were judged on (presumably) the same criteria as anyone else, and found to be at an acceptable level. Maybe other people are better than you, and that's fine. But if you weren't "good enough", they probably wouldn't keep paying you, and your manager would probably say something. It's kind of the point of performance reviews.
Almost everyone is completely incapable of passing a Google interview. That's because they're astronomically hard and they only take the very very best people who are at the top of their fields. I've no hope of passing one either.
But so what?
There's always going to be some place that you aren't going to be able to get a job no matter how good you are. Look somewhere else - there's so many more options.
I would disagree with that. It's because coding problems are a very specific skill. It's essentially being good at riddles with extra esoteric knowledge thrown in.
But correct answer to the question isn't actually necessary. They're looking for your thought processes, and what it reveals about your knowledge and/or techniques, not necessarily correct answers. Some questions don't even have "correct" solutions.
Don't be too discouraged the vast majority of programmers are not going to be from elite institutions ever
I see so many takes like this, but I'm not yet convinced that this is gonna doom salaries long term. I haven't noticed a difference in the recruiting communication I receive in terms of salary, and my current salary is above average. Companies would be insane to ask current employees to take a pay cut to go remote unless they want people to leave.
As long as companies are focused on hiring the best people they can find, they're going to be motivated to continue supporting market rates.
Nothing. Based on numbers I've seen, there are probably a lot of companies out there where I'd take 75% of what their devs are making today if it means I can be permanently remote. Probably 50% if I could move freely internationally. Now multiply that by how many people are eligible once you expand your hiring range from driving distance to national/international.
Software was always an outlier in professional fields, as most industries require some form of degree or certification, so I think it's good to get ahead of the curve.
I star