Lead Data Architect; Google spanner

Overview

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.

• Define the Logical Canonical Data Model (LCDM) independent of physical storage.
• Design Spanner-native physical schemas: row key distribution (hotspot avoidance); interleaving decisions; secondary index strategy; decide where denormalization, projections, or materialized views are required.

• Define transaction boundaries under Spanner constraints: single-partition vs multi-partition transactions.
• Atomicity and consistency trade-offs.
• Classify workloads by strong consistency vs bounded staleness tolerance.
• Define idempotency and retry-safe patterns.

• Work with QA and platform teams to validate: CRUD contracts; query semantics; transaction in variants.
• Review and sign off on schema compatibility scorecards.

• Participate in workload replay analysis.
• Diagnose and resolve: hot key risks; transaction conflicts; index amplification.
• Size Spanner instances and estimate cost envelopes.

• 10+ years in large-scale data architecture
• Deep expertise in Google Spanner internals:
  True Time; distributed transactions; synchronous replication.
• Experience designing petabyte-scale, multi-region OLTP systems
• Distributed consistency models; failure modes in globally distributed databases
• Prior Oracle → distributed DB migration experience strongly preferred
• Canonical logical data model;
  Spanner physical schemas & index strategies
• Transaction design guidelines; performance readiness assessments; migration readiness sign-off per domain

Salary Range- $120,000-$130,000 a year