Since there wasn’t anything broken on our end, there shouldn’t be anyone else impacted by this. But as part of making sure that OP wasn’t visible by mistake, I had my team double-checked to make sure our previous fix from last year was properly retroactive. It was.
More generally, I don't think that tricking anyone is a viable way for us to run a business. We’re trying to create a marketplace that can open opportunities for engineers who wouldn’t otherwise have them, and we need the trust of engineers in order to do that.
Provided they're in the US. My experience as a European has been: more or less everything I apply to ignores my application. I haven't checked recently, is it changing?
I'm not implying you're wrong since you used the word trying to create. Moreover, you didn't specifically specify which group of engineers you're trying to create opportunities for. I don't even want to go in a right or wrong type of frame, because it doesn't matter, but my lack of eloquence might give that impression.
What I am implying is that the statement is a bit broad. On a more emotional (perhaps even non-rational) note: I feel spoken to yet left out, for years now.
We actually just (like, two days ago) shipped a change to be more restrictive about how we show jobs based on location. And we have a few things in the works (unfortunately I can't share details) that might result in significant increases in activity for engineers outside the US.
> Moreover, you didn't specifically specify which group of engineers you're trying to create opportunities for.
The simplest way to put this is "we want engineers who can do the job to be able to get hired". That is obviously a pie-in-the-sky goal that is more aspirational than anything else (you're never going to bat 1.000), but it's the guiding principle.
In a more on-the-ground sense, we think our assessments allow engineers who do well on them to get company attention that they might not otherwise get. And we have hard data to suggest that we are correct. Each assessment with a score of 3 or higher on an application roughly doubles the chance that that application is accepted, for example, and the overwhelming majority of outbound messages on Triplebyte go to engineers with at least one such score on their profile.
But if I had to guess? It's because we've been ramping up a feature that is increasing the amount of outbound on our site by a very large margin (currently almost an order of magnitude) from where it was a couple of months ago.
As far as I can determine, the last deliberate interaction I had with Triplebyte was in May 2020, when I got an email with your name and address on it saying that my profile was about to be made public, and I replied the following day asking you to delete my account. (I assume you never saw that email, and in any case I never bothered to follow up on it through other channels.)
(EDIT: on closer inspection, the reply with my account deletion request went to candidate.support@triplebyte.com, not to you personally.)
I don't recall ever logging into my Triplebyte account between then and yesterday, and I couldn't find any evidence of doing so in my browser or search history. I guess that's your word against mine, but if you have reason to believe I'm mistaken, you're welcome to send it to me privately.
> The support response you received was incorrect
I'm very curious as to where the incorrect information came from, then.
At the very least, a couple of U.S. companies with remote positions that claimed to be U.S. only (or "work authorization required?"), reached out to me.
I'm going to have our support team get back in touch with you via email for further details here. Can you reply here if you haven't been able to do at least one round of back-and-forth with them within the next day or so?
Nope. Just to show that I'm not yanking your chain, this is the email I'm referring to: https://imgur.com/2FpAiik
The redacted name and email address are exactly the same as when I contacted you yesterday.
To be clear, I'm not trying to criticize you for not taking action on this message, because for all I know it could have gotten dropped by a mail server along the way. I'm just using it to illustrate the fact that I wasn't even aware that I still had an active Triplebyte account, so I find it implausible that I logged in, set my profile to public, and then completely forgot about it.
> Can you reply here if you haven't been able to do at least one round of back-and-forth with them within the next day or so?
Sure, will do.
Yeah, of course. Totally fair.
(Further comms via email)
But I think some companies select U.S. only because Americans tend forget about other countries where people may be in the same time zone.
It's possible German companies are reluctant to engage with a Swiss person because German salaries are lower than what I understand Swiss salaries to be (German CoL is also much lower though)
> As mentioned on HackerNews, we cannot locate any emails from you before today. After getting in touch with the product team, I realized I had made a mistake. Upon doing a bit of digging on the back end, you set your profile set to be visible in 2019 prior to the 2020 events.
I guess I can't concretely disprove this story, but I have a really hard time buying it. I don't remember even being given the option to make my profile public when I tried out Triplebyte in 2019. To back up my recollection, the messages that they sent out about the "public profiles" feature in 2020 described it pretty unequivocally as a new feature that hadn't existed previously. Archived versions of Triplebyte's FAQ from 2019/2020 make no mention of it; they only talk about the ability to be matched with companies after completing a full interview with Triplebyte (which I never did).
And if the person who initially responded to me truly did just make a mistake, that would certainly be no big deal -- but it seems like an oddly specific and convenient mistake to make.
I responded about 24 hours ago saying why I found these explanations unconvincing, and haven't heard back. I'm posting here not to try to pressure Triplebyte into a response, but because (a) I don't know how much longer this thread will stay open to new comments, and (b) I don't really think it's likely that I'll get any further closure about this issue, so I don't plan to spend any more of my time and energy on it. People are welcome to read the discussion and judge for themselves.
> To back up my recollection, the messages that they sent out about the "public profiles" feature in 2020 described it pretty unequivocally as a new feature that hadn't existed previously.
The "public" profiles we announced (and rolled back) at the time were distinct from the visible-to-Triplebyte-subscriber-companies profiles we have today (and had in late 2019). "Visible" is doing double-duty here between public-to-the-internet (which we never ended up doing) and visible-on-our-platform (which predated the 2020 announcement).