Jobify

The job board logic lives in a free plugin, not the theme

Astoundify's description is explicit that Jobify integrates "Mike Jolley's free WP Job Manager plugin" and calls it the first fully integrated theme of its kind. That sentence is the buying decision. The listings, the submission flow and the admin side of the board belong to a plugin that is free, publicly maintained and used by plenty of sites that do not run this theme. Jobify supplies the presentation: the homepage, the job cards, the search hero, the dashboard styling.

Read that arrangement as a division of ownership. Your job data stays portable and does not depend on Astoundify's release cycle to exist. In exchange, the theme's quality is measured by how well it follows a plugin it does not control, which is why the changelog is worth more scrutiny here than the demo screenshots.

The employer-to-candidate loop the vendor describes

The vendor lays out the flow in three steps: a company submits a listing with details about the position and the company; a candidate visits the site, searches an interactive map, filters the results and applies; and the site administrator can require a subscription or a one-off payment to create a listing. Live searching and filtering sit behind that middle step, along with custom shortcodes for register, login, jobs, job dashboard and job summary.

Only the first half of that loop ships for free. Resume uploads depend on the Resume Manager plugin, which the vendor marks as sold separately, so candidates can post or upload CVs only if you add it. Resume-submission pop-ups are described for the free NinjaForms plugin and for Gravity Forms, the latter also sold separately. Salary fields, company detail pages and the job dashboard are theme territory rather than plugin territory, which is where Jobify spends its own effort.

What Listing Payments can and cannot do

The monetisation story has a boundary the vendor states plainly: Listing Payments integration creates custom job packages that can be purchased or redeemed during job submission, and it "can only be used to sell job packages and not be set up as an entire store." The plugin is sold separately.

That rules out treating Jobify as a shop with a job section attached. You get one product type — the posting package, redeemable at submission — and nothing that resembles a cart catalogue of unrelated goods. If your revenue model is employer subscriptions or per-post fees, that is enough. If it involves selling courses, merchandise or memberships beside the board, plan on WooCommerce or another system handling that separately, outside the theme's described scope.

Map search, filtering and the mobile claim

Search is described in terms of an interactive map plus filters on the results, and the vendor frames the theme as mobile-friendly so that visitors can search jobs and submit listings from a phone. The changelog backs up parts of that over time: an option to remove Google Maps for GDPR compliance in version 4.1.2, self-hosted Google fonts added in 4.1.0, a browser geolocation popup fix in 4.0.9, and a mobile search-filter fix as far back as 3.19.1.

What is not documented in the supplied material is the filter taxonomy itself — which fields you can filter on, how the map results relate to the list, or whether map search needs an API key. Treat the demo as the place to test that, and note that the GDPR map-removal option implies the map is central enough to need an off switch in some jurisdictions.

The plugin bridge is what the vendor keeps patching

The changelog reads as a list of integration repairs rather than design work. WP Job Manager compatibility updates appear at 1.32.0, 1.33.2, 1.36.2, 1.38.0, 1.38.1 and 1.39.0. Version 4.1.8 added a WP Job Manager form field editor through the Extensify plugin. Company listing plugin conflicts, Gravity Forms conflicts, WooCommerce version bumps and translation fixes recur across years.

Recent releases shift the plumbing. Version 4.3.4, dated 21 July 2026, moves licence activation and automatic updates to the Astoundify Themes Updater plugin, removes the legacy ThemeForest updater and in-theme activation handshake, and states that existing activations migrate automatically. Version 4.3.3 logs a vulnerability fix alongside WordPress 7.0 compatibility.

This tells you the theme is actively kept in step with its dependencies. It does not tell you the current build is free of issues, and it says nothing about how quickly a future plugin release will be supported.

Composition: shortcodes, templates and the block editor question

Jobify's own page-building contribution is modest and concrete: page templates for home, testimonials and pricing, custom shortcodes for register, login, jobs, job dashboard and job summary, widget-ready areas, and full XML dummy content. Design changes run through the WordPress Customizer for logo, background and text colours. Elementor appears in the vendor's compatible-with list, and the changelog records fixes to Skin 1 and Skin 2 Elementor demos, so Elementor is a supported route rather than the theme's canvas.

The marketplace attribute "Gutenberg Optimized: No" describes whether the theme's design system was built around the block editor. It does not remove the block editor from your site, and nothing in the supplied evidence shows block-based page building being blocked. What it does suggest is that Jobify's layouts were designed around its own templates and widget areas, so a team that builds every page from block patterns will find less to reuse here.

Where this arrangement stops fitting

Jobify makes sense when the board itself is the product: employers pay to post, candidates search and apply, and the site's value is the listings rather than the marketing around them. The free core plugin keeps your data portable, and the theme's templates, shortcodes and search hero give that data a presentable front end without asking you to adopt a proprietary builder.

It fits less well when the extensions matter more than the theme. Recruiter-grade resume handling, paid packages and Gravity Forms resume modals all sit behind separate licences, and those purchases — not the theme price — determine whether the site does what you promised. Budget for them before you commit, and check the marketplace file list: PHP, CSS and JS files are what the theme package contains, not the plugins.

Questions & answers