It starts with a getting to know you phone screen at the end of which they will give you a take home coding exercise that you can finish within a week. Spend as much time needed to understand and complete the exercise but I would recommend not taking too long. Maybe between 24~48 hours is good depending on your level. Make sure to practice proper TDD, proper object modeling, clean/idiomatic Ruby. If the team likes your work, you will have another phone screen done by two engineers. This will be very technical and the questions will tend to revolve around your past work based on what you have in your resume. Prepare to be able to dive into the very technical parts of your project and don't stay too high level. They use this phone screen to gauge how well you understand the underlying technologies that you used. When you pass this, you will then be invited for a 6-hour on-site interview. This will be divided into 4 parts: 1) TECH - A different pair of engineers will do a second round of tech talks with you. This is basically the same as the technical phone screen. Again, don't stay too high level. Get into the weeds. Draw diagrams. Write sample code if you must to get your point across that you know your stuff! :-); 2) LUNCH - A different pair of engineers will take you out to lunch. They will look at how well you get along, what your interests are aside from coding. Talk about your hobbies or geek out about something in your life aside from computers. Stop talking once in a while and ask questions to know about what they like to geek out about. 3) PAIRING - Another pair of engineers will observe you. This time, in a pair programming environment. If you're not familiar with pair programming or if you don't even do it at work, make sure to brush up on this otherwise this will be the most unnerving part. At least it was for me. I'm not used to someone looking at what I type as I code and I got too self conscious and easily got lost in the weeds at times. The work here will be a continuation of your take home coding exercise where they will give you requirements that require a change in your code. They will focus more on how you code so don't worry too much about completing the requirements within the given time. Focus more on proper TDD, about using idiomatic Ruby, about wrapping your head around the domain and understanding where the change needs to be. There will be no whiteboard here so if you're like me and you need to draw things out to understand the domain, try and ask if you can get some paper and pen. I didn't ask for these which is how I got confused easily. 4) PRODUCT - This will be an architectural design session another pair of engineers will ask you to design a product from UI flow, HTTP API design, object/data model, etc. Prepare to dive down to the very technical aspects too like database locking, handling contention, includes vs joins, etc. You're not expected to code anything here. They just want to find out how well you can think in the big picture but also how you can link that to the underlying design/architecture. I got lost in the weeds during data modeling because I jumped straight to object attributes instead of focusing first on the relationships between objects. Brush up on your UML, particularly object modeling. Also, brush up on Adaptive Path's sketch boarding to make your UI flow design smoother. At the end of that, you can leave and they will deliberate as a group on what were your strong points, weak points, and if there were any red flags. Naturally, being a top-quality engineering team they will only want the cream of the crop and they will be heavily biased in their opinion of you by the red flags. Feedback is quick. I got mine by morning of the next day when I was told I did not make the cut and gave me the reasons. If you didn't make it, feel free to ask for more details on the feedback as they do provide useful feedback that will help you improve. If you made it, you rock! Braintree has one of the best software engineering environments from what I've seen and if you pass, you're one of my heroes!