SleekView for WP Job Openings: applicants as tables
WP Job Openings stores jobs and applicants as custom post types with rating, stage, and resume fields. SleekView turns those records into a hiring grid you can sort, filter, and edit inline as candidates move.
♾️ Lifetime License available
Hiring pipeline as a real table
WP Job Openings registers two custom post types: awsm_job_openings for roles and awsm_job_application for applicants. Each application carries postmeta for rating, stage, source, and form-builder answers. The default applicant list shows fixed columns, hides screening questions behind tabs, and forces hiring teams to drill into a job before they can compare candidates. That breaks the moment a single role gets twenty applications.
SleekView reads the same custom post types and renders one cross-job grid. Stage, rating, source, and any custom screening field become sortable columns or filters. Interviewers see only the rows assigned to them, hiring managers see the full pipeline, and HR can pivot on time-in-stage without exporting anything.
Inline edits go through the plugin's normal hooks, so notification emails to candidates and admins still fire when you advance someone from Screen to Interview. Bulk reject, advance, or tag turns a forty-applicant queue into a fifteen-minute review session.
Workflow
From applications to a real hiring grid
Pick the post type
Add screening columns
Save interviewer views
Bulk advance or reject
Sample columns
A typical WP Job Openings applicants view
WordPress posts/postmeta
| Applicant | Job | Submitted | Rating | Stage | Status |
|---|---|---|---|---|---|
| Sasha Bell | Backend Engineer | 2026-04-18 | 4.5 | Interview | Shortlisted |
| Wei Liu | Backend Engineer | 2026-04-19 | 3.0 | Screen | In Review |
| Aaron Klein | Marketing Lead | 2026-04-20 | 5.0 | Offer | Shortlisted |
| Pia Nilsen | Backend Engineer | 2026-04-12 | 2.0 | Rejected | Closed |
Comparison
Default WP Job Openings admin vs SleekView
Default WP Job Openings admin
- Applicant list shows limited columns
- No global view across all jobs
- Cannot edit rating or stage without opening the record
- Filtering by stage requires drilling into each job
- Custom screening questions are hidden behind tabs
SleekView
- Cross-job applicant grid with stage, rating, and source columns
- Inline rating and stage edits
- Save views like Top rated or Final round
- Surface custom screening fields as filters
- Bulk reject, advance, or tag applicants
Features
What SleekView gives you for WP Job Openings
Hiring at a glance
See every applicant across every role with rating, stage, and source in one grid. Calibrate candidates against each other instead of role by role.
Filter by stage
Slice the table by stage so each interviewer sees only their queue. Save Screen, Interview, and Offer views per round and share by role.
Edit rating inline
Update ratings, stage, and reviewer notes from the list as interviews wrap. Hooks fire normally so notification emails go out as expected.
Audience
Who uses SleekView for WP Job Openings
Hiring managers
Track candidates across roles and rate them right from the hiring grid. Compare backend and marketing applicants side by side instead of switching screens.
Interviewers
See only the candidates assigned to them at a given stage. Score interviews inline and add reviewer notes without opening each application record.
HR teams
Audit pipeline metrics like time-in-stage, rejection reasons, and source from one screen. Export filtered views for diversity or compliance reporting.
The bigger picture
Why hiring grids beat per-job applicant lists
Hiring on WP Job Openings rarely fits the per-job admin screen the plugin ships with. A single backend role can pull twenty applications in a week, a marketing role pulls forty, and the team needs to see them next to each other to calibrate ratings. Drilling into one job at a time forces interviewers to keep mental notes about who they liked across roles, which is exactly how good candidates fall through the cracks.
A real grid with stage, rating, source, and submission date in one row turns the pipeline into something you can review in a single sitting. It also makes the data legible to HR, who care about pipeline health metrics like average time-in-stage, source quality, and rejection reasons. Those numbers exist as postmeta but never surface in the default screens.
SleekView does not replace the application form, the candidate emails, or the resume storage. It just gives the people who actually run hiring a view of their own data that matches how they think about the work.
Questions
Common questions about SleekView for WP Job Openings
Yes. Rating is stored as postmeta on the awsm_job_application post type, and SleekView surfaces it as a sortable, editable column right in the grid. You can sort by rating, filter to four-star-and-up candidates, and edit ratings inline as interviews wrap.
 Yes. Any custom field added through the WP Job Openings form builder, including dropdowns, file uploads, and checkboxes, appears as a column or filter. Right-to-work, salary expectations, and notice period fields stop hiding behind tabs and become first-class hiring data.
 Yes. SleekView writes through the same hooks the plugin uses, so candidate confirmation emails, admin notification emails, and any webhook integrations fire exactly as they do when you edit through the default screens. Stage changes trigger their normal email flows.
 Yes. Select rows and apply a stage change to all selected applicants at once. The hooks run per row so notification emails still go out, but the click cost drops from one-by-one drilling to a single bulk action. Useful at the end of a screening round.
 Yes. If your application form captures source, whether through a dropdown, hidden UTM field, or referrer, it becomes a filter and column instantly. You can compare hire rates by source or build views that surface candidates from specific job boards.
 Yes. Filtered views export to CSV with the chosen columns. Hand a list of shortlisted candidates to a client, share interviewer scores with finance for offer approvals, or archive a closed role's pipeline for future reference.
 No. Resumes stay where WP Job Openings puts them, in the WordPress Media Library or as the plugin's secured file attachments. SleekView surfaces a link to the resume on each row so reviewers can open it in one click without changing how files are stored or secured.
 Yes. SleekView surfaces submission date and any stage-change timestamps the plugin records as columns and filters. Build a view of candidates stuck in Screen for over a week, or sort by days-since-submission to spot pipeline bottlenecks before they cost a hire.
 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.
Lifetime ♾️
Most popular
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
€749
Continue to checkoutBrowse more
- Checkout Field Editor
- Givewp
- Thirstyaffiliates
- Woocommerce Google Analytics Pro
- Shipment Tracking
- Woocommerce Pre Orders
- Bigcommerce
- Yith Woocommerce Product Reviews
- Payu Money Woocommerce
- Iconic Woothumbs
- Yith Woocommerce Bookings
- Wholesale Suite
- Woocommerce Sezzle
- Wpc Buy Now Button
- Funnelkit Funnel Builder