Art of Problem Solving Software Engineer interview questions

Multiple screen-share coding interviews: the first was with the hiring manager, the second was with one team-member, and the final round was a full day of coding and math interviews with the team and some key stakeholders.

An hour of ad time. You first solve a puzzle when you apply for the job. Then, you have the first round with a current engineer. After that, you have a second round with another. Then, you may have a few more rounds with various people, including the CEO. I would not recommend applying at all unless you went to a prestigious university or have several major awards to show for at math. They aren't looking for your coding skills or how to get the job done. What they are looking for is your pedigree: whether you competed in the Putnam, a math competition the founder was fond of; whether you went to the Ivies, etc. etc. You can read on the reviews by current employees on glassdoor to get a sense of it. That explains why their sites are badly written. The whole interview was really easy. They explained to you what they are doing--a form of advertisement. And then, you solved a few puzzles. The puzzles are high-school level. So, I assume almost everyone would be able to solve them. The interviewers asked about my experience but their expressions showed no interest in my answers. You are decided almost entirely by your pedigree. Some were not even listening to what I was saying--which I felt insulted.