Initially, I met with a Director of Engineering for Udemy at a school event. They invited me in for a quick informational meeting two weeks later. I went to the office, met some of the team, and discussed the interview process at length.
The following week, I was given a coding challenge to complete on Friday. Then, I came in the following week to present my work. There was a 45-minute session with one group, another 45-minute session with another, then lunch.
They asked for my feedback about the process, which I provided. They said they'd get back to me the following week with a decision after interviewing several other candidates.
Almost exactly a week after the on-site, I received a very polite rejection email providing feedback about my code and encouragement to stay in touch, as new positions are always opening up.
How could you break this function?
What would be a way to keep access tokens secure in production?
The following metrics were computed from 1 interview experience for the Udemy Lead Software Engineer role in San Francisco, California.
Udemy's interview process for their Lead Software Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Udemy's Lead Software Engineer interview process in San Francisco, California.