Couple of options come to mind.
- Create a master batch/PS script that runs the first job and then the second job. This gives you the most flexibility in that you can control when, if ever, the second job should run. This is probably how I'd do it.
- Add both jobs to the same task as separate actions. The scheduler runs the actions sequentially and this has been a recommended approach for a while. But some caveats here as I've never actually done it this way. Firstly, the second action doesn't run until the first action completes, based upon observations, but this isn't documented anywhere. Secondly, the second action is going to run irrelevant of the first action's results. If you need to run the second job only if the first completes then you'll have to implement some sort of solution that allows for this detection.