System designHard~20 minCore Designs / 27 of 30

Interview question

Design a backend boundary where subscription plans control which product features an account can use.

Design subscription entitlements and access

Designs plan entitlements, provider webhooks, idempotent billing updates, access checks, grace periods, and support overrides.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I would model plans and entitlements separately from payment provider records. Provider webhooks update subscription state through an idempotent ingestion path, then the application derives effective entitlements for the account. Product APIs check those entitlements server-side before allowing gated actions. The UI can display plan state, but it cannot be the source of access truth.

Full answer below

Practice focus

Entitlement modeling, billing provider events, idempotency, access checks, plan changes, grace periods, auditability, and failure handling.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
Billing is not only payment collection. Product access depends on a trustworthy entitlement boundary that keeps provider events, plan rules, and API authorization consistent.
I would model plans and entitlements separately from payment provider records. Provider webhooks update subscription state through an idempotent ingestion path, then the application derives effective entitlements for the account. Product APIs check those entitlements server-side before allowing gated actions. The UI can display plan state, but it cannot be the source of access truth.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I would handle lifecycle states such as trialing, active, past due, cancelled, expired, and grace period. Plan changes may be immediate or scheduled for the next billing period, so the access layer needs clear effective dates. Webhooks can arrive late, duplicated, or out of order, so updates need event ids, timestamps, and reconciliation jobs. Support overrides need expiry, reason, and audit records.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I would add a periodic reconciliation job with the billing provider, alerts for webhook failures, and a cached entitlement read model with fast invalidation. Access checks should fail closed or degraded based on product risk; for example, read access may continue during provider outage while privileged write actions are blocked. I would record why access was denied so support can distinguish plan limits from stale billing state. I would also define plan migration behavior for existing customers, audit entitlement overrides, and monitor entitlement mismatches, webhook lag, failed checks, override usage, and migration errors.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Trusting the frontend to decide plan access.
Treating payment provider state as the only local model.
No idempotency for billing webhooks.
No grace-period or cancellation behavior.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Cannot define effective entitlements at a point in time.
Ignores out-of-order provider events.
No reconciliation path with the billing provider.
Support overrides have no expiry or audit trail.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

How would you handle delayed or duplicate billing webhooks?
Where would entitlement checks live?
What happens during a billing provider outage?

Continue the section

Next in Core Designs: Support Impersonation

Step 28 of 30

Design support impersonation

Opening drill

System designHard~20 minCore Designs / 27 of 30

Interview question

Design a backend boundary where subscription plans control which product features an account can use.

Design subscription entitlements and access

Designs plan entitlements, provider webhooks, idempotent billing updates, access checks, grace periods, and support overrides.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Entitlement modeling, billing provider events, idempotency, access checks, plan changes, grace periods, auditability, and failure handling.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
Billing is not only payment collection. Product access depends on a trustworthy entitlement boundary that keeps provider events, plan rules, and API authorization consistent.
I would model plans and entitlements separately from payment provider records. Provider webhooks update subscription state through an idempotent ingestion path, then the application derives effective entitlements for the account. Product APIs check those entitlements server-side before allowing gated actions. The UI can display plan state, but it cannot be the source of access truth.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I would handle lifecycle states such as trialing, active, past due, cancelled, expired, and grace period. Plan changes may be immediate or scheduled for the next billing period, so the access layer needs clear effective dates. Webhooks can arrive late, duplicated, or out of order, so updates need event ids, timestamps, and reconciliation jobs. Support overrides need expiry, reason, and audit records.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I would add a periodic reconciliation job with the billing provider, alerts for webhook failures, and a cached entitlement read model with fast invalidation. Access checks should fail closed or degraded based on product risk; for example, read access may continue during provider outage while privileged write actions are blocked. I would record why access was denied so support can distinguish plan limits from stale billing state. I would also define plan migration behavior for existing customers, audit entitlement overrides, and monitor entitlement mismatches, webhook lag, failed checks, override usage, and migration errors.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Trusting the frontend to decide plan access.
Treating payment provider state as the only local model.
No idempotency for billing webhooks.
No grace-period or cancellation behavior.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Cannot define effective entitlements at a point in time.
Ignores out-of-order provider events.
No reconciliation path with the billing provider.
Support overrides have no expiry or audit trail.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

How would you handle delayed or duplicate billing webhooks?
Where would entitlement checks live?
What happens during a billing provider outage?

Continue the section

Next in Core Designs: Support Impersonation

Step 28 of 30

Design support impersonation

Design a backend boundary where subscription plans control which product features an account can use.

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section

Design a backend boundary where subscription plans control which product features an account can use.

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section