Earlier quoted context omitted.
I still recall an interview I did at a recently public company in New York, for a DevOps position. 4/5 of the interviews went sailingly, with heavy emphasis on networking, scripting, and AWS knowledge. Then the lead engineer sailed in, five minutes late. He gave me an algorithm question straight from the Google playbook (I don't remember the question, sadly), then after I asked for a few minutes to ponder, proceeded…
What an ass. I wish there was a way to report bad interviewers. Maybe some tech media company will do hidden camera interviews and publish a scathing rebuke of the practice.
Ten years of experience, still failing phone screens
61–70 of 340 posts
Re: Ten years of experience, still failing phone screens
#62Earlier quoted context omitted.
> This post ought to be the final nail on the coffin of the cult of leetcode/whiteboard style inverviewing. Looks like he has ADHD. Maybe somebody with more time can go through his blog post line-by-line and figure out what's going on. Most of my Coderpad stuff compiles and runs the first time, so I don't use his incremental test method, or see a need for it. Maybe he learned programming on heavy-weight IDEs and got…
A lot of devs have ADHD.
Re: Ten years of experience, still failing phone screens
#63This post ought to be the final nail on the coffin of the cult of leetcode/whiteboard style inverviewing. Just looking at this guy's repo and his writing style -- you'd be foolish to waste his time or yours on leetcode-style hazing. Your conversation should be strictly high-level. If you must, pick a file at random from one his larger projects, and ask a few straightforward quetions ("I'm new to Go - can you explain…
> This post ought to be the final nail on the coffin of the cult of leetcode/whiteboard style inverviewing. Looks like he has ADHD. Maybe somebody with more time can go through his blog post line-by-line and figure out what's going on. Most of my Coderpad stuff compiles and runs the first time, so I don't use his incremental test method, or see a need for it. Maybe he learned programming on heavy-weight IDEs and got…
Re: Ten years of experience, still failing phone screens
#64> I often make trivial mistakes just trying to get a "first draft" of a program out In my experience, it's helpful to add simple tests as you go. I have done some live coding tests in Python recently, which I'm not super familiar with, and the first couple I did, I made a lot of trivial errors that caused my solution to fail until I went back and cleaned them up. Luckily the interviewers kept their mouths shut while…
Re: Ten years of experience, still failing phone screens
#65at this point of my career i straight out refuse technical/coding interviews i have a GitHub account with 7 years worth of contributions, multimillion dollar exit, projects online and previous senior roles on my cv if they still don’t trust me to do my job, the one i’ve provably done about a decade, their loss nowadays it’s easier to find high-dollar consulting gigs than deal with dysfunctional hiring processes advic…
I've gotten nearly 100% of the jobs I've gotten in the past 15 years through friends. Interview process real easy after the informal "backchannel" reference check has happened. Just hi, how you doing, when can you start.
Re: Ten years of experience, still failing phone screens
#66Re: Ten years of experience, still failing phone screens
#67at this point of my career i straight out refuse technical/coding interviews i have a GitHub account with 7 years worth of contributions, multimillion dollar exit, projects online and previous senior roles on my cv if they still don’t trust me to do my job, the one i’ve provably done about a decade, their loss nowadays it’s easier to find high-dollar consulting gigs than deal with dysfunctional hiring processes advic…
I'm on your team. up front technical "gotcha" style evaluations feel like they don't respect where I'm coming from, nor my track record of work - and are a cue that the job is not the place I want to be at. I've gotten nearly 100% of the jobs I've gotten in the past 15 years through friends. Interview process real easy after the informal "backchannel" reference check has happened. Just hi, how you doing, when can you…
better spend more time maintaining those connections
i myself never really practiced algorithms, so in an interview they’ll see me as a weak learner
however the reality is complete opposite - i have spent thousands of hours on piano and guitar and speak 3 languages
i have the opposite of learning disability and learn stuff quicker than many of your algorithm-knowing employees can
Re: Ten years of experience, still failing phone screens
#68Earlier quoted context omitted.
They could just need training and feedback. A lot of places just throw any rando engineer into an interview with no coaching on how to behave, how to set guide rails for the candidate, how to empathize and pace the interview, what the evaluation criteria and rubric is. And then after the interview, the person has no idea if he conducted the interview properly. Totally open loop. Just yeet him at candidates untrained…
I've been that person :( I still cringe when I think back on some of the early interviews I did.
some people don’t
Re: Ten years of experience, still failing phone screens
#69Interviewing is really tough. The OP replaced some coding questions with other questions and if he were to interview a bunch of people with them, we'd get another set of blog posts complaining how ridiculous his interview questions were. "Why is it bad to write a file to the disk one byte at a time?" What are they interviewing for, low level disk experts? "Here's a stack trace from an open source project, can you tel…
> What are they interviewing for, low level disk experts? Why would only low level disk experts be able to answer that?
Re: Ten years of experience, still failing phone screens
#70Earlier quoted context omitted.
I still recall an interview I did at a recently public company in New York, for a DevOps position. 4/5 of the interviews went sailingly, with heavy emphasis on networking, scripting, and AWS knowledge. Then the lead engineer sailed in, five minutes late. He gave me an algorithm question straight from the Google playbook (I don't remember the question, sadly), then after I asked for a few minutes to ponder, proceeded…
What an ass. I wish there was a way to report bad interviewers. Maybe some tech media company will do hidden camera interviews and publish a scathing rebuke of the practice.
The last place I did interviews at, we'd bring all interviewers into a quick debrief meeting and talk about whether to give the candidate an offer (going off the notes we took during the sessions). It was pretty obvious if someone had a particularly bad session and could be weighted against other peoples' input
Unfortunately it can be really hit and miss