[june_twenty]

I am inherently passionate about the things I do. That doesn't mean doing over time. It means that when we're in a planning meeting I am contributing and trying to get the best outcome. When I write code, I clarify requirements and I write the code to a high standard following recommended practices. I do static analysis on the code and fix it. I test it before it goes to QA.

Not for a promotion but because that is why I am there. Anything less would be mind numbingly boring.

[johnea]

I've always felt that this word is missused in modern HR.

To me, passion at work might be something like making out in the broom closet with a (willing) coworker 8-)

Passion is an inherently emotinal state, not always the best basis for clearly thought out action.

The idea that this is all a management ploy to get more work for the same money is already well represented here, so I won't dive into that, but that is also a significant part of why I don't like this concept in HR recruiting.

[thunky]

> I am contributing and trying to get the best outcome

So doing the job you were hired for is being passionate?

[june_twenty]

Based on planning sessions I've been in - yes. There's lots that will just passively sit there until called upon.