Process
The process took 4 weeks.
After more than 3 weeks of waiting after submitting my application, I was contacted by the CTO and we made an appointment for a call 1.5 weeks later. On that date, nobody called me, and after I reached out to the CTO to ask why, they said it was a mistake and we rescheduled the call for the next day.
After a quick intro from the CTO during the call, I was asked to tell something about myself and my experience. After that, I was asked a number of technical questions which can be considered easy for a person who has multiple years of experience in mobile development.
At the end of the interview, they promised to reach out to me regarding the results, but I've never heard back anything from them.
Questions
- Which thread should one perform UI updates on iOS on?
- How to accelerate algorithm execution on iOS?
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the DeepL Mobile Developer role.
Success Rate
DeepL's interview process for their Mobile Developer roles is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for DeepL's Mobile Developer interview process.
DeepL Work Experiences
- 3.0Smart colleagues hindered by weak leadershipEngineering Manager • Current EmployeeMunich, BavariaAugust 13, 2026Pros: Extremely smart people across the orgCons: Poor leadership and middle management
- 1.0Widely used product but lacks empathetic leadershipSoftware Engineer • Former EmployeeBerlinAugust 17, 2026Pros: A product that millions use dailyCons: The leadership is not empathetic at all.
- 3.0Good benefits but swiftly deteriorating cultureTooling Engineer • Former EmployeeLondon, EnglandOctober 30, 2024Pros: - Good salary and benefits - Interesting workCons: - Lack of internal support - Lack of understanding from HR - Unpopular policies from top-down
