I actually went through three interviews- an online assessment, a programming and math test onsite, and then an interview with a few people onsite. Things went great the whole time, or so I thought. I talked about the many projects that I worked on with multiple teams. I told them my initial impression of Foundation and what I liked about it. I think they were confused about the wording of their own questions on the written portion. Like, when I would rate my skills against other *senior* engineers like I was asked, (Let's say, a 6/10 in a javascript category versus other senior engineers) they took it to mean that I was rating myself in that skill, period. They were really, really concerned that I thought myself only 6/10 in javascript, and was asked later (in person) what I thought I could do to "get better". I was kinda taken aback by this but called them out on it in the in-person interview- "I was not rating myself a 6/10 in Javascript- I was rating myself 6/10 in javascript against other senior engineers, like the question was written." I was sent a letter in the weeks since that they've identified other candidates whose skills were a better fit. I think however that they would have known this prior to the end of the third interview. For quite some time afterwards, I saw that the position was still posted online. It was just an odd series of interviews. I don't think that they know how to interview senior candidates very well.

After applying I was sent an email 1-2 days later to take the next steps in the hiring process. I was instructed to schedule an appointment that would be 2.5 hours which would include a math test and programming test on site. When I arrived it appeared they didn't know exactly what test to give me at first. I ended up taking the "programmer test". The math test was timed and on a computer but I did not see anywhere for the total number of questions. The time was about an hour for the math test. Brush up on your algebra and geometry. I then started the programming test, which included basic C# language questions, questions about databases, and front end development questions related to JavaScript libraries. You'll need to explain key features of the technologies and their usages. It also asks you to "code" ( writing on paper) example classes and data structures. This part was a bit tedious, much rather type code rather than write code on paper. You'll need to know why you are using the techniques you use daily that you may take as a given, because those are the questions that you'll be tested on. For example, explain how lambda expressions work. I botched some of the questions I knew the answer to, probably due to fatigue from the hour long math test. Needless to say I was not asked back for an interview. But they responded back in 1-2 days which was awesome.