Lead Data Architect (Google Spanner)Own the target-state data architecture on Google Spanner, ensuring the new data model satisfies functional correctness, performance SLOs, and transactional semantics required by 1000+ applications—before large-scale app rewrites occur. This role is not a schema converter. It is a distributed systems architect role.Key Responsibilities Data Architecture & ModelingDefine the Logical Canonical Data Model (LCDM) independent of physical storage.Design Spanner-native physical schemas: Primary key strategyRow key distribution (hotspot avoidance)Interleaving decisionsSecondary index strategyDecide where denormalization, projections, or materialized views are required.Transaction & Consistency DesignDefine transaction boundaries under Spanner constraints: Single-partition vs multi-partition transactionsAtomicity and consistency trade-offsClassify workloads by strong consistency vs bounded staleness tolerance.Define idempotency and retry-safe patterns.Compatibility & Contract ValidationWork with QA and platform teams to validate: CRUD contractsQuery semanticsTransaction invariantsReview and sign off on schema compatibility scorecards.Performance & ScalabilityParticipate in workload replay analysis.Diagnose and resolve: Hot key risksTransaction conflictsIndex amplificationSize Spanner instances and estimate cost envelopes.LeadershipAct as final authority for Spanner data design decisions.Mentor domain architects and engineers.Provide executive-level architectural rationale.Required Skills & Experience10+ years in large-scale data architectureDeep expertise in Google Spanner internals: TrueTimeDistributed transactionsSynchronous replicationExperience designing petabyte-scale, multi-region OLTP systemsStrong understanding of: Distributed consistency modelsFailure modes in globally distributed databasesPrior Oracle ?
distributed DB migration experience strongly preferred