Codility vs Kombo

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.