Triplebyte Blog

We help engineers join great companies
Try our coding quiz

Share this article

The Future of Triplebyte

By Ammon Bartram on Oct 22, 2019

The Future of Triplebyte

As my dear friend and co-founder Harj announced this morning, I will be taking over as CEO of Triplebyte.

We’re doing something important at Triplebyte. Our mission is to build an open, valuable and skills-based credential for all engineers. This is important because millions of people have skills (and deserve good jobs), but don’t fit the profile that recruiters seek. Another way of saying this is that talent is uniformly distributed, but opportunity is not. Our mission is to broaden the distribution of opportunity.

When Harj, Guillaume, and I started the company, this mission was just an idea. The company was only the three of us, and it took us months to get a job for our first candidate. Everything was an experiment (and most of those experiments failed). Now Triplebyte is over 100 people. And we work with thousands of engineers every week.

Watching this mission come to life has been incredibly rewarding. I feel honored to be in the CEO position at Triplebyte, with so many talented people. And I think that we’re still just getting started. Credential bias is a HUGE problem, and fixing it is a huge opportunity.

Finally, I want to thank Harj. Triplebyte would not be where it is today without him. It’s been a wild ride, and I look forward to working with him in his new role as Chairman.

Get offers from top tech companies

Take our coding quiz

Liked what you read? Here are some of our other popular posts…

How to Interview Engineers

By Ammon Bartram on Jun 26, 2017

We do a lot of interviewing at Triplebyte. Indeed, over the last 2 years, I've interviewed just over 900 engineers. Whether this was a good use of my time can be debated! (I sometimes wake up in a cold sweat and doubt it.) But regardless, our goal is to improve how engineers are hired. To that end, we run background-blind interviews, looking at coding skills, not credentials or resumes. After an engineer passes our process, they go straight to the final interview at companies we work with (including Apple, Facebook, Dropbox and Stripe). We interview engineers without knowing their backgrounds, and then get to see how they do across multiple top tech companies. This gives us, I think, some of the best available data on interviewing.

Read More

Bootcamps vs. College

By Ammon Bartram on May 19, 2016

Programming bootcamps seem to make an impossible claim. Instead of spending four years in university, they say, you can learn how to be a software engineer in a three month program. On the face of it, this sounds more like an ad for Trump University than a plausible educational model.

But this is not what we’ve found at Triplebyte. We do interviews with engineers, and match them with startups where they’ll be a good fit. Companies vary widely in what skills they look for, and by mapping these differences, we’re able to help engineers pass more interviews and find jobs they would not have found on their own. Over the last year, we’ve worked with about 100 bootcamp grads, and many have gone on to get jobs at great companies. We do our interviews blind, without knowing a candidate's background, and we regularly get through an interview and give a candidate very positive scores, only to be surprised at the end when we learn that the candidate has only been programming for 6 months.

Read More

How to pass a programming interview

By Ammon Bartram on Mar 8, 2016

Being a good programmer has a surprisingly small role in passing programming interviews. To be a productive programmer, you need to be able to solve large, sprawling problems over weeks and months. Each question in an interview, in contrast, lasts less than one hour. To do well in an interview, then, you need to be able to solve small problems quickly, under duress, while explaining your thoughts clearly. This is a different skill. On top of this, interviewers are often poorly trained and inattentive (they would rather be programming), and ask questions far removed from actual work. They bring bias, pattern matching, and a lack of standardization.

Read More
Get the Triplebyte newsletter Subscribe

Get the Triplebyte newsletter

Be the first to get the latest Triplebyte content straight to your inbox.