You should probably extend your post to include the sql-server- integration-services tag, since the SSIS people may know if SSIS has any support for this.
I don't know SSIS, so I can only answer from a general Agent perspective. Agent has no support for this itself. You would have to set up a job that monitors the SSIS job step and kills it if has been running to long. This job could be started from an initial job step of the SSIS job. That job would wait for ten minutes and then kill the other job. Alternatively, you could schedule a job that runs every ten minutes or so and checks for the other job.
And, no, I don't have the full details to do this, since I don't work with SSIS.
But as you can see it is a bit of a kludge, and I am not sure that it is a good idea in the first place. What would be the benefit to kill the job?