<story><title>Triplebyte expands its recruiting platform beyond YC, signs up Apple, Facebook</title><url>https://techcrunch.com/2017/03/09/triplebyte-expands-its-recruiting-platform-beyond-yc-and-signs-up-apple-and-facebook/</url></story><parent_chain><item><author>lettergram</author><text>Having interviewed with TripleByte, I think this is a bold and poor decision.&lt;p&gt;Upfront, I didn&amp;#x27;t pass a TripleByte interview I had (one of the few companies I haven&amp;#x27;t passed).&lt;p&gt;My interviewer showed up late initially, then took a break and showed up 10 minutes late after the break. Further, the interviewer nit picked super irrelevant details, and acted exceedingly smug and condescending. Some of the stuff he told me I was wrong about was related to my research. Even after attempting to explain it several times, he just said, &amp;quot;No, you&amp;#x27;re wrong, you don&amp;#x27;t know what you are talking about.&amp;quot;&lt;p&gt;I then literally brought up the paper and sent it to him, before he said something along the lines of... Oh, well I guess that is right.&lt;p&gt;Overall, it was one of the worst interview experiences I have had, and I don&amp;#x27;t believe they are good way to recruit. Hell, I even passed all their coding questions with flying colors. It was the silly video conferencing interview with a smug engineer who really made the interview fall apart.</text></item></parent_chain><comment><author>zug_zug</author><text>I had an interesting experience with triplebyte which wasn&amp;#x27;t as objectively bad as yours, but it also makes me skeptical of  the company.&lt;p&gt;First round was multiple choice questions, relatively straight-forward. Second-round was skype-call and just felt incredibly subjective. I was asked questions around building out memcached to support arbitrarily-sized values, and I got the same &amp;quot;smug&amp;quot; vibe you sensed.&lt;p&gt;The interview style was very 
&amp;quot;Him: How would you do X?&amp;quot; 
&amp;quot;me: Well that&amp;#x27;s not a simple problem, there are a lot of solutions each with tradeoffs.&amp;quot; 
&amp;quot;Him: Okay so name one&amp;quot;
&amp;quot;Me: So you could do X&amp;quot;
&amp;quot;Him: BUT THEN Y [GOTCHA!]&amp;quot;
&amp;quot;Me: Yes, that&amp;#x27;s one of the tradeoffs of X&amp;quot;&lt;p&gt;It wasn&amp;#x27;t clear to me what the heck he was even looking for. Was he hoping I&amp;#x27;d list race-condition problems? Had he not even considered race-condition problems? Was he looking for a theoretical solution or a real-world solution? Also he kept going on random tangents (&amp;quot;That brings me to an interesting question, how would you shift a gigabyte of memory 1 bit?&amp;quot;). He seemed very concerned with efficiently bit-packing the header in this problem, which seems silly to me when we&amp;#x27;re talking about storing gigabytes.&lt;p&gt;My understanding was that triplebyte was seeking to be the SATs of engineering, however SATs do heavy validation with test-retest reliability and such, I had no particular reason to suspect triplebyte&amp;#x27;s interview was any more objective than any other company&amp;#x27;s.</text></comment>
<story><title>Triplebyte expands its recruiting platform beyond YC, signs up Apple, Facebook</title><url>https://techcrunch.com/2017/03/09/triplebyte-expands-its-recruiting-platform-beyond-yc-and-signs-up-apple-and-facebook/</url></story><parent_chain><item><author>lettergram</author><text>Having interviewed with TripleByte, I think this is a bold and poor decision.&lt;p&gt;Upfront, I didn&amp;#x27;t pass a TripleByte interview I had (one of the few companies I haven&amp;#x27;t passed).&lt;p&gt;My interviewer showed up late initially, then took a break and showed up 10 minutes late after the break. Further, the interviewer nit picked super irrelevant details, and acted exceedingly smug and condescending. Some of the stuff he told me I was wrong about was related to my research. Even after attempting to explain it several times, he just said, &amp;quot;No, you&amp;#x27;re wrong, you don&amp;#x27;t know what you are talking about.&amp;quot;&lt;p&gt;I then literally brought up the paper and sent it to him, before he said something along the lines of... Oh, well I guess that is right.&lt;p&gt;Overall, it was one of the worst interview experiences I have had, and I don&amp;#x27;t believe they are good way to recruit. Hell, I even passed all their coding questions with flying colors. It was the silly video conferencing interview with a smug engineer who really made the interview fall apart.</text></item></parent_chain><comment><author>ammon</author><text>I&amp;#x27;m sorry that the interview went poorly! I&amp;#x27;m especially sorry about the lateness. I just pulled up our notes from your interview, and I was your interviewer! So that makes it especially bad :(&lt;p&gt;I&amp;#x27;m not an expert in all areas. At the end of the interview we have a section where we let the discussion go into whatever technical area the engineer wants to talk about. It sounds like you&amp;#x27;re an expert in an area where I am not. In those cases I try to ask questions and push deep, but (depending on the topic) that can be hard.&lt;p&gt;edit: removed discussion of the specific topic discussed. Sorry, folks below are right&lt;p&gt;Expertise is something our model handles less well (it&amp;#x27;s much harder to standardize). This certainly results in us failing some great people (and it sounds like that may have happened here). I&amp;#x27;m happy to talk about this  more. Give me an email at ammon@triplebyte.com.</text></comment>