The good engineer should not be doing bleeding-edge work so much as he should be doing things that are challenging even in small ways every now and then, and re

The good engineer should not be doing bleeding-edge work so much as he should be doing things that are challenging even in small ways every now and then, and rewarded for his efforts. I once worked at a small place that has a really, really brilliant architect on staff (easily the best engineer I have worked with so far). He turned down invitations to interview at some rather prestigious tech companies and was happy to remain in his little kingdom. Most of the time he was fixing bugs, adding smallish new features, etc. - i. e. he was not doing cutting-edge stuff. But he had the freedom to improve the code base as a whole. So every time he had to fix a major bug he would do some refactoring that made the code better, not just for him but for the entire team, as this always involved tweaking the APIs he wrote for the team. It is pretty challenging to improve upon something that is already pretty darn good.