Medly Pharmacy Software Engineer Interview Questions
& Process

The interview process was good! Two aspects that stood out to me during the interview process were: 1) The 4 rounds of interviews were mostly conversation based, except for one ~30 min of whiteboard / shared screen coding. 2) I had the chance to meet (virtually) with 8 people; probably the most I've met for an interview. The first part actually took me by surprise, because I was expecting the standard, run-of-the-mill whiteboarding interview rounds. But it was quite the opposite! The interviews were very discussion oriented, focusing on past projects and work (what I've built in the past), and also and best practices and opinions when it comes to software engineering (distributed systems centered around microservices). I realize that the efficacy of whiteboard coding interviews have always been hotly debated, and I found it refreshing and interesting that Medly took a different approach to technical interviews. The engineering recruiter, M., did a fantastic job coordinating and being the point of contact. No joke - she's the BEST recruiter I've had the pleasure to work with. I say this because most recruiters I've communicated with in the past have been fairly 'neutral' (not in a bad way). But M. was really personable, energetic, and helpful - it gave me a great first impression of Medly! M. always followed up very promptly after each round of interviews, and as well as advising me of what to expect for the next round. This was the first time I felt that an internal recruiter was 'on my side', wishing and helping me to succeed in the upcoming interviews. M was also accommodating with my very hectic schedule, since I was searching for a job full time.

A recruiter will send you a coding challenge before reviewing your credentials. In my case, I successfully completed the challenge but never heard back from the recruiter even after following up. My advice for interested candidates is to never do a code challenge for a company before at least having an intro call. Having the opportunity to communicate with the recruiter and ask questions before spending time completing an assignment is essential since otherwise you're just wasting candidates time. From a hiring perspective this is also advantageous since many engineers refuse to interview with companies that initialize their process with an assignment or leet code type problem.

I went through Medly's interview process and it was a great experience. They had practical system design questions and coding exercises. Be ready to discuss your previous projects and what you contributed. You'll be talking to PMs, designers, eng managers, and other engineers. Also, the recruiter, Margo, was amazing. She answered all my questions about the company's growth, profit, funding, the tech stack, and the engineering team. Super efficient, responsive, and accommodating. I didn't end up joining, but chose another offer that was a better fit for me.