Taro Logo

Software Engineer Interview Experience - Seattle, Washington

August 1, 2023
Negative ExperienceNo Offer

Process

  1. Phone screening with recruiter: Went very well. Discussed projects I had worked on, I work at a competitor in the telemedicine space so most of it was around digital clinic experience. 2. Interview with Engineering Manger: Went very well. Again discussed my projects I had worked on. We connected on what I was looking for as far as team dynamics. Got an email 30 minutes after letting me know they were moving me on to the technical interview. Email said it was not a coding exercise but instead a conversational interview. 3. Technical interview: 1st attempt -> Interviewer was a no-show. Contacted the recruiter after waiting in the meeting for 30 minutes. Recruiter replied 4 hours later explaining there was a mixup and that another recruiter would reschedule the technical interview. I did not receive anything from the new recruiter so after 2 days I used their own calendaring link and rescheduled it myself. I sent the confirmation to the original recruiter. After another day she finally replied letting me know that method for rescheduling would work. Attempt 2 -> Interviewer was 10 min late to the technical interview. They stated they had only been there 2 months and were surprised they were interviewing. This was the same interviewer that was a no-show. Technical assessment went pretty well. We had both a high level architecture and patterns, as well as a deep dive into platform specific technical decisions. Then the they said they would send me a link to the live coding portion. So that was fun, considering it wasn't supposed to be there. But I dealt and it was actually productive. The instructions were: "Go through the code". 3. Followup email: I hadn't heard anything from the recruiter in a day so I reached out and asked about the coding exercise being a surprise. I received an automated email 20 minutes later saying they were going another direction with hiring. All in all I was grateful for the experience and practice. From what I've heard from others in the space and former employees, it's a great place to work but their people team is dysfunctional. A lot of miscommunication, inexperience with hiring and lack of leadership that predates the labor market shift. Perhaps the wave of candidates now applying was just a perfect storm that exposed the leaks?

Questions

Swift related questions:

  • Discuss a property wrapper and give an example of one in practical use.
  • Discuss protocol oriented programming
  • Walk through making a network request.

Coding: "walk through the code" -> we were strolling!

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Maven Clinic Software Engineer role in Seattle, Washington.

Success Rate

0%
Pass Rate

Maven Clinic's interview process for their Software Engineer roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Maven Clinic's Software Engineer interview process in Seattle, Washington.

Maven Clinic Work Experiences