My interview process with Dooly was quite positive overall. Everyone I met with was very kind and personable. The process started with Dooly's in-house recruiter reaching out to me to see if I would be a good fit for the role. I had a good feeling about the company and role after speaking with her, and knew I wanted to move further in the interview process right away. Afterwards, I had a short interview scheduled with the Directory of Engineering. This was a non-technical chat where we shared a bit about our professional backgrounds and why I was interested in working for Dooly. The next two interviews were more technical in nature. The first technical interview was a pair-programming challenge with the CTO. I really enjoyed this exercise as it was very hands-on (rather than a leetcode-style puzzle question). It felt like the day-to-day work I've done as a full stack developer in other roles. I was given the option to use a technology of my choice, which was a nice bonus. The second technical interview was a deep-dive discussion regarding a project I've worked on in detail. The engineer conducting this interview asked me to verbally explain the architecture of a project I worked on, and then drilled into various parts of it through probing questions. The final interview was with leaders of PM and UX. I would classify this as a "behavioural" interview where I was asked questions assessing my general aptitude surrounding product development and design/ux. After I completed the interview process, it took just over a week for them to come to a decision. My application was unfortunately passed on due to my lack of experience with their front-end technology of choice. However, I was also told there may still be opportunities for me to become a Dooligan in the future!

The process was very transparent and respectful of my schedule. Everyone was very kind and welcoming and all of the interviews and there were no curveballs or tricks. After a quick chat with the Hiring Director, the process is kicked off. A clear breakdown is provided of each portion of the interview. For me the process involved: A pretty casual chat about past experiences. A technical interview (pair programming). A technical deep dive on a past project. A chat with the Product Engineering team. Overall the process took about 2 weeks, but that was mostly due to my existing schedule.