Oracle Product Designer (Engineering) Case: Designing Autonomous Database Provisioning and Lifecycle on OCI

This case mirrors real Oracle enterprise-cloud scenarios and emphasizes security-first, data-driven design within the Redwood Design System. You’ll design the end-to-end provisioning and lifecycle experience for Oracle Autonomous Database (ADB) on Oracle Cloud Infrastructure (OCI) for a large enterprise migrating from on‑premises. What the case covers: - Problem framing: Align on business goals (migration velocity, security posture, cost governance), target users (Cloud Admin, DBA, App Developer, FinOps Analyst, Security/Compliance), and constraints unique to OCI (tenancies, compartments, regions/ADs, IAM policies, Keys/OCIR, tagging, quotas). - Core flows: 1) Create ADB wizard (networking/VCN selection, keys/KMS, workload type, sizing/auto-scaling, tagging, cost preview); 2) Instance details & lifecycle (start/stop/scale/clone, backup/restore, rotate keys, patch windows, connection strings); 3) Error/approval handling (policy denies, quota limits, break-glass flows, audit trails); 4) Migration assist (from on‑prem to ADB, cutover and validation UX); 5) Observability (performance metrics, logs, alerts, incident triage). - Enterprise non-functionals: WCAG 2.2 AA accessibility, localization/RTL readiness, performance budgets for heavy data tables, data residency/compliance cues, consistent Redwood components and patterns across OCI services, API/CLI parity considerations. - Collaboration & constraints: Tradeoffs with engineering on feasibility and sequencing, alignment with PM on MVP vs. future iterations, security/legal review for regulated industries, support/readiness and documentation touchpoints. - Success metrics & validation: Define leading indicators (time-to-provision, policy-deny resolution rate, error rate, task success) and lagging indicators (adoption, cost overruns avoided, support ticket volume). Propose a lean usability test plan with enterprise participants and a telemetry plan (events for wizard drop-off, most-corrective actions, empty-state engagement). - Deliverables during session: Clarifying questions, problem statement, success criteria, IA map of OCI context (tenancy/compartments), key user flows, low‑fi wireframes of 2–3 critical screens (create wizard, instance detail, error/approval), edge cases (network/policy/quota failures), and a brief rollout plan. - Follow-up prompt (if time allows): Extend the design for multi‑cloud connectivity or incident response for a regional outage, explaining how the UI communicates failover and data safety. Interview flow (Oracle style): - 5 min: Context brief (interviewer shares constraints, enterprise personas, Redwood guardrails). - 10 min: Clarifying questions and problem framing (candidate drives). - 25 min: System thinking, IA, and flow sketches with explicit OCI/IAM considerations. - 20 min: Wireframe walk-through (accessibility, localization, error states, cost transparency, auditability). - 10 min: Metrics, experiment plan, and MVP sequencing with engineering dependencies. - 5 min: Reflection and tradeoff discussion. Evaluation rubric (weighted): Problem framing (20%), System/IA thinking across OCI constructs (20%), Security/compliance depth and failure-mode handling (20%), Interaction/visual execution with Redwood patterns (15%), Communication and cross‑functional collaboration (15%), Metrics/test plan rigor (10%). Bar-raising signals include: precise handling of IAM policy denies and quota errors, clear cost governance UX, and parity thinking across UI/API/CLI.