I think the author was reading too much into these questions. I bet these people came up with random questions they thought were deep, especially coming from a mental health lens, but struck a nerve in the author. They essentially weren't prepared for the raw human experience that was shared here.

I think regardless of whatever you face during an interview, true mastery is to let your humanity at the door and pull up a facade. If you cannot do it in that context, you dodged a bullet imho.. you wouldn't be able to recognize yourself a few years down the line working there with them daily.

I fail to recall the exact wording of the discussion topics, but they were, in fact, non-technical — covering such lovely topics as the hardest day of my life, my biggest life challenges, and other similar “trauma-baiting” questions.

Ha, I don't think anyone who asks these questions expects that you'll respond in a fully unfiltered way... These kinds of questions are part and parcel of non-tech interview processes.

You can redirect with some subtlety "Well, my hardest ever day at work was..." to avoid talking about dead babies or whatever. Your interviewer doesn't get to look over your whole life history and determine whether your /truthfully/ chose the actual hardest ever day. So really it's a chance for you to say "Here's a [big] challenge I once faced, and here's how I survived/overcame it."

I was excited, it was a game company, and I'd wanted to get back into games - or more specifically, game engines - for a few years. The tech of this particular company was interesting, an in-house engine developed by wunderkind, of course, and they'd invited me for an interview because I had done a fair bit of low-level work, which would be handy for their rough edges. Apparently.

Half way through the interview, I had an epiphany. I really didn't want to work there. It was cultural, it just wasn't going to fit.

I didn't waste any more time. Half-way through a white-board challenge, I put down the marker and said, plainly, "okay, I've seen enough, I don't want to work here - thanks and let me not waste any more of your time", picked up my coat and left.

It wasn't a bad interview. It wasn't a terrible one. Nor was it because of the whiteboard question, or anything like that.

I just didn't like the guys. That's all it was. And I couldn't stand the idea of working for them - just the way the interview proceeded. I don't need to give details.

It was really the only time I ever got up mid-interview and left.

Would be funny if the interviewer wrote the exact same blog post; "I had the worst candidate interview today, I asked him a simple ice-breaker question before getting into more technical stuff, and he just went off about his family and relationships for an hour; weirdest interview I ever gave."

There is, and should be, a red flag for these situations. No make that RED flag. If you go into an interview that leaves you feeling the least bit helpless or at someone's mercy then run screaming. Not politely, not quietly. Just say to calmly to the person that you find the situation abusive. It is. As you go out, if you see anyone or have a chance to talk to anyone, just tell them you found that your interviewer to be personally abusive. That you will not be willing to take the position if it is offered, that you will share you perception with others around you and expect an apology.

Then fall down and appreciate that you did not end up in that situation. And tell everyone you know not to apply or work there.

I had an interview many years ago, that wasn't nearly as traumatic, but the interviewer asked me about my failures like 4 different ways.

- Tell me about a time you made a professional mistake. - Tell me about your biggest failure. - Tell me when you last shipped a bug. - Tell me when you took down production.

Never asked me about my accomplishments, or the positives. I'm prepared for being asked about making mistakes, and have a few examples ready to give depending on the job I'm interviewing for, but to get asked so many times in a row was just deflating.

I'm glad I didn't get that job.

Let me preface this by saying, I know this might be a privileged take. However, I've had some bad interview experiences but one thing I have never had happen and I never will do is cross the "just business"/"personal" line with anyone I may or am working with.

> hardest day of my life, my biggest life challenges, and other similar “trauma-baiting” questions.

I would take these types of questions as "from a professional standpoint". If the interviewer corrected and wanted personal answers, the interview would be over.

Earlier this year I was told I failed an interview because when asked why I wanted to join a company, my answer "could apply to other companies in the same stage of life." They apparently required me to be _uniquely_ interested in their company. There were other oddities about their interview process.

Some interviewers just want to feel special.

I have a lot of interaction with mental health professionals, due to an organization in which I participate. Have, for the last 45 years.

Many, many of them are "Doctor, heal thyself" type folks. Definitely non-boring people. I am quite sure of this, for reasons that I won't go into, here.

Sorry it didn't work out, but you dodged a bullet. Take it from me.

Yikes. Good thing you didn't wind up there.

The furthest I've gone in these jazz style culture interviews is asking people what they do outside of work for fun. This was for fully remote async positions. And it was important to know you had other stuff going on because the mental/personal health risk in failing at remote work is massive and life altering.

If, through wherever that discussion went, I wasn't 100% sure that you could stand on your own feet and wouldn't sink into the abyss, it was impossible to move forward. It was a tough line to walk sometimes because you don't want to pry personally. But that doesn't appear to be a universal opinion, it turns out.

My worst job interview ever - in-house creative team at telecom company in downtown Chicago.

I walk into a darkened cubicle farm, down to the only lit corner office for a 'lunch interview'.

Interviewer is sitting at their desk eating a hot pocket on a paper plate.

Didn't even offer me any.

First interview I walked out of.

Not the last.

I would've ended the interview. "I don't want to waste any more of your time. It's clear to me I won't be a good fit here. Thank you for the consideration." <end call>

> covering such lovely topics as the hardest day of my life, my biggest life challenges, and other similar “trauma-baiting” questions.

> talking about failed relationships, family struggles, and interpersonal challenges in previous work environments.

I think that's an interpretation that wasn't necessary (though I agree they're terrible and risky interview questions). I'd stick to hard challenges is my professional life, hard problems I had to solve, etc. My personal life is none of their business.

And I think there's the possibility you may have been rejected for sharing too much. But I agree that kind of question does invite sharing too much.

Beats my worst interview. For some reason I mentioned that I like reading. The guy then demanded to list the last ten books I read. I just named ten random books that I had read at some point in my life, even in childhood. Pretty bizarre. Glad I didn’t get that job.

It’s kinda ironic that after interviewing with a mental health startup, you ended up so emotionally disturbed that you might now need some actual mental health support to tackle the thoughts it brought up. I’m sorry you had to go through that.

> Even if you hire a cracked engineer, it’s probably not gonna be a good experience all-around if you can’t make a human connection.

"Cracked engineer" is throwing me, but maybe I've just never seen the word cracked used this way before. Should it be "crack", like "crack team"?

I had one job, where at the very end of the process there was a multi-hour evaluation by a psychologist / consultant they used. Went over my full life history, school, jobs, etc.

It was all disclosed up front, so no surprises. Not really that bad.

Sounds like a behavioral interview that silicon valley sometimes uses - the questions are designed to ascertain how you deal with difficulty, stress, and certain situations which they absolutely can't legally ask about directly - they are looking for you to discuss challenging times where you succeeded by working harder, doing more than peers, etc. It's not about shaming you, and understanding what they are looking for and why is key - they want people who stick with them through difficult times that they anticipate having.

For interview questions like these, they can only tease about what they are really after - finding employees who "go the extra mile" or "stay late" or "don't give up in the face of adversity". They are looking for you to find evidence of these patterns to corroborate your story. If they drove you to the answer they were after, it wouldn't be a passing score in their interview summary write-up.

Name and shame company: Canonical

They make us write essays and life stories and reject in 24hrs.

Felt the exact same frustration.

Are you quite sure it was a real business and not just some weirdo pretending to be a business for fun?

I came here expecting it was a yet another story about Canonical.

I was asked what my hobbies are during an interview once and it made me believe they were just looking for a personality hire or a pretty face.

These are essentially sociopath screens where they expect you to memorize some STAR stories and regurgitate them on demand. And I don't mean screen out.

>covering such lovely topics as the hardest day of my life, my biggest life challenges, and other similar “trauma-baiting” questions.

And this was for a mental health startup!? Please name-and-shame them. Awful.

I have a two way tie for the worst interviews I've ever had, for very different reasons.

First, in 2023 I interviewed for a startup as a lead architect.

They had me do some virtual whiteboard stuff, and so I was drawing rectangles and cylinders and mentioning things like "database" and "message queues" as generically as I could.

They would interrupt me and say stuff like "Which message queue? Where do you download that?". The interview went on for a long time, with many bizarrely-specific questions for a whiteboard interview, but I figured that it was just their way to make sure that candidates didn't bullshit them by handwaving away important details.

They did make me an offer a few days later, but not for as much as I wanted. That's fine, no hard feelings over that.

But then a week later the CEO emails me asking for technical help on a question. I was on the train when I got it. I don't remember the exact question but it was something to do with RabbitMQ and Redis, and it was pretty easy, so I just typed out a quick answer to my phone and replied without even really thinking about it. Then another half-hour later he responds back to my reply asking for more detail on everything.

After his last reply I sent a response like "I am happy enough to continue this conversation but I'm afraid I will need to start billing the time it takes for me to reply. Give me a call and we can discuss the rate.

He didn't reply.

And then I realized something: this company was using interviews as unpaid consulting. That's why they were asking for bizarrely-specific stuff during the interview, and that's why the CEO was still trying to get free consulting out of me even afterward.

Really pissed me off, and I am very glad I didn't accept their offer. I am generally a person who is happy to help answer technical questions for free [1], but I felt like my trusting nature was kind of weaponized.

---------

Second was last year at a big bank.

I was really excited for this job, so I showed up to the interview in my best (and only) suit, made sure everything looked nice, and had studied for many of the technical questions I thought they were likely to ask the previous night.

Off to a bad start, it was one of the hottest days in NYC of the year, and I sweat a lot by nature, so in combination with the full suit, by the time I got to the building I was already kind of drenched in sweat.

Once I get in, they start giving me some conceptual algorithm questions on the whiteboard. I don't remember the exact question, but I remember they asked the runtime complexity of my solution and I said "Looks like O(n + log m) where n is the length of list A and m is the length of list B". One of the interviewers very confidently corrects me an says "You got your n and m backward".

I look at the board, go through my solution, and, no, I actually hadn't gotten the variables backward.

I have no idea what you're supposed to do in a situation where you're right and the interviewer is wrong [2], so I just do a trace through my solution and explain that, no, my variables were appropriately assigned. He still confidently "corrected" me again.

At this point I really don't know what I'm supposed to do, because I'm not going to just lie and say "oh you're right", but if I'm wrong, then I do want to know why so I don't repeat the mistake in the future. So I ask him "Ok, let's trace through this again because I really don't think my understanding is wrong here".

It was this bizarre gaslighting experience, because he would agree with every premise of why I thought the answer was O(n + log m), and every reasoning step along the way, but then still insisted I got the answer wrong. I do really know my Big O complexity, I have been doing this for a very long time, so eventually I just said something like "I guess we need to agree to disagree" because my time for that interview was almost up.

Then there was another interview immediately afterward. The interviewer started asking me very specific questions about Java Spring MVC (like about which annotations to use and whatnot)

Now, I don't have Java Spring on my resume, I haven't touched Java Spring in more than a decade, and Java Spring was not in the job listing. I didn't even consider studying Spring MVC because the listing didn't even mention that this would be web-based.

So I tell the guy something like "umm, I don't really know Spring. I know how a web request works so I'm happy to answer conceptual questions on the whiteboard, but I'm afraid I would have to learn the specific syntax".

And he responded "Well this is not a junior role. You shouldn't have to learn."

So of course I get the specific Spring questions wrong, and fine, if they wanted a person who knew Spring, that's ok, even if they should have put that in the job posting.

But then he asked me to, on the whiteboard, design a basic web request where there was a global counter [3]. I use an AtomicLong, which to my understanding is what pretty much every human who writes Java uses for counters.

He asked me why I used an AtomicLong, and I said "because it's what everyone uses, and because it doesn't block and because compare and swap for a small surface area like that is pretty cheap".

The guy then, corrected me, and told me to use a mutex. I said "I don't think a mutex is necessary here, if it's just a counter I think an atomic is fine."

He was very insistent, and told me to rewrite it with a mutex, and at this point I am starting to question my own competence, so I yield and just rewrite it with a ReentrantLock, which he again "corrected" me saying that I should use `synchronized`, and at that I push back and say "no, ReentrantLock is fine".

I left the interview feeling like a moron; I was so sure about this stuff before, but maybe I didn't have the understanding I thought I did.

I'm friends with a few graybeard C and C++ programmers on Discord, so when I got home I told them the questions and asked them how they'd solve them, and they solved the problems in the same way I would have.

Then I realized that this interviewer, who was principal level, didn't know what an atomic was, and I think he also had no idea how to use ReentrantLock, and so when I used them he just assumed I was wrong. Moron.

[1] And that's still true; feel free to email me if you want to geek out about software :)

[2] And it seems like the answer I get for that varies between each person. I'm not sure anyone knows.

[3] With, to be clear, no further arithmetic or anything being applied to it, before someone asks.