Azure Cosmos DB Architect
Azure Cosmos DB Architect
Posted 9 days ago
SENIORITY
Lead
About the role
- Design, implement, and optimize Azure Cosmos DB solutions for high-volume transactional workloads.
- Define and implement data modeling strategies, partition key design, indexing policies, and data lifecycle management.
- Architect highly available, resilient, and scalable solutions leveraging Cosmos DB best practices.
- Monitor and optimize RU consumption, throughput, latency, and overall database performance.
- Troubleshoot production issues, investigate performance bottlenecks, and implement corrective actions.
- Support day-to-day operational activities including deployments, schema evolution, capacity planning, and incident resolution.
- Partner with application, infrastructure, and architecture teams to ensure optimal integration with Azure services.
- Establish disaster recovery, backup, and business continuity strategies.
- Create operational runbooks, documentation, and engineering standards.
- Provide recommendations on cost optimization, scalability, and long-term platform improvements.
- 7+ years of software engineering and database development experience.
- 3+ years of hands-on Azure Cosmos DB experience in production environments.
- Strong experience with:o Cosmos DB data modeling and partitioning strategieso Query optimization and performance tuningo Throughput management (RU/s optimization)o Indexing policies and change feed processingo Multi-region deployment and global distributiono High availability and disaster recovery patternso Monitoring and observability tools
- Experience supporting high-volume, always-on enterprise applications.
- Strong understanding of cloud-native architectures and distributed systems.
- Experience with Azure services such as Functions, App Services, AKS, Event Hubs, Service Bus, and Application Insights.
- Strong troubleshooting, communication, and documentation skills.
- Experience in financial services or regulated industries.
- Knowledge of microservices architecture and event-driven systems.
- Experience with .NET and/or Java-based applications.
- Familiarity with DevOps practices, CI/CD pipelines, and Infrastructure as Code.
- Experience establishing governance, operational standards, and performance best practices.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
