It really depends on how big the job is. Think of a project as a “container” for multiple tasks. If in order to execute the “job” you need to have multiple tasks to complete it, create a project that houses all the tasks that make up that job.
If the job has a short lifespan and doesn’t require a lot of components to complete it, then it’s better off as a task. Try it out and if tracking all the work becomes overwhelming in one task, you’ll know it’s time to create a project and break the work down into multiple tasks.