[_ivi7]

I totally understand regarding the security clearance.

I updated my comment in terms of framing it as an ultimatum - that's not what I would say in the interview process.

Showing examples of fake code seems like a possibly great middle-ground here. As long as that code is an accurate reflection.

[CodeSgt]

I have a hard time imagining that if their code base is awful, they'll present you with awful fake code that accurately represents that.

[drudoo]

Thanks for the clarification. Ultimately I think a developer (and other employees) should be able to work with any task and (in this case) the status of the code shouldn’t determine if you want the job or not.

Personally I value other factors such as work/life-balance, coworkers, work-benefits and salary higher than the individual task I’m completing on a day to day basis.

[icedchai]

Just because you "should be able to" doesn't mean you'll want to. If the job is going to be unpleasant because the code base is steaming dumpster pile of garbage, that would be nice to know. Maybe you'll appreciate that kind of challenge, maybe not.

[_ivi7]

These are good points... I certainly value these factors as well.

And agree with you, to a point, that an engineer "should" be able to work with any task or codebase. We aren't primary care doctors in a community clinic who are obligated to treat every person who comes through the door.

I know myself pretty well. I know the kinds of environments in which I am most productive. I know the kinds of environments that I find to be a tedious and mentally exhausting slog. I prefer to avoid those. Some codebases are just awful to touch. I think it's OK to have some boundaries around that.