why aren't all 12 resolved? a statement only gets an assessment when the public
record can support or contradict it. opinions and what-ifs never can, and 0 checkable
ones are still open, waiting for their date. predictions held up or didn't;
assertions are supported or contradicted. on every card:
▮▮▮▮▮ certainty ·
▮▮▮▮▮ debate potential. speakers are clickable
Opinion
Poels: Building engineering teams outside San Francisco beats centralizing
“What I'm here to tell you today is that it's not only possible to build world class, great development teams in places outside of San Francisco, but in actuality, it's better.”
What-if
Eventbrite would never have IPO'd without its Nashville engineering hub
“Without the work happening in Nashville, IPO never happens for us. Just full stop. We never have an IPO if we didn't get ourselves to a place where our books could close regularly and consistently.”
Insight
Rejecting international engineers for lacking English fluency was a colossal mistake
“Over the course of the first two years doing hiring in Mendoza, we let, we did not hire probably three, maybe even four great engineers purely because they didn't speak English very well. And this was a colossal mistake.”
Assertion Not checkable as stated
Eventbrite achieved Google-level hiring advantages by empowering its regional hubs
“The reward for giving them that trust and autonomy has been, we are the place to work for engineers in both Mendoza and Nashville full stop. We are the best place to work and it's known by everybody that advantage that Google used to have over us. In San Franc…”
Insight
Assigning minor tasks to remote engineering hubs destroys morale and recruiting
“The outcome of giving your distributed teams work that's less important is you will not have distributed teams who are excited to come to work. You won't be able to have them attract other great engineers in market.”
Assertion Partly supported
Lemkin: Eventbrite's 1x Revenue Acquisition by Bending Spoons Included 50% Premium
“Like, even with Eventbrite selling at one X today, I think it was still like a 50 or 60% premium that Bending Spoons had to pay.”
Assertion Not checkable as stated
Removing himself from local interviews vastly accelerated Eventbrite's Mendoza hiring
“And when I figured that out, that's when I got out of his way and start letting him hire just without me in the process. And that accelerated our ability to hire and grow really, really fast.”
Assertion Not checkable as stated
Eventbrite's Mendoza engineering office saw zero turnover for its first four years
“In this office where we've experienced this great growth of going from five people to a 110 on the engineering and design side, we didn't lose our first person until. A full four years after we started building the team.”
Assertion Supported
Eventbrite found a top-ten Rails contributor in a Mendoza startup
“The engineer that I met was, he was one of the top 10 contributors to the rails project lifetime. And he actually hadn't done any contributing for more than a year, but I look up the list of people who contributed to rails and he was like number nine lifetime.”
Assertion Not checkable as stated
Poels: Mendoza engineering salaries are roughly 30% of San Francisco levels
“First off, the salaries in Mendoza are roughly 30% what they are in San Francisco.”
Assertion Not checkable as stated
Annual engineering turnover in Eventbrite's Mendoza and Nashville hubs is under 5%
“If I look at Mendoza and Nashville together over the course of the time we've had these two offices, the total turnover we've had in these two offices combined has been less than five percent a year across these two.”
Assertion Not checkable as stated
Eventbrite retained 21 of 40 engineers over seven years in San Francisco
“I'm proud to say that when I started at Eventbrite with 40 engineers in the company at that .21 of those engineers are still there. I've been there seven years and two months and we still have 21 out of 40, which is terrific for San Francisco, but we still had…”