Solicité el puesto a través de un captador. El proceso duró 4 semanas. Acudí a una entrevista en Helm.ai (San Francisco, CA) en feb 2024
Entrevista
I was interviewed in Feb 2024. The entire process took 4 weeks.
1. Recruiter call
2. 1 hr Tech screen (coding question. not leetcode style)
Once tech screen was successful, I was invited for virtual onsite
1. 1hr coding interview (Graph question)
2. 1hr python debugging session.
3. ML System design.
4. ML & Math test
5. Project discussion
All the interviewers were really nice and genuine. The ML and Math test was unusual(The person conducting this interview was seemingly uninterested.) The test was about knowledge of ML and calculus. Not sure if you need calculus to effectively do your job.
Preguntas de entrevista [1]
Pregunta 1
questions are not usual leet code style questions.
Solicité el puesto a través de un captador. El proceso duró 1 semana. Acudí a una entrevista en Helm.ai en may 2023
Entrevista
The initial phone screen involved verbal questions about MNIST data, in particular data augmentation. Don't waste your time studying ML for the technical screen. My interviewer was very curt and acted like interviewing me was an inconvenience.
Preguntas de entrevista [1]
Pregunta 1
The technical screen is leet code problem 200. If you can solve that in less than 30 minutes you win and get to go on to the next set of interviews.
Solicité el puesto a través de un captador. El proceso duró 3 días. Acudí a una entrevista en Helm.ai en feb 2023
Entrevista
Recruiter reached out, scheduled a tech screen with a research scientist, told me that it have an ML algorithm problem and will not be a LeetCode question. Guess what, it was a LeetCode question. After the interview, recruiter ghosted and did not reply to messages on LinkedIn. Got an auto-generated rejection email after a week.
