EY's experienced US hiring runs on SAP SuccessFactors. You search roles on careers.ey.com and apply through its flow, and the careers site footer credits “the SuccessFactors software provided by SAP,” with a backend that carries the production-tenant signature of a SuccessFactors-powered system. You create a candidate profile and submit there, so a real vendor parser reads your resume before a recruiter does. It is not Workday, not Avature, not Taleo, and not Oracle; a legacy ey.taleo.net URL is dead. EY-Parthenon, the firm's strategy practice, uses the same SuccessFactors instance.
Two accurate nuances matter before you apply. US campus and early-careers hiring runs a separate stack, a Radancy TalentBrew front end with a Yello application workflow at usearlycareers.ey.com, so students land on a different system than the experienced SuccessFactors flow. And EY's careers page offers an EY Watson Candidate Assistant chatbot to upload your resume, but that is a candidate-facing front end, not the parser; SuccessFactors is the system of record that reads the file. Contract and gig roles route to a separate platform, GigNow.
What that changes: because a vendor ATS ranks your resume before any human, the mechanics matter twice over. Use a single column, keep contact details in the body rather than the header, use a real text layer with standard section headers like Experience, Education, and Skills, avoid tables, text boxes, and graphics, ship a DOCX or a clean text-layer PDF, and mirror the posting's exact titles and skills so the parser ranks the file. The interview and any assessment are later, separate stages, not the resume screen.
The sufficient condition is content that proves value: a specific, quantified client or program outcome on every line, mapped to the values and three mindsets below. Keyword-matched formatting gets you ranked and read; demonstrated impact gets you advanced.