Braintree Software Developer interview questions

There's an initial phone screen from a recruiter. Following that, there's a code submission process, which precedes a more technical phone screen, which in my case was conducted with two members of one of the engineering teams. If you pass all of those, then there's an onsite interview that's quite lengthy (all-day). There are a variety of different sessions that evaluate general technical background, product design, and pair programming ability. Keep in mind that the onsite is a long day and the pairing session is done towards the end of your interview. To echo some of the other interview entires here, the types of questions are really geared more towards practical experience as opposed to purely 'academic' scenarios (which I found refreshing). You'll speak to quite a few different people; everyone that I spoke with was great. I felt like I was able to develop a good rapport with all of the folks that I met. In general, I think the content of the interview was pretty well thought out and well-rounded. Overall, the interview was challenging but not overly difficult. I was fortunate to work with an excellent recruiter who was prompt and courteous throughout the entire process (which was rather lengthy due to the holiday season). I met close to a dozen people at Braintree during the process and everyone was really pleasant to deal with. Despite the fact that I didn't receive an offer (which is also something I completely respect - I definitely recognized mistakes I made during the onsite pairing session), I'm glad I had the experience of interviewing at Braintree.

1. Initial HR interview where HR talks about previous experience. 2. Technical phone screen. Spoke with two engineers. They were nice to talk to. Also gave advice at the end. 3. Take home coding exercise. The coding challenge is pretty easy. I think they are mostly looking at how you structure your code. I used TDD and got a pretty decent design. HR told me that they liked my code and would like to schedule an onsite interview. 4. The onsite interview was a lot of fun. Four rounds total. First round was mostly about explaining a previous project. They don't want high level stuff. They really get into the details, so make sure you go prepared. They also asked some functional programming questions which was a little neve wracking, but I somehow made it through without screwing up. Second round was just office tour and informal conversations about company culture, etc. Third round was the system design round. This was probably the best part of the whole interview. I had to design a famous website. They give you all sorts of weird scenarios and see how you would solve for them. We got into a lot of low level details. Last round was the pair programming round. I had to extend the code I had submitted in the 3rd round. It was pretty easy. I think they are mostly looking at design again and how you communicate about how you are solving the problem. I was not able to completely solve the problem but I talked about what design choices I would make in implementing it and how I would go about it. I did TDD here as well. All in all the interview was a great experience. I was exhausted by the end of it but still came out happy. They asked questions which a normal engineer solves in their day to day.