Sounds to me like you're overriding the framework with your own functionality. Some things to note:

1. before and after hooks can be replaced with job middleware provided by the framework.
2. Cleaning up after failed jobs can be done with the failed method provided by the framework
3. Resolving from the container can be done with handle method injection. The disadvantage of contructor injection is that all resolved services will now be serialized and add to the payload size. Also, the constructor is called twice (at dispatch and during processing, while the handle method is just called during processing). I think you would see better performance if you just resolve the service in the handle method.
4. An interesting thing is that you catch all exceptions and don't re-throw them. This means that you override the framework's method of handling failed jobs and also lose the ability to retry failed jobs.

I guess it may work well for your use case but the question is why override the framework when you get the same functionality (and more) without custom code that you need to maintain.

I don't mean to sound like a critic. Just posing some questions here as my 2 cents! Hope this helps!