Earlier quoted context omitted.
" but the interview engine is already running at full speed:" I dont know if this is a recent thing, but I had a similar thing where an interviewer was racing forward, and would only accept the answers he had in mind. In Python, he asked me how to search for substring. I was thinking but he started hurrying me. So I said regex and started writing a regex. "No, there is an inbuilt method" I couldnt remember the method…
I probably would've done the same. "I don't remember what the function is called" would've been fine-ish, but reaching for a regex is just insane.
The worst job interview I ever had
311–320 of 589 posts
Re: The worst job interview I ever had
#312I always wanted to tell the story of my weirdest interview. It's bad in a different way from OP's. This was for a "Machine Learning Engineer" contractor position. - Hi, I'm gobdovan. How are you? says I. The interviewer doesn't bite: - How many prompting techniques do you know? (ok?..) After a couple confused seconds, I respond with 2-3 techniques and ask if I should explain them, but the interview engine is already…
I've had an interview like this in the past. At the time, I chalked it up to a power trip and the indignant behavior that comes along with it, as it is especially embedded in the culture of the country that I'm based out of. Having said that, talking to a relative, I found out that this style of "interviewing" is often done when they already have someone for the position, but need to show (for compliance reasons, or…
The questioning very quickly veered away from technical stuff and into stuff like, "where do you stand spiritually?" and other questions probing into whatever bizarre cosmic insights I could pull out of my ass at the time. He was the really intense kind of boss who wants to make sure you know of it with the hard back/shoulder slaps and micromanagement, and I could see his office from the boardroom which basically had an array of monitors all wired up to CCTV so he could watch (and hear) people from the comfort of his desk.
If any of that wasn't a red flag, getting hired literally 5 minutes after leaving the office was probably the biggest. I lasted about 6 months and even trying to leave was an ordeal.
Re: The worst job interview I ever had
#313This… was a mistake on both you and the interviewer. All interview questions - unless it’s impossible to twist your answer to fit this - is scoped to “… at work”. Nobody who asks “tell me about yourself” is asking you to talk about how you met your partner, how many cats you have, or that experience you had, that one time, at band camp. It would be redundant and awkward to literally say “… at work” at the end of ever…
Re: The worst job interview I ever had
#314Earlier quoted context omitted.
No, but I gained something just as valuable. After the interview, the recruiter who introduced me to this job said they had another role for me. But first, he wanted links to the other positions I'd applied to, what those positions were paying, and how far along I was with each one. I told him I wouldn't do that and he said that it was ok. Haven't heard from them in a year or so, but I'm sure that other interview is…
Why would a recruiter expect you to give that?
They're banking on you offering it because saying no would rule out any mysterious prospects they have to offer, but really they're looking for new leads and if it comes from a candidate then it's warmer. Just have to be polite when you give them vague info and say you're not able to share more than that.
Re: The worst job interview I ever had
#315Earlier quoted context omitted.
> They specifically asked personal questions - parents stuff, relationship, etc. In the US any employer who asks you about personal relationships during an interview is opening themselves up to an illegal discrimination lawsuit.
Which protected characteristic does "personal relationships" fall under? It's vague enough to mean almost anything you want it to be, and I struggle to imagine any sort of successful prosecution.
Re: The worst job interview I ever had
#316I always wanted to tell the story of my weirdest interview. It's bad in a different way from OP's. This was for a "Machine Learning Engineer" contractor position. - Hi, I'm gobdovan. How are you? says I. The interviewer doesn't bite: - How many prompting techniques do you know? (ok?..) After a couple confused seconds, I respond with 2-3 techniques and ask if I should explain them, but the interview engine is already…
It's also pretty sad that now "ML engineer" means prompting...
I started doing "ML" ~ 20 years ago building classifiers people would laugh at today and even at the time barely impressed people when they were 95% correct.
I moved into NLP and built NERs that missed 2-10% of named entities per document routinely. Best of breed approaches and models rarely fared better.
Learned the cornerstones in school for ML; linear regression, ANNs, traditional RL, image classifiers, A* bots, etc, most of which got baked into transformers later on.
Then the transformers went from interesting novelty to useful. I couldn't build a useful one locally, but the toys versions were still fun to play with.
Then the novelty LLM went from useful to generally applicable. Then they became a silver bullet.
I still can't build one locally. I can distill or build or fine tune if you give me some rented GPUs. But to call this ML is very much a stretch.
I still use the traditional ML a lot, but mostly for evals and analysis.
I get being naturally bummed by this but I can't justify feeling anything but vaguely nostalgic about it. Someone with a $20 subscription can mog anything I can build with the skills I picked up.
If someone hands you a silver bullet you'd be a fool to decline it and spend your time hand casting a crude piece of brass. If the difference between 95% and 99% means you know how to aim or oil the gun, that's the world we live in.
Building a good RAG pipeline or prompt optimization or LLM consensus is dumb stuff that produces a better result than anything I could do from my 2010 ML/AI textbooks. I don't lack the knowledge or capacity to compete, I lack the compute.
That's the job now for 99% of companies.
Re: The worst job interview I ever had
#317This… was a mistake on both you and the interviewer. All interview questions - unless it’s impossible to twist your answer to fit this - is scoped to “… at work”. Nobody who asks “tell me about yourself” is asking you to talk about how you met your partner, how many cats you have, or that experience you had, that one time, at band camp. It would be redundant and awkward to literally say “… at work” at the end of ever…
But it was also part of the worst interview I have ever had and these misguided 5 minutes for a weird intro were on the low end of the wtf scale.
Re: The worst job interview I ever had
#318Re: The worst job interview I ever had
#319Re: The worst job interview I ever had
#320Earlier quoted context omitted.
I think this is a very cultural thing. When I interview candidates at my current job, we are interested in hearing about their life outside of work, since we want to know how we can best collaborate If they have to pick up their kids in the afternoon, then it's probably better that they work closer with the other parents than of they're late risers who prefer coming to the office at 10
If the interviewer was fishing around for information for when I start work or if I have kids, the only thing that'd come to mind is whether they're trying to frame me as a slacker to disqualify me from the interview process. Maybe the above is an European thing.
I don't even remember (been a while since I did lots of interviews) if you're allowed or not allowed to ask any of the aforementioned things but I can tell you from experience that about half the candidates would mention their partner and/or kids anyway, because it just is usually not a problem. But it's not such standard fare that someone not mentioning would raise a flag either. I guess most of us just don't think about it.
Also, tech is a bit different and I am not that old - but in Germany you could see a ton of personal details absolutely no one is interested in on CVs, but it's getting better. (What your parents do for work, if you are married, what name you had before marrying, if you have a driver's license for a desk job, what primary school you went to, etc.pp)