Icon blog
Triplebyte Blog

We help engineers join great companies
Try our coding quiz

Share this article

Triplebyte in New York

By Triplebyte on Jul 18, 2017

Triplebyte in New York

We're excited to announce that Triplebyte is now available for engineers and companies in New York!

Until now we've only been working with companies based in the Bay Area and engineers who want to work there. As we've grown, the biggest request we've had from engineers has been expanding to new locations. The most requested location has been New York, we've seen applications to Triplebyte from engineers either based in New York or wanting to relocate there double since the start of this year.

That's why we're excited to make New York the first new location we're expanding to. We're launching with a great initial group of partner New York companies, which we'll be adding to over time. As in the Bay Area, we'll be working with a mix of companies across all size and stages. We're working with exciting late stage startups hiring in New York like WeWorkPelotonDropbox and Palantir. We're also partnering with earlier stage companies working on things like changing online education (Teachable), fixing healthcare by using data to improve the efficiency of clinical trials (Trialspark) and helping us sleep better (Eight). We'll also be working with companies taking an engineering approach to the finance industry like Bridgewater and Jane Street

If you're an engineer based in New York, or looking to relocate (we'll fly you out for interviews and cover the costs), the first step is completing our programming quiz here.

If you're a company in New York hiring engineers and you'd like to learn more about working with Triplebyte, you can get started here.

We'll be opening up to more locations throughout the year and are excited to help more engineers find their ideal company!

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