For me the interview process went very smoothly and things were wrapped up in about 2 weeks. It included an initial phone screen with a technical recruiter, a short take-home coding project, a 4 hour block of interviews with various team members / managers / execs, and finally a 1 on 1 final interview with my potential manager.
Technical interview - very short and casual - questions like how did you get into tech, my background, what I’m looking for in my next role, etc.
Coding assessment took me about 3 hours to complete over the weekend. The project was very clearly scoped and explained. Built a small web service which has about 3 endpoints for creating and validating scheduled user appointments. Added some tests. Used flask, sql alchemy (which they use for their product) and a SQLite db. Was reviewed in a week and I moved to the next stage.
The four hour block included a) a live coding assessment with other engineers b) a system design interview with other engineers c) a cross discipline work process interview with a product designer and d) leadership / eng-culture interview with a VP of tech.
The live coding assessment was easier than I thought (was expecting algorithms) and it thankfully ended up being a short prompt to request some JSON data and parse it for the longest sentence. Used Python (that’s their preferred language but any language would do) made a couple mistakes since I had mostly been using Ruby in the past year and had silly syntax issues but they were very helpful and understanding.
The system design interview involved viewing a mock-up and designing a content system including database design schemas and API endpoints. Though they were very flexible and you could have discussed various other approaches and systems and the important part here seemed to be gathering requirements and asking questions and discussing trade offs before making recommendations.
The cross-discipline interview was mostly about how you work with other teams and non-technical people including project management practices and handling work and deadlines and communication.
The leadership interview was about how the company and engineering teams are setup and we discussed how engineering collaboration and culture is developed. Mostly discussed my experience working on teams and the scope of my previous work projects.
Waited a few days and got my final interview with my potential manager. We talked about my background, what challenges I’m looking for, etc. Learned more specifics about what the pod was working on to see if I’d be interested. Definitely got a lot of insight into their current work and projects which included integrations with several massive household-name tech companies who have purchased the product. Definitely got the chance to click with the manager and enjoyed the interview.
Got my offer a couple days later and accepted shortly after. The offer was very competitive. For a company that is trying to hire a lot of engineers and secured lots of series funding recently they moved pretty fast as I’d expect and seemed quite thorough. I also felt Iike I was given enough chance to get some good insight into the culture and work to make my decision.
How do you work with others & what sort of processes do you value when working with other engineers?
Describe a technical project you enjoyed working on and its challenges.
Talk about a mistake you made and what you learned / would have done differently
The following metrics were computed from 5 interview experiences for the Maven Clinic Senior Software Engineer role in United States.
Maven Clinic's interview process for their Senior Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for Maven Clinic's Senior Software Engineer interview process in United States.