35
Career-property configuration
Company career configuration at the recorded property; it does not verify a successful application or executed workflow.
← All company lists
HR and recruiting · October 2026 research
SAP SuccessFactors company list
Review 106 operators by their recorded SuccessFactors workflow and source date. Career configuration, applicant policies and employee-system disclosures provide different levels of detail.
Research dated 2026-10-23. Original source dates and website scope stay with the records.
SAP SuccessFactors research summary
106 reviewed company operators
Research dated
Contact-free research examples · CSV
106 reviewed operators: 85 have Recruiting-only primary scope and 21 have other or mixed HR workflows. Career-property configuration and company disclosures retain their individual workflow, entity and regional limits; no full-suite or current-customer count is claimed.
Download the 4-row CSV previewChoose the SuccessFactors source and workflow
71
Company disclosures
Company policies, reports and help pages describe Recruiting or other HR workflows at their stated dates and scope.
35 career-configuration records + 71 company disclosures = 106 operators. Workflow scope is a separate classification: 85 Recruiting-only and 21 other or mixed.
Preview the list
Source mix, findings and four contact-free examples from the 106-operator SAP SuccessFactors research cohort. The full account file is not offered; commercial reuse and delivery rights remain unresolved.
CSV columns: name · domain · sourceClass · checkedOn · scope
Four companies in the preview
These approved examples illustrate the 2026-10-23 research. They are not a representative sample of all customers.
BMW Group
bmwgroup.com
company careers cname configuration · 2026-10-22
Configured SuccessFactors Recruiting career property for BMW Group; no broader HCM/ERP or successful application claim. Paid status unknown; current runtime unverified.
Volkswagen Group
volkswagen-group.com
company careers cname configuration · 2026-10-22
Configured SuccessFactors Recruiting career property for Volkswagen Group; no broader HCM/ERP or successful application claim. Paid status unknown; current runtime unverified.
Bayer
bayer.com
company careers cname configuration · 2026-10-22
Configured SuccessFactors Recruiting career property for Bayer; no broader HCM/ERP or successful application claim. Paid status unknown; current runtime unverified.
adidas
adidas-group.com
company careers cname configuration · 2026-10-22
Configured SuccessFactors Recruiting career property for adidas; no broader HCM/ERP or successful application claim. Paid status unknown; current runtime unverified.
Workflows and source dates in this list
WhosBuilt analysis of the saved October 2026 research. Findings describe this selected cohort, not market share.
85 / 106 · 80.2%
Recruiting is the main recorded workflow
85 of 106 primary records establish Recruiting alone. The other 21 describe other or mixed workflows; they are not a count of full-suite deployments.
Selection emphasized careers and privacy pages before broadening to reports and help pages. These proportions describe this selected package, not market adoption. A Recruiting-only primary record does not prove that the company uses no other modules.
Research 2026-10-23 · reviewed company operators · WhosBuilt saved-record analysis
16 / 106 · 15.1%
Historical statements keep their dates
16 of 106 primary records are marked historical. Later website and contact checks do not change the period described by an older statement.
The historical flag marks reviewed older primary records and does not measure the age of every source. The remaining 90 records are not confirmed current subscriptions or executed deployments. Undated policies and static configuration can also be stale.
Research 2026-10-23 · reviewed company operators · WhosBuilt saved-record analysis
How this list was checked
Original sources checked 2026-10-22 to 2026-10-23 UTC. Publication, policy, reporting-period and file-change dates remain separate. Sixteen primary records are marked historical; undated policies and static configuration can also be stale. Later website and contact checks do not refresh these observations.
106 reviewed operators: 85 have Recruiting-only primary scope and 21 have other or mixed HR workflows. Career-property configuration and company disclosures retain their individual workflow, entity and regional limits; no full-suite or current-customer count is claimed.
| Source class | Count | Scope |
|---|---|---|
| Career-property configuration | 35 | Company career configuration at the recorded property; it does not verify a successful application or executed workflow. |
| Company disclosures | 71 | Company policies, reports and help pages describe Recruiting or other HR workflows at their stated dates and scope. |
Recruiting is the main recorded workflow: Denominator: all 106 accepted operators in this product package, counted once per operator. Workflow scope and historical status are separate classifications and can overlap. WhosBuilt analysis of the saved company research and separately reviewed findings; no source refresh.
Research dated 2026-10-23; original source observations ran 2026-10-22 to 2026-10-23 UTC. Counts describe this selected package, not the product's customer base.
Historical statements keep their dates: Denominator: all 106 accepted operators in this product package, counted once per operator. Workflow scope and historical status are separate classifications and can overlap. WhosBuilt analysis of the saved company research and separately reviewed findings; no source refresh.
Research dated 2026-10-23; original source observations ran 2026-10-22 to 2026-10-23 UTC. Counts describe this selected package, not the product's customer base.
- Sixteen primary records are historical. The remaining 90 do not confirm current subscriptions or executed deployments.
- Recruiting-only primary scope does not establish that the company uses no other modules; the other 21 records are not full-suite deployments.
- Company sources support scoped operator records. Supplier leads, access failures and unresolved identities do not establish adoption or non-use; market share, paid status and buying intent remain unmeasured.
Source access dates do not refresh historical statements. Static signals do not prove execution, payment or buying intent. Published contacts do not establish deliverability or outreach permission.