4 ms·
* Lots of typos. One is fine. Too many suggests someone who is poor at English communication. It doesn't matter how good someone is, if they build the wrong thi
by muzani 9y ago
* Lots of typos. One is fine. Too many suggests someone who is poor at English communication. It doesn't matter how good someone is, if they build the wrong thing.
* Generic boring template-ish resume. Usually these guys don't care much for craftsmanship.
* Too much specialization. 80% specialization is fine, just not 100%.
* For startups, a history of only working at big companies. Especially at the management level, where they tend to overspend and frustrate programmers.
* For larger teams, someone who has a history of only working solo. Some of these guys refuse to communicate, attend daily stand ups, or do daily commits.
* Putting a salary history in your resume.
- arbie 9y ago> * Generic boring template-ish resume. Usually these guys don't care much for craftsmanship. I thought standardized resumes made it easier for HR systems to parse.
- muzani 9y agoA bit hard to explain without examples, but you can have the usual format just fine. Some minor things like color, jokes, icons, or a slightly different template. But there are just some really lazy, generic types of resumes which make this person seem really cookie cutter. Like they just downloaded the first resume option on Google or MS Word and took out some words, replaced with their own text.