Timeline for I worked for a company affiliated with a very publicly failed project. Should I take it off my resume?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 6, 2013 at 18:38 | comment | added | SnakeDoc | Now, if you were in Management at CGI when this went down, then you'd have a lot more to worry about. | |
| Dec 5, 2013 at 21:55 | history | edited | IDrinkandIKnowThings | CC BY-SA 3.0 |
Readability and grammar.
|
| Dec 4, 2013 at 20:06 | comment | added | Kaz | But you do not necessarily work for that person! If you are hired there, you might not actually work with the person who tossed the resumes of others. And anyway, there is nothing wrong with that person. I'm not an idiot, or hard to work with, yet I'd tend to toss the resume. You're not hurting anyone by tossing their application; just protecting your interests. If you have 50 applications for one job, you must necessarily toss 49, and you cannot worry too much about which combinations of 49 make you an asshole more than others. | |
| Dec 4, 2013 at 19:39 | comment | added | HLGEM | Yes and anyone who would reject you solely becasue you worked for such a company is someone you would not want to work for anyway. So keeping it in is a win all the way around. | |
| Dec 4, 2013 at 19:31 | comment | added | Kaz | The fact is that if you're not coming from a company where there was a public disaster, there is no such suspicion. There is a possibility of suspicion here. You could have had something to do with that project. People who reject resumes from a big pile use heuristics, not deductive logic. Although with passage of time few will remember, the question is what to do in your resume now, while the recent events are fresh. | |
| Dec 4, 2013 at 19:12 | history | answered | HLGEM | CC BY-SA 3.0 |