3 ms·
I don't know anything about the story of Otherbranch's business (they launched ~about a year ago†), but Patrick, Erin & I briefly worked on a firm with similar
by tptacek 1y ago
I don't know anything about the story of Otherbranch's business (they launched ~about a year ago†), but Patrick, Erin & I briefly worked on a firm with similar business dynamics (Starfighter, a contingency recruiter based on CTF qualifiers). The prospect of eventually writing posts like this is part of why that business got wound down.
I think the points in this post are mostly all well taken, but I also think a hiring manager looks at this and says "yes, this a vendor talking their book". Most of the relationship between a recruiting firm and a tech company is a disagreement about what the threshold for a viable candidate is!
† https://www.otherbranch.com/shared/blog/rebooting-something-like-triplebyte https://www.otherbranch.com/shared/blog/rebooting-something-...
- rachofsunshine 1y agoYeah, to some extent you have to be willing to deal with this stuff in recruiting, which is why I've taken on the clients under discussion at all. In my Triplebyte postmortem (also on the blog), one of the mistakes I talked about was that Triplebyte was aggressive about trying to dictate terms. We told people how they had to hire. Otherbranch takes a softer approach: if you ask for my opinion, I'll tell you what I think. Otherwise, I'll do my best to find you what you asked us for, with the understanding that some sets of constraints reduce the probability of success to ~zero. That goes on the candidate side, too. I get a fair number of people who will come in and tell me "I only want a remote job where I can take a day off whenever I want and only want to work on a super clean codebase and also get paid 250k a year" - and those people are almost never going to end up with jobs. But the tradeoffs they want to make are their business, not mine, until they ask me to do otherwise.