Triplebyte acquired by Karat
karat.com
karat.com
Then they started abusing trust and implementing dark patterns: https://news.ycombinator.com/item?id=23279837 https://news.ycombinator.com/item?id=27255742 https://news.ycombinator.com/item?id=23303037
I was honestly thinking about using them myself until it became clear that they had no ethics. Once trust is lost...
I had less success when I came back 2-3 years later and tried to get another role through them, but I'll always be thankful for the initial foot in. At at time when many places didn't want to consider me at all for having no professional experience, triplebyte was willing to give me the chance to interview and judge me on my answers instead. Even just the interview process was a good learning experience and I could research any topics I didn't know afterwards.
I like to riff off one of the questions from my triplebyte interview when I now interview candidates- the "used car" architecture question. Makes for a great open ended technical discussion.
Once they gave a basic architecture, we'd make some tweaks like scaling or adding other complications and ask how they'd modify that architecture to fit.
I finally managed to get into Triplebyte’s program. I did a phone interview with them, failed it, then came back a few months later and passed it. They flew me out to California where I interviewed at five companies. No offers at four of the five. It was the very last company that I interviewed at where I got a job. Had I not gotten that job, I would probably be trying to sell insurance right now or something.
I’ve been at Google for a year now, so it ended up working out pretty well in the end.
It's surprising how quickly after the public-profile-incident (https://news.ycombinator.com/item?id=23279837 https://news.ycombinator.com/item?id=23303037 ) they fell off the radar.
We were simply never able to make the marketplace version of Triplebyte work after moving away from the transactional model we had in the early days. We tried some new tactics near the end that seemed to be bearing fruit, and I think in a world where tech hadn't crashed in mid to late 2022 we would have had a reasonable shot. But sometimes you find product-market fit right around the time the market goes sour. C'est la vie.
The reason we fell off the radar is that we'd been spending a lot of money on ads and stopped at around the time of that backlash (due to a change in business, not due to the backlash itself). Turns out you can boost your profile quite a bit when you're pouring a lot of your cash into ad campaigns! (Also, the physical ads wouldn't have made much sense since that pivot also coincided with all of us sitting in our tiny Bay Area apartments for the next year, lol.)
It’s a shame because I know there’s people like me stuck in a dead end job somewhere despite being a senior level engineer (I was working construction!) and these people will have nowhere like triplebyte to help show the industry their skills.
The issue of "talent but no experience" is a glaring inefficiency, but it's the kind of inefficiency that (so far, at least) it's been very hard to make a business out of. (And to be clear, this isn't just employers being evil, a lot of their behavior is rational and it's not like candidates never lie or cheat either.)
I have some thoughts on this that I'll probably be batting around with my new bosses a bit once we're settled in with Karat's teams. Since Karat focuses more on screening than on trying to be a marketplace, it's a more natural fit for their (our, I guess I should say now) existing business anyway. Hopefully we can make it work.
As a mere jobseeker in the pipeline, I wasn’t sure if the representative understood the reality of recruiting. To me, the ambition sounded ignorant; companies do not want to outsource and centralize their hiring in a third-party that is also hiring for their competitors.
The biggest single barrier we faced for early TB was pricing (we were charging 20% of first year's salary) and the demand that companies skip candidates straight to onsites (which we were promising them at the time).
Later on, our biggest barrier was differentiating ourselves from Linkedin and the like: companies saw Linkedin as the primary sourcing tool, and because they were hiring non-engineers there, it was one they usually wouldn't get rid of. So we were always the secondary tool, which meant (a) we tended to get the roles they couldn't hire for elsewhere, which selected for the hardest roles, (b) we had to justify ourselves in a way linkedin didn't, and (c) we were the first to be cut when the economics turned against us.
You were the only way to get well-assessed devs in the door despite non-technical hiring managers and an HR department asserting any assessment was discriminatory.
Government can't buy open source since lack of support fails due diligence, so wash OSS through vendors offering enterprise support. Similarly, talent can't be hired well directly, so wash great talent assessment for enterprises while they stay compliant, it should be a gold mine.
Most every enterprise in America needed (needs) that, and any of them running a Transformation had someone that would have been a sponsor.
(Btw, looking for folks interested in setting up a new kind of systematic person-role matching, and while still somewhat marketplace-like, profit could be on the order of $500K per match. Know anyone interested in trying that?)
Is this referring to Magnet? I thought that was neat product idea.
Magnet grew out of four main observations:
* Our users got much better results when we helped them search rather than leaving it to them.
* What company users fundamentally wanted was to - as our head of finance put it during a discussion last January that ended up leading to the creation of Magnet - "swipe a credit card and get candidates".
* The most interest we'd seen on the candidate side was when we could tell them what companies really wanted, and bringing that in-house meant we could show that information very accurately and without incentive for companies to be dishonest, and
* We had a fundamental lack of activity problem. We talked often about how nice it would be if we had Linkedin's spam problem, because we had lots of ideas for how to solve that problem if we actually had it, which we didn't.
So we built Magnet, which ended up increasing activity on platform by a factor of like five and made companies way happier. We scaled it up over time, and right as we really turned it up in June, the market fell out from under us. And it's a testament to just how well it worked, at least on paper, that our number of connections between candidates and companies actually grew through much of fall 2022 despite the collapse in hiring.
That's not to say Magnet didn't have problems. It did. It had issues with fraudulent profiles (there turned out to be quite a few of these - a lot of job sites are dealing with this problem at the moment in the remote-work world), and we were definitely hitting a point of diminishing returns as we scaled it to some extent. But given how quickly it was built, and how bad the market was, the fact that it took off at all suggests that there was probably something there.
TripleByte felt like a premium product that cared about both sides of the transaction but when I came back to it years later, maybe I had changed but the site just felt... bad, like that it was just a job mill. It didn't feel premium, it felt like a hokey recruiter site with a Silicon Valley skin.
It doesn't help that companies also treat(ed) it like a job mill. I would have companies reach out, tell me my resume looked great and fit all the criteria then would turn me down for lack of experience when I responded.
This is essentially correct.
Our original model worked, more or less, for a small pool of candidates. But acquiring those candidates was extremely expensive in ways that scaled poorly as Triplebyte grew. Basically, we were dependent on ads for growth (anyone who used Reddit at the time probably saw a lot of our ads, shout out to /r/againsttriplebytemike), and the marginal cost of ad conversions grows as you try to scale how many people you're bringing in.
Slightly less cynically: if your business can't exist without VC funding, but can't justify the expectations of that funding, you never really had a business to begin with. You borrowed one temporarily. This is normal for startups, and VCs know that they won't always (or even usually) succeed, but you can't sit on your break-even-ish business when that's not what VCs were funding you to do.
For what it's worth, early TB's efforts (and for that matter, late TB's efforts, both before my tenure and during it) were sincere, it's just that that sincerity is predicated on actually being able to make a working business out of it.
Harj recently described Triplebyte's user acquisition trajectory publicly in a video from Y Combinator: https://www.youtube.com/watch?v=BtzUo6vL3Iw&t=473s from timestamps 7:53 to 9:33. But yes, ads worked for a while, until they didn't.
To be fair, none of my friends that I referred to TripleByte actually passed their (2017) screening process. So it was a site that was very useful to a very small subset of engineers. I'm sure there's a viable business in that premium market, but probably not a unicorn scalable tech company.
In the past 10 year being unethical wasn't considered immoral by a lot of such startups. I remember the intern incident at Repl.it or how AirBnB destroyed the rental market in certain geographies or the whole Uber incidents.
(What was the project track for??)
They recommended practicing on interviewing.io, a site with closed membership that kept me waitlisted for over a year (and only then let me in because I complained about the situation on HN, not because I'd actually waited long enough to get off the waitlist).
So as far as I could see, Triplebyte advertised one thing, delivered the opposite at every opportunity (I'm also still bitter that the site with the tagline "No resumes, just show us you can code" opened its interviews with "So, where have you worked in the past, and what did you do there?"), and didn't even pretend to be interested enough to give you advice that was, theoretically, possible to follow.
I set up identical profiles and passed all the relevant quizzes at Triplebyte, Hired, and LinkedIn (all 3 offer timed, multiple choice question tests with limited retries), but only LinkedIn was able to match me with opportunities willing to pay what I was asking. Triplebyte and Hired both let you set a floor salary, but have no ability to set a floor total compensation, which meant it was effectively worthless for determining if a company was competitive for me.
In Oct-Dec '22, I got ~400 LinkedIn recruiter messages (3% with high enough total comp), ~20 triplebyte messages (0 with competitive comp) and ~10 hired messages (0 competitive). None of these recruiters were connections beforehand on any platform, so it's just representative of the total number of recruiters on each platform. (In case anyone is interested, I also cold-applied ~20 places, and none of those resulted in me making it past the hiring manager stage, if that. I ended up with 2 offers, both from random LinkedIn recruiter outreach.)
Especially as the hiring markets starts (continues?) to contract at the middle and lower ends, being willing to give these types of outreach a chance is going to become a differentiator.
I just retook the Linux LinkedIn test and what a bunch of garbage it was. Lots of memorising commands (e.g. nm-connection-edit) and obscure Bash nonsense.
And it only says whether you're in the top 30% or not, which apparently I am despite the fact that I guessed half of the answers. I just guessed the least intuitive option every time heh.
Tell me more. Having trouble thinking of something that wouldn't change how I'd percieve a senior dev's skillset.
* What is evaluated first, file globs or variable expansion?
Both are things that you might need to look up once in a lifetime. If you're getting to the point that are memorising rules like these, then you're writing too much Bash and should switch to a more robust language.
Their biggest issue was probably corporate politics, no HR org wants to hand over a huge chunk of their power and purpose within a company. Their business model also didn't fit a VC startup model, no real room for exponential revenue growth
After confirming the skill-ranking capabilities with our first hires, we integrated Triplebyte into our hiring process to save developers hours of wasted time on pointless coding exercises that are thrown away after each interview only to start over again with the next company. This was an advantage for us, we had a better signal to noise ratio on candidates and we found more talent willing to take a triplebyte test than our own in-house tests. Further, the triplebyte tests were maintained and refined over the years to an accuracy I believe is going to be very difficult to replace.
Yesterday, Karat announced a shutdown of Triplebyte with less than 2 weeks notice. They don't care to offer a solution to any of Triplebyte's customers. In their words they "only purchased a technology that Triplebyte made available to other companies" i.e. "we don't want anyone else using this".
The Karat website uses floaty words like "interview cloud" and emphasizes live-coding interviews as part of some legacy product that would put us back into the stone ages when it comes to our current hiring process. Karat expressed no intention on offering solutions to replace what Triplebyte did best. Karat do not care about the inconvenience of their customers. Karat provides less than two weeks notice to paying customers that they are cancelling service.
If the tests go away, I don't know what I will do to help gauge candidate skill without traditional and wasteful live / take-home / repo-based tests.
As an evaluation tool, TripleByte was great. As a user of Magnet (the recruitment marketplace), it was not so great. We signed up during the hiring frenzy of 2020 and the good candidates we tried to get were all getting offers from much more established brands. We didn't see any success there, but TripleByte Screen is an excellent product I hope remains available.
The way I saw it, it removes a lot of stress and pressure for the candidate, and puts some of it onto the interviewer.
Literally all of our feedback was completely ignored. They didn't touch on any of the topics they said they would, and even though we explicitly told them it wasn't an algorithms heavy position that was their entire focus. On the plus side I did pass the interview, but we ultimately decided that using Karat would have had a real negative impact on our hiring.
We had a few months of really painful full interview loops with candidates not appropriate for the positions.
I do want to stress the useless part here too- even with the notes of how the interview went I wouldn't be able to make a decision on things, since they didn't hit the points that were actually relevant to the role.
(EDIT: Note that I previously contracted with Karat and feel loyalty to them, but have no formal association or stake in them, nor do I represent them.)
What a contrast this is.
Karat is probably the best/fairest you can do for purely algorithmic interviews, but I'm not sure they're even able to do anything else (the parent commenter's experience suggests not).
I would also consider it more of an exam than an interview - the process is very standardized and sterile, and obviously since it's being outsourced there is no way for the candidate to ask any questions about the company.
(disclaimer as well: went into the interviewer onboarding with them as a contractor but dropped out as I wasn't comfortable proctoring tests that I myself wasn't an expert at).
I'm curious why you're so intense about this- do you have some sort of stake in karet?
Communication is hard, and not everyone has time or energy to bridge the gap, which is fair! It's just a bummer to hear that this has somehow lead to words like "awful", "real negative impact", "useless". That feels very intense to me, and I have probably responded in an intense way as well. There was no harm intended
Given the usual nature of coding screens - intentionally generic and standardized, so a company can use the same screening process for different teams - it made a lot of sense to me that a task like that could be outsourced. Since you are usually not developing a relationship with the interviewer at that point, there’s no real reason they need to be and employee of the company you are interviewing for. A couple of times I’ve had coding screens where the interviewer didn’t seem to be paying attention. Since some engineers get forced to do these screens, they might not be focused on giving a good candidate experience.
It actually makes a lot of sense to do it this way on both ends.
You know the interviewer is going to be a good interviewer who knows what they are doing & how to judge you. The interviewer can be completely independent from the decision without having bias or judgement attached to where the candidate ends up.
I've certainly had interviews where I knew I was doomed from the second I walked in the door because the interviewer was in a bad mood, they didn't enunciate clearly, just a bad vibe, whatever. That sucks as a candidate. This situation would make a fairly demeaning process slightly better if done well.
The lucrative cottage industry of interview assessments won't be going down so soon as long as there are perverse incentives and gatekeeping in place.
Even people who got declined usually still left feeling quite positive, because we would turn the obviously-failed interview into, basically, a free hour coaching / teaching session for them to succeed next time.
Further - you guys lurk all over HN commenting like this every time there's an interview thread. It's submarining and it's gross.
One thing I didn't appreciate with these rules from a candidate perspective (and encouraged my decision not to continue my onboarding with Karat), there seems to be no way to learn from the process. I actually bombed my practice interview (and knew it would happen even before the interview) but the interviewer was very reluctant (due to the above rules) to actually solve the problem with me, where as a conventional non-Karat failed interview would at least give me the solution in the end and I'd at least learn something.
Still I don't know if I would trust hiring to unknown potentially awful interviewers.
I guess it could be generalized that these companies are more likely to value philosophies that are similar to a few of these abhorrent practices-
1. Flawed concepts of "Meritocracy" based hiring/promotions
2. Stack ranking
3. RIF's based on some extremely shortsighted metrics like quarterly revenue numbers
4. PIP style performance improvements
5. More MBA types managing engineering teams
...
The only place I see Karat style services fit is to eliminate 'noise' candidates from DDOS'ing the entry level hire pipeline.
When they made some missteps and got (deservedly) bad press for it, and then struggled after, I felt bad for them in the way I'd feel about a friend that screwed up.
The honest comments in this thread from Triplebyte folks is refreshing too and I really hope for the best for them.
I wouldn't be surprised if an OpenAI + Zoom solution makes Karat obsolete.
I, for one, won't shed any tears. I've wasted too much time conducting interviews. I'd like to have more time to focus on work.
What didn't scale was the ability to get high-quality candidates in the door in the first place.
If you're going to try to build a business on the basis of eliminating the bullshit from interviewing (which is a terrific thing to try to do) you have to make sure your client companies are on board.
After aceing their Linux kernel screening test in 2019, their model of “we will call you, you cannot contact us” have made it nearly impossible to work out physical scheduling for an interpreter to sit alongside the conversation.
After all, one does not need a voice to do professional “bit arrangements”. We all have IM, texting, email, and fancy transcribing machines.
There are many forms of vocal disabilities.
[0]: https://triplebyte.com/blog/rethinking-triplebyte, discussed here https://news.ycombinator.com/item?id=27541676
That pivot was motivated, more or less, by the fact that we'd never found a good way to attract candidates that wasn't "dump tons of money into ads". (Even in the early days, when our branding was good, most of our candidate acquisition was from ads; only maybe 25% was word-of-mouth.) It just didn't work: senior engineers simply didn't find the things we could offer them compelling enough.
Fundamentally, if you're a hiring market paid by companies, you're selling access to talent. And finding cost-efficient ways to get that talent is a core problem of your business. We tried a few approaches to that, but none really took off. (The most successful was our Screen tool, but the problem with that was that companies mostly wanted to screen candidates they saw as low-value - juniors and international candidates, mostly - and were terrified of screening high-value senior candidates. The product worked well, but didn't get the candidates that would let us stand out, basically.)
During 2022, we pivoted back to a focus on companies, and actually saw quite a bit of success with our last few efforts in a way that, with more runway, we might have converted into some really good candidate experiences. Unfortunately, this coincided with a collapse in tech that both tanked companies' desire to hire and tightened their belts as they braced for a hostile fundraising environment, and we couldn't overcome that environment even with a product that did seem to have reasonable fit.
I wonder if you would would have had better luck targeting engineers on the cusp, or people with significant experience who didn't have the confidence to identify as senior.
That was my situation when I started using Triplebyte, and the assessments did wonders for my confidence.
I did however end up taking a counter-offer from my company that promoted me to lead.
However, I raved about Triplebyte to everyone I knew (similarly unconfident engineers considering a job change), and would have loved to continue doing so, as well as using it on my next job search.
I'm really sad to hear you couldn't make it work, it was excellent from the candidate side of things.
Three weeks later I got an email from Triplebyte saying they were "pausing your process".