I've been in the DevOps field for a few years and I'm trying to update my resume to better showcase my skills. I have a lot of services and technologies I've learned over time, and it's becoming crowded. For my skills section, I used to have categories like 'Languages:' and 'Technologies:', but I'm considering breaking it down further.
Currently, I'm thinking of sections like:
**CI/CD:** AWS, Kubernetes, Terraform, Helm, ArgoCD, Jenkins, Linux, Docker, GitHub Actions
**Monitoring:** Prometheus, Grafana, Fluentbit, Elasticsearch, Kibana
**Languages:** JavaScript, Python, SQL, Bash, Go, C/C++
I also want to include some IT/compliance skills like Entra ID (Azure AD), OAuth2, SSO, and IAM, plus some additional skills in Networking, Kafka, and GCP, but I'm unsure how to fit everything neatly. I've already cut out some older technologies I no longer use like MySQL and .NET.
I notice job descriptions often recommend specific AWS services as well. Should I mention services like EKS, VPC, EC2, IAM, and Lambda on my resume, or keep them in the experience section? I'd love to hear your thoughts and experiences on this! Thanks!
2 Answers
Group your skills by function rather than by vendor. For example, keep a general 'Cloud' category for AWS and avoid listing old tech you haven't used in years. Tools like Jira and Bitbucket can go in the experience section instead of the skills section to keep things concise.
I think it's best to focus on the key skills that match the jobs you're applying for. If you can show evidence of your skills during interviews, that's worth more than listing tons of them on paper. Tailor your resume for each job, but have a general version on hand too. Maybe keep your skills section lean—with just the most relevant stuff highlighted.
I agree! Having a tailored resume is crucial, but a general one is useful for quick applications. Always explain your skills in your experience section to provide context.