Privileges Required to use Jobs 
To use jobs, you need either:
scheduler-administrator role
scheduler-job-administrator role
object, system, partition or isolation goup-level permissions
Submitting or Restarting Jobs
To successfully submit a jobs, you have to have one of the following privileges:
Submit - privilege rank on the jobs, or on jobs in its partition, isolation group or system-wide
All - privilege rank on the jobs, or on jobs in its partition, isolation group or system-wide
As well as the following privileges
Submit Onto - privilege rank on the queue where the job is supposed to run , or on queue where the job is supposed to run s in its partition, isolation group or system-wide
View - privilege rank on the process server that serves the queue and where the job is going to run, or on process server that serves the queue and where the job is going to runs in its partition, isolation group or system-wide
Optionally, if you want to use a library, submit frame and/or time window, you will need View privileges on them, as well. If the jobs has a default submit frame, a default time window, or uses a library (in parameters or in the code) you will require View privielges on the objects or you will not be able to submit the jobs or restart the job.
Jobs can reference the following objects, you need at least View privileges on these objects when you want to submit a jobs that references them:
Credentials
Events
Library - if the job uses code from the library.
Locks