Could be interesting, you need to give him SQLAgentoperatorRole to allow him to execute any sql jobs on that server, are you also aware that if you give him that role, he will able to also do the following.

Create/modify/delete his own jobs

enable/disable any jobs

view properties on any job

edit any jobs that he owns/creates

start and stop any job

view job history for all jobs

delete job history for all jobs

It is the most priviledged out of all the job roles and implies a lot of trust, you can in theory do it by granting access to certain stored procedures to allow starting the jobs, but that is not that easy and can be a pain to troubleshoot to get exactly right.