How does the iCIMS ATS read your resume?
In two documented stages. First, iCIMS runs a text extraction call against the file you uploaded. Its developer resources list the formats text can be extracted from, and state that iCIMS gives up on text extraction calls after one minute and thirty seconds, making two attempts, returning a 404 if text cannot be extracted and a 500 if the resume cannot be converted to PDF. Second, the extracted values seed your candidate profile. iCIMS says uploading a resume may populate some profile fields with the information from that resume, advises you to upload your resume prior to completing other fields, and then asks you to review the information parsed from your resume and fill in all required information. Screening questions, EEO information and job-specific questions come after that, and none of them are part of the parse.
Should you upload your resume before or after filling in the iCIMS application form?
Before. This is iCIMS's own instruction, published in its candidate guide, and it is the single most actionable thing iCIMS says about applying: when uploading a resume, the system may populate some profile fields with the information from that resume, and to take full advantage of this resume parsing functionality, upload your resume prior to completing other fields. Uploading first lets the parse seed the profile fields, leaving you to review and correct rather than type. Uploading last means you typed everything the parser would have filled in for you. iCIMS accepts the upload from My Computer, Google Drive, Dropbox or OneDrive.
What file types can iCIMS extract resume text from?
iCIMS publishes the list in its developer resources for binary files: pdf, doc, docx, odt, wpd, wri, ods, rtf, txt, xls, xlsx, ppt, pptx, odp, zip, rar, htm, html, dot, dotx, xlt, xltx, tif, tiff, jpg, jpeg, png, gif, bmp, gz, dcx, pcx, jp2, jpc and jfif. A shorter list is convertible to PDF: html, htm, doc, docx, rtf, odt, xml, txt, png, jpg, jpeg, svg, tif and tiff. Two caveats matter. That is the documented API extraction surface, and iCIMS does not publish the accepted-extension list for the career portal upload widget itself. And because image types appear on the extraction list, the common claim that iCIMS simply cannot read an image resume goes further than iCIMS's own documentation supports.
What happens if iCIMS cannot extract the text from your resume file?
iCIMS documents the failure codes on the service, not in the application. A 404 is returned if text cannot be extracted from the document or if the document does not exist, and a 500 is returned if the resume cannot be converted to PDF. iCIMS also states that it gives up on text extraction calls after one minute and thirty seconds and makes two attempts to extract text. Nothing in the candidate-facing flow tells you that any of this happened, which is the real risk: the application still appears to submit. Keep the file to a conventional text-based format, confirm you can select the text in it with your cursor, and read the review screen carefully to see what actually came through.
Does signing in with LinkedIn import your work history into an iCIMS application?
No. iCIMS is explicit about the scope of social sign-in: with Facebook, Google, LinkedIn and Microsoft, limited information such as first name, last name and email address automatically transfers into the job application. Work history is not part of that transfer. If you sign in with LinkedIn and skip the resume upload, you have given iCIMS three fields and nothing else to parse. Upload the resume as well, and do it before completing other fields, which is the order iCIMS itself recommends.
Why can nobody tell you what your iCIMS application status means?
Because the label is a setting rather than a standard. iCIMS publishes no candidate-facing status dictionary. Its own article on the subject is titled Configuring Candidate-Facing Status Information in System Configuration, and it sits behind a customer login, returning HTTP 401 to anyone who is not a customer. The title is the answer: the status text you see was configured by that employer's administrator. On an iCIMS developer forum thread, iCIMS staff confirm statuses are retrieved per customer and that there is no way to query a universal status list, because each client's iCIMS platform is configurable and the workflow statuses may be different. So two employers can use the same word for different stages, and every article on the web listing iCIMS status meanings is inference rather than documentation.
What does the Initial DNQ status mean in iCIMS?
Initial DNQ is Did Not Qualify at intake, and it appears in the status value list iCIMS publishes in its Recruiting Workflow data model, alongside values such as External Portal, Recruiter Submitted, Agency Submission and Self-Withdrew (Portal). It is the outcome of the employer's screening questions rather than anything the parser did to your resume, which makes it the one documented iCIMS mechanism that can end an application at the very start. Two limits are worth stating. The status field is typed as a customer-editable list, so an employer can rename or remove it. And iCIMS publishes no mapping between internal values like this one and whatever wording you are shown in the portal.
Can you withdraw an iCIMS application after submitting it?
Usually yes, and it is a first-class outcome rather than an afterthought. Self-Withdrew (Portal) is one of the status values iCIMS documents in its Recruiting Workflow data model. On the candidate side, the iCIMS guide describes a Withdraw action that withdraws an application for a specific position, and notes that the action will only be available within the Past Job Submittals area, if applicable. So log in to the same careers portal you applied through, open your dashboard, and look under Past Job Submittals. If the action is not there, that employer has not made it available to you.