SQL Database Design for Job Schedule Dependency

I am tasked with migrating a legacy application which schedules jobs based off a specific sequence and hierarchy. I am trying to come up with a multi- table design to make it scalable and easily updateable. Not sure where to start. This is how the job schedule hierarchy looks right now.

Job1 is the parent job which has o run first after which the level 2 jobs have to be picked up based off their priority(Pls note that the multiple jobs might have same priority.) The next level of jobs cannot start until its parent job has complete running( for e.g. Jobs 3, 4, 5 cannot run until Job 2 has been completed)

So the order in which this should run is, 1, 7,6,2, 3, 5, 4 Can we fit this into a database design.