Speechify Ios Engineer Interview Questions
& Process

To apply, you need to provide a lot of detail on a tough project you worked on, plus your CV. They don't even look at your application with automation because you immediately get an email to set up a technical challenge. This is the first red flag. The second red flag is that the challenge is a 90-minute, video-recorded task done without a live person. The challenge itself is also pretty hard. I finished it with no errors and all tests passed, showing I used debugging tools well and had good expertise. The third red flag is that after 4 days, I got a standard rejection email saying no feedback could be given. I was confused how I could be rejected for the next stage with my experience and a great technical exercise, especially since this company seems to have tons of job openings. I can only guess they don't want to pay what they advertise and are looking for cheaper labor from other countries (I'm in London). I really think you shouldn't waste your time here.

I applied online and got an automated email for a coding challenge. I had 1 hour and 45 minutes to fix bugs in an iOS project. The challenge had three parts. Part 1 was debugging an iOS app with two tabs (Projects and Analytics) that had UI bugs, memory leaks, and crashes but all features had to keep working. Part 2 was fixing concurrency in a reminder service using three methods (callbacks, Combine, and Swift Concurrency) to fetch reminders at the same time and pass all tests. Part 3 was finding and fixing one bug in a login screen to move to the next step. Some files were marked as do not touch and changing them meant automatic failure. The time limit was short for all the debugging needed in multiple parts. It's tough, but I'd say it's too bad if you're not super prepared, I didn't know some of the APIs well (like dispatchGroup, TaskGroup, NavigationStack with path parameter) so I was learning them while taking the test.

The whole process was pretty chill and accommodating, taking about 4-6 weeks overall. It involved roughly 5 stages, covering things like SwiftUI, Live Debugging, and Swift Concurrency. The last interview was a live LeetCode problem and a system design question. It started with HR, then went through 2-3 recorded technical interviews, and finished with one live technical interview.