4 ms·

I am not sure it's true. You are hired for your skills so tomorrow you are another developer who can solve the tasks he is given in this specific tech environme

I am not sure it's true. You are hired for your skills so tomorrow you are another developer who can solve the tasks he is given in this specific tech environment. >> You need to deliver solutions, you need to show the business the impact of those solutions Most of the time people who interview (and eventually say yes/no) are tech people, discussing business problems and solutions is cute yet pretty useless. It's funny when you interview someone and he wants to look enthusiastic and tells you the information they found from the open source - and you go like "dude, you have no clue what's happening in these walls" ) 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 )

mjr00 5y ago
> 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.
- democracy 5y ago
  Even in FAANG, do the devs really know the business impact or they just use the business vocabulary to BS around? I mean I can also bullshit anyone about the business impact, I just don't believe that many people (even non-tech) do really know the real business impact. I know for a fact they don't )
myrandomcomment 5y ago
It has been my experience and my expectation that Sr. roles in engineering have a grasp of the business and the impact of what they deliver has on it. Jumping roles at a certain level at the likes of a FAANG 100% require that you have created / managed / delivered a project that had business impact.

mjr00 5y ago

> 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.

democracy 5y ago
Even in FAANG, do the devs really know the business impact or they just use the business vocabulary to BS around? I mean I can also bullshit anyone about the business impact, I just don't believe that many people (even non-tech) do really know the real business impact. I know for a fact they don't )

myrandomcomment 5y ago

It has been my experience and my expectation that Sr. roles in engineering have a grasp of the business and the impact of what they deliver has on it. Jumping roles at a certain level at the likes of a FAANG 100% require that you have created / managed / delivered a project that had business impact.