HiBob vs Oracle HCM Cloud

Bob's developer changelog is a steady stream of Public API surface: Skills, Employer, Time Off calendars, Goals, and Hiring search endpoints, most of them adding read or sync paths for external systems. Against that background, two entries stand out — the MCP server moving to OAuth-based user access with an expanded toolset, and AI CV Matching replacing the previous AI CV Summary with an explainable match score built on criteria the recruiter defines.

HiBob is turning Bob into a system other software reads from and writes to, rather than a destination product. The API additions make every module — skills, employer entities, time off, hiring — reachable from outside, and the OAuth MCP server extends the same access to AI tools under user-scoped permissions. The CV change shows where the AI investment is aimed: not at generating text for recruiters to read, but at producing structured judgments they can be asked to justify.

Expect the criteria behind CV Matching to become configurable through the Hiring API the same way the module itself was, and for the remaining Bob modules without public endpoints to follow Skills and Employer into the API.