4 ms·

Everyone uses the FAANG loop + system design + leetcode design now I don't know when that change happened but it is practically universal

jimmychoozyx 3y ago
Everyone? Nah that's Hyperbole. In my experience about 40% do. I've never had an issue simply showing an open source past project I created, going through my portfolio of other project examples, and my resume.
- britzkopf 3y ago
  I stopped interviewing about 4 months ago because this, in my experience, is NOT hyperbole. Also, 80% of job descriptions, threw kubernetes into the requirements on top of 10 other competencies seemingly just because they can.
  - jimmychoozyx 3y ago
    Good to know. Ya know... I posted that without experience in the current market. It was more of a "this is what it was like a year ago" sentiment. Thinking more about it... I can see how 40% is too low an esimtate. Thanks, good to hear what it is currently like out there on the job hunt. I am about to begin one myself.
- webdood90 3y ago
  40% of the general population? sure for desirable employers with competitive pay, I'd guess closer to 80%.
yogurthewise 3y ago
I've had about 6 different interviews these last couple of months, and none of them gave me leetcode type questions. The closest I got was code snippets where I had to explain what was going on, or very easy fizzbuzz type coding questions.
- midwestcode 3y ago
  What companies? Every company I've interviewed with in my loops recently have me coding in the first technical screen. I've had five of these interviews so far, various sizes. On-site is multiple levels of tech screens. And this isn't even for FAANG-exclusive companies. FWIW, I'm interviewing in a HCOL area for companies that pay well, so it may be more competitive. People often speak of the mystical company that doesn't make you code in the interview, but I haven't come across it once in the current market. I also don't know how comfortable I'd be joining a team that doesn't make me write code in some capacity during the loop... but I also recognize the ridiculousness of expecting correctness, optimal solutions, or the types of questions being asked. Discussing those things, sure, but expecting regurgitation is nonsense.

jimmychoozyx 3y ago

Everyone? Nah that's Hyperbole. In my experience about 40% do. I've never had an issue simply showing an open source past project I created, going through my portfolio of other project examples, and my resume.

britzkopf 3y ago
I stopped interviewing about 4 months ago because this, in my experience, is NOT hyperbole. Also, 80% of job descriptions, threw kubernetes into the requirements on top of 10 other competencies seemingly just because they can.
- jimmychoozyx 3y ago
  Good to know. Ya know... I posted that without experience in the current market. It was more of a "this is what it was like a year ago" sentiment. Thinking more about it... I can see how 40% is too low an esimtate. Thanks, good to hear what it is currently like out there on the job hunt. I am about to begin one myself.
webdood90 3y ago
40% of the general population? sure for desirable employers with competitive pay, I'd guess closer to 80%.

yogurthewise 3y ago

I've had about 6 different interviews these last couple of months, and none of them gave me leetcode type questions. The closest I got was code snippets where I had to explain what was going on, or very easy fizzbuzz type coding questions.

midwestcode 3y ago
What companies? Every company I've interviewed with in my loops recently have me coding in the first technical screen. I've had five of these interviews so far, various sizes. On-site is multiple levels of tech screens. And this isn't even for FAANG-exclusive companies. FWIW, I'm interviewing in a HCOL area for companies that pay well, so it may be more competitive. People often speak of the mystical company that doesn't make you code in the interview, but I haven't come across it once in the current market. I also don't know how comfortable I'd be joining a team that doesn't make me write code in some capacity during the loop... but I also recognize the ridiculousness of expecting correctness, optimal solutions, or the types of questions being asked. Discussing those things, sure, but expecting regurgitation is nonsense.