Skip to lesson
Exit
The Role & the Core Services Charter1 / 2

1 min lesson

Have a defensible opinion, not a neutral summary

Walk through each part of "Have a defensible opinion, not a neutral summary", then explain what each one does.

Step 1 of 2

Have a defensible opinion, not a neutral summary
Delivery semantics
When you choose at-least-once with idempotency over chasing exactly-once and why.
Backpressure
How you shed or queue load under a burst instead of falling over.
Idempotency
Where the idempotency key lives and how you dedupe on the consumer side.
Reliability budget
What SLO you'd set for auth latency and what you'd trade to hold it.

"It depends" is a fine opening, but it cannot be the whole answer. A senior backend leader is hired for judgment, which means committing to a position and naming the conditions that would change it. Neutral summaries of both sides read as someone who has read about the tradeoff but never had to own it at 3am.

OAuth 2.0 / OIDCOpenID Connect. The modern single sign-on standard, built as an identity layer on top of OAuth 2.0. Where SAML is XML and enterprise-legacy, OIDC is JSON and what newer tools implement first. Press Enter for the full definition.JWTRBACRole-Based Access Control. Granting permissions by role rather than configuring each person individually. Press Enter for the full definition.token rotationat-least-onceidempotency keysbackpressureDLQSLOsrate limiting
Interview move

For each bonus tag - OAuth, JWT, RBACRole-Based Access Control. Granting permissions by role rather than configuring each person individually. Press Enter for the full definition., event-driven, developer-platform - prepare a one-sentence proof of use that includes the tradeoff you hit. "I moved us to short-lived JWTs with refresh-token rotation because session-table lookups were the hot path and I accepted the revocation-latency window that creates" beats simply listing "JWT" on a slide. The tradeoff is what proves you actually shipped it.