First, there's a take home programming assignment which is to be completed ideally in under two hours. The program is an appointment scheduling application where you're asked to design and implement a web service which will handle users requesting appointment registration. It's fairly straightforward in its requirements and you'll submit it via git.
Once they reviewed the take home assignment, they reached out to let me know they'd like to move on to a formal interview which was entirely online due to COVID. They got me set up for a 5 hour interview online with various teams covering different topics.
Session 1 was the coding portion. I was asked to create an application which read user posts from an endpoint and then we'd process them to find the longest sentence amongst the posts. I wrote this in Java which proved challenging as the endpoint they had set up for me to call was actually a gitlab hosted link, not a REST service, so you cannot read you have to scrape. The interviewers for this session were friendly and understanding that it was hard to call given it's not an actual service.
Session 2 was application design. The interviewers had a UI mockup and I was asked to design the back end and database structure to support it. There was lots of discussion around how I'd store this information in the database, what services would be called, what the JSON payloads would look like, etc. It was role playing an engineer seeking requirements from their product owner. It was genuinely very fun and my favorite part of the interview. The interviewers were hilarious and very talented, this portion made Maven very memorable.
Session 3 was more behavioral questions administered by just one interviewer. They were super friendly and kind. They asked about times when I've made a mistake, how I would approach different situations, and what I thought of X Y Z. It was just getting a feel for how I problem solve and interact with others.
Session 4 was with the engineering director and where you'd learn the most about the actual position and job you'd be doing. We talked a little about the teams, org structure, and position levels/titles. I felt like a cow being pushed through a processing line. There wasn't much emotional connection or warmness during this session and it wasn't long enough to get a full idea of what the position would be like.
A few days after the formal interview was over they reached back out quickly with feedback that they wanted to proceed with an offer. The offer was very competitive. One thing stood out to me, they specifically said "We're going to get together a number because we want to come back to you with an offer you're genuinely excited about. We want you here." They really understand people, and made me feel special.
What was a time that you made a mistake and what did you learn from it?
The following metrics were computed from 1 interview experience for the Maven Clinic Senior Software Engineer role in Boston, Massachusetts.
Maven Clinic's interview process for their Senior Software Engineer roles in Boston, Massachusetts is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Maven Clinic's Senior Software Engineer interview process in Boston, Massachusetts.