I agree with Scott and I have a question for you Ram too - how often do these jobs run?
This is relevant because if you run the jobs nightly (for example) to create new tables, populate them, then move the data out of those tables, drop the tables, and finally shrink the database, it is just going to grow again the next day. I would MUCH rather keep the disk space consumed by the instance so I know I have enough free space for the next run.
Now, if these jobs are run once per year, and the database is a read-only database, then I may shrink things, but like Scott, I only shrink the db files and not the whole database. I very rarely shrink a live system because it grew to that size at one point for a good reason, so it is likely to just grow all over again.
On my dev/test instances, I shrink files once I do the restore so I am not wasting disk. Dev/Test has a LOT fewer inserts so the autogrow can be set lower and I waste a lot less disk with that. But, like Scott said, I am shrinking the file not the database.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!