Banana Skins in a Python Developer Interview

Large IT company, office 404. Interview for the position of Python developer.
Participants: department head, senior developer, HR manager. And I’m the candidate.

Department head:
— We’ve covered everything.
Looks out into the hallway.
— Oh, Jamie! Would you like to ask the candidate one last question?
Jamie works in a neighboring department, does something completely different, and has never programmed in Python but once read something.
Jamie sits down at the table. He wasn’t there last time, but today, his presence will decide my fate.
Jamie:
— What is the maximum list size in Python?

I instantly turn pale. While this question touches on the basics of the language, it rarely affects a developer’s day-to-day work. But, to my shame, I find it difficult to give a precise answer.

The department head and the senior developer exchange glances.
Department head (to the senior developer):
— Hmm, let’s look at other candidates.

And just like that, after an hour of discussing technically complex issues, one unexpected and impractical question from a random person in the office can dash the hopes of joining the team.
In this interview, as in many others, technical expertise was not the deciding factor. Sometimes, a question completely unrelated to the developer’s daily tasks determines everything.