Interviewer got upset with me because I refused to provide an example of how I implemented a concurrency control policy in my former employer's production codebase. How would you handle this?
Posted by 9ubj@reddit | ExperiencedDevs | View on Reddit | 124 comments
I have been shopping around for a new role and I landed a few interviews here and there. Also, I am a C++ dev and I have mainly worked on the internals behind distributed systems and for the defense sector. So think stuff like preventing deadlocks, mutual exclusion around operations on file descriptors and other I/O devices from multiple threads, yada yada.
I had an interview with a big-ish company recently and the interviewer straight up asked how I implemented a concurrency control policy and asked for specific details. I could not answer this exact question for IP (and TS) reasons, so I paused and explained to him this and then I tried to "reframe" the problem such that I could answer his question without revealing any secrets.
Lo and behold, he cuts me off and starts saying "I need you to explain to me exactly how you implemented the solution - no tangential examples or anything!" and then he sprinkles in "You need to be a better job showing me your knowledge of C++"
This was interview 4. They invited me for interview number 5 and the technical question was to solve the Ages of Three Children puzzle with "woman" misspelled as "women" numerous times in some word document. At this point I snapped and just asked the guy to withdraw my application.
Part of me feels like we can't be picky in today's job market but on the other hand, I feel like all of this points to how crappy the workplace would have been should they have made an offer. What would you do?
Isogash@reddit
A single interviewer being difficult is an immediate no-no for me. Companies that hire people like that are terrible places to work.
9ubj@reddit (OP)
Worst of all he revealed he was the hiring manager at the end lmao
autisticpig@reddit
Now imagine what your reviews will be like with that person :)
9ubj@reddit (OP)
The good news is that the interview was virtual. He was picking inside his nose with his thumb numerous times. I specifically remember how his thumb was making an "S" shape. I'd gag if it was in person and I had to shake his hand
actionerror@reddit
Thumb? đ
tripsafe@reddit
Yep thatâs enough of this thread for me
actionerror@reddit
Oh dear, even worse. And the company chose to keep him around. Enough said.
9ubj@reddit (OP)
For over a decade too. He said he was a veteran there
eightbyeight@reddit
You dodged a nuke
Choperello@reddit
I mean you do you but unless concurrency solution is some fancy new algorithm that would be genuinely new IP it feels like a strange hill to die on. Itâs standard swe stuff. You can replace the name of secret system X with some generic name like âcustomer data systemâ or whatever and most interviewers would be fine with that and donât care.
Breadinator@reddit
The OP made it clear the interviewer wanted specific details. This is a non-no and can easily violate your legal obligation to your current employer, depending on the way the arrangement was made when you joined.
In the US, in addition to any NDA you signed, your disclosure of such details may also fall under the Defend Trade Secrets Act or the Uniform Trade Secrets Act (depending on the state). You don't need a special, proprietary algorithm; just knowing how to apply it specifically (or even just what doesn't work) can be enough.
Choperello@reddit
Feels like Iâm that case you open with âI am legally barred from discussing ANYTHING concrete about these projects even the boring non sensitive stuff, I can go to jail if I doâ. If the interviewer still pushes then you end up in a well I canât work here situation.
9ubj@reddit (OP)
Exactly what I tried to do - hence the comment about reframing the problem
Choperello@reddit
I guess? I wouldnât call that or have said Iâm reframing the problem. Iâd call it the real problem as it actually was Iâm just changing some names to preserve employer confidentiality. Reframing the problem usually means lemme actually change what you ask me into something I think is similar but not what you asked.
ryhaltswhiskey@reddit
TS (in the post) = Top Secret. I can see why this person would be cautious.
Choperello@reddit
Feels like in that case youâd just open with âI am legally barred from discuss anything concrete about these projects even boring stuff that is run off the mill stuff. I apologize but technically I can go to jail if I doâ.
Graumm@reddit
Agreed, details about threading/concurrency are usually not specific to a company. Generally you can even talk about what the thing is, without getting into the details that would actually be considered IP. You aren't there to deliver working code.
I would only be guarded in this way if it was under a security clearance, or if the details of the concurrency/threading are a part of a company's value proposition/competitive-edge rather than just the expectation.
9ubj@reddit (OP)
It was under security clearance, hence the TS comment
Frenzeski@reddit
Yeah when you have a security clearance you have to take this shit way more seriously. Itâs not like an NDA where you might get sued, you can go to jail for breaching it
9ubj@reddit (OP)
Yes. And I don't have a problem with answering the question. I have a problem with the fact that "it was his way or no way", without putting any emphasis on the fact that I can face civil and/or criminal penalties for being too forward.
IMO a professional would say "Ok, I understand. Let's try something else. If you have X and Y, which mechanism would you use to prevent a deadlock." That way he still gauges my knowledge without putting me into a legally precarious situation
dizekat@reddit
Luckily I just have to write some stuff like say a cache or an algorithm rendering a bunch of circles with depth sorting or the like.
Everyoneâs been moving away from coding interviews, and they donât know how to do non coding interviews so, yeah :/ . I like coding ones because i can just write it really quickly and then talk about possible improvements etc.
CorrectPeanut5@reddit
My first corpo job you have to take a 2 day interview training class before they would allow you to conduct an interview. I don't think most companies put that kind of effort into training anymore.
9ubj@reddit (OP)
=P It's not terrible. I always just use the example of having multiple loggers writing to stdout. If you don't wrap the message + flush in a mutex, then you get garbled output.
But yea, agree 100%. You move away from leetcode (which imo is a dumpster fire) to puzzles and riddles and personality tests and it ends up just being another dumpster fire
dizekat@reddit
So the thing i tend to dislike about talking is that oftentimes they do not themselves know the subject very well either. I think the happy medium is just small pedestrian realistic coding examples, like say implementing a simple LRU cache with keyed access.
Although the interviewer not knowing shit also happens with coding when theres no test by running.
One time I failed a JS interview, and only afterwards realized that the odd questions the guy was asking were as if i sorted an array without providing a comparator, in which case it sorts by string value.Â
I provided the comparator as a lambda and the guy must have not known lambdas, so hes trying to prod me into realizing thereâs a bug in there that I didnât make. And I am primarily a C++ programmer so it is not like i got burned by the stupid sort 50 times myself, i write a sort i provide a comparator.
Frenzeski@reddit
Yeah fuck that person
Imoa@reddit
The number of commenters that just glossed straight past the security clearance is really obnoxious.
Interviewer shouldâve been cool with the adjustment. Not rolling with it just kills the conversation on the spot.
Izacus@reddit
Well, OP also glossed over that working for project with military/governmental secrecy has real consequences for further job search. This is one of them.
ReikaKalseki@reddit
That is how reddit and the internet in general work. Not only do a lot of people, even otherwise skilled people, possess poor reading comprehension, but it is also very common to just ignore facts inconvenient to one's soapbox so that you can still argue like anyone who disagrees with you is ignorant.
jisuskraist@reddit
I think the problem today is AI. If I'm interviewing a candidate and starts lingering the answer I will suspect he is using AI and doesn't have a concrete csse where they implemented the technical thing they are explaining to me.
Graumm@reddit
My eyes glossed right over that, and not everybody knows the acronym. I'm with you then.
If they have a problem with you talking about a system under a security clearance then fuck them. You never know what might get back to them or how they might interpret it, and it can have nasty legal consequences.
9ubj@reddit (OP)
Oh, sorry, yes. TS = top secret and there's also SCI. Common for a lot of electrical engineering companies (and this company provided software for that industry)
VictoryMotel@reddit
I agree, if I was interviewing and someone wouldn't even describe the solution to something I would assume that they don't know it and won't be able to implement it on the job either.
ChallengeDiaper@reddit
This is my take as well. The IP and TS justification doesnât seem ârealâ to me. This is standard stuff. I obviously wasnât there during the interview, but from here, I can understand the interviewers frustration.
Smok3dSalmon@reddit
I had a brutal 5 round on-site on the same day which included a lunch interview. The last round was the most important and I bombed it bc I had 4 sodas and my back was killing me bc everyone wanted to stand during our interview. I asked the interviewer if I could sit down and he said no. I gave them unsolicited feedback on my way out.
FearlessAmbition9548@reddit
Theyâre morons obviously but why would you have 4 sodas lmao
Smok3dSalmon@reddit
I was talking for like 6 hours. My throat was dry and all they had was Lacroix and other sparkling drinks.
NoodlesGluteus@reddit
No water?
k958320617@reddit
Exactly. Can't believe people even drink that stuff any more, never mind FOUR!
WhenSummerIsGone@reddit
i had something similar after traveling across 2 time zones. it was brutal and i absolutely could not think by the end of the day. I wish they had left me alone during lunch.
Smok3dSalmon@reddit
Yeah I was trying to be socially polite bc they were putting their best foot forward. But it was exhausting having to play foosball and exchange pleasantries with so many random people. Everyone used the occasion of interviewing me to get a drink and stand.
They werenât even rude or anything, but the room I was in had no chairs⌠I suppose they do stand ups in there.
This small miscommunication on their behalf resulted in them optimizing for standing endurance⌠this isnât a retail job lol.
The best part was the train home was full and I had to stand. đ
sonofasonofason@reddit
I fractured my foot the day before my interviews at Google, and so my foot was in a medical boot. I emailed the recruiter asking if they had a taller chair I could use while whiteboarding, so I wouldn't have to stand all day.
He wrote back offering options of a tall chair, lower whiteboard, wheelchair provided by staff (!), an additional lunch escort (!!), or they could adjust the interview to use a laptop instead of whiteboard.
I told him I'd be good with just a taller chair. They ended up ensuring all my interview rooms had both an elevated chair and a lower rolling whiteboard . And they reserved a parking spot for me that was closer to the building.
I was blown away by their accommodation. That was like 10 years ago though.. the market is a little different these days :(
RepulsiveFish@reddit
This is wild to me bc when I interviewed there as a new grad 10+ years ago, one of my on-sites ended up being in a room that didn't have a white board, and the interviewer had to scramble and find a piece of paper for me instead.
And then two or three of the on-site interviews were problems that could be solved with depth-first search, so they decided they had to do extra rounds virtually later to get more data on me.
aMonkeyRidingABadger@reddit
Getting asked similar questions can happen because the interviewers pick their own questions without consulting the other interviewers.
Technically thereâs a sheet that gets handed off where you can write the question(s) you asked, but I remember that it wasnât used very often.
ritchie70@reddit
My employer has a bunch of absolutely non-technical questions that you are supposed to draw from for interviews - we're not a technology company, we're a retailer with a massive IT department. Almost everything is custom at the store level, although we are getting better about buying instead of building.
I tend to ask one or two of their questions and one or two to figure out if they're actually 1) at all technically competent and 2) if they have any idea how a store works.
9ubj@reddit (OP)
Crazy. You tell them nowadays that you fracture your foot and they ghost you. When you follow up, they say: "Oh sorry, we decided you weren't a culture fit."
My god...
pepejovi@reddit
"Your bones are too weak"
bdanmo@reddit
the chortle I just chortled
nus07@reddit
Well itâs Google and thatâs why they are one of the most desired places to work for despite everything.
Immediate_Fig_9405@reddit
lol they said no? wtf
TinStingray@reddit
This is the funniest shit I have ever read.
Groove-Theory@reddit
That's an ADA lawsuit waiting to happen someday
jujubean67@reddit
People really are power tripping on these shitty interviews ffs
EricH112@reddit
I am reminded of an interview I had where they forced one of the employees who was in a motorcycle accident the week before and had a mangled leg to walk up to the second floor to interview me. The man was so high on pain killers I doubt he could evaluate anything. I realized this is how they treat their people and purposely bombed the rest of the sets to go home early
9ubj@reddit (OP)
Funny. Imagine if someone had an inguinal hernia surgery a week before, and they quite literally had to sit down due to post-op pain. And imagine that they didn't want to reveal to the hiring team that their crotch is literally being held together by sutures, staples and mesh until everything heals up
Smok3dSalmon@reddit
Oh man no way. Thatâs brutal. Haha
Careful_Ad_9077@reddit
The best part is that it's the only interview and this is where the company is supposedly showing their best face.
9ubj@reddit (OP)
EXACTLY! I was going to point that out in the post but didn't want to make it too long winded. But I am just thinking to myself like "guys! your workers can't even spell basic words and you think any decent engineer is going to waste 6, 8, 9 rounds on you?"
CrayonUpMyNose@reddit
Currently dealing with a team with extensive spelling errors in their internal docs and I can confirm the spelling is only the tip of a giant iceberg of behavioral "not my job" and "I'll do it by myself without other people's input" issues.
Urtehnoes@reddit
I had someone submit a database schema to me with "performance" spelled "peformance" in every instance. The drama I faced refusing to green light something that would've taken them maybe 20 minutes to fix across their entire branch.
Lazy. Lazy. Lazy.
ritchie70@reddit
We have a JSON data feed that goes from one vendor through corporate to dozens of other vendors.
It has a field name misspelled.
Our documentation specifically says that it is misspelled because nobody noticed until there were way too baby recipients to fix it.
chicknfly@reddit
I dealt with a codebase like that. There was an attribute in the database table that was misspelled, and so the automated Entity Framework created objects with that name, which lead to the JSON objects having that name âfor consistency.â đ
WhenSummerIsGone@reddit
i think this is a sign of too much coupling between things that should probably not be
9ubj@reddit (OP)
I don't know how I didn't put two and two together. You bring up a really good point - misspelling can make things impossible to find if you use utilities like grep and vim's regex search (which I use heavily)
5plicer@reddit
At least they're consistent. :)
oupablo@reddit
Spelling errors are a weird one for me. I work with a lot of people for whom english is their second language. Spelling errors in messages are whatever however I find spelling errors in design docs to be quite strange. The document clearly has the little squiggle under the word and it'd take you a half second to tell it to correct it but you chose not to. Although, I'd much rather go back to this than the new hell which is 47 page docs that are generated by AI comprised of 90% fluff.
9ubj@reddit (OP)
I really like what you said about the tip of the iceberg. This is exactly what I saw at my last workplace!
siliconsmiley@reddit
One of the most important lessons for me about interviews is that I am also interviewing the company that is interviewing me. Yeah, it's rough out there. But expecting you as an interviewer to divulge IP is a huge red flag.
Ok-Read-456@reddit
probably dodged a bullet there honestly
hawk5656@reddit
I wish I had dogded this bullet, I did not see the writings in the wall while interviewing for a known toxic gaming company, I naively thought my experience would be different.
DanFromShipping@reddit
Rockstar? But I assume every gaming company sucks to work for.
Dry-Definition-6526@reddit
did you get any feedback after the withdrawal
9ubj@reddit (OP)
Interviewer number 6 emailed me while while interviewer 5 was interviewing me. I told interviewer 6 that I withdrew already. He emailed me a few days later and said they were going to "tighten their process." This company has been around for 30 years... I mean they had 30 years to tighten their process
tripsafe@reddit
To be fair interviewing evolves as people cycle through, company goals change, and technology changes. They could have only come up with their current interview format in the last year or two. But still, I donât want to give them too much benefit of the doubt since there are numerous red flags.
ritchie70@reddit
I was hired by my employer around 25 years ago.
I was interviewed by 5 people, one after another, in one afternoon. 2.5 hours total, in person.
They decided I was not right for that role.
A couple weeks later I was called to interview for a different role. Interviewed with four people in the same way.
Got a job offer a couple of days later.
I later found out that most of them were ânoâ on me but the one developer who interviewed me was a strong and persuasive yes.
Guy who got the first job and I did orientation together and worked pretty closely for most of his tenure.
I eventually wound up running the team that he had been hired to as an IC after he moved to a different position.
Now we do a remote interview 3 on 1 by peers, then if they make it past that they are interviewed by the hiring manager then the director, all as separate events across weeks.
I think the old way was better.
reboog711@reddit
I work at a 100+ year old employer. There is no consistency in the interview process, and I've helped with more than 3 "interview working groups" to standardize over the past decade. Every time leadership changes we go back to wild wild west.
positivcheg@reddit
Unless interviews are recorded and reviewed upon a claim of the interviewee, itâs not tightening but just ignorance :)
gefahr@reddit
eBay?
boring_pants@reddit
I'm sorry, is five rounds of interviews common in the US?
I've never had to do more than two.
jujubean67@reddit
It's common in Europe too, I've never interviewed at a place that had only 2 rounds in my 15 years lol. Maybe at 1-2 person companies.
boring_pants@reddit
Huh, I've interviewed at companies ranging from 5 to 2500 people in the same time frame. I wonder if it's a country thing or perhaps just an industry niche thing. I've mostly done C++ application development, and perhaps web dev (for example) has a different hiring culture?
OkPush3638@reddit
In the data science / ML engineering field I've never seen more than 2 (maybe 3 if you include a phone screen)
jujubean67@reddit
Beats me, I've worked with everything from Ruby, Python, Go, Node, Elixir etc. people have always loved to waste my time.
QueenAlucia@reddit
I've only ever interviewed for companies doing 2 rounds in my 13 years lol I am in London though, it is Europe but maybe it is different? First interview is usually with product to gauge your culture fit and overall qualification and then a second round for technical deep dive.
jujubean67@reddit
I've always had multiple technical rounds for as long as I can remember, even with UK companies lol. Granted I do work remotely so maybe that's the reason for the extra checks. But 2-3 rounds of technical + behavioural + maybe product is the usual IME. And I'm not even counting recruiter interviews in this.
QueenAlucia@reddit
Ah maybe that is the difference, I am in person most of the time, at least for the technical round.
ryhaltswhiskey@reddit
Not common. I've never done more than three. But I'm also not getting interviews at any FAANG.
CorrectPeanut5@reddit
Only FULL TIME jobs. Contract it's rare to have more than one tech interview.
9ubj@reddit (OP)
Unfortunately yep. I'd say 4 is about the average for a tech job, but this place told me there was going to be 4 more after I had already completed 4 tech screens. I thought on 5 we were going to start talking about salary and HR stuff since I had gone through 4 tech screens already. So when someone who could barely speak English asked me to solve some silly puzzle I simply couldn't take it anymore and lost my shit
Exowienqt@reddit
I refuse to continue a hiring process that's more than 3 interviews. Basic filtering interview, finer filtering interview for the position, and a team fit/face check.Â
I got my university degree, thank you very much, I got tested quite thoroughly. If they are searching for someone they can string along with BS, they are not looking for me.Â
9ubj@reddit (OP)
Wanna know what's funny? I hold several publications in the area. One of them is approaching 100 citations. They can literally google my name and find my publications. They are even listed in my CV.
But that's not enough. I have to solve the Ages of Three Children puzzle instead.
Anyhow, to your point - 100%. 3-4 interviews max. I already passed 4 tech screens and at the end of the 4th interview/screen, they told me there's 4 more...
ryhaltswhiskey@reddit
WAT
That company loves to waste manager's / developer's time apparently
dexter2011412@reddit
could you explain how you reframed the question and where you learnt these that isn't non-standard?
I'm guessing it's like an advanced variant of the standard approaches. How does one gain intuition for something like this?
So at what point do the things become revealing IP and not just an explanation of the approach taken?
9ubj@reddit (OP)
He was asking what the operations that needed concurrency control were doing, and why they needed concurrency control. There's nothing wrong with asking about sync primitives. However I could not get into what the operations were doing due to IP and TS reasons.
I don't have a problem with him probing about my knowledge of multithreading. I do have a problem with him trying to probe IP/TS info out of me when I explicitly tried to work with him to show that I know a bit about multithreading but without revealing IP
dexter2011412@reddit
awesome, that helps a lot, thanks!
could I reach out to you for a few more questions?
bdanmo@reddit
jfc
apartment-seeker@reddit
you were in the right
hiddenhare@reddit
The interviewer had been given a scorecard, and one highly-weighted item on the list was "demonstrated previous experience writing multithreaded C++ code". If you happened to have an interview where you didn't discuss specific multithreaded C++ code that you've implemented in the past, that part of your score would have defaulted to 0, probably causing you to fall below a threshold where your application would be rejected automatically.
This happens when the people in power notice that hiring is important and impactful, so they decide to take personal control over all hiring. Those leaders will be personally involved in as many interviews as possible for as long as possible, but they'll eventually reach a breaking point where that becomes impossible. At that point, they'll "delegate" interviews to other staff, but those staff will be handed an objective scorecard and their subjective impressions of the candidate will be ignored. (The excuse is usually "for legal reasons, we need to be certain that our interview process is fair and objective".) This practice destroys 90% of what makes interviews useful, but for some leaders that's a small price to pay in exchange for the illusion of control.
Orzhov_Syndicalist@reddit
Exactly this.
Our company just did hires for two new data jobs, and I could not get an answer from my manager, the one who was doing the actual final hiring decision, on what, specifically, we were looking for. Traits? Skill? Knowledge? Teamwork? We had sheets and a grading system similar to what you had above, but none of it seemed to cohere into anything resembling a concept. It was just a bunch of grades.
actionerror@reddit
Bullet dodged. Believe me, you donât want to work with that asshole day in and day out. Mental health is also very important, even in this job market.
KronktheKronk@reddit
You should be plenty capable of describing patterns without revealing IP.
CowardyLurker@reddit
Plot-twist! Theyâre just testing to see if youâll cave to pressure. /s
Seriously though, good for you. Showing a touch of self-respect. Obviously youâll keep your chin up. Props.
JamesWjRose@reddit
I would have immediately walked AND told them that I would post their name and company name so everyone could avoid them
Barbacula@reddit
You did the right thing. That was the tip of the iceberg.
Dry_Author8849@reddit
IP theft intent. You should warn him and ask if he would be ok on you revealing to a third party their IP and codebase.
Any person with two neurons should cheer your attitude and see it as a green flag. I'm sure he could come up with a different way to test your knowledge.
You can clarify the answer to him "I will not commit IP theft and break a NDA I signed".
Cheers!
bigorangemachine@reddit
I run interviews... asking for solutions during an interview is a no-no.
That guy wanted free work.
I got some great answers about how systems work and how people integrated tough solutions but never any specifics.... broad strokes only...
M4K1M4@reddit
I was rejected because I wrote a different syntax for for loop instead of the one the interviewer wanted. He was visibly offended by it, even though it made no difference. It is what it is.
ReDucTor@reddit
That's a pretty big red flag, if it was someone relatively young it could be the situation of them trying to prove themselves as superior which I have seen, but if it's someone that should definately know and you don't desperately want the job then raise it with the recruiter or any HR as this could be a huge issue for the company as it's borderline corporate espionage through a job opportunity.
Short-Situation-4137@reddit
The interviewers seems to be an asshole, plain and simple. You dodged a bullet.
chain_letter@reddit
Not even a "would you do it for a scooby snack?"
mikkolukas@reddit
This is the point where I would stop, take deep breath and consider my options.
I would probably collect my things, politely say my goodbyes and not return.Â
9ubj@reddit (OP)
Lmao yep. I could like feel my heart beating hard the moment he said that. And yes, you're 100% right. My mistake was wasting more time than I should have on this company
F0tNMC@reddit
If the interviewers are dicks, then it's pretty much guaranteed that the company is full of dicks.
squngy@reddit
Not necessarily, but at the least it is full of people who are tolerating dicks, probably from desperation.
9ubj@reddit (OP)
I finished my masters in 2018 and applied to several places hoping the mud would stick. Early 2019 I got interviewed by a company and the two interviewers were arguing with each other during the interview. Worst year of my life...
dizekat@reddit
I had a perfectly good interview experience and then some time after I got the job unexpectedly I had to pull a 8pm to 4am 7 consecutive days shift.Â
With a really idiotic unhandled exception bug they had which had it alerting me more than once per hour (then I had to wake up a product person so they email one of the three âcustomersâ they had who were triggering the bug in the course of normal use). Lacking proper tests they had no way of deploying any fixes on a short notice, so it took longer than a week to fix.
So yeah as others said consider yourself lucky, the job can be absolute shit given that the interviewing was shit.
squngy@reddit
Dodged a bullet!
If they do this shit in interviews, I'd bet they do worse in their actual work.
Probably stolen IP all over the place.
honestduane@reddit
They were just trying to do non-kinetic extraction of competitive intelligence and technical data from you
eslforchinesespeaker@reddit
If you got a fifth interview, it sounds like they probably conferred, and interviewer four was over-ruled. Maybe they understand your point about IP. Maybe youâre famous as the guy who bailed mid-interview because of a typo.
Hard to guess what an offer would be like, or what the employee experience would be like, based on an inept recruiter.
Sounds like youâve got good hard skills and experience, and are likely to find something. Good hunting.
9ubj@reddit (OP)
Much appreciated but really I can't believe we've come to this point. It's not even the typo itself - it's the double standards. Their best foot forward is aggression, typos, silly questions but god forbid my CV has a typo in it...
West_Helicopter_6719@reddit
post text" is an interesting choice of words
ummaycoc@reddit
Sometimes things are scheduled out then you hear from everybody.
UncheckedMoonrise@reddit
In my opinion you did well: tried reframing the problem, not disclosing IP, explained why. If the interviewer crashes out, itâs a red flag.
I wouldnât worry unless this happens again, which I bet it wonât.
I am also currently looking for a new job, and I am also balancing between being picky and accepting the tough market realities. But some red flags are just bad enough, in my opinion.
9ubj@reddit (OP)
I understand the job market sucks right now but I hope that this post alongside the numerous other posts similar to it help gently coax people into being at least a bit more picky. Job interviews have always sucked but this is getting excessive
Stay true to your morals!
yuhSendNodes@reddit
Let me guess, the company starts with a "C"?