Pretty straightforward technical question. Got a working solution and then refactored pieces of it to use functional programming with the time available. Interviewer was clearly busy with something else and then ended the interview 15 minutes short. I figured this meant the solution was good enough.
In the next round with the HM he spends about 10 minutes talking about his role at the company and then says, “Unfortunately, we won’t be moving forward with your candidacy due to the results of the coding round”. Still mindblown that they would not just schedule the next round but this guy talks about his experience for 10 minutes as though everything is fine. You’d think he’d have better things to do.
Anyways, the explanation is that I didn’t use functional programming which is ironic because in my refactoring I explicitly called out I was refactoring the code to use functional programming and with more time I would move out almost all of the pieces to use that style. It’s also pretty petty to kick someone out for leaning more on OOP than functional, especially when there are time constraints. I personally associate that kind of debate with more junior engineers, so I guess you can’t really pick your interviewers.
Something about transferring money? I can’t remember well now.
The following metrics were computed from 10 interview experiences for the Paxos Senior Software Engineer role in United States.
Paxos's interview process for their Senior Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Paxos's Senior Software Engineer interview process in United States.