> Maybe that's not a job I want, if the hiring manager is lazy enough to 'require' side projects to consider a candidate.
I understand that you might not want a job there and that part of a job interview is deciding if the company is a fit for you. But I wouldn't call a hiring manager lazy because they want to see examples of your work, in fact that's their job. How is a hiring manager suppose to make a thorough evaluation of a candidate if they don't show their work?
So ask candidates questions. You really expect candidates to have work relevant to your interview to show? But you can ask how they deal with problems, cultural preferences, etc.
> So ask candidates questions. You really expect candidates to have work relevant to your interview to show? But you can ask how they deal with problems, cultural preferences, etc.
First of all thanks for being so disingenuous with your responses. But a programmer is actually creating things ie, code and programs which can be shown. A manager is talking to people, going to meetings, emailing people, ie not much work to show, because their work boils down to talking to people. So basically different jobs have different job interview processes, you wouldn't hire a designer or architect without seeing their previous work.
I understand that you might not want a job there and that part of a job interview is deciding if the company is a fit for you. But I wouldn't call a hiring manager lazy because they want to see examples of your work, in fact that's their job. How is a hiring manager suppose to make a thorough evaluation of a candidate if they don't show their work?