Cloud Architect

Company Description

Molecular Connections (MC) has over two decades of experience in delivering Big Data and Data Science Solutions, leveraging AI-powered proprietary models to drive digital transformation for clients. MC specializes in AI, ML, and Linked Data Store technology to create efficiencies across various industries, including pharma and STEM, enabling content engineering and generating new revenue streams. Recognized for innovation, MC collaborates with global leaders and offers end-to-end software development and data insights powered by proprietary platforms. Ranked among the top 15 best companies for women to work for in India, MC emphasizes diversity and excellence in its workforce. Subsidiaries include Molecular Connections Analytics and Molecular Connections Research.

Role Description

The Cloud Architect is a hands-on, build-oriented role responsible for designing, scaling, and operating the cloud platform that MC's Platforms' product and AI infrastructure. This role is AWS-first and DevOps-native, embedded within Product Technology and Platform, and owns the architecture of a multitenant environment serving multiple internal and external workloads. Reliability and cost efficiency are outcomes of good architecture, not the starting point.

Key Responsibilities

• Design and operate a scalable, multitenant AWS platform serving multiple product lines and customer environments, with clear tenant isolation, shared services, and environment segmentation.
• Own infrastructure-as-code at platform scale - Terraform, CI/CD pipelines, environment promotion patterns, and drift management.
• Establish DevOps-native engineering practices across cloud operations: GitOps workflows, automated infrastructure testing, and self-service provisioning for product engineering teams.
• Design and operate cloud infrastructure supporting AI workloads - including model inference and data pipelines, with a focus on reliability, performance, and observability.
• Define compute, storage, networking, and observability standards across environments; embed cost transparency and governance as a byproduct of well architected infrastructure.
• Support migrations and production readiness initiatives.
• Leverage automation and AI-assisted tooling to reduce operational toil across capacity planning, anomaly detection, and incident triage.

What Success Looks Like

Within the first 6–12 months, the Cloud Architect will have: 

• Delivered a well-architected, multitenant AWS platform with documented standards, IaC coverage, and self-service provisioning for engineering teams.
• AI and data workloads running reliably across environments, with observable performance and clear operational runbooks.
• Reduced operational toil through standardized, automated patterns and GitOps native workflows.
• Cloud costs that are transparent and predictable; a natural result of well governed architecture, not a separate workstream.

Qualifications Education & Experience:

• 7+ years in cloud engineering or architecture roles.
• Deep, hands-on AWS expertise (primary cloud); proven experience designing multitenant architectures with tenant isolation, shared services, and environment segmentation at scale.
• Infrastructure-as-code expertise at team scale - Terraform required; experience with Terragrunt, Atlantis, or module-based IaC governance preferred.
• Strong DevOps engineering background - CI/CD pipeline design, GitOps workflows, and experience building self-service platform capabilities for product engineering teams.
• Experience supporting AI/ML workloads in cloud environments (inference, training, or data-intensive pipelines).
• Understands the cost implications of architectural decisions and can implement tagging, allocation, and rightsizing governance without it becoming the primary focus of the role.

Soft Skills:

• Operations-first, pragmatic mindset - comfortable owning outcomes, not just recommendations.
• Able to drive architectural decisions through influence rather than authority, and communicate trade-offs clearly to both technical and non-technical stakeholders.
• Brings solutions and concrete proposals when confronted with ambiguity or competing constraints.