> everything you do directly impacts the product and customers, vs being a tiny cog in an insignificant wheel. This is why I actively sought smaller companies

> everything you do directly impacts the product and customers, vs being a tiny cog in an insignificant wheel. This is why I actively sought smaller companies when I was fresh out of uni. I knew I didn't want to be a tiny, insignificant cog in a giant machine, far removed from the users. At the place I'm at now I'm wearing many hats. I architect solutions along with customers. I implement them, and have a lot of freedom in how that's done, including tools. And there can be lots of interesting programming challenges in the details of this work, be it algorithmically, programming language-wise etc etc, which needs figuring out. If I have questions regarding some new feature I'm developing I can pick up my phone and call some of our customers to better understand their workflows and needs. Likewise I get very direct feedback, which I like. Most customers don't know what's possible and not, so if you design or implement a good solution it's not seldom you'll be perceived as a literal wizard. I guess I was somewhat lucky with the place I'm at. My team lead is easy going and doesn't micromanage. Our CEO said he learned quickly that the less he's in the way of us programmers the better, so he lets us do our thing unless there's something precarious. As you said, I could probably get paid better elsewhere. But I earn enough, and I enjoy what I'm doing so far. That said, it's not for everyone. You'll probably will need to be tolerant of less-than-great quality code, not mind juggling several things at once, and not mind talking to customers directly.