What are your worst interviews you’ve done? I’m currently going through them myself and want to hear what others are like. Dijkstras algorithm on the whiteboard? Binary Search? My personal favorite “I don’t see anything wrong with your architecture, but I’m not a fan of X language/framework so I have to call that out”
Let me hear them!
(Non programmers too please jump in with your horrid interviews, I’m just very fed up with tech screens)
At university, a prof for theoretical CS (the kind of professor who thought CS students don’t need computers) was looking for someone to program something for him. The requirements really showed that he had no clue about programming. His assistent, sitting beside him, obviously knew that, too.
I basically told that prof that he had no idea what he was talking about, and suggested that he should attend a basic programming course before I left.
When I was in Uni, we had the opportunity to apply for co-op at Black Berry when they still made phones with their own OS.
I was getting into mobile dev at this time and applied and got an interview.
I didn’t know what I was expecting but what I got was a 10-20min sales pitch for their phone and I wasn’t asked a question… I don’t think. From what I gathered afterwards they just wanted to hire/rehire one guy and had to interview others to be in the co-op program.
Believe it or not I wasn’t sold on black berry after that.
I interviewed for a part-time web developer role during the summer of my second year at university. The “employer” wanted the interview at their house. No problem, I guess it’s a small operation and I’d work remotely?
The interview was fine. It was a guy that worked with his wife, and they needed someone to pick up some work over a few weeks. Midway through the interview, the guy’s wife came downstairs - in what I can only describe as the kind of dressing gown you’d see in porn.
She walked over, asked if I was “the guy”. The man said, “oh yeah, he looks good don’t you think?”, to which she responded “yeah, he looks like he’ll do the job nicely”. She then came over and put her hand by the back of my neck, and asked if I wanted to help out with a problem they’d been having.
Being a socially awkward 20 year old CS student, I said something along the lines of “uhh no that’s okay thanks, I’d better get going soon”, and the man escorted me out. I had received an email minutes after to say the job was mine if I wanted it.
I turned the job down, saying that something else had come up. I’m 70% sure that the job was a threesome or some weird cuck thing, and if I didn’t have a girlfriend and wasn’t awkward as fuck I’d probably have gone back and plowed his wife/written some PHP. Either way, that’s my worst interview experience - and probably will be for the rest of my days.
On the other side, one guy I interviewed for a startup was really qualified and we wanted to offer him the role. I thankfully Googled him, and found a Twitter account against his name where he had pics of him balls deep in a blow up doll. We didn’t hire him.
It’s certainly a bad sign if you leave the interview and you’re not sure if the job is for writing PHP or pleasuring his wife.
PHP stands for Pleasuring His Partner.
PHP = Pleasuring Her Poosay
I interviewed for a shop in Ottawa.
I was working at the time, but it was declining situation so I was Motivated.
So I show up a the appointed time, and I meet a guy who can best be described as ‘a little grizzled’ and ‘a little stressed’. We go over my resume, first off the bat.
“These are the things we need from you,” he said, tapping items on a list. “And these are places you suck,” he said, tapping the same list.
I basically checked out at that point; there was no way I was suitable for this post. I could learn it, but it was a lot. And while I had a lot of other skills that showed up on the job desc and my CV, missing so many important pieces was insurmountable. It wasn’t a super-fun experience no matter how interesting he was - he was a great lead hand - and I left without much fanfare. Great rambling talk about all kinds of things, but it’s the worst I’ve ever flamed out in an interview; and the fastest.
Imagine my surprise when he 'strong-hire’d me. I actually said to the recruiter, “Yeah, you’ve got it wrong. No no, and it’s totally okay, but you’re off by one or something. You mean to call the name above mine or the name below mine, and that guy is probably gonna love this job. But you don’t mean to call me. No stress, all good, but yeah, I’m not the guy you wanted to call.”
It was a great job and that guy was my lead. Brutal honestly is fabulous if you can take it.
My first ever software interview was with a small company that made a web app for traveling nurses. It was mainly a calendar with additional functionality to help nurses manage cases.
I was given a pre-interview programming task to complete. The task was relatively simple and would not take long to complete so I agreed.
When I logged in with the credentials they provided it looked like they had a very robust testing environment. There was a complete copy of the app running on the server with fake information in the database.
The code itself did not follow any style guides and was rarely documented. This caused me to spend much more time completing the task than I had estimated. Once I completed the task and verified functionality I notified the company. They checked my work and scheduled an in person interview with the lead developer, CTO, and CEO.
During the interview they attempted to access the test server with my code so we can discuss. My code could not be found on the test server and it was at this time we learned that the lead developer had given me complete access to the production servers including direct database access. The “fake” data that I used in my own testing on a production server was actual patient records. It was a huge HIPAA violation on their part and I withdrew my application for fear that this company will soon be in legal trouble.
I suspect they thought I was going to report them because they offered me $3000 for the “work completed.” It turns out their programming task was a feature that they wanted implemented into production anyways. I think if it were not for the lead developer’s mistake I would not have been paid anything. There was no offer of compensation for the completion of the task before the mistake was revealed.
Having read some of the comments from the interviewer perspective in this thread, I am glad they got you and not one of the yahoos other interviewers got.
I had an interview where they asked me to set up 3 micro services (with full functionality), a Kafka broker, a frontend and to configure everything to run on Kubernetes.
According to them this would take “more or less 4 hours” and those hours would obviously not be paid.
I’m still not sure whether they were just trying to get free work out of people or if their expectations for what a software engineer is supposed to do in half a day are completely absurd.
I had a similar task to
“Set up a web service, load balancer and infrastructure to scale it to handle a large amount of requests. Harden the security of it to the best of your ability. Document how it works, how to scale it, why you built it the way you did, what measures you took to harden it and why, and any future improvements you would suggest. All code and documentation should be production quality. This should take about four hours.”
Maybe you can write this code in four hours, but all this documentation and motivation as well? Fuck off.
They also asked for a made up report from a security audit (this was for a security engineer position) containing a dozen realistic vulnerabilities with descriptions, impact assessments, and remediation suggestions. Once again of production quality. This is at least six pages of highly technical, well researched, and carefully worded text. Four hours is tight for this task alone.
And if those are their expectations going forward they can keep their position. Imagine doing twice that much every day.
I had an interview like this, it was supposed to be Pair Programming which i had been doing very well for 5 years in RoR.
I get to the interview and they haven’t actually done any pair programming, they WANT to.
And the interview was ‘write a tic tac toe game in ruby on rails in one hour’
And they literally had nothing, we were in the zoom call the guy was like ‘okay go’ but every time i asked him any questions he told me to just do whatever i thought was right and he didn’t want to influnce me.
I got RoR and dependencies and apache installed and either finished or almost finished mariadb in that hour but i was doing it all over my own home internet so didn’t really get very far and they seemed really annoyed!?!
Then the best part was the senior programmer told me that they don’t have time to do code reviews and all the engineers just merged whatever they wanted into master, but it was fine that way. I think he didn’t like having anyone review his code.
LOL
That last part is a nightmare
Oh my god I hate that, just set up an entire infrastructure before you even get to the question. The very least they could do is set up the cluster for you so you wouldn’t have to spend the time
If they are familiar with these task a solution can get outlined with words easily.
The author summarized it perfectly.
The biggest red flag is how all over the place the task is. They were trying to test every single thing they could come up with at the same time.
it’s definitely free labor for them, they’re incompetent and likely checking notes on how other more competent people would approach deploying in whatever fashion they want to
I’m a little ashamed of this one. I really wanted it, and I was a little desperate.
- HR Interview
- CTO interview
- 16-hour take home test
- 4-hour panel interview where the engineers grilled me on random things
- CEO Interview
Didn’t get it.
Fuck. This. Shit.
Been in an interview where the CTO asked me a bunch of questions and seemed interested, only to ghost me in the end. No reply even to my follow-up. Thankfully I found a better job.
I had one that was similar to this guys, got to the CEO interview and until that moment I was still excited to be there. They flat-out asked me “Here at ___ we know we’re making the world a better place - and because of that we’re willing to make ___ our number one priority in our lives. This is a hard question, are you willing to do the same?”
I was taken aback for a second. I then answered in the only way I could. “I see what you are doing and fully appreciate it. If I’m hired here ___ will be one of the most important things in my life. Whenever I’m working I will be 100% dedicated to the work, I’ve never shy’ed away from it. I’ll work nights and weekends when needed, sometimes those are needed. However you’re asking if it will be the most important thing in my life? My answer is no. It will be one of the most important things in my life, but my family and spouse is the my most important thing in my life.”
No shit, they ended the interview there, and I got a canned rejection email within 30 minutes. I’ve never been so angry at the audacity of an interview question like that. Who the fuck do you think you are demanding that you make yourself more important than my spouse?
Yes, it will be the most important thing in my life. I even brought my divorce papers here to prove it.
Ha!
Jesus. Good on you for not having any of that bullshit.
Would have been nice to ask that question in the application. Would have saved everyone a bunch of time.
Ridiculous take home tests are probably the number one reason I decline to continue interview processes. If you think that building a client, an API, wiring it up to some other third party API, then deploying is a reasonable scope for an unpaid interview challenge then you are very bad at scoping software projects and the most important thing I can do for you is tell you as much.
I told one start up if I built what they asked for in the interview, I would pursue funding from their investors and launch it as a competitor- it was that similar to what their actual app did.
Hi welcome to GM please go build a Chevy at home so we can evaluate your skills.
That sucks. Fuck them.
How about the other way around, I had this guy come in, he had been out of the business for a while and decided to go and be a mechanic for a few years. One winter in particular he decided that he was kind of tired of doing the mechanic stuff and wanted to come back.
I interviewed him on a phone screen. His knowledge was appropriately dated but he was not bad. I figure he’d be able to come in and get up to speed pretty quickly.
My company does kind of a nightmare scenario where they interview you all day long and you literally meet with everyone in groups.
First thing in the morning first group came through said he was great.
Second group came through asked him some questions and he was a little bit more cagey but still not bad.
The third group was the lunch group, They took him out to lunch and he threw out a bunch of racist stories and while people watching, made fun of people as they came into the restaurant for their ethnicity or their weight, or what car they drive or whatever else they could find.
The lunch crew came back and did a hand off but no one raised the flags right away so we went into the first after lunch crew. A couple of people from the lunch crew pulled me aside while he was in his next set of meetings and said they were extremely uncomfortable being around him and recounted the stories.
I had to bust up the interview and send him on his way. The person that was uncomfortable with what he said is one of the most IDGAF people I’ve ever met.
Years earlier we had a developer come in with a fantastic resume. They brought him in first thing he was rude, and we’re not talking autistic doesn’t know what he’s doing rude he was clearly making a lot of generalizations about people and being nasty about the questions. Skill wise he was absolutely fantastic and he would have been fabulous to be a lead in front of a complicated project, But he was impossible to be around. Toward the end of the Early interview they told him that they had all they needed. He asked him if it was because of his attitude and they said that it was a team job and they needed somebody that was capable of working with a team. He said they could just put him in a one-man team and have him architect things or do other work by himself. There was simply no chance they were going to hire him. You don’t willingly bring that much toxicity in the workplace if you can help it.
I retired as a programmer five years ago and now I drive a school bus. The difference in acceptable workplace behavior is pretty stark. In my software companies, nobody ever came anywhere close to saying anything even vaguely racist; meanwhile in the bus garage people routinely use the n-word and the g-word. And it’s not like this is Mississippi or anything - this is a suburb of Philadelphia where the entire transportation department would probably be sacked if parents were ever to become aware of how their bus drivers talk.
Oh, we know. We’re in a mixed race community and you can see the distaste on the bus drivers and teachers faces. We can see them ignoring the bullying, and we get to hear the stories when they go to tell the teacher or bus driver something going on and they just shut them down and tell them to go back to their seat.
Sorry what’s the g-word?
It’s a slur for Asians, more specifically Vietnamese. I can actually trigger my coworker to say it, by merely mentioning that I like Chinese food.
Rhymes with “mook”
As an interviewee it’s nothing much, but when they asked me to sort a list, I find that question to be completely pointless, I will never implement a sort IRL, and most people who get it right are because they have it memorized.
As an interviewer, a person who sent their take home as a .doc file inside a zipped folder. I didn’t understood why they sent it that way, but got the code to compile, and found very serious issues. When confronting the person they claim there were no issues, which happens so I pointed out at a specific line, and still nothing, I asked them if they knew what an SQL injection was and his answer was “yes, and you’re wrong, there’s no SQL injection happening there”, so I sent him a link for him to click that would call that endpoint on his local instance, and dropped the entire database for the take-home assignment. No need to tell you he wasn’t hired.
I will never implement a sort IRL
My answer to “what’s the best sorting algorithm” is “the SORT BY clause in SQL”.
TBH a take home assignment as a
.docfile would have been enough for me to pass. Even when going through resumes (for technical roles), i usually skip anything that’s not a PDF.In hindsight that should have been enough, but at the time I didn’t want to discard a possibly good candidate because of that (reasoning that maybe he had some reason for it). Being subject to SQL injections also is not the end of the world, everyone makes mistakes. Not realizing it even after me pointing the line could also be overlooked as “we need to train this person”. But insisting that there isn’t even after the interviewer tells you there is, means you don’t want to learn, and at that point I can’t help you.
I interviewed at Cisco once, with two managers. They started arguing with each other during said interview.
I didn’t get the job, and I didn’t want it, either.
to be fair, even if you got the job, ciscos high turnover rate, you’d probably be out the door in under 2 years anyways
In this industry, now, why would you stay at a fang? Especially past 2 years!! The only benefit is going to be the line on your CV. Unless you’re in the c-suite you are grossly undervalued,burdened with office politics, and worsening conditions.
I mean, the pay is still way ahead of anything outside FAANG, really.
Depends entirely on the business, subjective as hell.
Interviewed at two big, well-known tech companies. Had done a lot of mobile dev work at the time, but really wanted to switch to connected hardware and told the recruiters.
Showed up for the first on-site interview. Guy walks in. Explains the actual first interviewer couldn’t make it so he was a last-minute stand-in. Goes: “So, it says here you are intererested in mobile. That’s good. My team is looking for someone like that.”
I explained it was actually the other way round. What proceeded was an awkward hour of bullshit questions about train schedulers and sorting algorithms. Repeat five times that day. Every. Single. One.
Second company a few weeks later. Same thing. Except this time, 2/3 of the way through, a manager in HW group walks in. Grouses why he was asked to talk to someone, checks notes, about mobile. We had the greatest conversation after I set him straight. He wanted me to come back and do another loop just with his group. Except a week later, they announced a hiring freeze and I never heard back.
In retrospect, it was a good thing. I would not have been a good fit.
As the interviewee?
I show up at their office for a round of interviews. IIRC it was 4 interviews of about an hour each. Every single interviewer comes in 5-10 minutes late. They all look completely exhausted. Unprompted, they all commented that “yeah, this is a start-up so we’re expected to work 80 hour weeks. That’s just how it is.” I did not take that job.
Another place wanted to do a coding “pre-screening” thing. You know, where you go to a website and there’s a coding question and you code it and submit your answer. THIS place wanted you to install an extension that took full control of your browser, your webcam, your mic, etc. So it could record you doing the coding challenge. No, thank you.
As the interviewer? omg, the stories I can tell.
We had a guy come in for an hour interview. We start asking him the normal interview questions. Literally everything he says is straight up wrong or he says, “I don’t know” and then just gives up and doesn’t try to work out a solution or anything. But we have a whole hour with this guy and as interviewers we’ve been instructed to use the full hour otherwise candidates complain that they weren’t given a fair chance even when it’s TOTALLY obvious it’s going to be a “no-hire.” So we start asking this guy easier and easier questions… just giving him basic softball questions… and HE STILL GETS THEM ALL WRONG. We ask him what type of variable would you use to store a number? He says, “String.” WHAT?! I’m totally flabbergasted at this point. So finally I get a brilliant idea: I’ll ask him an OPINION question! There’s no way he can get that wrong, right? Looking at his resume, it has something like “Java Expert” on there. So I say to him, “It says on your resume you’re a Java Expert. What’s your favorite thing about Java?” His response? “Oh, I actually don’t know anything about Java. I just put that on my resume because I know they used that at a previous company.” So now on top of this guy getting every question wrong, we’ve established he has also lied on his resume, so basically just red flags EVERYWHERE. Finally, after a grueling 45 minutes we decide to give up asking questions and just end with the whole, “So we like to reserve the last bit of time so you can ask us questions. Do you have anything you’d like to ask?” Without missing a beat, this guy goes, “When do I start? I feel like I NAILED that interview!”
At another company I worked at, we would do online interviews that took only an hour. The coding portion of the interview had a single question: “Given a list of strings, print the contents of the list to the screen.” That was it. Sure, we could make the coding question harder if they totally aced it, but the basic question was nothing more complicated than that. The candidate could even choose which programming language they wanted to use for the task. That single question eliminated half the candidates who applied for the job. Some straight up said they couldn’t do it. One person hung up on me and then when I tried to call back they said the fire alarm went off at their place and they would reschedule. They never did. Many people forgot that I could see their screens reflected in their glasses and I could see them frantically Googling. There was one candidate that did so insanely poorly during the interview that we believe it must have been a completely different person that had gone through the initial phone screen, so basically they were trying to bait-and-switch.
I have a bunch of other stories but this post is already getting quite long.
Unprompted, they all commented that “yeah, this is a start-up so we’re expected to work 80 hour weeks. That’s just how it is.”
lol I’m walking out the minute they say that.
Seriously. There’s no way I would continue 3 or 4 more hours after that comment.
I’m genuinely terrible at not falling for sunk costs and have a bad habit of just letting inertia take me.
But unless you’re offering me 100k a week (in which case I’ll work for maybe a month before burning out), I’m not working a fucking 80 hour week.
At the time it was like watching a train wreck. This was much earlier in my career and I was like, “there’s just no way, right?”
I did get lunch out of it.
I resonate with so many of these. I hate the tech prescreen, but morons, cheaters, and liars make it necessary. The prescreen is purely there to weed out a good, like you said well over 50% of candidates right there.
And I’ll throw a thorn at you, I do store numbers as strings… When I’m dealing with currency lol. I’m 100% sure that’s what he meant of course, because he was thinking about float precision and how you wouldn’t want to risk currency imprecision during serialization or anything! Should have given them the job! /s
“Given a list of strings, print the contents of the list to the screen.”
print(stringlist)or if you want to get fancy:
print(", ".join(stringlist))When do I start? I feel like I nailed it.
/s
lol. I kid you not, someone did that. Then completely imploded when I pointed out that it’d just print the object reference and not the list contents.
Can you start next Monday? :p
Now I need more details, you said they can use whatever language they want, if you do
print(stringlist)in python it will print something like["first string", "second string"]and not an object reference.The candidate said they were going to use Java. I asked them if perhaps they weren’t coding in Python instead? They insisted it was Java. I forget the details but they proceeded to “fix” their code by doing some stuff that made absolutely no sense no matter what language they were using.
Was the string list an array or something?
I think the interview I least enjoyed was with an unnamed big tech company.
It was the first interview of the day and the guy came in with “so me and my buddy have been trying to solve this algorithm problem for years. I’d like you to try and solve it for me.”
Like… Dude, that’s not a reasonable interview question! You should not use algorithm questions that you don’t know of any answer to in an interview. You’re effectively asking someone to give you a solution to something way too complicated of a problem without even a few hours to think about the problem or sit down with it on their own.
That sounds suspiciously like doing actual work for them.
I had one interview where they literally got me to fix their Sendmail server while I was there.
I seriously hope you got the job.
I did.
I was there 5 months before heading back to grad school.
Oh god I’ve had an open ended one like that only once, and you’re right it’s terrible. Those questions would be great things to tackle as a team of peers where you’re all working together without the pressure, but dude you hold our careers in your hands. Pull it together
Aren’t most questions like this are simply looking at what approach you try and not a solution? They’ve been at it for years so they can easily tell if you’re trying something that makes sense or something trivial even if they don’t have a solution or even if there isn’t one.
The problem is you’re effectively leaving “can I program and work through the kinds of tasks this job entails” and entering “how do you work through a complex theoretical research topic” land.
White board questions should be relative softballs related to the work you’re actually doing to see how you think… Now that’s often forgon for “welcome to a game of algorithm and data structure trivia!” but this is just a much more extreme version of that.
Also if you don’t actually know the answer, how can you judge the direction? Even if you do know the answer for a problem that complicated, can you say the interviewee isn’t solving the problem in a novel and possibly better way?
I presume he was looking for specific terms like DAWG (directed acyclic word graph) and things like that as well… Which I know because he would teach me the names of things as I slowly rediscovered them in conversation. Personally, I don’t put much stock in grading someone on their knowledge of obscure data structures and algorithms either.
When I give interviews, I’m more concerned with the process than the results for some questions. I don’t really do it any more, but I’d sometimes ask one question not related to programming or anything on their CV just to see how someone works through a situation given a little bit of a curveball.
Sometimes you don’t have to solve it but instead ask them about what approaches they tried so far and suggest a new one. Just showing interest
Sorry, but the answer we were looking for is “I’ll need to work on this over the weekend.” That’ll be all for today. We’ll call you.
i got an interview as an embedded software engineer for a company that makes wireless camera flashes. high-precision real-time programming. i wanted to dive further into that area.
the first task was… reading comprehension, basic arithmetic, and pattern matching. i was flabbergasted. i wrote a really negative passage in their feedback form about how they apparently don’t trust their engineering candidates to be able to read, and how those pattern matching iq tests are bullshit since you can up your score by like 20% if you practice.
they called me back and explained that the reason they have everyone from cleaning staff to C-level take the standardized test is to create a workplace of “objective equality”. also they were really confused about my stance on the test because apparently i had scored in the top 5%. that’s the fastest i’ve ever noped out of an interview process.
That is pretty insulting tbh, going in assuming everyone is a moron. I kind of get what they were going for, but it’s something that could be easily solved just with a normal interview. They probably got burned once and decided “This is our standard going forward, everyone will suffer now”
I did one where I went through a few rounds of interviews, technical and otherwise. In talking with the developers, they mentioned that they were trying to integrate a certain client side framework into their backend frameworks build process, without success. Get to the final stages, and the director of engineering asks me to work on this take home project to, you guessed in, integrate the js framework into the build process of the backend framework.
I sent them a strongly worded rejection email. It was a realreal eye opening experience.
If it’s not a hassle, could you explain the implications of this request to someone who only understands basic coding?
Imagine you’re interviewing for an Architect position at a company that’s designing a hotel, and your take home assignment is to design a hotel.
Gotcha. Thank you v much!
They were trying to get them to solve a real world problem for free under the guise of an interview (made up) problem.
Hahaha. Oh, small business owners… smh Thank you!
It was a realreal medium sized start up ;-)
77
In addition to the excellent hotel analogy, they had a specific conceptual and technical problem, say, how to mix flour evenly into water when thickening a sauce. The challenge was to make a roux and show the steps I used to evenly mix the flour.
