It's best to learn to deal with processes. Some companies do have really bad ones, and if that happens you should leave, but all companies will have some level of process, and every job will have some amount of work you don't like doing.
Learning how to deal with this is a career skill. Remember that to your employer, you are not a coder, just as a firefighter is not a hose operator.
To your employer, you are someone who delivers, maintains, and supports software. That requires a lot of non-coding work, and as you advance in your career the time demand for the non-coding parts of the job will increase.
If you know how to deal with processes -- how to streamline them, avoid them, delegate them, and use them to your advantage -- you can build the kind of role you want. So, the good job for a person like you is a job where you understand how to work the processes in your organization.
Learning how to deal with this is a career skill. Remember that to your employer, you are not a coder, just as a firefighter is not a hose operator.
To your employer, you are someone who delivers, maintains, and supports software. That requires a lot of non-coding work, and as you advance in your career the time demand for the non-coding parts of the job will increase.
If you know how to deal with processes -- how to streamline them, avoid them, delegate them, and use them to your advantage -- you can build the kind of role you want. So, the good job for a person like you is a job where you understand how to work the processes in your organization.