I first heard about a position at Udemy via a Hacker News post, authored by their lead technical recruiter (Maggy Hillen).
When I sent an initial email, I was surprised at how responsive and polite she was. We scheduled an initial phone call according to my schedule, and we spoke about past experiences and various technologies I'd used. I was impressed by the level of technical knowledge she had, as well as her candor when I asked (in my opinion) difficult questions about the company's success and culture.
Following that call, we scheduled a follow-up technical interview (~4 days later) with one of Udemy's senior engineers (Cansin), and we walked through the design of a RESTful API within a Google document. The conversation was technical, interesting, and informative.
Within a few hours, Maggy asked if I would be willing to fly to their offices for an in-person technical interview. She put me in contact with Jennifer, who handled all travel arrangements.
The in-person interview was long (~5 hours) but not tedious, and each session was 1:1 or 1:2. I was also able to take a break for lunch with the company. It was a pleasant experience, and everyone made me feel welcome. The interview questions were broad (ranging from JavaScript API questions to Python decorators) but not difficult.
The day after my in-person interview, I was given a verbal offer, followed quickly by a written offer. The few questions I had about my contract were quickly resolved by the VP of engineering, and I was delighted to accept. Overall, the best interview experience I've had.
RESTful API design questions.
The following metrics were computed from 4 interview experiences for the Udemy Software Engineer role in San Francisco, California.
Udemy's interview process for their Software Engineer roles in San Francisco, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Udemy's Software Engineer interview process in San Francisco, California.