[MarkCole]

Sometimes in an interview its better to just say "This is not the right job for me" and end it yourself. I've done that a few times now for various reasons. Sometimes simply just because I know I probably wouldn't like to have the interviewer as a Colleague or Boss.

If I thought I was interviewing for a Django/Python job and they completely changed the job description on me I'd have probably cut it right there. You can't just completely change the job someone is interviewing for from under them.

I definitely feel you on it though, I'd much rather earn less in a comfortable job where I'm happy than go through the stress of interviewing and having to refresh my knowledge of CS trivia so interviewers can throw a few at me.

[akerro]

>they completely changed the job description

>the stress of interviewing and having to refresh my knowledge of CS trivia

I was recently visiting a friend from uni, he wanted to start working in a bigger company, so he took his chances on Amazon (they had office 10min walk from where he lived). He applied for Java/C++ backend role with some indication that's related to robotics.

First week interviewer told him to refresh knowledge from basics of machine learning, searching algorithms and path finding, so he spent all weekend reading wikipedia and our notes from uni. During the interview he was asked questions about his experience with JS, Angular and CSS. What interesting JS projects he did and why links to the projects are not in his CV.

He graduated with second best grade at the uni with a major project from autonomous sailing robot and failed interview in Amazon because he didn't do anything hipsterish with Angular on Github. I showed him link to the FACE of Amazon to cheer him up... and it worked, he decided not to apply there any more. What a waste of time.

[Beltiras]

For the interested, this is the page referred to: https://sites.google.com/site/thefaceofamazon/

[beilabs]

Interviewed for a large tech company a few months ago just for the sake of it. (VP of engineering role), corporate headhunter persuaded me to take the call even though I'm happy where I am.

5 minutes into the job interview the guy seemed very obsessed with my direct reports number. I have 12 engineers currently (CTO), have worked in China with 30 engineers reporting to me and in my previous life as a school principal I had 40+ staff and a few hundred students. With many other software roles in between around the planet.

Anyhow, it seemed that the position was not a good fit, they were recently acquired, the founders had all left and a new management team had taken over. Multiple interviews were expected as well as attending their office on-site on the other side of the planet. Ended the call once I heard this and told them this was not the right role for me. Have to be respectful but not every position is a good fit for the candidate. Trust your gut especially if red flags are raised. The guy conducting the interview seemed a bit shocked that i bailed on the process so quickly. Ain't no-one got time for the commitment some interviews require some days.

[LandR]

I interviewed for one position where it was C# and SQL.

Come interview technical test, they start asking JS questions. I asked if their would be JS in the role, as it wasn't specified anywhere, I've never done JS, don't want to do JS.

They sorta dodged the question a bit and continued to ask me JS questions. Which was pointless as I had no clue.

The whole interview they both sat their looking incredibly smug adn the whole interview had a definite sense of hostility and them trying to prove they were smarter than me.

I let the recruiter know straight after that I had no intention of going back for a second interview.

[expertentipp]

> "This is not the right job for me" and end it yourself. I've done that a few times now for various reasons.

I think this is the only weapon the interviewed person has. Not applying is not a solution as it will lead to even more disconnection. Apply, talk with people, disconnect when the bullshit level is too high.

Looking for years of experience in your exact Angular/React stack? Cheerio.

[zelos]

> Looking for years of experience in your exact Angular/React stack? Cheerio.

Yes, I don't understand that kind of thing either. Getting up to speed on something like React takes, what, a week or two? Frameworks are the easy bit of development.

[gaius]

I think a lot of it is HR departments and maybe even management themselves gold-plating the requirements in an effort to feel like they are contributing to the process, and possibly even justifying their own positions by "adding value".