3 ms·
You should not be creating a resume that you will then send to multiple jobs. You craft individual resumes for each job posting, using that posting's own keywor
by pc86 10y ago
You should not be creating a resume that you will then send to multiple jobs. You craft individual resumes for each job posting, using that posting's own keywords and required/recommended/nice-to-have skill set.
Resume screening is about cutting a stack of 100 down to 10, so it's all about finding a reason to say "No." If the job calls for C# WebApi and Angular experience and you start listing Python or Go projects, that's an easy no.
- vonmoltke 10y agoI thought the industry was desperate for talent. This doesn't sound like the kind of mechanism you would use in such a situation.
- e12e 10y agoDo you really want to aim mostly for the organizations that are "desperate for talent", or would you like to be contacted by the employers you would really like to work for? (Not that the sets need have no intersections..)
- vonmoltke 10y agoI'm under the impression that everyone is desperate for talent. Even the top-tier companies, apparently: https://news.ycombinator.com/item?id=12059056 https://news.ycombinator.com/item?id=12059056. So, are all these people just blowing smoke up out collective asses? I see conflicting statements like the one I responded to here and the one I linked posted all the time.
- pc86 10y agoRegardless of the current market for talent (which will change drastically based on the sector, the specific job, the company, the geographic region, etc), why would you not want to give yourself the best chance? Generic resumes receive a fraction of the responses that resumes crafted for the position do. This has been well studied and cited. So why not take 20 minutes to customize a resume?