Timeline for Should I send an errata after technical interview?
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 26, 2018 at 12:22 | comment | added | pmf | It might come across as obsessive and pedantic in the worst case, and won't make any positive difference, so leave it be. | |
| Jan 26, 2018 at 12:18 | answer | added | kolsyra | timeline score: 0 | |
| Aug 28, 2013 at 11:13 | history | edited | le-doude | CC BY-SA 3.0 |
added 481 characters in body
|
| Aug 7, 2013 at 10:23 | answer | added | Petter Nordlander | timeline score: 2 | |
| Aug 7, 2013 at 9:54 | comment | added | superM | I wouldn't write about the mistake only if it is something very small (like a typo) or something that could be slightly optimized (like re-arranging if-else clauses). | |
| Aug 7, 2013 at 7:39 | history | edited | le-doude | CC BY-SA 3.0 |
edited title
|
| Aug 6, 2013 at 16:37 | answer | added | user8365 | timeline score: 11 | |
| Aug 6, 2013 at 14:53 | history | tweeted | twitter.com/#!/StackWorkplace/status/364761167421390850 | ||
| Aug 6, 2013 at 14:18 | answer | added | emory | timeline score: 3 | |
| Aug 6, 2013 at 11:23 | comment | added | RMalke | I already did that. Returning home after the interview, I just noticed one of my answers was wrong. I call the interviewer, and said if I could send the correct answer soon as I got home. I don't know what the interviewer thought, but I sent the correct answer and was approved. (In the end I declined the offer...) | |
| Aug 6, 2013 at 11:21 | answer | added | back2dos | timeline score: 26 | |
| Aug 6, 2013 at 11:11 | history | migrated | from programmers.stackexchange.com (revisions) | ||
| Aug 6, 2013 at 10:46 | answer | added | Ross Patterson | timeline score: 16 | |
| Aug 6, 2013 at 10:37 | comment | added | le_douard | @gnat I have seen all questions until page 10 and couldn't find one. | |
| Aug 6, 2013 at 10:26 | comment | added | Marjan Venema | Personally I would give you bonus points for pointing it out. It shows you care about your work. Every developer knows bugs happen and the fact that you wrote one is less important than the fact that you noticed and corrected it. Also, don't send it as a PS, though not as the first thing either. Simply make it part of your thank you note as an "by the way, shortly after the interview I noticed that... " | |
| Aug 6, 2013 at 9:49 | history | asked | le-doude | CC BY-SA 3.0 |