Your resume, diagnosed.
Analysis for adaeze_nwosu_resume_v6.pdf · 1 page · target: Sr. Cloud Engineer
Overall Score
86 / 100
+12 since last scan
Last analyzed 2 min ago
ATS Compatibility
92Excellent, parses cleanly across all major systems.
Keyword Match
87Matched 27 of 31 target keywords for Sr. Cloud Engineer roles.
Outcome Density
74Most bullets describe activity, not outcome. Reframe 6 lines.
Action-Verb Strength
84Solid. Replace 'responsible for' (3x) with stronger verbs.
Formatting Cleanliness
96Clean structure, consistent spacing, no parsing risks.
Story Coherence
81Clear trajectory. Strengthen the 2022→2024 leap with metrics.
6 bullets describe what you did, not what changed
highConvert activity-bullets to outcomes: uptime, latency, $ saved, MTTR, etc.
Keyword 'IaC' missing, appears in 78% of target JDs
medAdd 'Terraform · IaC' alongside your AWS work in 2023–2024.
LinkedIn headline misaligned with resume target
medSync headline to 'Sr. Cloud Engineer | Terraform | AWS | Kubernetes'.
Two bullets exceed two lines
lowTrim 3rd and 5th bullets in 2022 role for scanability.
- • Bullets quantify production outcomes in 60% of roles
- • ATS-friendly structure with no parsing risks
- • Strong action verbs in the most recent role
- • Certifications and projects positioned correctly
Suggested rewrites
Before vs after, three sample bullets
Before
Responsible for managing the company's AWS environment and supporting various workloads.After
Owned a 250-account AWS organization across 6 regions; cut idle compute spend by 31% ($410k / yr) via Spot scheduling and right-sizing automation.Before
Worked on Terraform automation for cloud resources.After
Authored 40+ Terraform modules adopted by 3 engineering teams; eliminated 90% of manual cloud provisioning and reduced new-stand-up time from 5 days to 2 hours.Before
Helped improve security posture across the infrastructure.After
Drove cross-team migration to SCP guardrails + Splunk SIEM rules; reduced high-severity findings by 64% in two quarters.