CoverMyMeds Software Engineer Interview Questions
& Process

Started with a recruiter call that gave a good vibe. Then, a half-day session with about a dozen people, a mix of career and programming questions. They mentioned a pairing exercise on real business logic, but instead, I got a 100-line puzzle code listing with no comments. The recruiter had said no puzzles, so I treated it like one, not realizing it was a team exercise. This led to them thinking I wasn't a team player. The ending was sudden. Some interviewers were great, but others acted like arrogant rockstar developers.

I went through 2 rounds of interviews. First was a phone screen, then a technical interview. The technical interview was supposed to be a week after the phone call, but it got pushed back to two weeks later because stuff happened. I figured it was no big deal. On the interview day, I joined a Teams meeting and waited for about 30 minutes with no one showing up. I emailed the recruiter to ask why nobody came to the meeting. I got a reply late in the day saying the interviewer had something come up. That felt off, but I rescheduled again. When the day finally arrived, I met two people, an engineer and the hiring manager. They gave me three problems to solve in different coding languages, and I wasn't allowed to look anything up. The interviewers seemed pretty distracted and uninterested. These weren't like LeetCode problems; one was a whiteboard-style problem. I asked for help with syntax a couple of times, which I could have easily Googled, but I just got stared at. After it ended, I sent two follow-up emails but never heard back. They ghosted me. It was a really bad experience, and I'm honestly glad I didn't get the job.

The interview process had three major rounds. The first round was a resume-based phone interview where the technical recruiter asked questions based on my past work experience and projects. The recruiter knew a lot about technical stuff like web development. The second round was a live coding interview with a developer. They give you two programming questions to solve in one hour. They watch your approach and ask extra questions if you're stuck or run out of time. It was smooth, and based on my performance, I was called for the final round, an all-day coding interview at their office. The final round was a problem-solving round where they give you a mock-up or a customer problem and ask you to build a full stack web application solution that meets the requirements. The application is tedious and lengthy but doable. You'll work with company developers who observe and help you. I wasn't able to show enough working code by the end of the day. Overall, it was a good experience with friendly people and an excellent work culture. They try to get to know you, and you can do the same.