#Chompy resume, DevOps-Infra
1 messages · Page 1 of 1 (latest)
Chompy resume, DevOps-Infra
My personal opinion is that you would benefit from listing the skills used at each job in its own section instead of inline throughout the text so you can have more characters to describe what you did and the impact it had
also check for consistent capitalization of names, I see both Python and python
I feel like "Debugging X" is just part of the job that isn't worth a bullet, but idk
"Migrate AWS pipelines" migrate to what?
Same thing as my old resume: "lead" instead of "led"
It'd be wise to review the use of acronyms as well, I don't know what SME or EMR mean for example
"reduction of operational tasks by 60%" as in you reduced the amount of manual tasks?
@languid thicket That's a great idea, list the overall tech stack above (similar to your resume) and highlight the impact. Yeap.... debugging was 100% a filler bullet, i'll change that. I'll remove some of the terms such as SME (subject matter expert). EMR (is an aws service....so unsure if to keep or not), that is why I defined it as EMR Cluster. For reduction of ops tasks, yeah that was manual ops stuff
2nd revision:
Bumping for 2nd revision review @languid thicket
Unsure about the wording of "Promoted to lead and implement AWS data infrastructure..."
"resulting in observability into platform services" maybe just "resulting in increased observability"?
what do you mean by "designed data patterns"?
"100 users apart of the Enterprised Data teams" should this read "as part"?
You have another "Lead" where I think you want "Led"
YAML not Yaml
Conestoga College still relevant? Could free some space if you don't think so
otherwise looking okay
sorry for the delayed response, been away for a bit
Not sure why i've kept Conestoga in there. It was my first diploma so i think it helps to showcase a different line of thinking (business focus paired with my engineering side?)