- Work/Life Balance
- Culture & Values
- Career Opportunities
- Comp & Benefits
- Senior Management
Braintree Chicago, IL isn't hiring right now. Check out all Braintree jobs
I have been working at Braintree full-time
Caring culture, smart people, great benefits
Like most tech companies, squeezing every ounce productivity out employees is always top priority.
I applied through a recruiter. I interviewed at Braintree (Chicago, IL) in May 2017.
There were quite a few steps in the process.
1) A coding exercise which looks like it is intended to gauge your object oriented design skills and testing. This was fairly easy and straightforward.
2) Next you speak to 2 engineers over the phone about your work history. They also ask you how you would design a small application and want you to describe a solution in terms of OO. This was fairly easy as well.
3) They invite you on site and they have four sessions.
A) A two hour sit-down with 2 engineers who ask you about your history as well. They also asked about functional programming as well which I made clear I had never really used it. Switching from OO to functional is within most people's grasp but doing it on the spot can be nerve wrecking. When asked in the end how much they actually use this they clearly had different opinions on how much they actually do. It wasn't really clear what the point of the exercise was. I also got the sense they weren't too keen on TDD which was strange because it was something BT seemed to say they were big on in the job description.
B) Lunch with 2 engineers. This was fine. A little awkward since one was running late as he didn't know he was assigned for this portion of the interview.
C) A white boarding session with 2 engineers. They ask to design a web app and leave it very open ended. I definitely could have done a better job describing the architectural components. In real life, when we do a design session its always been more of a back and forth describing various tradeoffs but that didn't really happen here so it was hard to gauge what they were looking for.
D) A paired programming session with 2 more engineers. This was the easiest technically but the most awkward. We started 15 minutes late because they weren't able to setup the pairing station. The task was to add additional features in the first assignment they gave. Ive been pairing for years and usually adjust my style based on my pairing partner. I asked how they preferred I handle it, they said to just pretend they were junior engineers. What ensued was me talking for 40 minutes with almost complete silence on their end. One engineer was continuously yawning and seemed bored. A few times I attempted to prod for more discussion and participation on their end but was met with one or two word answers. Not really an ideal pairing situation....
Overall it was a pretty average interview. The recuriter was very responsive and friendly. It didn't seem a few of their engineers values aligned with the job description.