7 ms·

Why does getting a job in tech suck?

66 points by InfamousRece 2y ago

jarsin 2y ago
> Interest rates are most likely the single biggest factor for why tech hiring has gotten worse. The fed just made it official that the easing cycle is beginning. The 10yr has already front run them by about 1.7%. So if the article conclusion is correct tech job market could look good going into the new year.
- tmn 2y ago
  The effect takes place with a lag in both directions. Positive impact due to interest rates being lowered is likely further out than start of next year. But that’s just my guess
crackalamoo 2y ago
Really interesting idea overall. But I disagree with this part: > Algorithms are tiny parts of large systems. The algorithm part can usually be abstracted as an API call that provides some value(s) with inherent uncertainty; an ML endpoint is in essence an API call with few or no side-effects that returns an uncertain value. It turns out, the system design surrounding this almost always matters more than the algorithm and the dumb algorithms tend to do well enough anyway. I think this is basically dismissing almost all APIs and algorithms in favor of system design. But system design is pretty similar in many apps, while the value of each app is very different. So clearly the API/algorithm is very important, and often the most important part. I also disagree about AI not taking jobs. GitHub copilot definitely makes programming about 30% faster. To keep up the jobs, we would have to write 30% more code. But it seems innovation is the limiting factor more than typing code, so maybe we'll only write 15% more code, and we can have less devs.
- cellis 2y ago
  The current AI is producing more garbage to maintain, which means those who can do trash-compactor work will be in even MORE demand, and companies tend to over-hire in search of the garbage taker outers...so AI is creating MORE work, not less.
- ai4ever 2y ago
  agree that anyone making broad generalities like "algos dont matter" is always mistaken. but API design is more about the system, and how it is carved out into components, and what each component does is the algo. so, api and algo are tied together. compilers eased the production of assembly code. that didnt reduce the need for folks coding at a different layer of abstraction.
eclectic29 2y ago
A whole article about getting a job in tech and no mention of the abominable leetcode. Surprise! From junior to principal Leetcode is here to stay. Good luck solving 2 problems in 35 mins.
- ilrwbwrkhv 2y ago
  I explicitly said no leetcode when I was an employee and getting hired and reached close to half a million dollar salary. So at least another path is present if devs don't give in.
5350-uiop-1130 2y ago
AI has certainly made me feel like coding is low value. the derivative and repetitive nature of most coding tasks. when I ask GPT for some code and it spits out 200 lines of boilerplate in 2 seconds, i feel sick. what am i doing with my life.
- ein0p 2y ago
  Really? It automates the extremely boring and low skill part of your job and you "feel sick"? I feel pretty great about getting to focus on the actual problem rather than on boilerplate.
  - Borg3 2y ago
    No, you are absolutly wrong. If you would automate it yourself then its correct way of doing thing. You learn by the process, increasting your skill. But no, you choosed to do automation by AI, so you become nothing more that a frontend to put data in. Also, you are slowly loosing control about stuff you doing. I know, todays engineering culture is weird. Dont ask questions, its not of your concern, etc.. I wonder when that stuff finaly collapse.
    - deleted 2y ago
      [deleted]
    - joshstrange 2y ago
      This is a boring and tired take, I’m sorry but it is. Might as well take it to the logical conclusion that if you aren’t creating all your components (I’m taking IC’s, transistors, etc) by hand then are you really learning or increasing your skill. You’ve picked an arbitrary point in the tech stack and declared that any lower is not needed but any higher means you’ve lost control. It’s like the people that scorn higher-level languages.
      - ein0p 2y ago
        Precisely. LLM assistance is how I felt in the 90s about programming in Delphi and C++ Builder. It felt like cheating, but in a good way, I was getting to solving my problem in no time at all. Except back then it was mostly about the UI, and now it’s for other things as well
somethoughts 2y ago
I think an interesting follow-up discussion/blog post would be - okay getting a job in tech may suck... but doesn't getting a job outside of tech suck even harder? In other words, if you were starting college today, would you still do tech? Is it still better than getting any other job for equivalent pay bands? Specifically comparing early career job seekers: * Easier/harder to get $50-100K tech job versus $50-100K job in other fields? * Easier/harder to get $100-150K tech job versus $100-150K job in other fields? * Easier/harder to get $150-200K tech job versus $150-200K job in other fields? Other fields are things like marketing, accounting, law, medical, biotech. A quant/finance job is probably CS or CS adjacent these days so its basically a tech job. My take is that by the time you get above $130K there probably is not any other field outside of tech where this is possible unless there is some very unique skill. And instead of annoying but somewhat objective leetcode/live coding whiteboard interviews; hiring is way more subjective, credential based, network based and gate kept.
- cheschire 2y ago
  I would be interested in seeing how many tech jobs within two standard deviations of the mean pay above $130k, especially once you start adjusting for cost of living.
- nradov 2y ago
  Getting a job in medicine is usually somewhat more straightforward with less BS about skills tests, at least for the common specialties. Most organizations have shortages of physicians and other high-level practitioners so they can't afford to turn away qualified candidates unless there are major red flags. Of course medicine has other downsides as a career field which makes it maybe not a great choice unless you really love it.
  - Icathian 2y ago
    You can't really be making this comparison, though? Getting an MD and residency and rotations means you're in your thirties before you get your first real job. At least in the US. It's wildly more difficult.
mianos 2y ago
A big thing is the rise and rise of bullshitters. Wall to wall buzzwords and made up stories about what they did in their last job. Leetcode filters a lot, but it also filters out, just as many, if not more, people who can actually do what they say.
- blablabla123 2y ago
  It's a very strange filter though. At my current job there's a multi-stage hiring process with leetcode tests. And yet most people lack substantial domain knowledge, it's really frustrating. In fact the code base hardly has a visible architecture
  - wildrhythms 2y ago
    Indeed, Leetcode tests algorithmic knowledge but no domain knowledge. I work professionally as a front-end developer and I dread losing my job because I could never pass a Leetcode interview. I can thoroughly reason about web development, I know the stack front and back, it's my passion... but a Leetcode interview doesn't test for that at all. I think every tech-related company looked at the high bar at big tech, assumed the algorithm questions was the only signal (it's not), and have been poorly aping that ever since. I also think a simple 20 minute discussion between a hiring candidate and an engineer simply discussing how to build something will give you better hiring signals than any Leetcode challenge.
    - mianos 2y ago
      Yep, it's just some "cargo cult". I attended a meetup a number of years ago at a local trading firm, well known for a barrage of impossible puzzles and some simpler, like implement an order book for a matching engine. One of their senior guys did a talk on their trading system. I asked a basic question and the answer was so naive it was shocking. Maybe their best people don't do the talking.
- jazz9k 2y ago
  Leetcode is also there to filter out older developers. Most older developers probably never used those algorithms in college.
tekla 2y ago
It doesn't suck. Its mostly reverting to "how everyone else dealt with getting a job in the last 100 years"
yungporko 2y ago
in my experience it doesn't suck too much in the uk. i've never had a shortage of interviews and i've never had an interview like the ones frequently described by americans, where they have to write code on a whiteboard and solve extrenely difficult leetcode questions etc. i update my cv, upload it to the big recruitment websites, recruiters do all of the work, my phone rings 3-5 minutes later and the calls barely stop for a second until i've been in my new role for 2-3 months. interviews are always laid back conversations over the phone or a teams call with no curveballs, just the standard questions like what kind of stuff do you work on in your current job, what tech stack do you use, what do you think about [current popular thing], etc. i'd say i get an offer from about half of the interviews i do. my only real complaint other than the amount of recruiters who deliberately waste mine and their own time for reasons known only to them (which has always been a thing), is the very obvious coordinated push to get people "back in the office" spilling over and affecting developers, which means there are way less fully remote roles than there were even before covid.
PeterStuer 2y ago
"I think if your product doesn’t work with an off-the-shelf model, it’s unlikely to magically start working with a custom, in-house model." In my experience a lott of LLM usage in B2B is fairly basic (translation, summerization, data extraction, categorization) and fairly well handled by current SOTA foundation models. Could this be improved by custom/finetuned models? Sure, but in nearly all cases I have seen the ROI of improving other parts of the application is way higher than the investment in developing and maintaining custom models.

66 points by InfamousRece 2y ago

> Interest rates are most likely the single biggest factor for why tech hiring has gotten worse. The fed just made it official that the easing cycle is beginning. The 10yr has already front run them by about 1.7%. So if the article conclusion is correct tech job market could look good going into the new year.

tmn 2y ago
The effect takes place with a lag in both directions. Positive impact due to interest rates being lowered is likely further out than start of next year. But that’s just my guess

crackalamoo 2y ago

Really interesting idea overall. But I disagree with this part: > Algorithms are tiny parts of large systems. The algorithm part can usually be abstracted as an API call that provides some value(s) with inherent uncertainty; an ML endpoint is in essence an API call with few or no side-effects that returns an uncertain value. It turns out, the system design surrounding this almost always matters more than the algorithm and the dumb algorithms tend to do well enough anyway. I think this is basically dismissing almost all APIs and algorithms in favor of system design. But system design is pretty similar in many apps, while the value of each app is very different. So clearly the API/algorithm is very important, and often the most important part. I also disagree about AI not taking jobs. GitHub copilot definitely makes programming about 30% faster. To keep up the jobs, we would have to write 30% more code. But it seems innovation is the limiting factor more than typing code, so maybe we'll only write 15% more code, and we can have less devs.

cellis 2y ago
The current AI is producing more garbage to maintain, which means those who can do trash-compactor work will be in even MORE demand, and companies tend to over-hire in search of the garbage taker outers...so AI is creating MORE work, not less.
ai4ever 2y ago
agree that anyone making broad generalities like "algos dont matter" is always mistaken. but API design is more about the system, and how it is carved out into components, and what each component does is the algo. so, api and algo are tied together. compilers eased the production of assembly code. that didnt reduce the need for folks coding at a different layer of abstraction.

eclectic29 2y ago

A whole article about getting a job in tech and no mention of the abominable leetcode. Surprise! From junior to principal Leetcode is here to stay. Good luck solving 2 problems in 35 mins.

ilrwbwrkhv 2y ago
I explicitly said no leetcode when I was an employee and getting hired and reached close to half a million dollar salary. So at least another path is present if devs don't give in.

5350-uiop-1130 2y ago

AI has certainly made me feel like coding is low value. the derivative and repetitive nature of most coding tasks. when I ask GPT for some code and it spits out 200 lines of boilerplate in 2 seconds, i feel sick. what am i doing with my life.

ein0p 2y ago
Really? It automates the extremely boring and low skill part of your job and you "feel sick"? I feel pretty great about getting to focus on the actual problem rather than on boilerplate.
- Borg3 2y ago
  No, you are absolutly wrong. If you would automate it yourself then its correct way of doing thing. You learn by the process, increasting your skill. But no, you choosed to do automation by AI, so you become nothing more that a frontend to put data in. Also, you are slowly loosing control about stuff you doing. I know, todays engineering culture is weird. Dont ask questions, its not of your concern, etc.. I wonder when that stuff finaly collapse.
  - deleted 2y ago
    [deleted]
  - joshstrange 2y ago
    This is a boring and tired take, I’m sorry but it is. Might as well take it to the logical conclusion that if you aren’t creating all your components (I’m taking IC’s, transistors, etc) by hand then are you really learning or increasing your skill. You’ve picked an arbitrary point in the tech stack and declared that any lower is not needed but any higher means you’ve lost control. It’s like the people that scorn higher-level languages.
    - ein0p 2y ago
      Precisely. LLM assistance is how I felt in the 90s about programming in Delphi and C++ Builder. It felt like cheating, but in a good way, I was getting to solving my problem in no time at all. Except back then it was mostly about the UI, and now it’s for other things as well

somethoughts 2y ago

I think an interesting follow-up discussion/blog post would be - okay getting a job in tech may suck... but doesn't getting a job outside of tech suck even harder? In other words, if you were starting college today, would you still do tech? Is it still better than getting any other job for equivalent pay bands? Specifically comparing early career job seekers: * Easier/harder to get $50-100K tech job versus $50-100K job in other fields? * Easier/harder to get $100-150K tech job versus $100-150K job in other fields? * Easier/harder to get $150-200K tech job versus $150-200K job in other fields? Other fields are things like marketing, accounting, law, medical, biotech. A quant/finance job is probably CS or CS adjacent these days so its basically a tech job. My take is that by the time you get above $130K there probably is not any other field outside of tech where this is possible unless there is some very unique skill. And instead of annoying but somewhat objective leetcode/live coding whiteboard interviews; hiring is way more subjective, credential based, network based and gate kept.

cheschire 2y ago
I would be interested in seeing how many tech jobs within two standard deviations of the mean pay above $130k, especially once you start adjusting for cost of living.
nradov 2y ago
Getting a job in medicine is usually somewhat more straightforward with less BS about skills tests, at least for the common specialties. Most organizations have shortages of physicians and other high-level practitioners so they can't afford to turn away qualified candidates unless there are major red flags. Of course medicine has other downsides as a career field which makes it maybe not a great choice unless you really love it.
- Icathian 2y ago
  You can't really be making this comparison, though? Getting an MD and residency and rotations means you're in your thirties before you get your first real job. At least in the US. It's wildly more difficult.

mianos 2y ago

A big thing is the rise and rise of bullshitters. Wall to wall buzzwords and made up stories about what they did in their last job. Leetcode filters a lot, but it also filters out, just as many, if not more, people who can actually do what they say.

blablabla123 2y ago
It's a very strange filter though. At my current job there's a multi-stage hiring process with leetcode tests. And yet most people lack substantial domain knowledge, it's really frustrating. In fact the code base hardly has a visible architecture
- wildrhythms 2y ago
  Indeed, Leetcode tests algorithmic knowledge but no domain knowledge. I work professionally as a front-end developer and I dread losing my job because I could never pass a Leetcode interview. I can thoroughly reason about web development, I know the stack front and back, it's my passion... but a Leetcode interview doesn't test for that at all. I think every tech-related company looked at the high bar at big tech, assumed the algorithm questions was the only signal (it's not), and have been poorly aping that ever since. I also think a simple 20 minute discussion between a hiring candidate and an engineer simply discussing how to build something will give you better hiring signals than any Leetcode challenge.
  - mianos 2y ago
    Yep, it's just some "cargo cult". I attended a meetup a number of years ago at a local trading firm, well known for a barrage of impossible puzzles and some simpler, like implement an order book for a matching engine. One of their senior guys did a talk on their trading system. I asked a basic question and the answer was so naive it was shocking. Maybe their best people don't do the talking.
jazz9k 2y ago
Leetcode is also there to filter out older developers. Most older developers probably never used those algorithms in college.

tekla 2y ago

It doesn't suck. Its mostly reverting to "how everyone else dealt with getting a job in the last 100 years"

yungporko 2y ago

in my experience it doesn't suck too much in the uk. i've never had a shortage of interviews and i've never had an interview like the ones frequently described by americans, where they have to write code on a whiteboard and solve extrenely difficult leetcode questions etc. i update my cv, upload it to the big recruitment websites, recruiters do all of the work, my phone rings 3-5 minutes later and the calls barely stop for a second until i've been in my new role for 2-3 months. interviews are always laid back conversations over the phone or a teams call with no curveballs, just the standard questions like what kind of stuff do you work on in your current job, what tech stack do you use, what do you think about [current popular thing], etc. i'd say i get an offer from about half of the interviews i do. my only real complaint other than the amount of recruiters who deliberately waste mine and their own time for reasons known only to them (which has always been a thing), is the very obvious coordinated push to get people "back in the office" spilling over and affecting developers, which means there are way less fully remote roles than there were even before covid.

PeterStuer 2y ago

"I think if your product doesn’t work with an off-the-shelf model, it’s unlikely to magically start working with a custom, in-house model." In my experience a lott of LLM usage in B2B is fairly basic (translation, summerization, data extraction, categorization) and fairly well handled by current SOTA foundation models. Could this be improved by custom/finetuned models? Sure, but in nearly all cases I have seen the ROI of improving other parts of the application is way higher than the investment in developing and maintaining custom models.