|
|
|
|
|
by logicalmonster
1168 days ago
|
|
I don't know if I bombed exactly, but here's 2 of my most frustrating technical interviewing experiences that didn't go well for really dumb reasons. > Had a 6AM interview with a developer in India with a very thick accent and who didn't have a good microphone, which made it very difficult to communicate. He didn't have a copy of my resume, wasn't completely sure what job he was interviewing me for, and started asking me React trivia questions for what should have been a primarily Python role. > Had a technical interview with a cool startup doing some dumb leetcode style problem. We had some repeated video connection problems and started the interview 15 minutes late because we couldn't get a connection. Because of this, I was pressing and stressed out to finish the task on time and made a few silly errors because I didn't have time to think the problem through. Got most of the task done despite this, but it's frustrating to think that I missed out on this position because of some dumb video chat glitch. |
|