Principal Database Architect, Multi-Region Data Platform

Solvd Inc. is a rapidly growing AI-native consulting and technology services firm delivering enterprise transformation across cloud, data, software engineering, and artificial intelligence. We work with industry-leading organizations to design, build, and operationalize technology solutions that drive measurable business outcomes.

Following the acquisition of Tooploox, a premier AI and product development company, Solvd now offers true end-to-end delivery—from strategic advisory and solution design to custom AI development and enterprise-scale implementation. Our capability centers combine deep technical expertise, proven delivery methodologies, and sector-specific knowledge to address complex business challenges quickly and effectively.

Solvd is delivering a multi-year cloud modernization for a Tier-1 US payments platform: migrating a single-region AWS footprint into a multi-region, ultimately active-active architecture across three phases. The data layer is critical path; it spans Aurora MySQL, Cassandra, ElastiCache (Redis / Valkey), DynamoDB, DocumentDB, OpenSearch, and Neptune. We're hiring a Principal Database Architect to own the data-layer strategy for this program and lead a team of database engineers across both AWS regions. This role will be the senior design authority who can own cross-database DR strategy, RTO/RPO tradeoffs, consistency models, replication patterns, cutover planning, and executive-level technical decisioning. ## What you'll do

• Own the multi-region data architecture across six AWS-native engines: Aurora MySQL, Cassandra, ElastiCache (Redis / Valkey), DynamoDB, DocumentDB, and Neptune. For each, define the cross-region replication pattern (Aurora Global Database, DynamoDB Global Tables, DocumentDB Global Clusters, Cassandra multi-DC, MemoryDB or Valkey global datastore, Neptune Global Database) and the operational model that supports it. - Define and own the per-tier RTO and RPO commitments (Tier 0 / Tier 1 / Tier 2) and the cutover and failback runbooks and perform validation using Fault Injection Service / Game Days. - Sequence the data-layer cutover across all three program phases. Identify strong-consistency vs eventual-consistency decisions per workload, and where active-active is feasible vs where region-sharded ledgers or single-writer with replicated read-models is the right pattern. - Lead a team of Database Engineers across the engines. Set the technical bar, review designs, and unblock implementation. Partner with the client's DB and SRE leadership on architecture decisions and Operational Readiness Reviews. - Translate data-layer constraints into the application decomposition strategy. Where the monolith is being broken up into microservices, advise on data ownership boundaries (DDD-aligned), strangler-fig extraction patterns, CDC pipelines (DMS, DDB Streams, Kafka Connect), and the event-based contracts that decouple services from the monolith. - Produce the audit-grade artifacts the client and their regulators expect: replication runbooks, DR test evidence, RTO and RPO measurement methodology, and Well-Architected Reliability Pillar alignment. ##