4 ms·

Maybe I’m either a cynic or a realist. But in my old age (49) I would tell in CS grad who wanted to optimize their compensation 1. “Grind LeetCode and work fo

Maybe I’m either a cynic or a realist. But in my old age (49) I would tell in CS grad who wanted to optimize their compensation 1. “Grind LeetCode and work for BigTech” (c) r/cscareerquestions 2. Read through the leveling guidelines and figure out the politics of the organization. 3. Get on the right teams so you can show “scope” and “impact” 4. Get good at system design and behavioral interviews while you keep your coding interview chops 5. Diversify your RSUs when they vest and save/invest 6. Job hop when needed

isaacremuant 4y ago
To be honest, it's very direct and practical advice. I'd also add that you have to find a way to enjoy what you're doing or none of those points make sense, but being too passionate/involved can also be a mistake if you forget to be smart around the politics and marketing of career advancement.
nickpeterson 4y ago
I don’t know anything about SV or big tech hiring so I’m sure it’s reasonable hiring advice, I don’t know. That said, boy it sounds like a recipe for burnout.
- scarface74 4y ago
  Oh it very much is. I’m 49 and joined BigTech at 46. I recognized that a year in and decided not to play the game. I found out the minimum I had to do to stay at a mid level role working remotely and actively took myself off of that treadmill and used the extra money to reduce my expenses and save so at anytime I could afford to hop.
  - lhorie 4y ago
    Then you joined big tech at the peak of the pandemic boom, when it was completely fair game to for recruiters to be poaching even foreigners due to the outsized growth outlooks. You should be aware that the economic environment has basically taken a 180 since then, and your experience might be very different from someone joining the workforce today with no work experience. To counter the "cram LC" thing, the issue is that there are plenty of new grads doing exactly that who don't even get past ATS screening. You just don't hear about it much because places like cscq are echo chambers w/ high degrees of survivorship bias and there's qualitative levels of difference to "cramming leetcode" that can't really be captured in online discussions. Ultimately the generalization seems to be "don't pigeonhole yourself, set yourself apart in some way", which is, IMHO, not exactly a super insightful revelation. That has always been the "smart" way to play the game.
    - scarface74 4y ago
      My title is not “software engineer”. I pivoted into “cloud consulting” to get into BigTech. I fell into that role because I do have the combination of skills that the article author spoke of - and I’m an MBA drop out. But my route was very circuitous and I would never recommend it. As someone who considers himself a student of organizational behavior and being on the inside informs my viewpoint. Being that I’m billable. There is a direct line between my work and revenue I generate.
      - lhorie 4y ago
        Many of us went through circuitous routes. My title is SWE at a big tech company and I interview SWE candidates, so I think I'm relatively close to how the sausage is made in terms of the pipeline through which most engineering candidates go through to get into big tech. Personally I think "grind LC" is a very common meme perpetuated by folks on the candidate side, but it lacks a lot of context in terms of how modern big tech interviews are actually done. Focusing exclusively on code, for example, is IMHO, a counter productive way of hyper-focusing. I personally didn't even know what leetcode was when I joined my big tech company, for example. I did well in the loops because they evaluated various other things that I could demonstrate thanks to previous open source work (e.g. community building). What you're basically seem to be saying is that you fell into big tech thanks to a fortuitously aligned set of previous experiences, as many of us did. But that's the exact opposite of grinding LC as a newbie. Grinding LC is one way of hyper-focusing, and going by the numbers, it's no longer necessarily sufficient to land a big tech job.
        scarface74 4y ago
        I have only been involved in software engineering interviews at BigTech for senior devs in the System Design round (because doing System Design is part of my $DayJob). Just to explain my perspective. When I was in the real world and when I interviewed at my current job, I practiced being able to explain my experience in STAR format based on my “career document”. In the real world, all of my “interviews” were mostly just my talking to CxOs and directors at small companies. My loop for my current job was all behavioral after the initial screening and even that was more system design than anything else. If you know there is going to be a coding interview, wouldn’t it behoove you to practice that too - or “grind leetcode?” I did DS&A back as part of my job during the first decade of my career bit twiddling in C across multiple architectures and later on maintaining a custom compiler toolchain. But I would definitely have to practice to be interview ready at this point. The coding part of my job has gotten a lot easier during the last decade. It’s been about knowing what to write and getting buy in
HeyLaughingBoy 4y ago
There's nothing wrong with this list, but if you also (7) Get into a position where Sales & Marketing look at you as someone valuable, you'll end up far more successful than you would otherwise.
- scarface74 4y ago
  You eventually have to do that to show “scope” and “impact”. That’s true.
the_jeremy 4y ago
I think that learning about other roles is a way to significantly mitigate the luck inherently involved in getting "on the right team to show scope and impact".
ren_engineer 4y ago
AI might make this advice outdated, if AI is able to handle a decent chunk of common coding tasks then the people who understand business impact and where to focus efforts will be the most valuable engineers, not the leetcode grinders. Google's huge issue with launching stuff nobody wants and then shutting it down is a prime example of what happens when you keep rewarding algorithm/CS specialists over engineers who dedicated time to other things
- gardenhedge 4y ago
  Actually I think that is more of an issue with Google's MBA and Product/Project manager culture than rewarding algorithm/CS specialists
fortituded0002 4y ago
This is all solid advice but seems to be unrelated to gaining an unfair advantage. I interpret "unfair advantage" to be more about employability and how valuable you are in the field (starting with inside the business you are in) and not about putting more money in your pocket.
- scarface74 4y ago
  My value to my last company - - a 60 person startup where I was a senior software engineer /the de facto “cloud architect” - was much greater than it is at the second largest employer in the US. But, if your goal is to exchange your labor for as much money as you can, you optimize for what can get you the highest compensation based on your skillset and path dependencies - family obligations, desires, etc

isaacremuant 4y ago

To be honest, it's very direct and practical advice. I'd also add that you have to find a way to enjoy what you're doing or none of those points make sense, but being too passionate/involved can also be a mistake if you forget to be smart around the politics and marketing of career advancement.

nickpeterson 4y ago

I don’t know anything about SV or big tech hiring so I’m sure it’s reasonable hiring advice, I don’t know. That said, boy it sounds like a recipe for burnout.

scarface74 4y ago
Oh it very much is. I’m 49 and joined BigTech at 46. I recognized that a year in and decided not to play the game. I found out the minimum I had to do to stay at a mid level role working remotely and actively took myself off of that treadmill and used the extra money to reduce my expenses and save so at anytime I could afford to hop.
- lhorie 4y ago
  Then you joined big tech at the peak of the pandemic boom, when it was completely fair game to for recruiters to be poaching even foreigners due to the outsized growth outlooks. You should be aware that the economic environment has basically taken a 180 since then, and your experience might be very different from someone joining the workforce today with no work experience. To counter the "cram LC" thing, the issue is that there are plenty of new grads doing exactly that who don't even get past ATS screening. You just don't hear about it much because places like cscq are echo chambers w/ high degrees of survivorship bias and there's qualitative levels of difference to "cramming leetcode" that can't really be captured in online discussions. Ultimately the generalization seems to be "don't pigeonhole yourself, set yourself apart in some way", which is, IMHO, not exactly a super insightful revelation. That has always been the "smart" way to play the game.
  - scarface74 4y ago
    My title is not “software engineer”. I pivoted into “cloud consulting” to get into BigTech. I fell into that role because I do have the combination of skills that the article author spoke of - and I’m an MBA drop out. But my route was very circuitous and I would never recommend it. As someone who considers himself a student of organizational behavior and being on the inside informs my viewpoint. Being that I’m billable. There is a direct line between my work and revenue I generate.
    - lhorie 4y ago
      Many of us went through circuitous routes. My title is SWE at a big tech company and I interview SWE candidates, so I think I'm relatively close to how the sausage is made in terms of the pipeline through which most engineering candidates go through to get into big tech. Personally I think "grind LC" is a very common meme perpetuated by folks on the candidate side, but it lacks a lot of context in terms of how modern big tech interviews are actually done. Focusing exclusively on code, for example, is IMHO, a counter productive way of hyper-focusing. I personally didn't even know what leetcode was when I joined my big tech company, for example. I did well in the loops because they evaluated various other things that I could demonstrate thanks to previous open source work (e.g. community building). What you're basically seem to be saying is that you fell into big tech thanks to a fortuitously aligned set of previous experiences, as many of us did. But that's the exact opposite of grinding LC as a newbie. Grinding LC is one way of hyper-focusing, and going by the numbers, it's no longer necessarily sufficient to land a big tech job.
      - scarface74 4y ago
        I have only been involved in software engineering interviews at BigTech for senior devs in the System Design round (because doing System Design is part of my $DayJob). Just to explain my perspective. When I was in the real world and when I interviewed at my current job, I practiced being able to explain my experience in STAR format based on my “career document”. In the real world, all of my “interviews” were mostly just my talking to CxOs and directors at small companies. My loop for my current job was all behavioral after the initial screening and even that was more system design than anything else. If you know there is going to be a coding interview, wouldn’t it behoove you to practice that too - or “grind leetcode?” I did DS&A back as part of my job during the first decade of my career bit twiddling in C across multiple architectures and later on maintaining a custom compiler toolchain. But I would definitely have to practice to be interview ready at this point. The coding part of my job has gotten a lot easier during the last decade. It’s been about knowing what to write and getting buy in

HeyLaughingBoy 4y ago

There's nothing wrong with this list, but if you also (7) Get into a position where Sales & Marketing look at you as someone valuable, you'll end up far more successful than you would otherwise.

scarface74 4y ago
You eventually have to do that to show “scope” and “impact”. That’s true.

the_jeremy 4y ago

I think that learning about other roles is a way to significantly mitigate the luck inherently involved in getting "on the right team to show scope and impact".

ren_engineer 4y ago

AI might make this advice outdated, if AI is able to handle a decent chunk of common coding tasks then the people who understand business impact and where to focus efforts will be the most valuable engineers, not the leetcode grinders. Google's huge issue with launching stuff nobody wants and then shutting it down is a prime example of what happens when you keep rewarding algorithm/CS specialists over engineers who dedicated time to other things

gardenhedge 4y ago
Actually I think that is more of an issue with Google's MBA and Product/Project manager culture than rewarding algorithm/CS specialists

fortituded0002 4y ago

This is all solid advice but seems to be unrelated to gaining an unfair advantage. I interpret "unfair advantage" to be more about employability and how valuable you are in the field (starting with inside the business you are in) and not about putting more money in your pocket.

scarface74 4y ago
My value to my last company - - a 60 person startup where I was a senior software engineer /the de facto “cloud architect” - was much greater than it is at the second largest employer in the US. But, if your goal is to exchange your labor for as much money as you can, you optimize for what can get you the highest compensation based on your skillset and path dependencies - family obligations, desires, etc