> Long story short, screwed up a step I had done before in the fall without realizing. Then when it was fixed I submitted a ticket for a prod systems account rather than a QA one not realizing there would be a difference. (Just so many mistakes all in a row).
If your boss won't allocate time to automate and improve those little tasks, there's not much you can do. People are more prone to making mistakes than well-tested pipelines.
> The problem is at this point I have been on the team too long to ask any basic questions, one of the senior engineers even pointed out they shouldn't be helping me with certain processes at this point.
The bulk of a junior SWE's time should be spent on getting better at translating business requirements into code. Exposing you to some processes will set you to fail.
> I got my first swe job this past August
My advice is that you start interviewing for other positions once you approach 1 YOE, which is pretty close. Your post describes some typical issues small companies have when they try to scale. Hint: it often doesn't end well.
If your boss won't allocate time to automate and improve those little tasks, there's not much you can do. People are more prone to making mistakes than well-tested pipelines.
> The problem is at this point I have been on the team too long to ask any basic questions, one of the senior engineers even pointed out they shouldn't be helping me with certain processes at this point.
The bulk of a junior SWE's time should be spent on getting better at translating business requirements into code. Exposing you to some processes will set you to fail.
> I got my first swe job this past August
My advice is that you start interviewing for other positions once you approach 1 YOE, which is pretty close. Your post describes some typical issues small companies have when they try to scale. Hint: it often doesn't end well.