Phone call + take home test prior to onsite. Tour of the office + on-site pair programming after successful take home. Their office is ok-ish.
Take home test was easy and you were allowed to do it in a language of your choosing. In person pair programming was in Ruby only.
Failed after the onsite interview because apparently my tech skills weren't "up to par."
This part will come off as if I'm full of myself, but my tech skills are fine. I aced all my other onsite interviews and I currently have two offers from FAANG companies and a handful of offers from some other startups.
Betterment, I like your company and I will continue using your products, but your onsite interview isn't a test of tech skills, it's a test of Ruby knowledge.
I get it, maybe you only want to hire people who know Ruby and that's fine, however you shouldn't waste other people's time. You should follow GitLab's example and make Ruby a requirement if you're going to continue your practice of having an onsite where Ruby is the only allowed language.
I recommend going back to LC style questions in the interview or at least have a couple of mock projects ready in several languages similar to the take home test. Alternatively, stick to only interviewing candidates who know Ruby.
Onsite they give you a mock project where you have to complete the requirements. If you don't know Ruby + Rails, don't bother since it's the only language you're allowed to work with.
The following metrics were computed from 8 interview experiences for the Betterment Software Engineer role in New York, New York.
Betterment's interview process for their Software Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Betterment's Software Engineer interview process in New York, New York.