The reason Notice Consent is a distinct workstream from Cookie Consent. Writes the consent artefact tied to user ID, subscribes to withdrawal events, and the bulk of the effort — implements the suppression call to every downstream system so processing actually stops. Not required for Cookie Consent unless server-side mirroring of cookie decisions is in scope.

Key responsibilities

- Notice Consent artefact write: on accept/reject, call the Redacto Consent API and store the artefact keyed by user ID; mirror current state to the client user profile store.
- Withdrawal event subscriber: consume the Redacto withdrawal event and update the user record.
- Downstream propagation (the bulk of the work): for every system in the downstream inventory — CRM disables the marketing flag, marketing automation moves the user to unsubscribed, warehouse suppression flag is set.
- Discovery (rare): build custom connectors for sources not covered by out-of-box scanners.
- TPRM (optional):



implement the procurement webhook so current-vendor creation in Ariba/Coupa/Zycus triggers the workflow.
- Coordinate with QA on the downstream-suppression verification test — the actual suppression in the target system, not just the API call.

Skills and qualifications

- 3+ years in Node.js, Java (Spring), Python (Django/FastAPI), or .NET. Capri BE reference is Python.
- Experience integrating with at least two of: Salesforce, Dynamics, HubSpot, Marketo, Braze, MoEngage, Netcore, WebEngage, CleverTap, Snowflake, BigQuery, Redshift.
- Comfort with event-driven patterns (webhooks, pub/sub) and idempotent downstream writes.
- Familiarity with JWT / session token / API key + mTLS auth patterns for service-to-service calls.
- Understanding that the highest-risk defect class in this workstream is silent downstream propagation failure.

Preferred candidate profile

📌 Back End Developer (Hyderabad)
🏢 Pauls Techno Crafts
📍 Hyderabad