Maven Clinic Software Engineer Interview Questions
& Process

First, there was a phone screening with a recruiter. We talked about my past projects, especially my experience in the telemedicine sector, which is similar to their digital clinic work. Then I interviewed with the Engineering Manager. We again discussed my projects and what I'm looking for in terms of team dynamics. I got an email about 30 minutes later saying they were moving me forward to the technical interview. The email mentioned it would be a conversational interview, not a coding exercise. For the technical interview, the first attempt, the interviewer didn't show up. I waited 30 minutes and then contacted the recruiter. They replied 4 hours later, saying there was a mix-up and another recruiter would reschedule. I didn't hear from the new recruiter, so after two days, I used their scheduling link to reschedule myself and sent the confirmation to the original recruiter. After another day, she finally confirmed that method would work. For the second attempt, the interviewer was 10 minutes late. They mentioned they'd only been there two months and were surprised they were interviewing. It turned out to be the same interviewer who missed the first appointment. The technical assessment went reasonably well, covering both high-level architecture and patterns, and a deep dive into platform-specific technical decisions. Then, they told me they would send a link for a live coding portion, which was unexpected since it wasn't supposed to be a coding exercise. I managed it, and it was productive. The instruction was simply to 'walk through the code.' After a day without hearing back, I reached out to the recruiter about the surprise coding exercise. I got an automated response 20 minutes later stating they were proceeding with other candidates. Overall, I was thankful for the experience and the practice, despite the perceived dysfunctionality of their people team, which I've heard about from others.

It started with a take-home programming assignment that should take about two hours. The task was to build a web service for an appointment scheduling app, handling user appointment requests, and submit it via git. After reviewing the take-home, they invited me to an online interview, lasting 5 hours total across different teams. Session 1 was coding: build an app to scrape user posts from a gitlab link (not a REST service) and find the longest sentence. I used Java, which was tricky because the endpoint was a gitlab link. The interviewers were cool about it though. Session 2 was application design. Given a UI mockup, I had to design the backend and database, discussing storage, service calls, and JSON payloads. It felt like role-playing with a product owner, and was my favorite part, thanks to the fun and talented interviewers at Maven. Session 3 was behavioral, with one interviewer asking about mistakes, how I'd handle situations, and my thoughts on things, to gauge my problem-solving and interaction style. They were really nice. Session 4 was with the engineering director, where I learned most about the job. We talked about teams and the role, but it felt impersonal, like being processed, and wasn't long enough to get a full picture. A few days later, they quickly gave feedback and wanted to move forward with a competitive offer. They really emphasized wanting me there, saying they'd make an offer I'd be excited about, which made me feel special.

First, there was a recruiter screen, followed by a take-home technical assignment. They didn't provide any feedback on why I wasn't moved forward. The assignment involved building a web app for scheduling appointments. It was pretty open-ended, allowing focus on different components.