zlacker

>>winsto+(OP)
> Your profile is about to become public

That's pretty horrible.

But I have to ask ... since my understanding is that hiring companies make you redo the technical interviews again, what is the point of doing the Triplebyte interview process at all?

Also related, there was a startup that was scraping your Linkedin status and sending that to employers who subscribed, effectively doing the same thing Triplebyte is planning to do. There was quite an uproar over that, too.

Speaking of Linkedin, your employer can view your profile if it's public, so again, similar problem to what Triplebyte is doing.

>>redis_+dg
The hiring company has to follow a standardized flow for any candidates they get through Triplebyte. Triplebyte does their own evaluation and reports the results, and then each hiring company is only allowed to do a short non-technical[1] phone screen plus a single day of onsite interviews before either rejecting the candidate or extending an offer.

[1] and they enforce this—they specifically ask the candidate to report any technical questions asked during the phone call.

>>wolfga+Yg
"Only" a single day of onsite (presumably technical) interviews? Doesn't that kind of defeat the purpose of Triplebyte, which is to "O(1)" your job search, i.e. avoid a long interview process with each company?

>>SilasX+q41
Maybe. I did TripleByte, the usual process everyone is talking about. That led to 30 minute calls with a bunch of potential employers, then I selected 2-3 of them to do on-sites. The on-sites were single day technical whiteboarding sessions + lunch (taking 6-8 hours total, exhausting), then I got offers from those companies.

When I've gone to FAANG companies, I've gone through a lot more per company to receive an offer. Multiple visits to each campus, lunches, technical sessions, spanning potentially weeks or months. Overall I think TB saved a lot of time and I really enjoyed the process.

Of course, now they've really shot themselves in the foot.