Artium Software Engineer interviews, decoded.

First, there's a recruiter call. After that, a call with leadership, which might include an intro to pair programming if you're not familiar with it. Then, there's a half-day exercise where you'll program a synthetic project, maybe in a language you don't know. You'll walk the interviewer through this exercise, and you can look up language features if you need to.

The interview rubric is very specific, they are looking for a traditional TDD process: Write only the smallest test to satisfy the requirement, write only the code needed to make the test pass, refactor, repeat.

So the interview process here started off with a recruiter screen, then we moved on to a 1-hour technical assessment. After that it was a half-day onsite, and finally a leadership call. It was a pretty interesting experience overall. The recruiter didn't just go over my resume, we actually had a good conversation about things I like and didn't like etc. This company is super into TDD and pairing which was interesting. Pairing isn't for everyone though. They're also a pretty language agnostic shop, so you might work with a variety of different technologies.