> I would go even further and say for me it would be a big red flag to waste time on "business impact" - I am going in as a programmer. From my experience, my "

> I would go even further and say for me it would be a big red flag to waste time on "business impact" - I am going in as a programmer. From my experience, my "business impact" is somewhat close to a cleaner dude. And I don't want to take on additional (unclear) responsibilities I am not sure I know much about. Thank you, but I already know and do enough in my niche which happened to be software development and is a very specialised, demanding and valuable skill to have ) This is really going to depend on the company and industry. You're never going to get a senior or principal engineer role at FAANG without being able to explain, or better yet, quantify, what business impact you had through your work as a developer. In non-software verticals where developers are seen as a cost center it's different. But in general, those aren't going to pay as well. Plus you're never going to move up the career ladder if you see yourself exclusively as a developer and don't understand the wider business.