Earlier quoted context omitted.
Also, an explanation for why more companies aren't doing them given their effectiveness? They're extremely easy to administer.
Possibly legal and reputational risks, considering some groups do badly on IQ tests.
AI killed the tech interview. Now what?
551–560 of 651 posts
Re: AI killed the tech interview. Now what?
#552Earlier quoted context omitted.
I think you're projecting. You aren't posting this using your real name are you?! Here's something to consider, Dennis. Instead of using any type of reasoning that maybe I'm interviewing for a language you aren't familiar with where functions and procedure differences matter, you decided to just go off the handle and call me inexperienced and/or an idiot. This is what we call in the hiring business a "huge red flag."…
Look up my other responses - I decided to call you names _later_ . Other people also pointed that out to you. I'm sure you would thick twice before asking your 'gotcha' again (the question is fine in general but not as a gotcha).
>Lol a bit touchy aren't we?
You lost your composure and decided to start calling names after this. I haven't asked it since the late 90s, early 2000s. It was a for a Delphi position. It's a bonehead easy question any Delphi developer who got to chapter 2 of any Delphi book would have understood. It's still an applicable question for a SQL developer and it's just as easy. I even showed you sample code. I don't see why you aren't getting it.
Re: AI killed the tech interview. Now what?
#553Earlier quoted context omitted.
Yup, it was for a Delphi job in 1998.
Isn't this something the compiler is going to enforce anyway? Why does it matter? If that's the only difference it's kind of inconsequential isn't it?
You would be surprised how many bad applicants interviewers get. It's only gotten worse over the last 20 years.
Re: AI killed the tech interview. Now what?
#554Earlier quoted context omitted.
The equipment is irrelevant. What other career out there expects that practitioners also perform the work at home during their free time as a hobby?
I realize it's a rhetorical question, but pretty much everybody in the arts? I'd be very surprised to find a professional musician that doesn't play as a hobby.
Re: AI killed the tech interview. Now what?
#555Earlier quoted context omitted.
What do you mean by the "high" end? I would consider this sort of interview style necessarily precluding such a place from being considered a high-quality work-place. Not only is it a miserable way to interview, it's not an effective signal for engineer quality beyond rapid code snippet production. > Excluding places that do that leaves you with what exactly? Boutique shops filled with 20 year veterans? We are on a V…
“High end” was meant as shorthand for FAANG …high comp, not necessarily high tech complexity. You are correct about the deficiencies of the whiteboard interview. It is not a sane way to hire an individual. It makes sense as a way to hire someone in the top 20% from a large unfiltered pool. So wrt high/low, that’s what FAANG companies have to do, and for many nontechnical companies they outsource this work or emulate…
I just abandoned the code interview altogether and ask them questions about process. It's a very simple workaround, but very effective. I'll admit it helps that there are very few problems these days outside of specific problems to solve that require a high degree of technical competency to tackle.
Re: AI killed the tech interview. Now what?
#556Earlier quoted context omitted.
Look up my other responses - I decided to call you names _later_ . Other people also pointed that out to you. I'm sure you would thick twice before asking your 'gotcha' again (the question is fine in general but not as a gotcha).
>>You can often tell an inexperienced interviewer from the extremely domain specific question they ask which _they_ are familiar with. >Lol a bit touchy aren't we? You lost your composure and decided to start calling names after this. I haven't asked it since the late 90s, early 2000s. It was a for a Delphi position. It's a bonehead easy question any Delphi developer who got to chapter 2 of any Delphi book would have…
>I haven't asked it since the late 90s, early 2000s.
You overall gave the impression that you are currently asking it.
And a personal rhetorical question - aren't you too old to even state this 'gotcha' business _today_ about what you did in the past? What made you state it? If I gave you the benefit of doubt - that was slip, where you omitted the past tense.
(If I did that in the 90's I'd be a embarrassed to even mention it today.)
Re: AI killed the tech interview. Now what?
#557Earlier quoted context omitted.
You just send out a generic decline, and document it as there's a better candidate fit for the role. I'm not sure if you guys have been in charge of hiring, but there's no real alternative. In my most recent experience, we had one open position, and after interviewing 10 candidates, 3 of them were basically identical in terms of technical qualifications. How do you choose one over the other, other than the "vibes"? A…
a large company doing this (no documentation of a skills gap) who gets subpoenaed would lose 10/10 times
Re: AI killed the tech interview. Now what?
#558Earlier quoted context omitted.
Sure, but in this context, your FAANG experience is a negative signal for people who don't know you well yet. It's unfortunate for you, but a genuine factor you now need to account for. Your path through will probably look like having the luck of breaking in at one of these kinds of companies, and then staying for several years to demonstrate earnest commitment/fit while building a new network of connections, and the…
I find this attitude baffling. In my time at tier one companies I have worked with the best engineers I have come across in my entire career (even the worst engineers were more than competent) who were working on deep issues that could affect the revenue of the entire company because they’re laser focused on providing value to the business, instead of doing engineering for engineering’s sake. I have grown by far more…
Just like there are innumerable brilliant, effective engineers who would contribute tremendously to a FAANG but don't suit the modern interview funnel (leetcode, etc), smaller companies surely do miss out on strong, suitable FAANG engineers in anticipation of negative experiences they've had with others.
There are a lot of people who accumulate FAANG entries on their resume and many of them really don't suit smaller companies for a number of reasons.
Honestly, though while I'm only seeing a very narrow picture of you here, it sure sounds like you see these "tier one" companies as a desirable place to work, with prestigious colleagues and profound learning opportunities on high scale problems that just don't exist elsewhere, and surely for much more money. Are you sure you're really going to be happy somewhere else? Or might you get restless? That's precisely the kind of concern these smaller companies carry when seeing FAANG stuff on a resume, and it doesn't seem like it should be baffling that they would do.
Re: AI killed the tech interview. Now what?
#559Earlier quoted context omitted.
>>You can often tell an inexperienced interviewer from the extremely domain specific question they ask which _they_ are familiar with. >Lol a bit touchy aren't we? You lost your composure and decided to start calling names after this. I haven't asked it since the late 90s, early 2000s. It was a for a Delphi position. It's a bonehead easy question any Delphi developer who got to chapter 2 of any Delphi book would have…
I'm not getting it, I also see that 2 other people are also not getting it. >I haven't asked it since the late 90s, early 2000s. You overall gave the impression that you are currently asking it. And a personal rhetorical question - aren't you too old to even state this 'gotcha' business _today_ about what you did in the past? What made you state it? If I gave you the benefit of doubt - that was slip, where you omitte…
Yes, but you're the only one who threw a tantrum. Enjoy your career.
Re: AI killed the tech interview. Now what?
#560Earlier quoted context omitted.
I used to love getting to know the interviewer and doing things like that but IMO the market has shifted fundamentally on both ends for this to be effective anymore for most SaaS roles. This is anecdotal for US/Canada tech market over the past 10 years so YMMV. Developers Side: Since developers don't have job security anymore (at least for those who work on common languages like Go, Python, Java and Typescript) they…
>its become akin to management consulting or investment banking Not sure how those are similar.