I applied through a recruiter. The process took 3 months. I interviewed at Eventbrite (Madrid) in Jul 2022
Interview
In was a really long process Consisted of many interviews (actually the process with the biggest amount of interviews I've ever faced) First, there's an interview with HR. Classic. A few question about what are you currently doing, what do you want to do, why their company, if you're using their product, etc. Then, there's an interview with a Hiring Manager. Simple technical questions to know a little bit about your seniority level and you'll have to do an algorithm exercise. A really easy one and it's all about you solving it and not about how you solve it. They're not looking at your skills, you only need to solve. After that, there're 4 more interviews. You'll have to do a PairProgramming session, a meet with Product team, 1 coding challenge and 1 system design CodingChallenge You'll be in a meeting with 2 people, they'll send you a link to a coding_challenge and you have 30/45 min to solve it. It's an easy algorithm challenge and they want to see how you solve it. The steps you take, how you think about it and how you implement it. The interview with the Product team it's quite a soft skills interview. They ask questions like "Tell me about something you've built that particularly proud of", "Tell me about a time when you disagreed with your TeamLeader", "Tell me about something you've built that helped other teams" and that kind of questions. They want you to use the STAR method (situation, task, action, results) The PairProgramming session is about you developing an algorithm to solve an easy task and they'll ask you questions while you're writing code. The focus here is on why you do the things you do and they'll ask you questions about the algorithm and other stuff. Finally there's a system design interview. They present you with a solution of a ticketing selling system (quite like Eventbrite itself) and want you to improve it because the system "is having performance issues". Key ideas here: HTTP2 over HTTP, Elasticsearch for quick word filtering (and why not a kafka), load balancer, distributed database, static content caching and a few more things