Spark Hire
Spark Hire is wiring the job description into every AI judgement it makes about a candidate
A side-by-side editorial comparison of HiBob and Kombo — release velocity, themes, recent moves, and the top alternatives to consider.
HiBob is closing the gaps in its Public API, one module at a time.
Bob's developer changelog is almost entirely API surface work, shipped in a steady two-to-three-week rhythm. The pattern is coverage: modules that were UI-only or partially exposed — Employer, Skills, Hiring, Time Off, and now several employee tables — get first-class Public API endpoints. Alongside that, the Bob MCP Server moved to OAuth, and Hiring gained an explainable AI match score.
Kombo stops being a fixed-schema pipe and starts running its customers' code.
Kombo publishes a weekly digest per API family — ATS, HRIS, Platform, and occasionally LMS and Assessment — and the cadence is dense. The August run added two unified read models (Scorecards for structured interview feedback, Notes for recruiter commentary), a managed skills-catalog write API, five or more new provider integrations including Talent360, Emply People, Skello and Zellis, and steady expansion of the write actions that create employees and applications in downstream systems. Underneath, the sync architecture is being rebuilt around Sync Units, which split large syncs into independent parts and unlock per-model webhooks, alongside a shared access-token cache and a new Issues system that surfaces integration failures to customers with a webhook.
Bob's developer changelog is almost entirely API surface work, shipped in a steady two-to-three-week rhythm. The pattern is coverage: modules that were UI-only or partially exposed — Employer, Skills, Hiring, Time Off, and now several employee tables — get first-class Public API endpoints. Alongside that, the Bob MCP Server moved to OAuth, and Hiring gained an explainable AI match score.
Two threads are converging. The endpoint work is making Bob writable from the outside rather than merely readable, with create, update, delete and bulk operations arriving where only partial coverage existed. The MCP and AI work assumes something on the other end will consume that surface programmatically. Read together, HiBob is preparing Bob to be operated by external systems and agents, not just integrated with.
Expect the remaining UI-only modules to get the same CRUD treatment, and expect the MCP server's tool list to grow to match whatever the Public API newly exposes. The entries do not indicate which module is next.
Kombo publishes a weekly digest per API family — ATS, HRIS, Platform, and occasionally LMS and Assessment — and the cadence is dense. The August run added two unified read models (Scorecards for structured interview feedback, Notes for recruiter commentary), a managed skills-catalog write API, five or more new provider integrations including Talent360, Emply People, Skello and Zellis, and steady expansion of the write actions that create employees and applications in downstream systems. Underneath, the sync architecture is being rebuilt around Sync Units, which split large syncs into independent parts and unlock per-model webhooks, alongside a shared access-token cache and a new Issues system that surfaces integration failures to customers with a webhook.
The important move this month is Advanced Mappings, which puts customer-written TypeScript in the delivery path. Everything Kombo had built before it widened what data could be reached — custom fields, more providers, more models — while leaving the shape of that data fixed by Kombo's schema. Advanced Mappings changes the shape, and it went from launch on 24 August to enabled-by-default in every development environment six days later, which is not the pace of an experiment. Read together with Sync Units and per-model webhooks, the platform is being rearranged so customers can intervene in the pipeline rather than only consume its output.
Advanced Mappings is dev-only by default today, so the next step to watch is promotion to production environments and whatever execution limits, versioning or review that requires. The near-weekly rhythm of new integrations and model extensions is likely to continue regardless, since it is the pattern every digest in this feed shows.
Other HR products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either HiBob or Kombo.
Spark Hire is wiring the job description into every AI judgement it makes about a candidate
Tanda is moving from telling Australian payroll what to pay to actually moving the money
PeopleForce publishes an HR marketing blog, and buries its releases in half-yearly roundups
Ashby ships near-daily recruiting-ops depth while its AI layer arrives from off-changelog.
Teamflect keeps grinding on the parts of performance review nobody demos.
LinkedIn ad spend is now bought, tracked, and refunded inside the ATS.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. HiBob and Kombo are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HiBob and Kombo are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other HR products to evaluate alongside.
Top HiBob alternatives in HR are ranked by recent ship velocity. Browse the "HiBob alternatives" section above for the current picks, or visit /alternatives/hibob for the full list with editorial commentary on each.
Top Kombo alternatives in HR are ranked by recent ship velocity. Browse the "Kombo alternatives" section above for the current picks, or visit /alternatives/kombo for the full list with editorial commentary on each.