Sravya Kanagala
Cloud Architect
No profile blueprint available for this candidate.
Job Compatibility Score
Cloud Architect
15%Total Score: 15/100
Key Insights:
This candidate is a strong Data Analyst and Cloud/DevOps Analytics Engineer, but they are not a fit for the Cloud Architect role as defined by the job description. The core mismatch is in the level of strategic responsibility, depth of architectural design, and primary platform expertise.
- Role Misalignment: The candidate's experience is centered on building and optimizing data pipelines, analytics, and dashboards within cloud environments. The JD requires designing the cloud environment itself—defining standards, leading migrations, and governing architecture. This is a fundamental difference between a builder/consumer of cloud services and an architect of the cloud foundation.
- Platform Mismatch: The role mandates Google Cloud Platform (GCP) expertise. The candidate's proven, hands-on experience is exclusively with AWS and Azure. This is a critical gap for an architect role where deep platform-specific knowledge is non-negotiable.
- Skill Focus: Their skills are heavily weighted towards data engineering, analytics, and DevOps automation. While they touch on cloud services, the JD requires deep, proven expertise in core architectural domains like enterprise-scale IAM, networking, security frameworks, and cost governance design—which are not evidenced in the resume.
- Experience Level: With ~3 years of experience primarily in data analysis, the candidate is at a mid-level individual contributor level. A Cloud Architect role typically requires more senior, strategic experience (often 7+ years) with a proven track record in design and leadership, which is not yet present.
Recommendation: Do not advance for this Cloud Architect position. However, they could be a high-potential candidate for a Cloud Data Engineer, Analytics Engineer, or DevOps-focused data role where their skills in pipeline automation, cloud data services, and analytics would be a direct match.
📊 Candidate Evaluation Table
| Category | Details from Job Description | Claimed Experience | Relevant Experience | Evidence from Resume | Score |
|---|---|---|---|---|---|
| Job Titles | Cloud Architect | Not explicitly claimed. Titles are Data Scientist, Data Analyst. | 0 years. No direct architectural title or stated architectural responsibilities. | Professional titles are "Data Scientist" and "Data Analyst – Cloud & ML Systems". No "Architect" title. | 0/15 |
| Primary Role-Based Skills | Design end-to-end cloud architectures | Not claimed. | Not evidenced. Resume focuses on building components within an architecture, not designing the architecture itself. | Experience describes using AWS/Azure services for data pipelines and dashboards, not designing overarching cloud solutions. | 0/20 |
| Lead migration to GCP | Not claimed. | Not evidenced. No mention of cloud migration projects. | Resume details building new pipelines and analytics on cloud, not migrating existing workloads. | 0 | |
| Implement security, IAM, networking, compliance controls | IAM & compliance mentioned indirectly. | Limited evidence in an analytical/supporting role, not an architectural/implementation role. | "Supported compliance and audit initiatives (SOC 2, ISO 27001) through improved RBAC documentation and operational reporting." This is analysis/reporting, not design/implementation. | 2 | |
| Optimize cloud costs using governance | Not claimed. | Not evidenced. | No mention of cost optimization, budgeting, or resource governance initiatives. | 0 | |
| Define cloud standards and best practices | Not claimed. | Not evidenced. | No mention of creating standards, reference architectures, or governance frameworks. | 0 | |
| Secondary Skills | Support CI/CD pipelines and infrastructure automation | CI/CD claimed under DevOps skills. | Evidence of automation and orchestration, but for data workflows, not core infrastructure. | "DevOps & Automation: CI/CD Pipelines, GitHub Actions, Apache Airflow." Used for data pipeline orchestration (e.g., Airflow ETL pipelines). | 5/10 |
| Collaborate with engineering, data, DevOps, security teams | Implied in role descriptions. | Strong evidence of cross-functional collaboration. | Frequent mentions: "Collaborated with cross-functional teams," "Partnered with cloud and security teams," "Partnered with business teams." | 5 | |
| Tools & Platforms | Google Cloud Platform (GCP) | Not claimed. | 0 years. Resume shows AWS and Azure only. | Cloud Platforms listed: "AWS (S3, EC2, Lambda...), Azure (Azure Data Lake, Monitor, IAM)." GCP is absent. | 0/10 |
| Certifications | Not specified in JD | Not applicable. | Not applicable. | No certifications listed. | N/A |
| Experience Level | Senior-level, implied by architect role (typically 7+ yrs in cloud/ infra). | 3+ years in data/analytics roles. | ~3 years in data analysis/engineering, not in cloud architecture. | Professional overview states "3+ years of experience" in data/cloud analytics engineering. | 3/10 |
| Domain Expertise | Not explicitly specified. | Not specifically claimed. | Domain experience in E-commerce, Energy/O&G (implied from UOGEI), and general tech. | Worked at NOON (e-commerce), UOGEI (energy), Diyar United Co. (general), Unisoft (tech). | N/A |
| Consistency Across Summary, Experience, and Education | N/A | Profile is consistent as a Data Analyst/Cloud Data Engineer. | Experience and skills are highly consistent for a data-focused role, but inconsistent with the Cloud Architect JD. | Summary, experience, and skills sections all align perfectly to a data analytics and cloud data engineering profile. | 0/10 |
Scoring Notes: Points were only awarded where direct, relevant evidence from the resume matched the JD requirement. The score reflects the significant gap between the candidate's data engineering profile and the strategic cloud architecture requirements. The final score of 15/100 is driven by secondary skill collaboration and partial secondary skill alignment, which are insufficient for the primary role needs.