AVOID THIS COMPANY!!! Process started with recruiter call to discuss position, candidate background, experience and salary expectations etc., Initial call with the hiring manager was scheduled within a week and the first call was okay. I didn't receive any feedback for more than a week. When I sent an email to recruiter to check if he has any feedback, he magically scheduled next interview call. Design test document was very vague and mentioned that exercise is intended to be used only for hiring process. But, I highly doubt it. After wasting an hour on this interesting round and a week, I received an email with classic `unfortunately, we are moving forward with another candidate` text. Several glassdoor reviews also highlight negative interview experience. Ironically, interviewer didn't understand the latest cloud architecture concepts. He probably didn't know most of the cloud services mentioned in the presentation. Interviewer was more worried about project structure, C# code than high-level integration and architecture patterns. If you want candidates to propose architecture that match your fantabulous system, why do you even hire an external engineer?? No wonder there are so many architects from this company on LinkedIn. If you are expecting a specific design output, design test specification should clearly mention what you are looking for. If you think architects design systems based on one-liners, I'm very lucky that I didn't get a chance to work with so-called experts :) It seems like this company hires candidates after two or three applications. Now, I feel they are doing mock interviews to steal ideas from talented individuals.
Interview questions [1]
Question 1
Standard questions about software engineering, previous projects etc.,
I applied online. The process took 2 weeks. I interviewed at Phreesia (Toronto, ON) in June 2017
Interview
Phone interview with Recruiter, covered basic stuff, experience, pay
Detailed and semi-technical interview with VP Engineering, discussed architectures and some challenges they had solved in the recent past
Technical Coding interview (via Skype) with engineer in Visual Studio