3 ms·
> embellish your resume and work history. If you’ve read a tutorial on a technology, you list it. I'm going through a huge pile of resumes for a role I have op
by bojo 3y ago
> embellish your resume and work history. If you’ve read a tutorial on a technology, you list it.
I'm going through a huge pile of resumes for a role I have open this week and these are getting thrown out immediately. I have no interest in reading through 6 pages of bullet points with keywords bolded. It's tacky, too information dense, and doesn't call out what you are actually good at nor how you've applied it.
- throwaway202351 3y agoI think the 'correct' (from the perspective of getting an interview) approach would be to personalize your resume to include skills that are called out in the listing, even if you've just read a tutorial on it. Not to list a ton of irrelevant skills. An example would be if you had 5 years of experience in AWS and only a few tutorials of GCP for experience, but the listing specifically wants GCP skills, you list it. Not a case where you have 5 years of backend experience and start applying to senior frontend positions because you went through a React tutorial.