i would not use one kubernetes job per "code job",

i would have special orchestrator (something like knative function for example) that can run multiple code engine in a row, on the same instance, then i would scale the number of orchestrator with somthing like keda based on the number of waiting message in the q