The interview process for Quo was refreshingly different from the current trends in Software Engineering Hiring, focusing more on real world experience through your ability to effectively communicate rather than Leetcode-esque tests. The process consisted of 5 interviews, totalling roughly 3 and a half hours. Starting with a phone screen from a technical recruiter, then a first round technical screen with an engineering manager. While the rounds are conversational, there were standard questions that were asked to ensure standardization between candidates which helped the approach feel more structured and considered. The final round was a group of three interviews: a system design round, a deep dive technical round and a product/business sense round. Each was structured as follows:I The systems round asked me to design an electronic voting system, with emphasis on scalability and configurability in relation to real-world usage. The technical round required me to come with an example of something I'd built that I'm proud of, I was then asked to explain what I had built, some of the decisions I had to make in regards to tech debt and capabilities, what I would do different, etc. The final product/business sense round was a conversation on my experience building software to achieve business objectives and drive growth. Specifically how I can contextualize and evaluate requirements in relation to stakeholders/business objectives providing feedback and make decisions with those goals in mind. Overall I enjoyed the interview experience with Quo, it was professional, and focused on evaluating me for their specific requirements which I feel is a much better process, both for the candidate and employer, than the generic coding challenges the industry uses.