Had an initial phone screen with a coding question and a little bit of tech background-related discussion.

The in-house interview was very engaging, one of the most engaging I've had in a long time. They usually interview in pairs, and the questions are more real-world problems rather than something out of a coding problem book, or something that needs one tricky step.

The questions ranged from basic programming ability with constructs, ability to find issues in code, and ability to improve existing code/APIs.

There were some design-related questions and class hierarchy stuff tied to a neat, descriptive narrative—not anything boring.

Most of the questions were very specifically gauging the right fit for the role, and there wasn't one thing that sounded like a customary, "Yeah, we ask this to fill in some data" type of thing.

The coding and design discussions were very engaging, as they made sure it was more like a peer discussion rather than the "I ask the questions, I own the room" situation you get from most coding interviews in the industry.

My interview experience played a positive part in swaying my decision to join.

Coding, designing test harnesses for enterprise-scale systems, software design skills.