>> P.S.: The non-tech part is not that hard. Just don't be a dick.
This is probably true for junior roles but gets much more important for senior roles or ones where they are testing out your potential to take on greater responsibility shortly after joining.
An answer to a vague behavioral question can make a ton of difference. EG:
Question: Have you ever managed people?
Answer A: Nope, always an individual contributor.
Answer B: No, but at my last job I took ownership of a project that involved coordinating work of 50+ developers, UX people, QA, etc to deliver.
Question A is technically correct and "not a dick" but if the person has it in them to figure out to provide answer B (assuming it's true) they are more likely to get a more senior job and make more money.
This is probably true for junior roles but gets much more important for senior roles or ones where they are testing out your potential to take on greater responsibility shortly after joining.
An answer to a vague behavioral question can make a ton of difference. EG:
Question: Have you ever managed people?
Answer A: Nope, always an individual contributor.
Answer B: No, but at my last job I took ownership of a project that involved coordinating work of 50+ developers, UX people, QA, etc to deliver.
Question A is technically correct and "not a dick" but if the person has it in them to figure out to provide answer B (assuming it's true) they are more likely to get a more senior job and make more money.