Brethren, this is I. In a $bigcorp this is a problem because a lot of people don't want problems solved. Instead of being glad a problem is solves they will ge

Brethren, this is I. In a $bigcorp this is a problem because a lot of people don't want problems solved. Instead of being glad a problem is solves they will get pissed you stepped on their toes. Something that takes maybe 30min for me to do, some person/team expects me to wait weeks, months or years for them to do it. Problem is, I am not in IT-proper,devops or SWE. I work in security so "problems" are stuff that can land us on a news headline so I do piss people off and fix stuff. Interviews are also hard. They try to put me in some bucket and it is difficult. If I mention something I had to do to get something done, suddenly they think that's all I should do. I am on my second job right now(in a row) where they had to create a new job title for me. But in the last few years, the infosec world has adapted a bit and now there are titles for people like me. "The guy that gets a lot of access and does whatever to catch/stop/respond to intruders". It is also the hardest for people of this personality to appear to be teamworkers. If I collaborate with someone (let's say an incident response task) and I am done with my tasks and they're taking their time, I have to take over their task and finish it. In a bigcorp this is a problem because everyone wants credits and visibility. So for the actual team members I look good but for managers not so much. They see me as a liability unless I am careful and solve problems quietly and let others take credit when possible. But the person whose task I took over or mistake I fixed gets angry, doesn't matter how nicely I do things. This was so not a problem in a startup culture (unless you create work for others). Edit/Unrelated: my account is restricted because apparently I post "low value" content (still not sure if that is a code word or what it means), can you tell if and why the above comment is "low value"?