Sometimes it's hard to go well in job interview because not always the HR person knows about programming enough to let you show off a little bit with some interesting questions and then you end the interview at if you didn't leave a good impression.

And if they do know something it's that little part where you know only a little bit about and you still feel bad.

On the other hand, explaining complex shit in simple words is a job skill.

I've heard the advice to completely overwhelm HR with your expertise. They can't risk rejecting an expert so confuse the heck out of them with BigO and data structures and new technologies and whatnot.
Again, the hiring manager can call your bs but HR can't risk rejecting an expert at the expense of their own job.

@benj That's actually a good strategy, I will do that in the future.

@Fast-Nop Generally they don't know even the minimum to start the conversation like "Do you use X in here?", you know, just to show interest in the company and mention X before they mention, but they say they don't know and you cannot put pressure too much as well. :/

@Fast-Nop Generally they don't know even the minimum to start the conversation like "Do you use X in here?", you know, just to show interest in the company and mention X before they mention, but they say they don't know and you cannot put pressure too much as well. :/

@leoat12 well yeah, but then ask them about processes and shit.

HR isn't responsible for the hardcore tech stuff anyway - what they are supposed to smell is candidates who are a bad fit. Overwhelming people with tech who aren't experts probably counts. After all, how will someone like that ever be able to interface with project management or customers?

On the other hand, a job interview without tech folks from the company is also strange.