Press J to jump to the feed. Press question mark to learn the rest of the keyboard shortcuts

Triplebyte

u/Triplebyte_officialReddit Premium
Our mission is to build the world's best technical hiring process. Just show us you can code and we'll do everything we can to find you a great job you'll love. Take our online coding quiz to begin.
Karma
113
Cake day
July 5, 2017
Trophy Case (3)
One-Year Club

Reddit Premium

Since January 2019

Verified Email

2 points · 4 months ago

So is triplebyte a recruiting company or something?

I have no idea what it is outside the scope of this post and taking that online quiz.

see more

We're a hiring marketplace for software engineers.

Companies get access to a stream of job-seeking software engineers who've been pre-screened for technical ability via our quiz and interview.

In exchange for doing the up-front quiz and interview, engineers get to skip all technical phone screens and take-home projects at the companies we connect them with, and go straight to a final on-site interview. (We also schedule your interviews and pay for your flights and hotels if you're traveling for them.)

We coordinate timing of your job search on our end so you ideally end up getting multiple offers at about the same time, which creates a good competitive negotiating position for you.

Ah okay, cool. Good to know. I assume there is some kind of 'tag' for the questions behind the scenes so you can see that an applicant does badly on one set of questions or another?

see more

Indeed. The quiz engine is pretty smart behind the scenes. We test out new questions every week and optimize to show you the next most informative question.

Load more comments

(I'm one of the engineers & interviewers at Triplebyte. Hope you don't mind if I comment here.)

  1. Algorithms questions are maybe 5-10% of the interview. If you do fine on everything else, it's not a problem to not be super strong on the algorithms side. We just won't match you to companies that we know look for algorithms-heavy people.
  2. I wouldn't say the interview questions are categorically harder than the quiz questions, but then again they aren't multiple choice. We use the quiz to predict your probability of getting offers at all. We use the interview data to predict your probability of getting offers from each of the individual companies we work with. We're highly incentivized to get those probability estimates correct.
  3. The practical part of the interview is absolutely key. Your ability to build a small functioning React app quickly will work for you. Please practice -- maybe try building something like a simple version of TodoMVC starting from create-react-app. Your interviewer will give you super clear specs to follow step by step. Your goal is to get through as many steps as you can, in order, while writing clean working code. You can look up stuff on Google or Stack Overflow. And FYI, nobody finishes the whole thing!
  4. "Vastly underpaid in a small town and need to get my foot in the door" is a sweet spot. The reason you probably keep seeing our Reddit ads is that we've literally gotten many millions of dollars of job offers for Redditors in similar sounding situations.
  5. Like I said, I'm one of the interviewers. I've also met many Redditors who've come in to our office for lunch while they're out in San Francisco meeting companies. We really are rooting for you. Good luck, and FYI you'll always get detailed interview feedback from us, plus can re-apply after 4 months.
Original Poster3 points · 6 months ago

So, I passed. A guy named Victor interviewed me and he was awesome (plus he has a dog, +5 cool points). My feedback seemed hit or miss but he was very impressed with my knowledge on a few subjects (I very nearly scored 'excellent' in JS). I don't have my hopes up too much based on my scores in other categories but this feels like such an exciting opportunity for me.

See you soon?

see more

Excellent. Victor's great! Congrats. :)

I went through their process and got a few onsites out of it but no offers. Working with them was pretty good, but make sure you know that even if you make it over all their hurdles all it gets you is your foot in the door and you still have to go through the standard hiring process with the companies (take home coding tests, potentially multiple onsites, etc).

see more

FYI, if this "standard hiring process" happened, this is a bug and we'd like to fix it. The two things you mentioned (take-home projects or multiple onsite interviews) are not allowed for companies when hiring on our platform. If these happened, please make sure your Triplebyte talent manager knows so we can make sure those companies clean up their process.

US companies only at this time. We do work with lots of Canadian engineers who are potentially open to relocating. See https://triplebyte.com/candidate_faq#question-8 for international details.

"Startups" is an imprecise word, but I doubt you'd count Apple or Dropbox in that category. :) If you're interested in only late-stage or large-team-size companies, that's a certainly a preference your Talent Manager will take into account as they connect you with companies.

Moderator of r/cscareerquestions, speaking officially3 points · 7 months ago

To the person who reported this comment: yes, normally we don't allow people to link to their own commercial content like this. But in this case, it's sufficiently relevant since the original question was directly targeted at the company being linked to.

see more

Thanks.

Seriously? It's ?www.tracking.qiaodeo.com/shittyprogramming because the perfectly functional one-liner job quiz question isn't micro-optimized?

In fact, every benchmark I create puts the split function as faster than the for loop, probably because of some internal optimization: https://i.imgur.com/geP7LAt.png

see more

Have some gold :)

Thanks for running the benchmark! I wrote this quiz question, and am still surprised at the huge difference in performance. You're showing 12996 * 1000 * 40 = 520 million spaces counted per second, which is quite zippy. With that kind of cycle budget, I can't imagine that it's actually generating new Javascript strings for each of those split segments.

Really surprised to see the editor results. Are vim and emacs really that popular?

see more

Triplebyte's published data on editors and programming languages is quite different: Sublime 17%, Vim 14%, Eclipse 11%, IntelliJ 11%, VS 11%, Atom 11%, ... Emacs 4%.

Stack Overflow published some editor data too: Notepad++ 36%, VS 36%, Sublime 31%, Vim 26%. Note that they allowed choosing multiple editors.

It's a surprisingly fragmented market. Just looking at the engineering team here, we definitely have Vim, Emacs, Sublime, Atom, and someone dabbling with VS Code.

Comment removed by moderator11 months ago

We've found jobs for a growing number of ?www.tracking.qiaodeo.com/cscareerquestions readers via Reddit ads. Those engineers are pretty happy about the outcome, so we'll keep running ads on Reddit.

It's real. I'm one of the engineers here at Triplebyte and I personally interviewed one of the high school students we subsequently placed.

That said, it's also an outlier anecdote, which just makes it a fun and surprising story to share. Looking at the data, most of the engineers we work with have a few years of professional software engineering experience.

Original Poster2 points · 1 year ago

How much of experience is ideal to start applying at Triplebyte?

see more

We work with engineers of all experience levels (Junior, Mid-level, Senior on up through Lead/VP/Director). Experience shipping real software definitely helps though. No surprises -- check out our interview guide and see if that sounds like a good fit.

Also, there's no harm in doing a Triplebyte interview now:

  1. Triplebyte is confidential. We never share any information about you with any companies until you mark them as a company you want to speak with.
  2. Everyone gets detailed personal interview feedback on each section after the interview.
  3. You're always invited to re-apply after 4 months.

Looks cool but there are no stats -- all "-" or "0". Your endpoints are returning 500 errors.

HttpException [500]: Internal error processing get_report