Jobmonster

A theme built around an approval queue

Most WordPress themes give you a homepage and leave the substance to plugins. Jobmonster's vendor feature list puts a workflow first: employers submit and edit jobs on the front end, and an administrator then reviews each one and approves or rejects it before it appears publicly.

That single line changes what you are buying. The theme is a small two-sided application — employer side, candidate side, admin gate — rather than a set of page templates. If your plan is to let anyone publish a listing instantly, you will be switching off a feature the vendor built deliberately. If you want a human check on job quality, the gate is already in the design.

The same review logic extends to applications: the vendor lists employers approving or rejecting applications with a message sent to the candidate.

What employers and candidates see after login

Working from the vendor's description, the employer dashboard is not a thin profile page. It covers company profile editing, job management, and viewing and responding to applications, with separate sections for jobs, applications, messages, shortlists and advanced filters.

The candidate dashboard mirrors that: resumes, applications, job alerts, bookmarks and follows. The vendor also lists three ways to apply — including uploading a CV or choosing from resumes already stored on the site — and private messaging between employer and candidate, which the description attributes to an integration with the Frontend PM plugin.

That plugin detail is worth noting before you plan. The description says the theme integrates with Frontend PM; it does not say the plugin ships inside the theme package. Treat messaging as something to confirm on a test install rather than assume.

Two kinds of posting plan, both billed through WooCommerce

Unusually for a theme in this category, the vendor splits monetisation across both sides of the market. There is a job posting pricing plan and, separately, a resume posting pricing plan. Both are described as running through WooCommerce, which means packages, package add-ons and checkout are handled by the store plugin rather than by a bespoke billing system inside the theme.

The vendor's wording is about capability, not presets: you set the number and structure of plans yourself. Nothing in the supplied material gives default prices, plan durations or how a purchased limit is counted against a listing. Those are configuration decisions you make in WooCommerce and the theme settings.

The practical consequence is that WooCommerce becomes part of your stack even if the board's main income is employer packages — which affects hosting, checkout testing and the payment gateways you enable.

Custom fields are how the board models a job

The vendor claims unlimited custom fields, with distinct field sets for jobs, resumes, candidates and the application form. The field types named in the description are broad: text, number, email, URL, textarea, select, multiple select, radio, checkbox, date picker, image upload, file upload and video.

That covers the fields a real listing tends to need — salary as a number, contract type as a select, a closing date as a date picker, a company logo as an image upload. Because the application form has its own field set, you can ask screening questions without pushing them into the job record.

The vendor also describes advanced search fields that you can change to your liking, with keywords, location and category among the named options. What the description does not spell out is how each custom field behaves in filtering — whether a checkbox field becomes a filter, for example. That is the first thing to test on a demo, because a board with rich fields but thin filtering still leaves candidates scrolling.

Search by distance, and the map decision behind it

The vendor lists support for Google Maps and free open source Bing Maps, framed around finding jobs within a radius of the visitor's current location. Two providers matter for a practical reason: a map-based search usually needs an API key, quota and billing arrangement, and having an open source alternative gives you a fallback if the Google setup is not viable for your budget or region.

The description does not say whether the provider is a site-wide switch or whether a key is required for the Bing option. Check that before committing to a location-led homepage concept, because the "Search Map Home" variation in the nine demo layouts depends on it.

WPBakery or Elementor, and nine starting layouts

Jobmonster is one of the less common themes that supports both major builders. The vendor states you can choose WPBakery Page Builder or Elementor to customise the homepage, and the marketplace compatibility list observed on 3 November 2026 names Elementor, Elementor Pro and WPBakery Page Builder.

The nine named home variations — Resume, Jobs Listing, Search Map, Candidate, Career, Recruitment, Job Categories, Hiring and Employer — are starting arrangements rather than different themes, and the vendor advertises a one-click demo importer. Layout work beyond the homepage also has choices: the company directory comes in alphabet and grid layouts, and the single company page has two layouts.

A reasonable read of the evidence: the builders control page composition, while the job board itself runs on the theme's own listing, dashboard and field systems. The vendor does not detail which builder, if either, is used to edit the board templates.

Declared compatibility and the security entries in the changelog

Marketplace attributes observed on 3 November 2026 list WordPress 6.6.x through 7.0.x, WooCommerce 9.x, 8.x and 7.x, Elementor and Elementor Pro, and WPBakery Page Builder, with the package file list naming PHP, CSS and JS files. These are declarations from the listing, not the result of installing or running the theme.

Gutenberg Optimized is marked "No". That describes where the vendor put its design effort; it is not evidence that the block editor is unavailable.

The changelog visible in the source is worth reading for a different reason. The 4.8.6 entry, dated 17 June 2026, records a fix for a reflected XSS vulnerability in the frontend login form and improved input sanitisation in member authentication forms; 4.8.4 addresses SQL injection with a companion component. A board that accepts front-end submissions and logins has a wide input surface, so running a current release matters more here than on a brochure site.

Questions & answers