[rasjani]

> I was berated for not being able to remember if a System.Tick was 10nanoseconds or 100nanoseconds.

Had somewhat similar scenario. Company's internal headhunters had reached out to me once already before and I did few interview rounds with them and said no. Year later they reached out to me again and had to go thru tech interview again.. during that I did help(sleep) on python repl and mentioned why; since I haven't used sleeps on my own code I wanted I make sure that if sleep will yield cpu time or not. Mood of the interview changed at that point and got rejected by not having enough skills in Python.

Another case; One of the interviewers was late to the meeting and started to shout profanities cuz my Audio Quality was poor. And it was - thanks Sony XM's but the way he acted on the call really gave lasting impression on their "company culture"

[em-bee]

i recently failed a timed test because while it was asking a simple question about manipulating CSV data. i was unfamiliar with the CSV library because i simply never had to use CSV data before. so i had to look it up and that cost me to much time. on the other hand, another question in the same test was about variables in a function in a metaclass that were giving the wrong values because of a scope issue. i had enough experience to understand scope issues and was able to solve the problem easily.

the CSV question was easy to look up, and with time anyone could have solved it. failing it because it took to long was frustrating. the scope question would have been difficult to answer without experience, and even looking it up would not have been easy without knowing what to search for.