How Braintree Interviews Exceptional Developers • Hacker News Board

Re: How Braintree Interviews Exceptional Developers

#11

Post by dan_manges » Tue, Jan 10, 2012, 7:01 PM UTC

sjtgraham wrote: post #3

Off-topic but if there is anyone from Braintree reading this, I'm interested to know how you feel about Stripe and FeeFighters Samurai entering the market at a more competitive price point with lower barriers to entry (i.e. fill in a form and go vs. laborious and involved merchant application process) given that your pricing has remained resolutely more expensive.

We’re not surprised to see other companies entering the payments market. There are two primary service providers that a tech start-up needs: a hosting provider and a payments provider. There have been good hosting options for a while, but as Braintree identified a few years ago, the choices for payments were not that great.

On the price points, it will depend on your volumes for which pricing is more competitive. Here’s some insight into the approach that we took with our pricing as we bootstrapped Braintree:

http://www.braintreepayments.com/inside-braintree/reaching-y...

http://www.braintreepayments.com/inside-braintree/three-less...

Regarding the customer signup process, we think there is value in getting to know our clients and their business when they sign up with Braintree. It helps to make sure we can deliver the rave-worthy support our customers have come to expect. As with everything we do at Braintree, nothing is ever good enough for us and we’re constantly striving to make things better for our customers.

Re: How Braintree Interviews Exceptional Developers

#12

Post by thehammer » Tue, Jan 10, 2012, 7:08 PM UTC

dangrossman wrote: post #5

epenn wrote: post #4

Earlier quoted context omitted.

How are they supposed to know that a particular developer is exceptional otherwise? Even if they have a github or similar account for a potential employer to peruse, that ultimately only shows the end result of their thought process. It doesn't necessarily show that they were able to arrive at their conclusion/solution efficiently. How would you then account for that?

An exceptional developer has done something exceptional. Authored a popular JavaScript library. Founded and grew a business. Lead the team that introduced a new product line that's now used at 5 million businesses. Authored the research paper that led to a new Photoshop feature. Launched an app at a hackathon that now has 30k users and here's the code. These things speak for themselves. That's what makes them excepti…

We expect anyone applying to Braintree to be exceptional. It's subjective, and naturally some folks are more exceptional than others. Frankly, it's up to the candidate to decide if that label applies to them or not. What we're interested in is whether or not someone will be successful here. That's the sole purpose of an interview. Can this person do what we need them to do? And for the candidate, can this employer provide me what I need in order to be successful?

For us, it's more often the qualities that aren't as easily discernible from resumes and source code that have been better predictors of success. There are certainly companies that are best served by lone wolf, mercenary developers, and would be thrilled to have anyone with strong coding skills or impressive accomplishments. Communication and collaboration are more important to us, and as the post points out, you have to interview differently for those aspects.

Re: How Braintree Interviews Exceptional Developers

#13

Post by darksaga » Tue, Jan 10, 2012, 7:14 PM UTC

dangrossman wrote: post #5

epenn wrote: post #4

Earlier quoted context omitted.

How are they supposed to know that a particular developer is exceptional otherwise? Even if they have a github or similar account for a potential employer to peruse, that ultimately only shows the end result of their thought process. It doesn't necessarily show that they were able to arrive at their conclusion/solution efficiently. How would you then account for that?

An exceptional developer has done something exceptional. Authored a popular JavaScript library. Founded and grew a business. Lead the team that introduced a new product line that's now used at 5 million businesses. Authored the research paper that led to a new Photoshop feature. Launched an app at a hackathon that now has 30k users and here's the code. These things speak for themselves. That's what makes them excepti…

I would hardly think a developer who's "Founded and grew a business" would be applying at Braintree. Likewise, if Braintree were interested in hiring them, I doubt they could probably afford his/her salary.

I would probably have a heart attack if I saw a Braintree release that announced they just hired John Resig as a JS developer. This is the league I think of when I hear the word "exceptional developer" being tossed around.

Re: How Braintree Interviews Exceptional Developers

#14

Post by mjwalshe » Tue, Jan 10, 2012, 7:56 PM UTC

brass_cannon wrote: post #6

dangrossman wrote: post #2

Will an exceptional developer really go through a phone interview, several hours of unpaid coding, a code review, another hour long phone interview, another interview where they must prove "strong opinions about software practices", an interrogatory lunch, an afternoon solving made up logic puzzles, then a pair coding session? That sounds like torture to me. Don't exceptional developers' portfolios and resumes say en…

I'm not a developer, so I can't confidently comment on the value of specific code evaluation techniques. In other disciplines however, it can often be fairly easy to sort out the talented folks from the merely competent through a brief screening and interview. The trouble with such a shortened interview process is it's inability to determine if this person will be a good fit with the company's culture and team. Simil…

When I interviewed at a coop they had a specific coop interview (after the technical interview) to see if you would fit the coop world view.

I remember joking that you just ask a potential employee if they cried for Boxer in 1984 if the say no you don't hire them :-)

Re: How Braintree Interviews Exceptional Developers

#15

Post by kstenerud » Tue, Jan 10, 2012, 9:19 PM UTC

What I'm seeing here is overengineering of the interview process.

There are three things you want to figure out:

1. Are they able to do the work, and if so, can they do it well?

2. Are they a cultural fit with your company?

3. Do their goals align well enough with yours? (do they have a genuine interest in the space you're in, are they just using you as a stepping stone, etc).

Points 2 and 3 can be discerned by the phone interview, the in-person interview, and the lunch.

Point 1 can be discerned by looking at and talking about a non-trivial open source project that the candidate has built. Basically, you want to dig into architectural or technical difficulties they faced (you always have these in non-trivial projects), and how they surmounted them. The finished product is more than enough to gauge competence and discover excellence. It's only if they DON'T have anything big they can show you that you need to resort to coding assignments.

Logic problems and brain teasers are a relic of a (thankfully) bygone era of bad hiring practices. There's no evidence to support the theory that people who do well at brain teasers do well at architecting and building applications. All you end up doing is potentially pissing off the candidate.

In the end, you need to understand that it's a two-way street. An exceptional candidate is likely to have many offers to choose from. Waste their time, and they'll go with someone else, leaving you with two kinds of people: Those who have a keen enough interest to suffer through your interview process, and those who are desperate enough to suffer through your interview process.