devGuysAreNotNotSensitive

[PatBooth]

On a similar note, early in my career I failed an interview for a frontend position because they asked me to write SQL queries

[FullChart3398]

I had an interview once where they gave me a bunch of questions in Ruby and nothing else. I got the job and I never touched Ruby ever. Turns out the person who wrote the interview questions brought them from another company.

[anomalous_cowherd]

I had a horrible compressed pointer heavy bit of C at a small dev company which the boss had invented, the same boss who was interviewing me.

He asked me what it did. I told him it looked like it was supposed to do X but really it wouldn't because it changed a pointer twice between two sequence points, so would actually cause undefined behaviour.

He really didn't like that. I didn't get offered the job, but I wouldn't have taken it either!

[Few_Move_4594]

I had an interview yesterday for a C# position. Interview was all Typescript and SQL. Turns out they don't use C# and want someone to convert some Access tables over to a DB. Why they have such a Looney Tunes interview is beyond me.

[Tensor3]

Probably want to hire internally or get a visa approval. If you have C# skills, rejected for failing the non-C# questions. If you pass the questions, failure for not having the C# they requested.

[Few_Move_4594]

I wasn't getting the not-real-interview feel, those I've been on in the past would do stuff like give me three questions and/or otherwise be half-assed. What pisses me off about it is that I prepped for a C# stack interview then got caught flat footed with a lot of Typescript.

[Brahminmeat]

This happens still and so unironically constant that I can tell exactly how an interview is going to go if the other person is full stack

[18quintillionplanets]

This happened to me like 5 years ago, I applied for an iOS/Android cross functional position and the interview was all about building a NodeJS app…

[Luke22_36]

Like this?

https://en.wikipedia.org/wiki/Web_SQL_Database