✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for WP Job Manager Applications

SleekView reads the applications stored by WP Job Manager Applications, groups candidates by the application status you pick, and writes the new status back to the application post so your recruiting pipeline lives on a board rather than a long list of post entries.

♾️ Lifetime License available

SleekView Kanban board for WP Job Manager Applications

Hiring pipelines built on WP Job Manager applications

WP Job Manager Applications stores every applicant as a job_application post under the job listing they applied to. Each application carries a status, which is whatever set of states you configured for your hiring process. The default admin gives you a long list of applications across all jobs, filterable by job and status, which is fine for searching but useless for actually running a recruiting pipeline meeting.

SleekView Kanban turns the same applications into a board. The grouping is the application status, the columns are the stages you already use, and the cards are the individual applicants. Card fronts show candidate name, the linked job listing, the source, the date applied, and any custom field you added through the application form builder. Recruiters get a board view of who is in screening, who is in interview, and who needs an offer.

Drop a card from Screening to Interview and SleekView updates the application post status. WP Job Manager Applications sees the change exactly as it would from the post editor, so any email triggers and integrations tied to status changes still run. Cards inherit the job listing context so a hiring manager who filters to one job sees only their pipeline, while a recruiter sees the full board across jobs.

Workflow

From application posts to a hiring kanban

1

Connect to the applications post type

Point SleekView at the job_application post type. SleekView reads each application along with its post meta, the associated job listing relationship, and any custom application form fields you collect through the plugin form builder.
2

Pick the application status to group by

Choose the status field as your grouping. SleekView reads the configured status values and builds one column per stage. If you use a multi step pipeline like screening, phone screen, interview, offer, hired, each becomes its own column on the board.
3

Choose what shows on each card

Pick the fields displayed on each card. Most teams use candidate name, the job they applied to, the date applied, and a custom field like years of experience or current location. Recruiter notes can show as a meta line so the next action is visible at a glance.
4

Enable drag-and-drop with writeback

Turn on writeback and dragging an applicant updates the application post status. Hooks fire as normal so email notifications to candidates, alerts to hiring managers, and any external integration on status change still trigger the way they always did.

Sample board

Sample hiring board for one open role

Applicants for a senior product designer role grouped by stage with candidate name and date applied on each card so the recruiter can run a Monday stand-up.
Screening
42
Maya Chen, senior product designer
Applied Mar 02, 9 yrs exp
Brett Olsen, senior product designer
Applied Mar 03, referral
Helene Roux, senior product designer
Applied Mar 03, portfolio strong
Interview
14
Karim Patel, senior product designer
Phone screen Mar 05
Sofia Ruiz, senior product designer
Onsite Mar 08, fit strong
Wei Lin, senior product designer
Onsite Mar 09, panel ready
Offer
3
Roman Voss, senior product designer
Offer Mar 11, awaiting reply
Avery Park, senior product designer
Offer Mar 12, negotiating
Mira Bose, senior product designer
Offer Mar 13, verbal accept
Hired
2
Dario Kim, senior product designer
Start Apr 01, contract signed
Lena Frost, senior product designer
Start Apr 15, onboarding set
Yusuf Aydin, senior product designer
Start May 01, paperwork done

Comparison

Default applications list vs SleekView Kanban

Default applications list

  • Flat post list of applications, every record looks the same regardless of stage
  • Changing a candidate stage means opening the application post and saving the form
  • No card view, no portfolio link or experience field surfaced without clicking through
  • Filtering by job is OK, but a multi role pipeline review still feels like reading a CSV
  • Hiring manager visibility requires custom roles and complex shortcodes to scope

SleekView Kanban

  • Reads job_application posts with their associated job listing and meta
  • Drag updates the application status the same way the post editor would
  • Card fields include candidate, job, applied date, and any application form field
  • Filter by job listing, stage, source, or any custom application field
  • Per role boards or a multi role overview, both built from the same data

Features

What SleekView Kanban gives you for WP Job Manager Applications

Pipeline per role

Pin one board per open job and recruiters get a dedicated view of that role's funnel. Each board only shows applications for one job listing, so the columns and counts always reflect what is happening for that specific position right now.

Hiring manager scoped views

Hiring managers who only have access to their own roles get a filtered board with just those jobs. SleekView respects the same capability checks WP Job Manager uses, so private candidate data stays private and drag-and-drop access scopes correctly.

Time to fill visible

Card meta can show the date applied so recruiters spot candidates who have been sitting in Screening for too long. Sort the column by applied date and stale applications surface at the top instead of getting buried under fresh ones.

Audience

How recruiting teams use the kanban view

Recruiting stand-up

Run a daily stand-up on the board. Drag candidates forward as decisions get made, leave notes in custom fields, and assign the next interview slot inline. The list view is gone and the funnel is finally the interface.

Hiring manager review

Share a per role board with the hiring manager who owns the position. They drag candidates forward as they review applications and you do not have to chase email replies for every status change.

Source tracking

Color cards by source field, so you can see if most of your Interview column came from referrals or from a job board. Sourcing reports stop being a quarterly export and become a glanceable property of the live board.

The bigger picture

Why a kanban view changes recruiting on WordPress

Recruiting is fundamentally a pipeline. Every candidate is in a stage, every stage has a count, and every position has a target rate. The default WP Job Manager Applications screen treats applications like blog posts, which is technically accurate to how they are stored but emotionally wrong for how recruiters actually work.

A board exposes the pipeline as the first class object. The columns are the stages and the cards are the candidates. Card meta surfaces the things you actually want to know before you click, like the role, the applied date, and the most relevant custom field.

Drag-and-drop turns stage changes from a four click round trip through the post editor into a one second movement. None of this changes how WP Job Manager Applications stores data, because SleekView writes status changes back through the same hooks the post editor uses. It just changes how a human sees and operates the pipeline.

For sites that hire frequently or for recruiting agencies running multiple roles in parallel, that difference is the difference between a recruiting tool and a long list.

Questions

Common questions about SleekView Kanban for WP Job Manager Applications

Both. WP Job Manager Applications stores its data as the same job_application post type regardless of edition. SleekView reads the post type directly and picks up whatever status values you have configured. Paid features like extra fields and notes show up on the card front the moment you map them.

 

Yes. Dragging a card writes the status update through the same WordPress hooks the application admin uses. Any candidate notification email triggered on status change, including ones sent by complementary plugins, will still send because the underlying hook still fires.

 

Add the new status value to your application status configuration the way you usually would, then refresh the board. SleekView picks up the new column automatically because columns are built from the distinct status values present on the data and the configured taxonomy.

 

Yes. Scope a board to the jobs owned by the current user using the job listing relationship as a filter. Hiring managers see only their roles and can only drag those cards. SleekView respects capability checks so admin only fields stay hidden where they should be.

 

Yes. Resume and cover letter attachments show as quick links on the card front when you map them. Application form custom fields appear as card meta. Anything stored on the application post or as related media is fair game for the card layout.

 

It triggers whatever hooks listen on the application status change. If you have integrations that already send to Slack, Zapier, or a BambooHR API on status change, those keep working because the kanban writes through the same hook path. Nothing in SleekView blocks downstream automations.

 

Yes. Group by the source field instead of the status field. SleekView builds one column per distinct source value. Card meta can keep the stage in view so a sourcing leader sees both at once, which is useful for weekly source quality reviews.

 

Yes. Pagination is per column, so even a Screening column with thousands of candidates only loads the visible window at any one time. Search and filter are pushed to the database to keep performance even, regardless of total application volume.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView