#Concerned that my resume might be too technical

1 messages · Page 1 of 1 (latest)

grand gorge
#

Concerned that my resume might be too technical

elder raft
#

i had a few feedbacks, the first role description needs to be fully past tense to match the rest.

yea, i think the description of the roles is too much info about implementation and too technical. Put the descriptions of your tasks in plain language. i then would have technologies at the end of the role and list the things and tools used for the role. For your project, mention the features of the app, not just saying built out and app that did this

#

oh, don't include end date for first then, when you are glossing over easy to miss the date is in the future

#

i actually like most of the phrasing, its just throwing me off that you are mentioning all the specific amazon services. As reading it, i simply just need to know it was previously hosted on (something bad/ not efficient

#

and that you made the decision to migrate to an auto scaled resource conscious service

#

idk if that makes sense

#

i can pm you a description of one of my resume role at amazon if you need example

elder raft
#

i think its better now, i am being overly picky and changed few words to sound better

Migrated Digital Time Card service, used by 6000+ workers daily, from resource-intensive VMs to auto-scaling containers, improving scalability and reducing infrastructure costs by $10,000 annually.

Migrated traffic-data pipeline processing 250 million events daily across cloud services to a scalable Kubernetes cluster. Set up manifests, CI/CD pipelines, and Kafka topics, achieving a 50% reduction in infrastructure costs.

Designed a CI/CD pipeline on Azure DevOps, leveraging Docker multi-stage builds and pipeline caching, reducing application build times from 3 minutes to 80 seconds.

simple ivy
#

If you put up an updated resume and tag me, I'll see if I can take a look sometime, but the points udddy had above sound good (last one is a bit bloated bc it's just basic docker best practices so I'd reduce it to one line - but as an intern, you're fine with this)

simple ivy
#

General

  • Switch location / dates in education for formatting consistency + relevance
  • Remove courses (adds nothing here)
  • If your roles were internships, please specify that in your title or your resume will get thrown out by a lot of people
  • The technologies bullet is a bit awkward and rarely works for students - I lean towards removing them here or try to integrate the (relevant) technologies into your bullets
  • Projects are good, I would just specify the other parts of the stack if you can for recruiters (React, TypeScript, Dart) - you're not at a high enough level where you can get away with excluding it
  • Your awards should specify the project, not just some generic bs like "Designed a project". You can remove the bulleting to save space on the indent, and consider leading with the placement first.
  • This is one of the few times I will say the "Concepts" section on your resume is acceptable, but it's always better to incorporate it in your experience / projects.

Role 1

  • Good project, but you can (should) make the purpose of this clearer - I'm not exactly sure how this product would be used

Role 2

  • How did you address bottlenecks?
  • You led a monitoring initiative? Can you elaborate on this?

Role 3

  • Nit: "Revamped CI/CD pipelines to utilize caching"
  • The second to last bullet doesn't need to have that fluff ("greatly improving testing processes")
fluid gorge
#

saving

fluid gorge
fluid gorge
elder raft
#

yes, but also specify what exactly you did. That bullet tells us nothing, what tpe of algorithm did you use to improve speed.. did you change the number of API calls that were hitting database, did you add validations to the frontend so you aren't just sending and doding all the processing in the backend etc

#

those are the more important details than simply saying data in O(1) time and space complexity

#

@fluid gorge