Integrate an External Privacy Eligibility API into Request Processing
Quick Overview
Integrate a privacy eligibility API with a shared processing gate, explicit denial and outage states, freshness-aware caching, retries, and auditable enforcement.
Integrate an External Privacy Eligibility API into Request Processing
Company: Verily
Role: Software Engineer
Category: System Design
Difficulty: medium
Interview Round: Onsite
An existing system processes requests associated with identifiers. A government-provided API can return a decision indicating that a request must not be processed for privacy reasons. Design the integration so the decision is checked and enforced reliably.
### Constraints & Assumptions
The actual API schema, legal rules, freshness requirements, and failure policy are unspecified. Describe the enforcement architecture and identify policies that require an authoritative decision rather than inventing them.
### Clarifying Questions to Ask
- Is the API response an eligibility decision, a list of restricted IDs, or another representation?
- How fresh must the decision be, and can it change after processing starts?
- If the API is unavailable, must requests wait, fail closed, or follow another approved policy?
```hint Place the gate before irreversible work
Checking eligibility after downstream processing may be too late to honor a denial.
```
### What a Strong Answer Covers
- A central enforcement point before protected processing.
- Authenticated API calls, decision validation, bounded retries, and explicit unavailable state.
- Carefully scoped caching and audit evidence without unnecessary sensitive data.
### Follow-up Questions
- How would you handle a denial arriving after a long-running request has begun?
- What prevents an alternate processing path from bypassing the check?
Overview: Integrate a privacy eligibility API with a shared processing gate, explicit denial and outage states, freshness-aware caching, retries, and auditable enforcement.
Integrate an External Privacy Eligibility API into Request Processing
Verily
Nov 4, 2026
mediumSoftware EngineerOnsiteSystem Design
0
0
An existing system processes requests associated with identifiers. A government-provided API can return a decision indicating that a request must not be processed for privacy reasons. Design the integration so the decision is checked and enforced reliably.
Constraints & Assumptions
The actual API schema, legal rules, freshness requirements, and failure policy are unspecified. Describe the enforcement architecture and identify policies that require an authoritative decision rather than inventing them.
Clarifying Questions to Ask Guidance
Is the API response an eligibility decision, a list of restricted IDs, or another representation?
How fresh must the decision be, and can it change after processing starts?
If the API is unavailable, must requests wait, fail closed, or follow another approved policy?
What a Strong Answer Covers Guidance
A central enforcement point before protected processing.
Authenticated API calls, decision validation, bounded retries, and explicit unavailable state.
Carefully scoped caching and audit evidence without unnecessary sensitive data.
Follow-up Questions Guidance
How would you handle a denial arriving after a long-running request has begun?
What prevents an alternate processing path from bypassing the check?