The backend of Wagtail is completely geared towards authors, and a lot easier to use in my opinion, and it's got a media library built in. Django-CMS extends the standard django admin backend, may require a third party plugin for a media library, and tends to encourage more frontend editing, so authors will more immediately be able to see how a page looks. It also tends to be more flexible and can do more (which may be a good thing or a bad thing, depending on your goals). If you need more control over permissioning, workflows, etc. then django-cms may be a better choice.
I personally love both of them, and would recommend either.
One point that put me in doubt in favor of Django CMS was the support for editing single page sections, you can do that in Mezzanine but it is not "native".
The thing that drew me to django CMS to start with still exists today, which is that django CMS recognizes that Django is a powerful application framework and the CMS embraces this. It also provides powerful front-end editing capabilities for you and your non-technical stakeholders, even for existing Django apps.
django CMS has addon applications for both jobs (Aldryn Jobs) and weblogs (Aldryn News & Blog).
If you're interested, you can join a free Guided Tour each week that will actually cover some how this all works in django CMS: https://www.divio.com/en/academy/aldryn-cloud-django-cms-gui...
For a fully-blown jobs site by the way you'd probably want to expand the Jobs application but it's open source software already so could be a good start.
Doesn't hurt that it looks awesome as well.