Oracle Taleo Decoded:
Why DOCX Is Not Optional

Taleo's PDF extraction layer is one of the oldest in commercial use. It frequently produces output where words run together without spaces, paragraph breaks are lost, and section headings disappear entirely. Text in PDFs with embedded fonts that are not in Taleo's library renders as question marks or boxes. The failure is not consistent — sometimes a PDF parses partially — which means you cannot rely on testing with one document to predict how another will parse.

Taleo processes only the main body content of Word documents. Text placed in the Word header region — including your name, phone number, and email if you positioned them there for visual symmetry — is not extracted. The candidate profile created by Taleo will have no contact information, which recruiters cannot correct without asking you to reapply. Place every piece of contact information in the first paragraph of the document body.

The standard round bullet character (•, Unicode U+2022) and similar symbols like ◦, ▸, and – created with Word's automatic list formatting are stored as Unicode characters. Older Taleo database configurations use Latin-1 character encoding, which does not support these characters. Every bullet point in your resume becomes a literal question mark in the stored text. Use plain ASCII hyphens (-) or asterisks (*) for list items throughout your resume.

Taleo reads DOCX files by extracting the raw XML paragraph sequence. Word's multi-column layout is implemented using table structures or section formatting that Taleo either skips or reads left column then right column sequentially. Either way, the result is garbled — job titles from one column appear next to dates from another, and the parser cannot identify any coherent work history.

Taleo maintains two parallel data stores: the uploaded resume file and the structured profile fields. Many enterprise Taleo deployments configure keyword search and candidate ranking to operate on profile fields rather than the document. Recruiters searching for 'Java developer with 5 years experience' are querying profile fields, not resume text. If you skip filling out employment history, skills, and education in the profile form, you may be invisible to recruiter searches even with a well-parsed resume.

This is the single most impactful decision for Taleo applications. Use Microsoft Word or Google Docs (downloaded as .docx) with a single-column layout. Do not submit PDF regardless of how clean your design is — Taleo's PDF parser has documented, widespread failures across all PDF types.

Open Find and Replace in Word (Ctrl+H) and replace the bullet character • with a hyphen -. Do the same for any other special characters you have used as list markers. This prevents the question-mark rendering issue in Taleo database configurations that use Latin-1 encoding.

Delete any Word page headers and footers. Your name, phone, email, city, and LinkedIn URL should all appear in the first few lines of the document body as plain text. Format them on a single line separated by a pipe character, or on separate lines — either works. Do not put any important content in headers, footers, text boxes, or table cells.

When Taleo asks you to enter your employment history, education, and skills in form fields — do it thoroughly, even if you just uploaded a resume. Treat these fields as your real resume and the file upload as a backup. Include every relevant job, every skill from the job posting, and your complete education history. This is what recruiters search.

Name your sections 'Work Experience', 'Education', 'Skills', and 'Certifications'. List work history in reverse chronological order starting with your most recent position. Taleo's parser is trained on conventional resume structures — functional and hybrid formats that reorder or rename sections are frequently misinterpreted.