Real, anonymous reports from people who interviewed for Mobile Engineer at Speechify, newest first and distilled into what to expect across the loop.
I went through their process twice, and both times the common thread was how automated and impersonal it felt. When I first applied, I had a normal recruiter conversation, then a SwiftUI coding challenge, and later a debugging challenge that also involved an actual recruiter. It was still tightly constrained, but at least there was a person in the loop. The second time I applied recently, the process had shifted to a more automated setup: I had to keep my camera open and complete the same kind of debugging coding challenge without any recruiter joining afterward. After that test, nobody followed up with any meaningful feedback.
After an automated invite, I was sent a private GitHub repo and told to complete an assessment in 90 minutes. The setup was very proctored: my screen and camera were recorded, and it felt like someone would be watching the whole time. The tasks themselves were framed around implementing a set of requirements, and I had to work quickly inside the time box.
The interview process typically begins with a straightforward HR conversation focusing on the candidate's background and soft skills, which serves as a preliminary assessment before technical evaluations commence.
Candidates often face automated coding challenges that are timed and proctored, requiring them to complete tasks under surveillance, which can create pressure and affect performance.
The technical rounds include hands-on coding tasks, such as building SwiftUI apps or debugging existing code, often with tight time constraints and specific requirements, which test both coding skills and problem-solving under pressure.
Candidates are expected to utilize AI tools during assessments, but often have to use their own resources, which can lead to frustration if not clearly communicated beforehand.
Post-interview communication tends to be minimal, with many candidates reporting a lack of feedback after assessments, leading to feelings of frustration and uncertainty about their performance.
Some candidates experienced invasive requests during the interview process, such as access to personal GitHub repositories or installation of monitoring software, which raised concerns about privacy and boundaries.
