Process
I applied on their website.
After a while, I received an email from a recruiter wanting to set up an initial over-the-phone screening interview. No behavioral questions were asked at the initial screening; it was just an exchange of basic information (typical).
Then, I was given a take-home coding challenge to complete over the weekend.
I was ghosted after submitting the coding challenge.
Questions
The coding challenge was a two-part take-home question, completed on their website.
In retrospect, the coding challenge was to implement an election determination algorithm, extremely similar to Moore's Voting Algorithm.
Was this helpful?
Interview Statistics
The following metrics were computed from 61 interview experiences for the Coursera Software Engineer role in United States.
Success Rate
Coursera's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having good feelings for Coursera's Software Engineer interview process in United States.
Coursera Work Experiences
- 4.0Good Salary, No ProblemsSoftware Engineer • Former EmployeeNew York, New York, United StatesJune 8, 2021Pros: The salary is very good, according to the effort.Cons: There are no cons or problems.
- 5.0Great people tackling a huge market with a golden missionSoftware Engineer • Current EmployeeMountain View, California, United StatesJuly 19, 2015Pros: Coursera is opening the world's most elite educational institutions to everyone in the world, and creating opportunities for people to dramatically improve their lives. It's a mission that gets me right out of bed every morning.Cons: The goals are audacious, and the business model is still in flux. This isn't a better mousetrap, like Uber cabs; it's a new configuration of a vast, complex ecosystem.
- 4.0Overall, a great experience with a few kinksSoftware Engineer • Former EmployeeDecember 21, 2021Pros: Managers cared about my growth and experience. The compensation was very good. The culture was balanced, and people believe in the company's goals.Cons: Some growing pains balancing engineering needs with product goals. The product was not divided very cleanly across teams, which caused problems from time to time.
Coursera Interview Questions
