First they set up a phone screen with the typical round of questions for the role. Then they sent me a take-home problem which was a fairly straightforward exercise in static typing. Next, we set up a Google Hangouts interview. I would have preferred to interview in person since I wanted to see them in person, but they seemed hesiant. (They probably didn't want to waste the money). Anyways, the Hangouts interview went well enough. They asked me to explain some FP code and some more esoteric stuff. We had a whiteboarding section where I implemented some straightforward list operations in two ways. Then they gave me a unit-test driven problem, but we didn't finish that section and it seemed underdeveloped. Finally we talked a bit more about the role and their culture. They ended up flying me out to their office and we discussed more about the role, what they're doing, and what it's like there. Overall it seemed like a decent fit. The recruiter seemed like they really wanted my decision as soon as possible. I told them I needed some time to think about it, mainly because I needed to convince my wife to move to Chicago. A few days later they told me they needed a decision by that night, but my wife wasn't convinced about Chicago, so the deadline passed. It's too bad, despite being a little disorganized in the interviewing, they seemed like a generally fun group to work with. Overall I would probably recommend them to anyone with and interest in their style and the govt. market. (I also ironed things out with my wife, so we're happily job searching again. Talk to your SO beforehand if you would need to relocate!)

Take home assignment followed by an onsite or virtual if remote. Home assignment required implementing a widget. The onsite consists of a code comprehension session and pair programming session on a feature update. There are also some easy/friendly behavioral questions.