Live data from Hacker News

Ask HN: Tell me about how you bombed a technical interview

news.ycombinator.com

51–60 of 130 posts

Re: Ask HN: Tell me about how you bombed a technical interview

#51
post #16

I found myself interviewing with a hedge fund last year because they liked some of my open source stuff (and approach to API design)... I had about six conversations with a bunch of the team and a conversation with the CEO to sell me on the position. The last step was a seventh “conversation” with the Chief Data Officer to figure out if this was something I really wanted. The CDO had different ideas… he joined the Zo…

That’s not bombing the interview in my book, that’s just being thrown in front of a bus. Seems like they have terrible hiring practices.

The whole process was pretty informal as I never actually applied (they reached out because of my code!)

I’ll never know exactly what happened, but it I had to guess I think the CDO felt undermined by the “rogue” employees who sourced me as a candidate and pushed me through the process without his consultation…

Re: Ask HN: Tell me about how you bombed a technical interview

#52
I was kinda goaded into an interview by someone. I've always been a Linux, C, and lately, some Go guy. This company was Windows and .Net. So I politely declined, but this person told me to just interview and it would be fine.

So I joined. Person who made all these assurances is on, as well as this younger guy. Proceeds to ask some rather academic type questions about features of languages I haven't looked at in 20 years. To be clear, not bad questions, but more suited to someone just out of CS, or from Java/C# land.

Rather than just BS my way through, I declined to answer and said I'm not comfortable speaking to it.

The original guy who asked me to interview got flustered, cut it short after the third question, and said I'm not so and so material.

The whole thing was a bit surreal to me, to be honest.

Re: Ask HN: Tell me about how you bombed a technical interview

#53
One of my first interviews was at a place that made a job interviewing web app platform. After a programming exercise they decided to bring me in for an in-person interview. Long story short, I bombed with every person that I talked to over the course of the next 3-4 hours.

The first part was a system design interview. I had never done one of these, and my experience up to this point was basically working on small scale web apps at a local software development agency.

Next I continued on to an algorithm-focused white board exercise. It was something about trees, but again I was not able to articulate anything. I remember saying something like, "Recursion is bad", and immediately I could sense that that was a mistake. What I meant was that with Python you have to be mindful of recursion because you can get that "Maximum call stack size exceeded" error.

Next we ate lunch. I attempted to engage in conversation with an engineer by asking her where she had studied. She replied, and I then made the mistake of speaking negatively about the school that I knew was her school's competitor. Basically my attempt at comradery fell flat and I just looked like an idiot. The thing is that in reality I could care less about people's schools. I was just trying to be conversational, but failed.

After lunch, I had a meeting with a person who held a high-ranking position in the engineering department, possibly a director. His spacious office with a window indicated his significance. During the meeting, he inquired about my academic background and what I had learned in school. This particular part of the interview left me with the impression that I had failed to learn anything of value.

He had me work on some problem about a "Bipartite Graph" - Like prove that this graph is bipartite, or something like that. He had me do it on his window with expo markers, and it was taking me so long to get through this problem he actually left the room for a good 5 minutes and left me in there to mull it over.

The final part of the interview was with the front-end people. I don't remember much about this other than talking about React, since it was the hot new thing at that point.

By the end of the day, I knew I had done a bad job, and I felt very dumb. I remember emailing the guy shortly after leaving, basically apologizing for doing such a bad job, and that, "I promise I will do a good job if you choose to hire me".

I still cringe thinking about this experience, but it's also kind of funny that I could have this type of experience at a company who literally made an interviewing platform. I thought that was pretty ironic. I recognize that I did a pretty bad job, but nobody deserves to feel like I did after that interview.

Re: Ask HN: Tell me about how you bombed a technical interview

#55
post #50
post #16

I found myself interviewing with a hedge fund last year because they liked some of my open source stuff (and approach to API design)... I had about six conversations with a bunch of the team and a conversation with the CEO to sell me on the position. The last step was a seventh “conversation” with the Chief Data Officer to figure out if this was something I really wanted. The CDO had different ideas… he joined the Zo…

I came into this thread to comment about a similar experience. Had a call set up with the company founder for a consulting role, for me generally this means an informal chat where they share the pains they're experiencing, I share my background and thoughts related to fixing those kind of pains and, if we both determine we can see it working, I put together a proposal. However, instead of the founder, an engineer amb…

I’m sorry that happened to you. Do you think that the engineer that ambushed you felt threatened by your candidacy? I’ve been around a bunch of engineers who hate hiring to “raise the bar”…

Re: Ask HN: Tell me about how you bombed a technical interview

#56
post #33
post #14

Earlier quoted context omitted.

TBH I disagree, I prefer strict functional programming, mostly for composability. Class components feel like translating everything into latin numerals and then back out again. Hooks help me avoid that pain. But is the API perfect? Nope.

There are also frameworks like solidjs which have similar syntax to React but avoid the complexity of hooks with a simpler API and no hook rules. Classes are not the only solution

Lately I've been investigating Svelte. It looks really good, but I think I'm going to stick with React/Nextjs simply because of the ecosystem and switching cost.

Again, this isn't 'American Idol for frameworks'; I'm not picking React because I think it's the best, or even better. I'm picking React because of the habitat, and because that habitat is now, in a sense, my hometown.

Re: Ask HN: Tell me about how you bombed a technical interview

#57
I was interviewing at Apple some years ago and was in the final on-site interview with some people from the compiler team. I offhandedly mentioned that std::atomics was allowed to be implemented with mutexes and was in this particular edge case on common platforms while I was explaining some decisions in example code. The interviewer immediately snapped back that it wasn't true. I pointed out is_lock_free(), which they didn't believe existed and offered to look it up to resolve the disagreement (rejected). It went on for several minutes before I could get the conversation onto a new topic, but the interview went from intense to actively hostile for the remainder. All the other sessions went well from my perspective, but that presumably caused a hard no. I still have no idea if there was some other point being made or the interviewer just wasn't familiar with that corner of C++.

Re: Ask HN: Tell me about how you bombed a technical interview

#58
post #34

"How would you deal with a problem employee?" Without missing a beat, I asked, "Does he have a weapon?"

My boss years ago had to fire an employee when a background check indicated that they were an IRA member. He fired the guy, got in a cab to the airport, and got the next plane out of Ireland back to the US.

Re: Ask HN: Tell me about how you bombed a technical interview

#59
post #25

If you've bombed an interview in a skillset that you've done productive work in, the fault is with the design of the interview. This doesn't mean that you won't be expected to skill up in the different set to pass those interviews, but don't take it personally either way. As an example, almost no bit of coding work is done in an environment with no reference material, no autocompletion, no compiler feedback, and no d…

That's exactly why so many of us get so frustrated with the state of technical interviews / technical hiring / HR at tech firms in general. The interviews seem designed as some kind of frat-like hazing gauntlet rather than a legitimate discussion / demonstration of how this professional could contribute to and benefit the organization.

I like the just talking approach. The best jobs I had when the interview was just talk.

But on the other hand so many people totally lie about their experience I can't believe it. People tend to have misleading cvs and overexaggerate their responsibilities very often. It makes me sad, because we can't just hire and continue the project, we need to spend few months getting people into the project, "giving a chance", to finally discover they just can't code, until we finally find the right person.

Post reply on HN