3 ms·
I feel the same thing as you, I think. I was never proud of it per se, but proud of how far I've gotten without one (20 years as a dev, 9 years at Google). But
by cmrdporcupine 6y ago
I feel the same thing as you, I think. I was never proud of it per se, but proud of how far I've gotten without one (20 years as a dev, 9 years at Google). But always felt a sense of impostor syndrome and now I feel it even more pronounced as I've started to look for work elsewhere and wondering if I'm at a profound disadvantage: middle-aged, spent a bunch of time out of the mainstream industry inside Google using non-"standard" tech stacks, no CS degree, and the industry has shifted to interviewing standards that prioritize new grads ("skill" testing algorithm/data structure questions that are far easier for people with recent CS class exposure, etc.)
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.
- jedimastert 6y ago> always felt a sense of impostor syndrome If it makes you feel better, I have a CS bachelor's and I still get imposter syndrome on a fairly regular basis
- cmrdporcupine 6y agoIt's endemic at Google, to the point that it's a cliche. 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.
- aphextron 6y ago>If it makes you feel better, I have a CS bachelor's and I still get imposter syndrome on a fairly regular basis 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.
- cmrdporcupine 6y agoIf you're like me you probably are entirely capable of passing those interviews -- with practice !-- and are probably absolutely fine as a programmer, but are at a disadvantage because it's not the type of stuff you've ever had to do on a regular basis. 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.
- dmarchand90 6y agoI don't have a CS degree either and this does worry me. Luckily it kinda seems like the interviews weigh heavily towards algorithms, which I think is feasible to study alone (might be hard to do while working admittedly). Don't be too discouraged the vast majority of programmers are not going to be from elite institutions ever
- chrisseaton 6y ago> I'm honestly incapable of passing these Leetcode/Google style algorithm interviews 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.
- cmrdporcupine 6y agoMost Googlers are also not capable of passing them. Because they make them harder every year. I've trained twice to give interviews at Google and I just find it demoralizing to administer questions which I myself would find difficult to solve. 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.
- pc86 6y agoI think interviewing at places that do interviews the right way is important. I've interviewed for senior/staff positions before when they immediately start talking about big o notation and asking me to reverse a string on a white board (seriously). Sorry but your CRUD line-of-business app with 150 total and ~10 concurrent users can use whatever algorithm the developer wants, and if anyone is reversing a string manually there is a problem. It's not even worth continuing the interview if they're asking a senior candidate junior-level questions. 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).
- cmrdporcupine 6y agoI agree, and this is how dev interviews always were up until I'd say about 2010 or so... but if you stroll through past conversations on HN about this topic (interviewing) you will see there's very strongly two camps but a _lot_ of people who really feel that the kind of interview you are describing lets in too many false-positives and leads to deadweight people who "can't code." I think of programming as a creative process. And like any creative process, set and setting are extremely important.