First, I got a multiple-choice quiz, which wasn't too bad except there were at least a few of those "spot the problem with this code" questions that actually had multiple problems but you could only pick one. That sucked, but I still passed it.
After that, I got a technical interview over Skype with some stonefaced dude who asked me almost nothing but computer science questions. I applied as a web developer, so it really shouldn't have been surprising that I know the difference between a binary tree and a binary search tree. The interviewer was stone cold and had no sense of humor. The following day, I got a rejection email.
Seems like yet another SV startup run by bros who want to disrupt an industry and have no regard for their "human capital".
Hopefully that was a fluke or they've changed since. Keep in mind that my experience is from 2 years ago.
All in all, I'm glad that I didn't get hired through Triplebyte because I probably wouldn't have gotten my current job, which is an awesome one in terms of the kind of work, the benefits, and the people.
Here is an abridged version the sake of brevity:
Hey [Ravenstine]
Unfortunately, we're not going to move forward with your application right now.
You did well in the Kanban problem. You talked well about HTTP. You write really nice, idiomatic front-end code. You understand how to build the front-end of a web application, and explained it well on our used car API problem. And you were friendly and we enjoyed talking to you.
We didn't see the depth of knowledge that we look for in front end programmers: you didn't show very deep knowledge of security or data structures. On the used car problem, you didn't seem very knowledgeable about backend web systems.
You might benefit from studying some of the following topics: Classic algorithms and data structures. Basics of HTTP. Advanced Javascript things like the ES6 features, async/await.
We recommend you study algorithms more deeply.
We think you're really high potential, and we'd love to talk to you if you're still job searching in four months (we of course hope for your sake that you're happily employed by then), or next time you want a job.
Best,
Triplebyte Team
---
Again, the fact that they provided this kind of feedback is actually pretty good.
My problem is not only that I believe I was interviewed on the wrong things(over half my questions were CS and algorithms but I was applying as a web developer), but the feedback also isn't entirely accurate.
Could I shore up on algorithms? Sure.
But look at this:
> You talked well about HTTP. [...] You might benefit from studying some of the following topics: [...] Basics of HTTP.
What the hell? Not only is that feedback contradictory, but it's horseshit. I wasn't stumped on the HTTP questions, and all my answers about it were accurate. I've written HTTP servers and have done some interesting things cutting together audio and streaming mid-roll through HTTP, so don't tell me I don't know enough about HTTP. HTTP isn't complicated.
> Advanced Javascript things like the ES6 features, async/await.
I'm not sure whether this is related to the question about promises in JS that I was asked, but I don't see how because I explained their function accurately.
> you didn't seem very knowledgeable about backend web systems
This one blows my mind. I had way more experience doing backend than frontend at the time. I don't know what I could have told them that would have suggested that I effectively know nothing about how HTTP and backend programming works.
---
Maybe my diction was poor, idk. If it was, it didn't seem to stop me from getting jobs outside of Triplebyte.
Perhaps I wouldn't have been as miffed about this if they had included algorithm and CS questions in the initial multiple-choice quiz. I shouldn't have gotten to the point of the interview only to find out that I didn't have the knowledge required.
1. You actually get feedback from their interview. In an interview at a company, if you're lucky, you'll get which interview you didn't do well at. Triplebyte sends you feedback like "Finally, $QUESTION[3] was probably his worst: good knowledge baseline, but gave the impression that this is an area where he doesn't feel at home. Didn't lead the conversation, and most items were shallow in details, especially when talking about scalability." This is one of many parts of the feedback I got from my interview.
2. They send you Cracking the Coding Interview. And a light jacket. For free. At least, they did when I interviewed. I think it was post-Triplebyte interview, so at that point they were sending my profile out to companies. They might not send it if they don't accept you; I don't know.
But even #1 is a very good use of your time. You get feedback about your interview that isn't just binary. They also send you links to specific references for the parts you could focus on.
I happen to work in a bank doing boring banking-like things and did not attend university. My experience has been that even if one passes their resume-blind interview, the companies are not resume-blind and are still looking for the hot-topic skills and experience du jour.
The people with that kind of skills/experience probably don't need Triplebyte anyway. And my guess is that if you are being turned away from hundreds of online applications that you do not either--despite whatever programming chops you actually possess.
Also, you would be given an option to schedule a practice mock test for the final interview.