I was reached out by Domino for an engineering-related role. During the recruiter phone call, I wasn't sure about the role but figured why not and I'd get to learn more about the company and a new type of engineering role. The recruiter was positive and gave me an idea of the topics that would be asked during the interview rounds. The technical problems would not be data structures, algorithms, or real-world ones like building an API, but a set of role-specific real-world problems in specific technologies. This was odd already since I've never seen these types of problems at any other company (startup or big corporate) in my years of experience. These problems did not test on computer science fundamentals, but the role-related troubleshooting problems. While I can see why a company would use this technical interview to see how the candidate performs on the job, it's very clear that they are looking for a software engineer with a specific set of troubleshooting skills that you will not normally acquire or can prepare for unless you've been in the same role before. This technical interview confirmed that Domino wasn't looking at computer science fundamentals, but role-specific troubleshooting skills and based on the behavioral questions I asked, would not involve me building anything, but doing mostly troubleshooting and integrations. Based on this interview process, I had a negative experience with Domino and would not recommend engineers interview unless they have specific troubleshooting skills and do not mind not having not having structured, standard interview questions that one would typically expect for the technical round.