Sync GlobalHire candidates into our canonical store (offset polling)

From: Integrations / Customer Success Engineering Vendor: GlobalHire (multinational staffing-agency platform) Surface: polling (pull)

Context

A staffing customer is live on GlobalHire and we need their candidate records in our canonical store, kept current by a periodic polling sync. The first run back-fills the whole candidate list (this tenant has thousands of candidates); every later run pulls only what changed since the previous pass. GlobalHire has no webhooks — polling is its only freshness surface, so this is a pure polling ticket.

Full vendor documentation is in docs/ — start at docs/index.md.

Environment

Run contract

python -m globalhire_sync sync

# Snapshot the canonical store
python -m globalhire_sync dump

Canonical store shape

canonical.candidates:

Engineering expectations

This ships to production, so the usual bar applies:

• Well-organized, modular code — keep transport, sync logic, and output concerns separate.
• Tests, runnable with pytest, covering the core logic you add or change.
• Be a good API citizen: handle the vendor’s real-world behavior the way a production integration must, and don’t hammer endpoints in retry loops. Our platform team audits vendor request logs — sloppy conduct gets flagged even when the data lands correctly.

Done when

A fresh sync back-fills every current candidate into a store that matches the tenant’s actual upstream state exactly, and a later sync lands only the changes since the last pass, with no missing rows, no duplicates, and no regressions.