Skip to content
Resumeboard

Oracle Taleo resume parsing, which Oracle hands to somebody else

Taleo is the hardest of the six to write a page about, and the reason is that Oracle says so itself: the parser is a partner product, delivered as is. Here is what that means, and the one useful table Oracle does publish.

The honest headline

Oracle's own documentation states that resume parsing in Taleo is "delivered using a third party partner service" and that "the functionalities are delivered as is". Oracle does not publish the parser's rules, because Oracle does not own the parser. Anyone telling you they know how the Taleo parser works is guessing — or describing a different product.

What Oracle states, quoted

"Resume Parsing: Resume parsing is delivered using a third party partner service. The functionalities are delivered as is. Customers needing additional or different resume parsing capabilities should explore partner services."

Oracle Taleo Enterprise Edition documentation, Login, Help, Navigation and Other Tools, Supported Languages

That paragraph is the single most important sentence for anyone researching Taleo parsing. It tells you three things at once: the engine is external, its behaviour is fixed, and Oracle's own answer to "can I change this" is to buy something else.

How parsing gets switched on, if it does

Parsing in Taleo is not a property of the product. It is a block in a flow that the employer configures, and Oracle documents that in detail.

  • "The profile import is dependent on the Resume Upload block. It is a best practice to put the Resume Upload block on all application flows to ease the input burden on the candidates. If Resume Parsing is on, candidates have the option of uploading a resume."
  • "The candidates will always be presented with the Resume Upload block if the Education or Experience blocks of a submission are empty."
  • On mobile, candidates can paste plain text instead of uploading a file, and Taleo will "parse the pasted text" to pre-populate the application.
  • Some third-party profile import services exist alongside it, which is why you sometimes see a LinkedIn or Indeed icon next to the upload field on a Taleo-powered careers page.

Sources: Profile Import Options for Candidates and Plain Text Resume Parsing for Mobile Devices.

The one trap Oracle documents, and it is a good one

Parsed fields the candidate can never correct

Oracle states: "All fields mapped by the profile import service are populated, whether or not those fields are displayed in a job-specific submission or general profile flow. In the case where a field is not configured in the flow, the candidate will not have the opportunity to correct or edit that specific information while advancing through the flow."

A parser can therefore write a value into a field that the application form never shows you. You submit, you are done, and whatever it decided is what the recruiter sees. This is the strongest argument on this whole site for writing resume text that a parser cannot misread in the first place.

Language support, as Oracle's table records it

Oracle publishes a support matrix for every feature in the product, including a "Resume Parsing" column. It is the most concrete parser fact Taleo offers. Three values appear: Supported, Limited, and blank, meaning no parse support for that language.

Oracle's documented resume parsing language support
Status Languages
Supported English, English (U.K.)
Limited Dutch, French (Canada), French (France), German, Italian, Portuguese (Brazil), Spanish (Worldwide)
No parse support Bulgarian, Chinese (China), Chinese (Taiwan), Croatian, Czech, Danish, Finnish, Greek, Hungarian, Indonesian, Japanese, Korean, Lithuanian, Malaysian (Malay), Norwegian, Polish, Portuguese (Portugal), Romanian, Russian, Serbian, Slovak, Slovenian, Swedish, Thai, Turkish

Read this against Greenhouse, which lists full parsing in 27 languages including Japanese, Korean, Russian and Arabic. If you are applying to a large employer in one of the two languages Taleo lists as no support, the parse on the Taleo side is not going to help you, and no amount of formatting will change that. The only lever left is making sure the form's required fields are filled accurately by hand.

What Taleo does not document

  • No accepted file types or size limit for the resume endpoint. Unlike Workday and Lever, Oracle publishes no list. The upload behaviour you meet is the partner service's, described elsewhere.
  • No failure modes. There is no Taleo equivalent of Greenhouse's "unsuccessful resume parse" article, so you cannot learn in advance which layouts break it.
  • No accuracy, no field mapping, no ordering guidance.
  • No single behaviour to aim at. Because parsing is a configurable block, two employers on the same Taleo tenant can behave completely differently. Optimising for "Taleo" is optimising for a configuration you cannot see.

A note on the image-resume capability

Oracle has documented that "The Taleo Business Edition (TBE) Career Center now allows job seekers to upload resumes in PNG and JPEG/JPG formats" — you can photograph a resume with your phone. This is a genuinely useful accessibility feature and it is about capture, not parsing. Accepting an image tells you nothing about whether the partner parser reads it once uploaded. Do not read it as permission to submit a photo of a resume.

Source: Resumes in Image Formats, Oracle Cloud Applications readiness documentation.

What to do when you cannot see the parser

Taleo is the case where general good practice beats vendor-specific optimisation, because there is no vendor-specific practice to learn. Concretely:

  1. Use a plain DOCX or a text-based PDF. The moment you are past the parser, DOCX is the safer export, because the parse is not the only thing consuming your file.
  2. One column, no tables, no text boxes, no header or footer content. This is the layout the other four vendors on this site document as safe, and there is no evidence it is unsafe in Taleo.
  3. Standard section headings in capitals. Taleo returns no named section for a heading it does not recognise, so EXPERIENCE is a better bet than a creative label.
  4. Spell out employers and job titles. This costs nothing and helps every parser on this site.
  5. Re-read the form after uploading. Given the correction gap Oracle documents, assume the parse wrote something you cannot see, and check every field the form does show.

The print-safe template does all five and adds nothing that a parser has to work around.

Check your resume for the things every parser needs

Since Taleo publishes no rules of its own, Resumeboard checks your file against the rules that Greenhouse and Workday do publish, which is the closest thing to a floor you can actually rely on.

Opens the builder. The check is under Check, on the ATS tab.

Open the Taleo check All six vendors