iCIMS Career Site Not Showing Jobs: 7 Causes and How to Fix Each One
Your requisitions are open. Your recruiter hit Approve. But candidates can’t find a thing. Here’s exactly why it happens and how to fix it.
An iCIMS career site not showing jobs problem almost never means something is dramatically broken. The cause is usually a quiet configuration mismatch the platform won’t flag to you. Jobs sit invisible to candidates while your team assumes everything is live.
We see this constantly in our iCIMS consulting work. Recruiters approve requisitions, hiring managers are waiting for applicants, and nobody realizes the job never made it onto the career portal. By the time someone notices, the role has been sitting dark for days or weeks.
This guide covers the seven most common reasons jobs don’t appear on an iCIMS career site and gives you a specific fix for each one. Work through them in order until you find the culprit.
Job Not Explicitly Posted to the Portal
Most Common CauseThe problem: In iCIMS, approving a requisition and posting it to a career site are two completely separate actions. A job can be fully approved, in Open status, and actively recruiting, but still invisible to candidates if no one posted it to the portal.
The impact: This is by far the most common reason for an iCIMS career site not showing jobs. It happens most often with recruiters who are newer to the platform, or in organizations that recently moved a workflow online and assumed the posting step was handled automatically.
In practice: In our audits we regularly find requisitions where a recruiter completed every step in the ATS workflow except the portal post. The job profile shows Open, the hiring manager has approved it, and the requisition looks complete from every internal view. But candidates get zero results.
The fix: Navigate to the Job Profile in iCIMS. Look for the “Post to Career Sites” or “Portal Postings” section (the label may vary slightly by your configuration version). Click “Add Posting” or “Post Job,” select the appropriate career portal, and confirm. The job should appear on the portal within a few minutes.
Requisition Status Isn’t Portal-Eligible
The problem: Every iCIMS career portal is configured with a set of requisition statuses eligible for display. Typically this includes statuses like “Open” or “Actively Recruiting.” If the requisition is sitting in “On Hold,” “Pending Approval,” “Approved,” or a custom intermediate status, the portal filter will exclude it.
The impact: A recruiter sees the requisition as approved and assumes it’s live. The portal filter doesn’t see an eligible posting status, so the job is invisible. No error appears. The job is just absent.
In practice: This happens most often when an organization customizes their workflow and adds intermediate statuses between “Approved” and “Open.” If nobody remembered to add those new statuses to the portal eligibility settings, every job that passes through them disappears from the site. It can affect dozens of roles at once before anyone catches it.
The fix: Check the requisition’s current status and compare it to your portal’s eligible status list. In iCIMS, go to System Configuration and find your career portal’s settings to see which statuses are included in the display filter. Either move the requisition into an eligible status or have your iCIMS system administrator add the current status to the portal filter.
Wrong Portal Assignment
The problem: Many iCIMS customers have more than one career portal. Common setups include a public-facing external career site, an internal employee portal, a branded divisional portal, or region-specific job boards. If a job gets posted to the wrong portal, it will show up in one place but not where you’re looking.
The impact: External candidates can’t see a job because it was accidentally posted only to the internal portal. Or a role meant for a specific business unit is appearing on the main careers page instead of the divisional one (or neither). The job IS posted, just to the wrong destination.
The fix: Open the Job Profile and navigate to the Portal Postings section. Review every posting entry and confirm it points to the correct career site. Remove any incorrect portal assignments and add the correct one. If you’re not sure which portal URL corresponds to which configuration, check with your iCIMS administrator or review your portal list in System Configuration.
Workflow Profile Not Mapped to the Portal
The problem: iCIMS career portals can be configured to only display jobs that use specific Workflow Profiles. If your portal’s display configuration includes a Workflow Profile allowlist and a new job was built with a profile not on that list, the job will be invisible on the site even after it’s been posted correctly.
The impact: This happens most frequently after system changes: when a new department gets its own Workflow Profile, when an acquisition brings in new entities with different configurations, or when an admin builds a new recruiting workflow without updating the portal mapping. Every job using the new profile goes dark.
In practice: We have seen clients launch internal mobility programs with their own Workflow Profile, only to discover their internal career portal was configured to display jobs from only the original set of profiles. Dozens of internal transfer opportunities were posted and invisible for weeks before a system audit caught the Workflow Profile mapping gap.
The fix: Go to your career portal’s configuration in iCIMS System Configuration. Find the section that defines which Workflow Profiles are included in the portal’s display settings. Add the Workflow Profile used by the jobs that aren’t showing. An iCIMS admin or a certified iCIMS consulting partner will need access to portal-level system configuration to make this change.
Missing Required Posting Fields
The problem: Some iCIMS configurations require specific fields to be completed before a job can successfully post to a portal. Common required fields include Job Category, Department, Location, Posting Title, or a job description with minimum content. If these fields are blank, the job may appear posted in the admin view but will fail silently to display publicly.
The impact: The recruiter goes through the posting steps normally. No error appears. The job is in the portal postings list. But the portal doesn’t render it because a required display field is missing. It’s a silent failure that’s easy to miss until candidates start asking why they can’t find the role.
The fix: Open the Job Profile and check for any fields that appear blank, especially category, location, department, and posting title. Fill in anything that’s missing and then republish the job to the portal. If you’re not sure which fields are required for your portal’s display rules, have your admin review the portal configuration or run the job through a test posting.
Location or Category Filter Mismatch
The problem: Many iCIMS career portals surface jobs through a search interface where candidates filter by location, job function, department, or other criteria. If the job doesn’t have a valid, recognized value in those fields, it may be technically posted but will return zero results when candidates search or browse the portal’s category filters.
The impact: The job is live, but candidates only see it if they search with no filters applied. Most candidates use filters. A job with a missing or non-standard location value effectively doesn’t exist for filtered searches, which is how the majority of job seekers actually browse.
In practice: We see this when organizations expand to new locations and use free-text location entries with non-standard formatting, like “Hybrid NYC” instead of “New York, NY.” The portal’s location filter recognizes standard picklist values only, so those jobs never populate the location dropdown and disappear from filtered searches entirely.
The fix: Check that the Location and Job Function fields on the job use values that match the picklist options configured in your portal’s filter. Avoid free-text entries in fields that drive portal filtering. If your portal has specific configured values for location or category dropdowns, use those exact values on the job posting.
Post Date Scheduled in the Future
The problem: iCIMS allows portal postings to be scheduled with a specific publish date. If a recruiter or admin accidentally set a future publish date, the job will be in the portal posting list and appear fully configured, but it won’t go live until that date arrives.
The impact: Everything looks right. The job is posted. The status is correct. The portal assignment is accurate. The job simply isn’t live yet because the publish date is set to next Monday, or next quarter, or some date nobody meant to set.
The fix: Go to the job’s Portal Postings section and look for a publish date or start date field on the portal posting entry. If there’s a future date set, clear it or change it to today’s date. Save and confirm. The job should appear on the portal shortly after.
📊 Quick Diagnosis Checklist
Use this table to match your specific symptom to the most likely cause:
| Symptom | Most Likely Cause | First Thing to Check |
|---|---|---|
| Job is Open, never appeared on site | Cause 1: Not posted to portal | Portal Postings section on the Job Profile |
| Job was showing, now disappeared | Cause 2: Status changed to non-eligible | Current requisition status |
| Job shows on one site but not another | Cause 3: Wrong portal assignment | List of portal postings on the job |
| New Workflow Profile, jobs never show | Cause 4: Profile not mapped to portal | Portal configuration Workflow Profile list |
| Job posted, no error, still not visible | Cause 5: Missing required fields | Category, location, and description fields |
| Job visible without filters but not in search results | Cause 6: Filter mismatch | Location and category picklist values |
| Everything looks configured correctly, job just not live | Cause 7: Future post date | Portal posting publish date field |
If you’ve checked all seven and the job still isn’t appearing, the next step is to look at your iCIMS portal’s search index settings or reach out to iCIMS support with a specific job ID.
For organizations with complex portal setups, multiple career sites, or ongoing configuration drift, a targeted review is often the fastest path to a permanent fix. FlowFam’s iCIMS managed services cover exactly this kind of recurring configuration work.
💬 Still Can’t Find the Problem?
We’ve diagnosed and fixed iCIMS career portal issues for recruiting teams across every industry. If you’ve worked through this checklist and the jobs still aren’t showing, we can find it.
Book a Free Consultation🔗 Related iCIMS Troubleshooting Guides
Career portal issues are often one symptom of a broader configuration problem. If you’re seeing other unexpected behavior in iCIMS alongside the missing jobs, these guides may help:
- iCIMS Workflow Rules Not Triggering: When automation fails silently and jobs miss status transitions or auto-posting steps.
- iCIMS Data Structure Explained: How Person Profiles, Job Profiles, Workflow Profiles, and Portals relate to each other.
- iCIMS Offer Letter Template Not Populating: Another quiet failure that happens downstream when configuration gaps accumulate.
If your team is dealing with ongoing configuration drift across your iCIMS instance, our iCIMS managed services give you a dedicated consultant who catches these issues before they impact recruiting outcomes.
❓ Frequently Asked Questions
🎯 Get Expert iCIMS Support
FlowFam is a certified iCIMS consulting partner. We help recruiting teams configure, troubleshoot, and optimize their iCIMS systems so roles get in front of candidates and opportunities don’t go dark.
Book a Free Consultation
