Implementing dynamic backoff for 429s on bulk user updates

Context:
Building a ServiceNow integration that pushes user updates to Genesys Cloud. I am hitting 429 Too Many Requests on POST /api/v2/users/bulk. I am currently parsing x-ratelimit-remaining and sleeping for x-ratelimit-reset, but my retry logic is still failing intermittently.

Question:
Should I be implementing exponential backoff on top of the reset delay? My current Python snippet just sleeps for the exact reset seconds. Is there a more robust pattern for handling transient 429s during bulk operations?