You replied to:

Yeah, basically, but it's mainly because the software developer interview process is fairly stupid and mostly just a matter of trying to smoke out people who basically can't even loop over an array or put things in a dict/map/hash/whatever.

That said, the reason it's stupid is because it has virtually no bearing on what you'll actually do day-to-day, and while all companies give more or less the same interview, their actual demands of you will vary a lot. And they may or may not provide training for the specific technologies the company uses.

So interviews really end up just being your interviewer kinda sizing you up based on how you talk the talk, and from watching how your brain works to solve whatever problem they put on their whiteboard for you.

My experience with interviewing is actually a little limited, I started with one of the firms that I knew I wanted to work for, and got an offer. So my job search started and ended rather quickly. This is based off of firsthand accounts of about a dozen or so friends of mine who interviewed at various places around the country, some are household names (Amazon, Google) and others are just random contractor shops (which are perfectly respectable places to work too, but nobody would know the company names).

Anyway, it's a bit of a crap shoot. But yes, those are the data structures I was referring to.