Dayforce¶

Dayforce's career sites (jobs.dayforcehcm.com) and their guest application, observed on live postings, last on 2026-10-22. The fixture page is tests/pages/dayforce/apply.html, served with the JSON it and the adapter read in tests/test_dayforce.py: one example of each rendering below.

Where the form is¶

• A job is jobs.dayforcehcm.com/<culture>/<namespace>/<career site>/jobs/<id>; the culture redirects to the site's own (en-US to en-AU), and the wizard's steps drop it. The double-send key is https://jobs.dayforcehcm.com/<namespace>/<career site>/jobs/<id>.
• Apply offers "Apply without an Account" (…/apply?flowSelection=true); atsfill goes straight to the guest form, …/jobs/<id>/apply/manualApplication?applicationSource=Manual. A closed posting shows no form: posting_gone.
• The site context (/api/geo/<ns>/sitecontext/<ns>/<site>/<culture>?jobPostingId=<id>) and the application template (/api/geo/<ns>/jobapplication/<ns>/<culture>/<job board id>/<id>) are public JSON and list every section, field and question. They leave out the options of the country and contact method dropdowns, bundled in the page, so there is no request read: the Test user, and a user, need those options.
• The page keeps its draft in sessionStorage (jobPostingApplication-<id>-<ns>); fill clears it and loads the form again.
• Dialogs cover the form on load: the employer's privacy policy where enablePrivacyPolicy (an agree box and Save; Cancel leaves the form, so atsfill accepts it, a declared side effect), the SMS consent where hasActiveSMSProvider (two radios, Save), the cookie banner (rejected). Accepting the policy is kept in the SiteConfig cookie of the browser profile.
• The wizard is Candidate Info, one page per questionnaire ("Questionnaire 1 of 4", then its name; some sites show no counter), an Assessment step on some sites, then Submit. Next ([test-id=application-next-step]) validates the step (POST …/JobApplication/validatesections, …/canuserreapply) and stores nothing.
• An assessment on another site before Submit ([test-id=embeddedassessment-openassessment-button]) is unsupported, external_step.

Reading the form¶

• Fields come from the template; ids are the form's own keys (firstName, countryCode), workHistory.<key> and educationHistory.<key> for a history entry, workHours.*, q<question id> for a question. The page's bundle maps template field names to keys (EMPLOYERNAME is companyName).
• Labels are the template's; the page's own are localized (Postcode, Country dialling code), so atsfill finds controls by id and test-id, never by label.
• Questionnaire controls are jobPostingApplication_sections_<page>_questionnaire_questions_<n>_<part>: <n> counts the questionnaire's statements too, except on the disability form, laid out on its own.
• Dropdowns are Ant Design selects: input[role=combobox] in .ant-select-selector, options in a dropdown portaled after main (.ant-select-dropdown holding #<id>_list), a virtual list that renders a screenful at a time. Their options are read by scrolling it. Some are searchable, some readonly.
• An option of a question shows its description (falling back to displayName); the option is named by it.

Each rendering, and on how many of the 27 surveyed postings' templates it shows (2026-10-20):

A template field, section or answer type outside this table is listed as unhandled_rendering.

Filling¶

• The resume goes first: uploading it (POST …/FileService/uploadresume) imports it over the Test user's information, so nothing is typed until the upload answers.
• The country goes before the state. A dropdown is opened from the middle of the window, the step's button bar covering the bottom; its option is clicked in the same script that finds it, the virtual list rendering its options anew as it moves. A searchable one is typed into first; a readonly one is scrolled to the option.
• A phone number picks the longest dial code its digits start with, the main country of a shared one (+1 is the United States), and types the rest.
• A section saves with its Update, the first submit button after its first field; a click while a dropdown is still closing is lost, so Update is clicked until the section closes. An open section keeps Next from going on.
• Some sites refuse a history entry dated in the future without an error; the entry stays open and the wizard on Candidate Info.
• A comment box is filled once its option is picked and the box shows, each of a box group's with its own answer. The wizard keeps only its last page, so the fields shown once filled are the comment boxes and source details each page showed before Next; a comment box showing that browser_read did not list is reported by its element id.
• Next can go unheeded right after a save; atsfill clicks it again, up to three times, until the step's controls change, the button reads Submit, or an error shows; an error adds its own <id>_help element, not a control. Submit is never pressed by fill.

Read-back and submit¶

• Nothing but the files reaches Dayforce before submit. The read-back is the page, taken from each step before leaving it: inputs' values, the dropdowns' shown item, the dial code and number, the checked radio's and boxes' labels, the file name shown under its input, the SMS radio as the dialog held it, and the acknowledgement box on Submit.
• Submit has not been observed. The page loads an invisible reCAPTCHA (recaptcha/api2), which may judge the send.

Known gaps¶