{"schemaVersion":"jobsearcher.job.v1","id":"7394e4af37eb57329dabc612","url":"https://jobsearcher.com/jobs/7394e4af37eb57329dabc612","canonicalUrl":"https://jobsearcher.com/jobs/7394e4af37eb57329dabc612","title":"Lead Data Architect (Google spanner)","description":"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","company":"Clifyx","rawCompany":"clifyx","city":"San Jose","state":"CA","isRemote":false,"isActive":true,"createdAt":"2026-07-24T00:13:18.502Z","occupations":[{"code":"15-1243.00","title":"Database Architects","slug":"database-architects"},{"code":"15-1243.01","title":"Data Warehousing Specialists","slug":"data-warehousing-specialists"},{"code":"15-1299.08","title":"Computer Systems Engineers/Architects","slug":"computer-systems-engineers-architects"}],"industries":[{"code":"541512","title":"Computer Systems Design Services","slug":"computer-systems-design-services"},{"code":"513210","title":"Software Publishers","slug":"software-publishers"},{"code":"541511","title":"Custom Computer Programming Services","slug":"custom-computer-programming-services"}],"jobPosting":{"@context":"https://schema.org","@type":"JobPosting","title":"Lead Data Architect (Google spanner)","description":"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","datePosted":"2026-07-24T00:13:18.502Z","dateModified":"2026-07-24T00:13:18.502Z","hiringOrganization":{"@type":"Organization","name":"Clifyx","sameAs":"https://jobsearcher.com"},"jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"San Jose","addressRegion":"CA","addressCountry":"US"}},"identifier":{"@type":"PropertyValue","name":"JobSearcher","value":"7394e4af37eb57329dabc612"},"url":"https://jobsearcher.com/jobs/7394e4af37eb57329dabc612"}}