Teladoc Health Software Engineer Interview Questions
& Process

A 1-hour technical interview with the Team Lead and a Senior Developer. After that hour, we move on to a 30-minute session with 2 LeetCode exercises, sharing screen and camera. One exercise is in SQL and the other is an algorithm problem.

I applied online and had an initial chat with the recruiter. Then, I met the hiring manager for a discussion about my background and some behavioral questions. After that, I had a take-home assignment, which they said should take about 3 hours. The final interview was a 1-hour session with senior engineers where we talked about technical stuff and went over the take-home project. They told me I was a finalist and then I had to do reference checks through an online survey tool. The recruiter really pushed to get this done fast. I got a verbal offer with a decent base salary and a bonus plan, but no sign-on bonus or stock options. I ended up taking another job that was better.

Started with an external recruiter, then a hiring manager interview. Following that, there were 4 online technical sessions and 4 onsite technical sessions. The whole experience was a bit rough. I was told the company is corporate and growing, not a startup, and has a slow delivery pipeline, which is fine, but it means expectations should be managed. Given the company's size, the interview process could really use some improvement; I expected better. The external recruiter was great though, very caring. They don't really have a structured interview process. The plan was online for pure technical stuff and onsite for team discussions, but that wasn't the reality. One online interviewer (a manager) was unprepared and the interview was very short. I arrived early for my onsite interview but was taken in about 30 minutes late without any explanation or apology. During the 4-hour onsite, I only got about 5 minutes to ask questions. The initial plan was all technical assessments online, but it seemed like the online technical sessions didn't really count, which was surprising. It was stressful due to a flight delay and lack of sleep. The Lewisville office is big but mostly call center and non-engineering roles, with only a few engineers, so it might not reflect a strong engineering culture. They use Rails, so learning about it deeply, including libraries and implementation details, is recommended. Practicing whiteboarding might help, but since they collaborate with other offices, software-based diagramming might be more useful.