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."
Yeah, OP just unwinded himself, no filter. You can be truthful and open with friends and family, close people to you. You absolutely shouldn't when talking with strangers.
It is also possible that they were trying to see, if the person had traumas that would interfere with their ability to work with toxic content, do red-teaming / etc tasks.
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.
I had something similar years ago. I applied for a job at a company, size around 150 people. Did two rounds of interviews which were great. They wanted me to offer the role. However, as a third round, I was going to do a meet and greet with the CEO and he was going to yay or nay me. At point I dropped out. If a CEO can't trust his delegate managers to hire the people they see fit for a role, then thanks but no thanks. That's not a company culture I want to spend most of my waking hours in.
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."
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.
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.
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 disagree that you'll find "many red flags for any job"
I've interviewed at dozens of companies, received and accepted or rejected at least 20 job offers in my life, and rarely encountered true red flags. This is very different than saying it's a perfect 10/10, all life is about tradeoffs. What GP is saying is that "there are things that are not worth any tradeoff, and you'll know them by ... ", which is good advice, esp for young people, who might be willing to make uncomfortable personal sacrifices to obtain a job.
i agree with you, i've interviewed at a lot of companies, too, and seen only 1 red flag in retrospect. the flag was "we need to hire for budgetary reasons"
Sure, but there are some jobs that are so bad that this advice readily applies to. The sort of job that takes you away from your life, family and friends in a way not entirely unlike poverty does. It's good to recognize whether working somewhere will turn into this because it's... hell... working at those places.
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.
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.
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.
Even if I wanted to, these questions aren't allowed in the company I work for, along with feedback related to "team fit". This is dictated by execs, dictated by legal, because it has nothing to do with proving competence, and opens up for employment discrimination lawsuits since you're persuading them (you have to understand the power dynamic) to reveal potentially protected info. For example, if a man say "Oh, I go hiking with my boyfriend!", he could also say "They didn't hire me because I told them I was gay!". Or, even "I spend time with my kids." since familial status is a legally protected class where I am.
As a person who does interviews, I have exactly zero interest in what people do for fun. I just want competent people that are nice to work with (in a productivity sense), and I only have 45 minutes to prove that, knowing that nearly everyone fucking lies. I see it serving no purpose other than helping enforce some monoculture within the group, because, genuinely, why else would you ask about free time activities during an interview?
Related, the only time I've asked this was early on when I didn't know how to interview. The only time I've been asked this, and answered, was with people who had just started interviewing (small startups and new hiring managers).
I think that's the best you can do for culture fit, cause at the end of the day it's just "can they shoot the shit and are they pleasant to be around". You can't really know a person technically or socially until they've been in the job for at least a little bit though.
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.
Not the OP, but having been in many similar interviews, I feel like it's an easy trap to fall into, especially if you've not developed a good bit of curmudgeonly cynicism.
At least when I've done these interviews, they will be extremely friendly, and they will at least act interested in everything you have to say. It's very easy to overshare when you think the audience is actually interested in what you have to say.
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.
I can imagine getting myself into a similar fix. I'd like to think I'd calmly clarify that while I enjoy it I don't get through as many as quickly as I'd like; I'm currently reading blah, and previously blah and blah, but I can't recall the last ten.
Because they're presumably just trying to call bullshit, since it can sound like such an easy probably oft-recomended 'hobby' to say you have, so it's 'oh yeah well what have you actually read recently then', not actually 'I now therefore expect you to have perfect recall over your read catalogue'.
Asking you to name a book or two to continue the conversation is fine, but 10 is ridiculous. That interviewer literally pulled the "oh you like _____ band?! name 5 of their albums" meme on you.
Asking for a list of 10 is a pretty specific version of a natural conversational follow up "what have you read lately?" Sounds like a coder with bad social skills. Like a bad sitcom where I could totally see a Sheldon asking that as a response
I got "tell me what you're passionate about" last time, and I'm curious what a bad reply would be, because I showed them a silly comic I drew on my phone. Apparently that was fine.
I mean, what's the cutoff for something like that. The last book you read seems innocent enough.
The last 3? No red flag yet...
10 though is kind of a lot.
"Actually, I just pulled up your goodreads profile, and it looks like your eighth-most recent book was 50 shades of grey. In addition to having a faulty memory, you're reading work-inappropriate material. Finally, you read that in 2021, so clearly you don't care about reading /that/ much. Dismissed!"
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.
It's a fairly common english phrase that originated out of the gaming culture of the US in the mid 2000-2010s.
"He's so good (plays aggressively) he must be on crack" sort of became "he's cracked", etc. Now that the people who were killing CoD lobbies are writing code full time or running companies, its seeped out.
Actually I think "it's cooked" came from this as well.
"Crack team" long predates video games and even crack cocaine. I think it is related to the phrase "get cracking", i.e., "get working", but I wasn't able to find a clear etymological line. One possibility is it refers to gunfire, but I wonder if it refers to harvesting, cracking corn, etc.
Notably, if someone is "cooked", it's bad. If someone is "cooking", it's often (but not necessarily) positive, most commonly in the form "let him/her cook" or "he's/she's cooking".
I believe it was emergent from FPS gaming culture, particularly following the popularity of Apex Legends. In Apex Legends you have an energy shield which serves as a buffer of hit points. When playing cooperatively it is useful to communicate when this energy shield is "cracked", thus the line "they are cracked" emerged. This originally meant a target player's shield is down in Apex Legend specifically, but it was then the Fortnite (and broader FPS) community which took this phrase and warped it to mean someone is precise or an excellent shot. Today it is certainly used in the context the original poster intended.
edit: Looking again, this may be overstated. Apex-era gaming culture likely helped popularize the usage, but considering older idioms like "crack shot," the actual etymological root is more likely there.
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.
Agreed. Reading the rest of these comments are makes me feel crazy / like I’m missing something. It doesn’t sound like the interviewer was making the candidate divulge traumatic information - but rather assessing how they deal with adversity.
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.
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.
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."
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.
If I learned anything from all my past mistakes in life, it's this.
- 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.
Some interviewers just want to feel special.
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.
You're going to find many red flags for any job, perhaps severe flags.
But you need a job.
Or you have to roll the dice because you have deep knowledge of the red flags for your current job.
Who finds 10/10 perfect jobs via an application process?
Note: I probably shouldn't be commenting since I don't need to apply for jobs and conditions here are likely different from yours.
I've interviewed at dozens of companies, received and accepted or rejected at least 20 job offers in my life, and rarely encountered true red flags. This is very different than saying it's a perfect 10/10, all life is about tradeoffs. What GP is saying is that "there are things that are not worth any tradeoff, and you'll know them by ... ", which is good advice, esp for young people, who might be willing to make uncomfortable personal sacrifices to obtain a job.
We may be there someday, but we're not there yet.
If they're hiding the many red flags, that's the biggest red flag of all!
> 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.
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.
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.
Even if I wanted to, these questions aren't allowed in the company I work for, along with feedback related to "team fit". This is dictated by execs, dictated by legal, because it has nothing to do with proving competence, and opens up for employment discrimination lawsuits since you're persuading them (you have to understand the power dynamic) to reveal potentially protected info. For example, if a man say "Oh, I go hiking with my boyfriend!", he could also say "They didn't hire me because I told them I was gay!". Or, even "I spend time with my kids." since familial status is a legally protected class where I am.
As a person who does interviews, I have exactly zero interest in what people do for fun. I just want competent people that are nice to work with (in a productivity sense), and I only have 45 minutes to prove that, knowing that nearly everyone fucking lies. I see it serving no purpose other than helping enforce some monoculture within the group, because, genuinely, why else would you ask about free time activities during an interview?
Related, the only time I've asked this was early on when I didn't know how to interview. The only time I've been asked this, and answered, was with people who had just started interviewing (small startups and new hiring managers).
> 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.
At least when I've done these interviews, they will be extremely friendly, and they will at least act interested in everything you have to say. It's very easy to overshare when you think the audience is actually interested in what you have to say.
Because they're presumably just trying to call bullshit, since it can sound like such an easy probably oft-recomended 'hobby' to say you have, so it's 'oh yeah well what have you actually read recently then', not actually 'I now therefore expect you to have perfect recall over your read catalogue'.
"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"?
"He's so good (plays aggressively) he must be on crack" sort of became "he's cracked", etc. Now that the people who were killing CoD lobbies are writing code full time or running companies, its seeped out.
Actually I think "it's cooked" came from this as well.
Funny enough, I've only ever heard 'crack team' used in a professional context.
If 'cooked' diffuses to corporate at the same rate then I'm very much looking forward to 'cooking the ops' during standup in 2035 :P
edit: Looking again, this may be overstated. Apex-era gaming culture likely helped popularize the usage, but considering older idioms like "crack shot," the actual etymological root is more likely there.
It was all disclosed up front, so no surprises. Not really that bad.
They make us write essays and life stories and reject in 24hrs.
Felt the exact same frustration.
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.
And this was for a mental health startup!? Please name-and-shame them. Awful.
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.