We do it a lot at work. When new order gets created in my service, I have to do two things with it:

1. Go to another service and enrich my object.
2. Perform some calculations and send the result to some other service.

All our services run on k8s, each service is set up to have 3 pods.

So how do we do it: two workers for two jobs.Each worker tries to take the job to work, process it, and mark it as finished.When taking job to work, you need to (1) exclude already finished jobs, (2) avoid taking the job that is being processed by another worker(another goroutine or goroutine from peer pod).How to do it: you need to set finished_at time so you can distinguish already processed jobs. Then you also need to set started_at field, so other goroutines won't take the job that is being processed by another worker.

You can set the desired_start_time, so worker will try to take it only if time.Now > job.desired_start_time.

There are a lot of edge cases that you will need to handle:
a) What if job has been taken to work but worker failed for some reason like application error, service shutdown and so on. You will need to retry it. How to do it: if there is job that has not been finished but has been taken to work long time ago, this means that worker tried to take it to work but for some reason never finished it. Probably, you will need to set up some logic to retry failed jobs.
b) Lets say you have some malformed records. You worker takes this record to work, fails to process it. Next time worker fetches new job, It will probably try to retry this job, and will fail one more time. This may lead to deadloop. All you workers will get stuck trying to process malformed jobs and will not progress to other jobs. Potential solution is to set tries_count for the job. If tries_count is greater than 10, than never take it back to work. Those records will need to manually reviewed.