Live data from Hacker News

Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

chrlschn.dev

201–210 of 286 posts

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#201

Earlier quoted context omitted.

Not him but 1.) DS and Algo knowledge are way overrated in day-to-day job functions. I have yet to have to implement a single DS or Algo from those classes (they are almost always available to the framework, standard library, or language), runtime complexity has literally never once come up in my life, and the most I've ever needed to know about data structures is "which one should I use here?" and 99% of the time it…

> runtime complexity has literally never once come up in my life There are definitely different types of programming jobs, but for some contrast: I have never had a job where runtime complexity did not come up as a significant factor somewhat frequently. It really comes down to what you’re doing, but at a certain scale or size of problem you really do need to know about algorithms, data structures, and runtime comple…

I'd estimate that 98% of companies are just receive-deserilze-validate-transform-store a.k a CRUD shops though some might have borken it down into distributed chunks (Micro Services) without any of the distributed tooling or mindset and awareness in place.

So... That's less likely where you'll need your dynamic programming or palindromes in constant time or space.

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#202

Earlier quoted context omitted.

> we occasionally have to let someone go on background issues What kind of issue would that be?

Undisclosed felonies is a popular one.

Had they disclosed the felony would they have made it that far?

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#203

Earlier quoted context omitted.

> 7. Background checks start in parallel with on-boarding. First week is spent with business unit teams to learn what the company actually, really does. Yikes!!! I’ve never heard of a potential employer giving offers before background check. Do you tell candidates this before they quit their current jobs?

On one hand it sounds off putting, on other hand it can be very awkward that you have hired a mole from competition who is there to understand your secret sauce and get out or that you have hired somebody who was in prison for computer crimes.

A week -1 background check would find anything a week 1 background check would find.

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#204

Earlier quoted context omitted.

Also, using scripting languages and misusing browser engines unironically yet expecting performance...

Using electron isn't a performance decision, it's a labor one. It's easier to write a website once and then just export to electron than it is to rewrite your application in QT or XAML or another native desktop framework and have to hire C++ or C# developers

If Browsers can do Figma and VS code, they're already a far capable and approachable platform at least for most desktop applications than Qt especially for anything that has some data entry such as ERPs etc. And it's free. Qt is not.

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#205
post #31

Not sure if it would be any better, and I say this as someone who hates leetcode-related interviews. Code reviews are way more subjective than writing a piece code (at the end of the interview session, if the code works, then that's a huge thing already). If I highlight something like "Perhaps we could inject that dependency, instead of harcoding it": sure, that seems probably the most correct assesment, but again, w…

I've come to the conclusion that any sort of job interview has a high level of subjectivity. Basically as an applicant, you roll the dice and hope that you have a good day and "click" with the interviewer.

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#206

Earlier quoted context omitted.

The problem is that it might have been true at some point but now there are resources to “learn” for interviews, so currently you will get people willing to grind. Nobody happy with their pay and job is going to grind leetcode. They could just ignore leetcode and ask puzzle problems instead to test ability.

Honestly, being "willing to grind" might be a good thing to target if it's a good proxy for being willing to do the work . However, I agree with the general sentiment that almost nobody is doing the research to ensure their interview process selects for the things they actually want.

> Honestly, being "willing to grind" might be a good thing to target if it's a good proxy for being willing to do the work.

Grinding is a poor proxy for work ethic. It is a good proxy for submissiveness.

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#207

Earlier quoted context omitted.

It seems like chasing golden unicorn super smart bois has been more of a problem than a solution in SV and companies like google. It starts to look like a schoolyard game or mensa. I'll just get the smartest of the smarts and rule the world! If I only get the alphas of the alphas, I'll surely win. Reminds me of all the NBA players getting schooled in FIBA, because the international teams have better chemistry. At one…

> It seems like chasing golden unicorn super smart bois has been more of a problem than a solution in SV and companies like google. It starts to look like a schoolyard game or mensa. > What I'm talking about isn't just awkwardness and lacking charisma. I'm talking about randomly telling women that they can tell she is on her period and things like that. These don't seem limited to SV and Big Companies™ like Google, a…

Maybe true, but in other industries, such as ones that are more "business and engineery, there's less of this obsession with getting an ultra-genius, although we know how valuable engineering talent is.

As a result you get pretty average people. Even the weirdos tend to be just quiet and reclusive. My brother on the other hand, went to work for a smaller B tier to google, and he had multiple co-workers that were just beyond bizarre.

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#208

Earlier quoted context omitted.

So you have someone start before you've decided to hire them. This sounds incredibly sleezy.

Sounds incredibly like a non-starter for people who aren't completely desperate. Then again, maybe that's who they're looking for.

It's bizarre to do with background checking specifically. Like WTF, you're gonna have someone come in and then fire them because of their past.

I thought it was bad enough these people trying to get you to start as soon as you clear HR.

I'd never even thought about the idea of starting before getting the greenlight... this is insanity.

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#209

Earlier quoted context omitted.

Honestly, being "willing to grind" might be a good thing to target if it's a good proxy for being willing to do the work . However, I agree with the general sentiment that almost nobody is doing the research to ensure their interview process selects for the things they actually want.

> Honestly, being "willing to grind" might be a good thing to target if it's a good proxy for being willing to do the work. Grinding is a poor proxy for work ethic. It is a good proxy for submissiveness.

You might be right, but I think it could be both.

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#210

Earlier quoted context omitted.

Doing the background check after the offer is fine, it's insane that they do it after the candidate already starts the new job. So what, I leave my current job to come work for you, and in the first week you tell me "sorry you failed our background check" and let me go? Who the F would ever agree to this kind of risk? >>8. End of first week, we occasionally have to let someone go on background issues Yeah, that's bon…

This is normal for non-tech employers. It is novel in tech, but not something that is bonkers in other sectors. We're able to have developers on the payroll three-four weeks before offers are out by competitors.

[deleted]
Post reply on HN