I've been in the DevOps field for a couple of years, and as I update my resume, I'm finding it tricky to categorize all my skills. There are so many tools and technologies I've learned that it feels overwhelming to put them on paper. For context, I'm focusing on the Skills section, typically located at the top of my resume. I had previously organized my skills under 'Languages:' and 'Technologies:', but I'm considering breaking down the technologies into more specific groups.
Here's my current thought for categorization:
- **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 additional skills:
- IT/compliance: Entra ID (Azure AD), OAuth2, SSO, IAM
- Other: Networking, Kafka, GCP (minimal), CDNs
There are some tools I've used in the past that I've decided to cut, such as MySQL, MariaDB, and MongoDB. However, I'm uncertain if I should keep other technologies, especially AWS services, which appear frequently in job postings. I tend to avoid individual AWS services in my list, but should I mention EKS, VPC, EC2, IAM, and Lambda, or just include them in the experience section? I really want to make my resume stand out and clearly reflect my skills. Any advice or experiences you can share would be greatly appreciated!
4 Answers
Consider grouping your skills by their function rather than the vendor. For example, just label AWS-related skills under a general 'Cloud Technologies' heading unless a job specifically asks for something detailed. And ditch any outdated tech you've not used in years. Tools like Jira are better mentioned in your experience section instead of the skills list to keep it concise.
Customizing your skills section for each application is crucial. I usually break it down into sections like Infrastructure as Code (Terraform, Ansible), CI/CD (GitLab), and Observability (Grafana, Prometheus). Also, mentioning specific projects alongside these skills can really showcase your practical experience, which recruiters love to see.
It's all about tailoring your resume! Focus on the skills that directly relate to the positions you're interested in. Listing every single tool can clutter your resume and dilute your strengths. Highlight those skills where you have real experience and can offer examples of how you've used them effectively.
Good question! I'm curious to see how others categorize their skills too. Just one note — it might be confusing to list AWS, Kubernetes, Terraform, and Docker under CI/CD since they are not exclusively CI/CD tools. A more accurate categorization may help you stand out.
That’s exactly the challenge—finding the right titles to define what you've done. Instead of CI/CD, maybe use something like 'Deployment Technologies' to convey that broader idea.
Absolutely! I tend to keep a generic version of my resume for quick applications, but I always make sure to elaborate on the skills in the experience section. Even the skills not listed in job descriptions can help you in interviews by providing talking points.