Ask Lemmy

I think the interview I least enjoyed was with an unnamed big tech company.

It was the first interview of the day and the guy came in with "so me and my buddy have been trying to solve this algorithm problem for years. I'd like you to try and solve it for me."

Like... Dude, that's not a reasonable interview question! You should not use algorithm questions that you don't know of any answer to in an interview. You're effectively asking someone to give you a solution to something way too complicated of a problem without even a few hours to think about the problem or sit down with it on their own.

Edit: this is from the perspective of a technical interviewer.

I've done around 200 or so technical interviews for mostly senior data engineering roles. I've seen every version of made up code, terrible implementation suggestion and dozens of folks with 5+ years of experience and couldn't wrote a JOIN to save their lives.

The there were a couple where the resume was obviously made up because they couldn't back up a single point and they just did not know a thing about data. They would usually talk in circles about buzzwords and Excel jaron. "They big data'd the data lake warehouse pivot hadoop in Azure Redshift." Sure, ya did, buddy.

Yes, they were "pre-screened". This was one of the BIG tech companies.

I had an interviewer hand me an IQ test before they were even willing to speak with me about the position. Awful experience.

To kick us off, mine from this week that I wrote down in another thread. In 60 minutes take an adjacency matrix as an input, good old int[][], and return all of the disjointed groups, and their group sizes in descending order.

I’m actually happy to say I haven’t necessarily had any bad programming related interviews. In fact, as someone with zero professional development experience but a healthy portfolio (side business for former employer, systems built for prior jobs not related to development) I’d say it was almost too easy to finally land a full time development job.