Anyone else experience a frustrating power trip interview?
Posted by Acceptable_System389@reddit | ExperiencedDevs | View on Reddit | 65 comments
Has anyone else experienced this?
Maybe I just need to rant and hear anecdotal stories to chill and move on. I interviewed for a C# Lead Developer position by a hiring manager for behavioral questions, and a Lead Dev from another team for technical questions.
The Lead Developer, I learn at the end of the interview, is mostly a Java & Angular dev. He proceeded to ask me lots of vocab questions about very niche C# keywords, and then ask me about niche ORM frameworks that were not listed on my resume or the job posting. I explained I wasn’t familiar with that specific ORM framework (and learned it wasn’t relevant to the job), but I was familiar with other ones like Entity. He was upset by this answer. At the end he told me he would expect a lead to know this ORM framework.
The worst part was he asked me a brain teaser question, and was looking for a front end related answer. Think “I just want to know your thought process” type question. Im a Fullstack dev, and I have only used React on the front end and was very clear about this. I only say react on my resume, and the job posting doesn’t mention any frontend work. As we walk through the brain teaser, I can tell he’s looking for a specific answer I’m not giving him. At the end of the interview I politely ask him how he would answer that question and he says he would use [insert very specific Angular keyword here that does not exist in React] and he told me he was concerned I didn’t mention it. I was confused… thinking yeah how did I not know that? I Google it after the interview- turns out my answer was correct… for React. And his answer was correct, but only for Angular. Since he wasn’t familiar with React, he just assumed I had no idea what I was talking about.
SpeakingSoftwareShow@reddit
Had one recently for a Technical Lead role. It was for a full-stack role and leading a cross-functional team, in a stack that I know extremely well.
First 3 interviews were great, but the fourth Interviewer got frustrated that I could answer questions well and not fall for gotchas. They then started hammering me on insane database internals questions. His justification was that they process a lot of data, so any technical lead needed to be able to implement an ACID compliant database *from scratch* to show they could handle the role and the amount of data they deal with. Not work with the db - literally if I could recreate something similar to postgres and how I would handle transactions, query parsing, etc...
I called them out on it, nothing that neither the job description, the recruiter, the hiring manager, or anyone else on his team mentioned this requirement before- and that I also thought it was a bit superfluous. Like if you want that, hire a staff-level database developer.
I later got feedback that my answers were too "by-the-book" and that I was clearly using ChatGPT to give good answers. I followed up with the recruiter later, and they shrugged and told me I'm not the first to complain about this person.
This role has been reposted on LinkedIn several times in the last few months. Looks like the haven't found the right database developer yet to lead their Fullstack team yet?
Acceptable_System389@reddit (OP)
Loll, so I’m curious what feedback did you tell the recruiter?
I know it’s best not to burn bridges. And right now I’m still heated from the interview.
Do people actually tell the recruiters feedback if things went poor or is it not even worth it?
I assumed not worth it. But there’s a few comments on here of people letting recruiters know.
SpeakingSoftwareShow@reddit
It's totally worth it. External Recruiters normally only get paid (or the bulk of their pay) when candidates get hired. If there is an asshole in a team blocking that from happening, then they absolutely can go back to the company's hr/people team. If it's a pattern of behavior then that can be dealt with.
Doesn't always go down that way, but it definitely doesn't go down if you don't give feedback 😁
Designer_Holiday3284@reddit
You dodged not a bullet but a bomb.
I had a very similar situation for a mid React Native frontend position some years ago. The interviewer, java backend lead, started doing many OOP questions like what the letters of SOLID meant!
Crazy fuck guy.
BOSS_OF_THE_INTERNET@reddit
I interviewed for a senior dev position at Hashicorp about 8 years ago. There were I think 4 interviews. I aced three of them (the manager interviews and the system design interview).
The tech interview was an absolute shitshow. I had to basically recreate a
mapin golang, which by itself is a pretty stupid tech interview topic IMHO. Any tech interview topic that doesn't cover a real-world situation is spurious in value at best, but I digress.Instead of me talking him through what I would do and then try to implement a solution, he had me tell him what to type, literally every word, parentheses, comma, etc.
He insisted on using TDD in the interview, which is fine, but then he would just sit there staring at me until I told him what characters and words to type into his terminal. I was visibly and vocally frustrated, and got a real sour taste in my mouth for that company.
I have several friends that work(ed) there, and they said this was highly unusual and not representative of their tech interview process. The interviewer was known throughout the company as a "difficult" person, according to my contacts there.
Of course I didn't get the job because of that one interview, which in hindsight seems like I dodged a bullet.
daguito81@reddit
I really don’t understand these bullshit academic questions that are completely useless beyond that interview.
The best interview I had was basically with a client of a consulting firm. I had already accepted an offer but because the consulting firm had already scheduled the interview I agreed to do it so it would t look bad on them and then your typical “I went with a different offer response “ I know it was a waste of my time but you never know. I asked for a much higher salary (borderline “gtfo” territory)
So I went to the interview 100% “let’s have some fun” And it was pretty amazing, everything they asked was regarding to their actual projects. Even as a freebie they commented using something and I answered like “I’m pretty sure you ran into or will run into this problem” and explained something that happened in our project and how we solved it. Guy was furiously taking notes ( I mean feee labor right ?). They were obviously asking questions of issues they are running into because processing a lot of data does come with its issues.
Either way. Beyond the part that I already had accepted another offer. The interview was like extremely useful for both of us. Even some questions I was like “I don’t remember the exact word, but I’m googling it right now aaaaand it’s that, the problem is that when that happens ….:”
No bs questions. No whiteboards. No leetcode. No waste of time. The entire interview was me proving I can solve their actual real world problems right there and then.
Now obviously I am fully aware of the danger of these. Companies interviewing to basically farm free labor are a thing. This was specifically because I just wanted to have a bit of fun, flex muscles and basically go all out.
Eventually they did offer me the absurd pile of money. I ended up taking the original offer though. I think overall conditions were better with everything factored in.
Taught also a small class about preparing technically for interviews so to prepare o went on an interview spree for a bit more than a year. Non stop interviews with no desire to switch job. Must have been 80 or so.
The amount of useless questions that scream “I have no idea what I’m doing but they told me to interview so I googled some random questions “ was astounding
bluesquare2543@reddit
I had a friend interview there earlier this year and the same thing happened to him. The interviewer made my friend tell him what to type, character-by-character.
I also interviewed with flying colors, but they called me sexist because the two women (that were not even close to the team I was interviewing for) did not like how I interviewed. One of them said I was "overprepared" whatever that means.
Fuck these assholes.
poolpog@reddit
weird. I talked with several Hashicorp people at kubecon last week and didn't get the sense that anyone there, technical or not, had this sort of 10X dev god complex. but of course, my interactions were not really equivalent to a technical interview.
BOSS_OF_THE_INTERNET@reddit
I looked back at old emails and then looked the guy up on LinkedIn...looks like he left Hashi a few months after I interviewed.
Acceptable_System389@reddit (OP)
That sucks, sounds like you just got stuck with that one guy.
poolpog@reddit
i think you meant to reply to the person above me, lol \^\^\^\^
Acceptable_System389@reddit (OP)
oops, yup, my bad
Acceptable_System389@reddit (OP)
Oh god, that one takes the cake for sure. Out of curiosity, was he interviewing you alone or was there a panel that also watched that madness unfold?
Some of the worst interviews I've experienced (not from me bombing the interview, but from dealing with a shitty interviewer), have been solo interviews. Or one's like today, where there was only one technical person in the room to ask the technical questions. It's like, since they know no one else is there to question them, they either:
A) Are a normal interviewer and things go fine
B) Decide to ask the most ridiculous questions you've ever heard and judge you based off of... who knows what, because no else is around to question it.
When I have technical interviews with a panel of devs, this option B has not occurred. (at least... not yet :))
BOSS_OF_THE_INTERNET@reddit
Nope, it was just him and I over Zoom. And now that I remember correctly, it was 6 years ago and not 8.
LongDistRid3r@reddit
If this is the way they treat you for an interview, expect to be treated like this as an employee. Then ask yourself if it is really worth the expense of your mental health.
Acceptable_System389@reddit (OP)
Yeah absolutely. The hiring manager loved me, but she was relying on him to assess my technical skills. If they followed up, it would be because of her vouching for a second interview round. But he essentially already told me at the end of the interview I wasn't fit for the role because I didn't know [insert niche ORM framework here]... (again, even though that ORM wasn't even relevant to my job posting, and it's not like I can't learn a new ORM framework if needed? This isn't rocket science...)
...sorry, ranting again :).
putin_my_ass@reddit
Maybe it's my full stack showing but I can't stand ORMs, I like to write my own SQL. So I'd fail his interview, but I'd have absolutely no problem handling whatever they need me to do.
Sounds like a skill issue on their end.
nappiess@reddit
Raw SQL in a codebase is a legacy pattern and absolutely unmaintainable. I would never work on a codebase with frequent raw SQL use. It should only be used for the 0.001% of scenarios that for some reason require a particular optimized query that the ORM can't get right.
Fair_Local_588@reddit
Nope.
Acceptable_System389@reddit (OP)
He really drilled those ORM questions in and seem appalled that I wouldn't know them. He specifically said "I would expect a Lead Dev. to know of this".
I almost wish I had a pettier reply at the time, like how I wouldn't expect a Lead Dev. to always have specific knowledge about specific libraries unless its necessary for this job position, because those libraries grow and may become irrelevant in a few years. I would, however, expect a Lead Dev. to have the skills to adapt and learn new libraries quickly without needing much or any support.
putin_my_ass@reddit
Yeah maybe it's my bias showing but to me a Lead Dev shouldn't use an ORM. To me, that's junior shit. I started doing only SQL before moving in to fullstack so to me it's so remedial I can't imagine offloading it to an ORM.
But I'm sure there's a technical justification...
lurkin_arounnd@reddit
Defining Jr vs Sr level based on whether they use some specific tech is the real Junior shit lol
No_Flounder_1155@reddit
Only real seniors write hex.
HowTheStoryEnds@reddit
You probably got interviewed by the person that wanted the job but didn't get selected, possibly because he didn't ask the right people or strongly enough or they outright rejected him. He still wants it though.
Cyclic404@reddit
Exactly, you are interviewing them as much as they are interviewing you. All it costs them is money, it costs you your time.
peripateticman2026@reddit
Indian interviewer?
ITAdvance@reddit
Two problems.
First, job descriptions are often bad. They don't relate to the actual job.
Second, job interviewers are often bad. Technical interviewers are unskilled, nervous and awkward.
bernaldsandump@reddit
Millions of ways to skin a cat… but make sure your way is the same as ours!!!
BLOZ_UP@reddit
Years ago went through an hours long in-person interview at a startup. I was coming from a defense company. The technical was dopey Google interview questions on a whiteboard which I did a best guess brute force in pseudo code but eventually gave up on optimizing it and said, sorry -- I can't do this on a whiteboard.
Then I interviewed with the founders. The first was fine. The second then berated me for working for a defense company. Said "what good has defense industry ever done for the world?" I sat there and smiled trying to contain my rage and then he said I can show myself out. I don't know if that was a trick question (Arpanet? Cryptography?) but I was certain I would never want to work there anyway.
LThalle@reddit
I was interviewing at a big game studio years ago and was in final round technicals. Last one was a single engineer, probably in his 50s. Asked me how my C++ knowledge was, and perhaps foolishly i assumed he meant for the role level (associate). Said maybe 7/10 as it's my main language. He proceeded to ask me a bunch of ridiculous questions I'd never needed to know and haven't since, e.g. "how would the compiler lookup table look if you do so and so arbitrary set of operations". And then if I ever tried to clarify any of the questions he'd just tell me the answer and move on, basically failing me on the question.
Later was told I'd been very close to the cut but "my C++ knowledge seemed somewhat lacking". I was fuming cuz I know it was 100% that guy.
Thankfully I ended up interviewing at another good studio and have been happy there since.
ancientweasel@reddit
You are interviewing them too.
poolpog@reddit
You don't want to work here.
Interviews work as a filter in both directions. Consider this a useful filtering event.
Acceptable_System389@reddit (OP)
I agree. I only wish I had stood up for myself a bit more at the end.
sammymammy2@reddit
It's not worth it :). Don't waste your breath.
EvilTables@reddit
The guy seems like an asshole. If anything it might be useful for their hiring manager to know that it was a bad experience , as it impacts their ability to bring on good talent.
upperdine@reddit
I had an interview like this once. The guy was absolutely desperate to prove I wasn’t qualified for the job so I just stayed polite and immediately after finishing the interview I emailed to withdraw from the process, citing everything that happened.
Some people are dicks, it’s not worth letting them get in your head.
Acceptable_System389@reddit (OP)
Did you ever get a follow up on that email? What did you say in there?
upperdine@reddit
I got a fairly generic “thanks for the feedback, we’ll investigate further” response. I just mentioned that while I was initially excited to work at the company, my experience during the interview painted a very poor picture and felt like my time was not valued.
atxgossiphound@reddit
I've had it happen twice, both cases right as I was finishing my PhD (I also had almost a decade of industry experience prior to starting my PhD, so interviewing wasn't a new thing for me).
One was at an algo-trading shop. I was warned that the lead developer can be a bit abrasive, but I was not ready for the grilling he gave me. He did not have an undergrad degree and made it clear up front that he thought degrees were worthless and experience was all that mattered.
He tried really hard to trip me up and finally gave up after we walked through the finer points of IEE 754 and why his special integer model was better (yes, he thought he invented fixed point arithmetic). I was gracious the whole time and just kept giving him answers to everything he asked. At the end of the day, I told them I wouldn't be pursing the opportunity any further. There was no way I could work with him.
The other was at Google. To borrow a phrase from the South, bless their hearts. The poor interviewer went through all the usual hard questions and started to get to the annoying ones. He asked me a question that was related to a chapter I had just written in my thesis concerning high-performance data structures for streaming data. I can't remember the exact question, but there was a really cool solution using SIMD processors that was (at the time) the fastest way to implement the solution. I was just happy to share it with someone.
After walking through the solution on the white board, he was clearly confused. My mistake was looking at him with a slight giggle and saying, "Oh, you wanted a lookup table that could fit in L1 as the answer." He replied with a clearly annoyed, "Yes".
Moral: Googler's can make you feel dumb, but don't you dare do it to them.
Darthsr@reddit
Years ago I had a similar interview but they asked me to do a riddle at the end of it. I immediately got up and thanked them for their time and went home.
Acceptable_System389@reddit (OP)
what was the riddle
bravopapa99@reddit
I had an interview like this maybe 20 years ago, I think the guy was trying to impress the other interviewers at my expense, and, to quote the great scholar Vin Deisel, "He did not know who he was fucking with." He was asking very specific questions about C++ but, little did he know, I had just finished a role as "C++ Guru" on an IBM contract!
So when it got to operator overloading, he spat out this mouthful of utter word salad which, to the uninformed ear probably sounded hip and cool, but alas for him, I had been given a copy of the ARM rules (I think that's how I remember it, it was all about type coercion and stuff, what the compiler refers to when code gets jiggy), so I let him finish, started answering by "Well, you obviously know about the comprehensive rules for data type conversion..." and then, my memory fails me here, but I basically asked him for his opinion on something specific, think Monty Python and the European or East African swallow at this point.
The initial silence was terrible. Then he gave a wrong answer and I said, "No, that's a common misinterpretaion blah blah" and corrected him at which point he decide that the interview was over.
Twats everywhere in interviews, sounds like its still the case.
shaidyn@reddit
Whenever I've run into a situation like that, it wasn't about me, and it wasn't about the interviewer, they simply had another candidate they wanted to get the job.
Acceptable_System389@reddit (OP)
I didn’t even consider that. Very possible.
charging_chinchilla@reddit
Bad interviews happen. Most companies do not have a good way to grade their interviewer quality so it's pretty much a crapshoot. Don't let it get to you. Ultimately, it's their loss as they'll be filtering out qualified candidates because of it.
Acceptable_System389@reddit (OP)
Thanks, these comments have been helpful in reminding me it’s not just me, it just is what it is sometimes.
hereforcatsandlaughs@reddit
I had an interview once with a national lab (while working at a different national lab, so I had some experience and context) that was supposed to be two people from the start, virtually. I hop in and there’s one person with his camera on and we start the interview. About halfway through the second person joins, doesn’t turn his camera on, and pretty much immediately asks how I would develop if I couldn’t use an IDE. I said “VIM I suppose, do you often work on projects where you’re unable to use IDEs? What do those reasons look like?” He stutters and moves on, never turning his camera on, asking somewhat inane questions like that one.
I did not get moved on to the next round 🤷🏻♀️
Beginning-Comedian-2@reddit
A couple months ago I had an interview with a company and the two people interviewing me wouldn’t turn their cameras on.
They ended their interview all but saying that they micromanage people and am I okay with that.
All their GlassDoor reviews say they micromanage people.
I decline the second round interview.
People who don’t turn their camera on are shady.
Acceptable_System389@reddit (OP)
Oh god, that's awful. And that's exactly what I mean by power trip. With stupid interview questions like that, that the developer can't even answer themselves.
Also not turning on cameras for a virtual interview is a pet peeve. I interview people all the time at my current job and make a point to have empathy for the interviewee, it's a vulnerable position to be in, and some devs that have worked at the same company for years on end forget what its like on the other side.
hereforcatsandlaughs@reddit
It was definitely not a question I had prepared for but I think it says more about who I would have been working with than anything so I’m not sad about that one.
Beginning-Comedian-2@reddit
I had an interview 2 weeks ago where I knew it would not be a fit 5 minutes in.
Acceptable_System389@reddit (OP)
That sounds frustrating. Did you know it was out of your league going into the interview? Or was the job posting super vague?
I think I called mine a power trip because... the questions just felt so irrelevant to being a Lead C# Developer. They felt more like a barrage of "haha gotcha, betcha didnt know this one."
There was also a significant age gap between myself and the dev interviewing me. It did feel a bit like he was looking down on me from the start, since he's a Lead for his dev team, and I'd be a lead for this other dev. team, we would technically be equals. He made it clear he is far superior than me... lol. (or at least that's how it felt. During the interview I avoided thinking about this because I like to assume positive intent, but now that it's over and I can reflect on it... it was weird).
Beginning-Comedian-2@reddit
I didn’t know it out of my league going in.
The job post was vague and “lead” can mean different things.
But based on how impersonal the interviewer was and his desire to “raise the bar in development” at the company (and initial interview question) I could tell I wasn’t what he was looking for.
After the interview I looked them up on GlassDoor.
Turns out they’re known for low balling foreign devs and rushing development in a disorganized way.
Maybe this new CTO was trying to change that and set a higher standard with US on-shore devs that were more classically trained in computer science, agile, and leadership. (I’m more mid-level, self taught, used to disorganized teams.)
And maybe part of his standardization process was showing upper leadership that he was thorough with each candidate.
Also, they said the role was hybrid in my city and I kept asking where the office was. He tried to dodge the question until finally admitting they don’t have an office in my city yet.
So it sounds like growing pains all around for the company and they’ll have no problem finding who they’re looking for.
But we both knew it wasn’t me early into the interview.
No need to torture each other by drawing it out.
PragmaticBoredom@reddit
I had a manager like this. He thought of himself as a modern teacher-philosopher, wiser than everyone else after listening countless management audiobooks.
Every conversation with him turned into a series of leading questions. He would pretend to ask you a question, but secretly have an answer in mind. He'd then keep asking more questions to hint that you hadn't yet arrived at the correct answer.
"Can you think of anything else?" "What's another way to think about this?" "Is there any other way to do it?"
It was a insufferable.
Be glad you got see this behavior in the interview so you could recognize how much you can't stand this person.
Acceptable_System389@reddit (OP)
That's terrible. And yup, I agree. The great filter has done its work. Like I said in another comment, my only regret is not standing up for myself at the end when I knew I wouldn't want to work with this guy anyways.
He took it upon himself to explain the level of responsibility a Lead Dev. must have, and how they need to work independently, and work with business. I was like yup, I know all this. I do all of this. I'm already a Lead Dev... but him and I had about a \~30 year age gap. So I wonder if that was a contributing factor.
drguid@reddit
Yes had many of those interviews.
Trying to maintain their code... now that's a nightmare.
One role I actually got offered ended up with me trying to figure out some weird math C# stuff that seemed to be used solely to save 4 bytes of memory. It was a basic CMS, not some high frequency algo trading platform.
propostor@reddit
Yeah I did once, kind of.
The guy who interviewed me had oddly similar experience prior to becoming a developer, which was a somewhat unconventional route and I think he held a bias against me because he also held such biases against himself.
However on paper I definitely had way more experience, in years and, well, actual experience of stuff I have done.
The technical part of interview was textbook academic questions on SOLID principles and Clean Clode, and that was it. No questioning on my actual work experience, things I had worked on, my knowledge of language, framework, domain, etc. Nothing.
All I can surmise is that he had only worked at that one company, studied SOLID and Clean Code from back to back and thought it made him a god.
My level at that time was senior.
They offered a JUNIOR position.
It was the most offensive job offer I've ever received, and made me question myself for a week afterwards.
Then I got a job elsewhere, at my level.
Acceptable_System389@reddit (OP)
That's funny you mention SOLID, because that's something I made sure I memorized before this interview. He asked me to list the SOLID principles and what they do. So sure, I did. But by the time I finished my answer, I was even thinking to myself how useless of a question that was.
I had just memorized the principles, a better question would've been for him to ask how I apply SOLID principles.
For the record, I took it upon myself to explain how I apply SOLID principles as a part of my answer anyways. But he seemed like he could care less anytime I got an answer correct. For every correct answer, he came up with a question that had nothing to do with anything. I'm almost positive he took one look at me and said "Nope" at the start of the interview. (I am guessing because of the age gap between us, but we would essentially be "equals" if I got the job as Lead Devs for different teams.)
propostor@reddit
Yeah I honestly think the guy noped me as soon as I told him my background.
I cut my teeth as a dev working in China and wrote a large web application for a mate's start-up from the ground up - and if I say so myself I think it was quite the feat that most new/junior devs never dream of getting to do, it was a huge skills springboard for me, straight in at the deep end.
Anyway he happened to be in China at roughly the same time I was there (and I don't think he was a dev at that point - not judging by the timeframes he told me when he introduced himself).
Among westerners who go to China, there's often strong negative judgement for damn near everything. "You're only an English teacher." "You can't speak Chinese." etc. With such sentiment, I think he might have immediately assumed something negative, perhaps assuming I was one of the many "traveller coder" types who try to make it freelance while backpacking and just pin together a few wordpress sites or something.
He certainly didn't interview me on anywhere near enough relevant topics. If I were to throw the negative sentiment back at him, I daresay his time in China was indeed just a bit of a jaunt, in the English teaching circuit, getting drunk etc, which is fine and quite common and can be fun, but that ain't the life I ever lived when I was there. So he didn't even know what to interview me on -- but he thought he did, because Clean Code and SOLID, yeah!
It's pretty much the only reason I can think for being so harshly judged after such a short, vague and irrelevant technical part of the interview.
Or he just didn't like me anyway, lol.
sozer-keyse@reddit
Something similar.
Interviewed at one company that had 4 stages: one with the hiring manager, 2 technical interviews with devs, then 1 more with a director.
First two stages went pretty well, the third stage was with a developer who was kind of an asshole. He spent half of the interview laughing at my face while I was formulating answers to technical questions. Got a call from the recruiter the next day saying they weren't going through with my application because I didn't understand a specific concept (which I learned quite easily afterwards anyway). The day after that, I got a call from another HR person telling me that the director was waiting for me on the Zoom call and was wondering where I was, apparently they didn't even give him the memo.
Thankfully, I got hired a month later at a company that didn't pull any of that BS.
discord-ian@reddit
Bullet dodged! It sounds like maybe this dev wanted the job. I'll just add I hate vocab style interview questions. Often, different technologies have different terms for the same thing or what is a very important concept in one technology is abstracted away in another. Vocab questions don't really offer any good signal on how good someone is going to be, especially at a lead level.
Acceptable_System389@reddit (OP)
I agree. He was already a Lead Developer for his team. I think it was a power trip because (I assume..) we had a significant age gap.. I'm a woman in my 20s, he was a man in his late 50s. Again, this is an assumption. I could be dead wrong, and he could just be a plain old dick. But you know... it crosses my mind.
If I had gotten the job, we would essentially be equals as Lead Developers for different teams. He made it clear to me at the end of the interview I am not his equal. Which he is basing off of... me not knowing three very niche keywords in C# and one niche ORM framework.
He kept repeating to me at the end of the interview how big of a responsibility it is to write code independently, take full responsibility, and to constantly interface with business customers about your code solution. I was like yup, I do all these things already. (I'm currently a Lead FullStack Developer on my team).
He kept repeating himself in a derogatory tone was as if I'm not getting it. I really did my best to emphasize my skills, my independent work, my work as a Lead Dev leading a team, my work interfacing with business. He just wouldn't accept it.
Ugh. Bullet dodged.
The_Big_Sad_69420@reddit
Yep, been through many of them.
OverEggplant3405@reddit
You found out early that they aren't the kind of people you want to work with. That's a good thing.
It's a familiar pattern: they ask a bunch of gotchas that have nothing to do with the job and clam up when you actually know them or (worse) try to gaslight you into thinking you got it wrong.
Someone asked me about the 12 factor app principles like I was supposed to have them all memorized, as if that's at all necessary or beneficial to doing the job. I told them heroku created them to market their cloud hosting platform, and he got offended like he didn't already know that. I even knew a few of them. He "corrected" me by repeating what I said as if he was reading it from a book. When I went to look, I was actually right. I had read through some pros and cons about each of them from various blogs years ago.
ocxricci@reddit
Red flags everywhere