Fundamentally, work for their problems, not yours, to solve your problem. Log patterns and avoid premature automation, but write down the time you and others t

Fundamentally, work for their problems, not yours, to solve your problem. Log patterns and avoid premature automation, but write down the time you and others take to fix issues and then you can say that technical debt because of blank cost the company X days this last Y period. Also work on projects that showcase you can get shit done to build up credibility. Everyone who comes in as a junior engineer with different ideas will come across as the hot shot who thinks he knows better. Reach out to the developers and ask them what are areas where automation would make their job easier. Reach out to management and ask them what they want more control over, or want done quicker through automation. Look for other costs, server costs, service costs, etc. Your frustration likely matters to nobody but yourself though. Find their frustrations and fix both simultaneously.