I love situations where the employer wants you to have 3 years of experience with an API that exists for less than a year.

As a CS student I get very frustrated over the fact that all my coding exams are done on paper. Yes a paper where you write the code down with a pen :)

A friend of mine is a recruiter in the tech industry. She told me that she regularly works with seasoned FAANG engineers who can't get jobs at different companies because they can't pass the whiteboarding interviews. If someone is good enough to keep his job at Google for many years, denying him a job because he can't rebalance a red black tree from memory is utterly ridiculous.

"forcing developers to interview while using a light themed editor" -- no job is worth that

"I want to develop front end apps!" - "Oh yeah? Well prove that P = NP first, then we can talk".

yo wait are you the guy from tiktok

As someone who is a software engineer for 15 years. I hardsmashed this like button

yes a week is necessary for centering a div please tell my boss

Support Engineer here. I interviewed someone once and I just asked them how to do an upgrade of our product. They googled it and paraphrased the doc they found. I was like "congrats you just solved a support case". We hired that person.

immediately liked after the "center the div" joke

interview: sort binary tree

Manager: "How'd you get the job?! Your code is terrible."

4:12

As a developer with ~20 years experience, I walked out of my last interview after the interviewer asked me to sort an array of strings...

Company product: CRM/ERP...

Me on my 2nd sem 1st year degree:

A pet peeve of mine, which I think companies should test for in tech interviews: Reading and reviewing code. As a programmer you spend 90% of your time looking through existing code. Getting a bugfixing task covers this to an extent. If I was in charge of hiring, I would have a task, where the applicant gets a code sample, maybe even a real pull request, and then explains their thought process as they walk through the code as they try and understand what it is doing. This opens the floor for meaningful discussions on possible improvements regarding naming, refactoring/architecture, documentation, and tests. Including an actual bug for them to find might make sense. And then at the end you could ask them to extend the code with a small function. The required logic doesn't have to be complicated.

A friend had a interview recently and I was so happy to hear that they only asked him about recent projects and his previous job experience. Hired on the spot with no whiteboard session.

Absolutely bang on. I was a developer for 25 years before choosing a career change for exactly this reason. I found increasingly, every time I went to a new job, I was being asked increasingly stupid questions. What was worse was I realised that even when I answered, the interviewers didn't understand the answer. I actually burst out laughing at one interview, my 3rd interview that week, and asked if they'd found the interview questions on line because I'd already been asked the exact same questions elsewhere. I've left that world behind now, and I'm glad.

On the internship application