“Leetcode tests you for CSS knowledge” #softwaredeveloper

[PopulousTutorials]

then, once they get the job,
the job:
"make this square bigger"

[hjewkes]

“Your solution is perfect, but it didn’t use React or CSS. Clearly you lack the requisite skills”

[MunyuShizumi]

Nothing screams CSS experience like balancing a binary search tree.

[Bibbatron]

"Yeah so imma need you to create GPT 3.5 in the next 30 minutes."

[RavenGhostwisperer]

I am a full stack developer - I still would look this stuff up. If that’s the level of questions in the interview, the employer has no idea what they actually want

[bruhmoment-]

Thank you for your time, but I've decided to move forward with other positions.

[Zayfod]

"can you write your code on a whiteboard and show it as you go?"

Okay, but you'll need to courier me a whiteboard and pens first.

[HaxxBlaster]

"Just simulate the universe in CSS for me real quick"

[douglasauclair]

I actually got a similar question from an AWS 'senior' dev lead with 5 years of experience. He asked: "Traverse a binary tree's outer leaves clockwise after removing one internal branch." I asked him back: "What customer would need this? What is the use-case for that?" He was like: "Just do your job." I answered: "I am: my job is code useful, working systems, not to code useless stupid binary tree traversals." I didn't get the job, thank God.

[lukasjacobs]

I'm a back end guy and I'd walk straight out of that.

Nothing against a technical interview. I've seen many good ones: discussing architecture, how to properly scale a database, how to structure a REST API to be properly RESTful (and then giving the applicant a weird edge case to see how they handle it). All of that is absolutely fine. But stuff from an algorithms class in the second semester of uni? No thanks. I'll show you my degree, either believe me I earned that or not. But don't insult me with this kind of shit.

[SpiceCh]

"Thank you for solving this issue for us. We will have our existing developers implement your code and move forward with other idio- I mean, candidates. Thank you for working for free."

[codelyoko]

This is why I absolutely hate programming interviews. For someone with an awful memory, being expected to memorise random algorithms off by heart feels incredibly unfair and flawed. It tells you nothing about my skill level as an applicant

[rlrihards]

At this point its easier to make a company yourself and hire yourself than trying to find a job.

[umadbroyo]

You fail the tech interview, I get an email that starts with "Unfortunately..." as soon as I apply. We are not the same... 😎

[MasterFrechmen]

This is so real man. The dev interview test are insane hard. Couple months ago i had an junior frontend- interview, where they needed someone with react/vue skills, which i have both. They gave me test, where i should create and app for catching viruses and malware...like wtf 😂🤦‍♂️

[TheFolkes]

thank you, we needed someone to do that for us for free. the position as been filled, thanks

[Wrappedinhair]

-"Are you familiar with AI.?"
-"It's not my field of expertise, but I have a basic understanding of neural networks, yes"
-"Great, can you make us one that will do your job for you?"
-"Wait, now? During the interview?"
-"That'd be great, thanks (also sign this NDA, giving us full right over your intellectual property tysm) 😊😊

[ufffd]

i’m a web dev, every day i clock in and reinvent a common algorithm with pen and paper

[Stolpskott]

I got one of these types of questions on an interview, where I was interviewing for a role as a tech support team lead.
I asked about why they were including programming algorithm questions on a team leadership or tech support interview, and the interviewer just shrugged and said it was one of the questions she had been told to ask. She had no idea what it all meant, they were just words on a page to her.
To top it off, the question was physically impossible, because (putting it in the terms of this question), it was asking for re-ordering of a dynamically populated list in less than the number of steps it would take to traverse the list.

[firesickle]

The interview question that confounds me the most is "Use 3 words to describe yourself"... "A fucking programmer."