We are seeking a highly experienced Database Architect to join our Platform Modernization team for a critical discovery and design phase. In this role, you will lead the technical evaluation, strategy, and planning required to migrate our application database ecosystem from our legacy cloud platform (Azure 1.0) to our next-generation modernized landing zone (Azure 2.0).
As a key architectural lead, you will analyze existing on-premise and legacy cloud database deployments, mapping them to optimized, secure, and modern Azure-managed services. This role demands a strong mix of deep hands-on database expertise, migration design pattern knowledge, and cross-functional alignment capabilities.
Key Responsibilities1. Discovery, Assessment & Mapping
- Legacy Assessment: Evaluate the existing database landscape across Azure 1.0 (IaaS and early PaaS environments) and legacy on-premises systems.
- Modern Mapping: Map legacy and on-premises database features to modern Azure Managed Database services(such as Azure SQL Managed Instance, Azure SQL Database, Azure Database for PostgreSQL/MySQL flexible servers).
- Cosmos DB Footprint Optimization: Analyze the current Azure Cosmos DB footprint to evaluate partition key strategies, optimize Request Units (RUs) configurations (Autoscale vs. Provisioned), and design highly resilient, multi-region replication topologies aligned with Azure 2.0 standards.
2. Migration Architecture & Strategy
- End-to-End DB Migration Planning: Design highly resilient, low-downtime, and zero-data-loss database migration pathways utilizing industry-standard tools (such as Azure Database Migration Service, DMS, or native replication features).
- Connection String & Security Architecture: Define and architect the transition strategy for application connection strings, standardizing secure access using Azure Key Vault, Managed Identities, and Private Endpoints to isolate and secure database traffic.
- Objective-2 Interlock: Lead architectural and milestone synchronizations (Objective-2 Interlock) across application engineering teams, cloud platform architects, and security officers to ensure database deliverables align with broader program milestones.
3. Post-Migration & Cutover Validation
- Post-Repoint Validation Plan: Design a robust, repeatable, and automated validation framework to run immediately after application services are repointed to Azure 2.0 databases.
- Performance & Integrity Auditing: Ensure the validation plan thoroughly tests data reconciliation, transactional integrity, latency baselines, and connection-pooling stability.
- Rollback Engineering: Design comprehensive rollback runbooks to mitigate risk during production migration cutover windows.
