Me postulé a través de un reclutador. Acudí a una entrevista en Noom (Chicago, IL) en feb 2022
Entrevista
I had a coding round after being reached out by a recruiter. The question was the same as the one described in the section with the Baseline/Temporary coach roles.
I have to say, the interviewer was late, and there is no correct way seems like. The whole thing turned into design question than a coding round which I was fine with. Having such vague requirements to the whole question felt a bad way to assess a candidate.
Preguntas de entrevista [1]
Pregunta 1
Same process. The question was the same as the one described in the section with the Baseline/Temporary coach roles.
Me postulé en línea. El proceso tomó 1 semana. Acudí a una entrevista en Noom (New York, NY)
Entrevista
Mainly went thru the initial HR screen and then we found out that we were not a good match due to difference in the infrastructure their team uses vs my own specialties.
Preguntas de entrevista [1]
Pregunta 1
What tech stack are you comfortable with using, and how do you usually go about building a software service.
Me postulé a través de un reclutador. El proceso tomó 4 semanas. Acudí a una entrevista en Noom en sept 2022
Entrevista
I was originally reached out to by a recruiter. Pretty standard tech interview process: 1. Recruiter phone screen 2. Tech screen (with coding) 3. System design (whiteboard) 4. Final round, 3 in a row (System design, coding, behavioral/tell me about a time where you...) Everyone was very nice, questions seemed appropriate for role level, and I received positive feedback throughout the process. After the final round of interviews, I met one last time with a coordinator who told me I would receive feedback within a few days at the latest. I checked in with her several times as days/weeks went by, and never heard anything - I was completely ghosted. I felt that I did very well on the final round, but who knows. Maybe they went into a hiring freeze or the position was filled, or maybe I bombed. I spent many hours interviewing with them and preparing, so it's a pretty bad look to be ghosted like this.
Preguntas de entrevista [4]
Pregunta 1
Tech screen: Write a program to model coach time-splits between three types of coaching. You are provided with a coach's default time split, as well as a list of "overrides" where the coach deviated from their base time split. Part of the question revolved around data modeling, part involved the algorithm used to find a coach's overall average time split over a period of time.
Tech final round: Given a list of GPS coordinates and timestamps for a workout, write a program (data model and algorithm) to determine the average splits for each mile/KM that the user ran. I was asked to consider gaps where a workout was paused and later resumed so that they would not count towards the split times.
System design: Given two users' list of foods eaten, discuss an algorithm that could be used to find foods that both users had in common. Follow up questions asked to discuss how to solve if duplicate foods are present, time complexity, space complexity, etc... Eventually the problem evolved to include millions of foods and a cluster of so many computers with limited memory to solve the problem.
Me postulé a través de una recomendación de un empleado. El proceso tomó 4 semanas. Acudí a una entrevista en Noom (New York, NY) en sept 2022
Entrevista
The process was overall alright, they didn't think I was quite good enough but oh well. The interviews were standard, two screens, an onsite with two interviews, and then a hiring manager convo if they think you're worthy. 1st phone screen - had to do the task time average calculation problem that other people have mentioned in their reviews 2nd phone screen - talked through how I would code up a basic problem (finding common things in two lists) and then had to talk about how to solve that problem at scale (so sys design-ish) Onsite interview #1 - come up with a data structure for a fitness tracker app that tracks mile/km splits (can pause in the middle of a workout) and then write a function that derives the splits from the data Onsite interview #2 - URL shortener for system design, pretty standard and they weren't expecting crazy scale so was pretty easy
