Process
I only went through the technical recruiter screening, which lasted 15 minutes but was scheduled for 30 minutes. It involved a brief description of myself and my experience. Then, there was a technical aspect of figuring out what the console would output. So, know your JavaScript, and know the tricky parts of JS.
Questions
Questions about what the console would output with setTimeout, or about scoping.
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
- 1.0Bad company for engineersSoftware Engineer • Current EmployeeMountain View, California, United StatesMarch 26, 2016Pros: - Great original mission. - Close to the Castro district in Mountain View.Cons: The current engineering leadership is poor. I would say it is one of the worst in the valley. The best engineers are leaving in droves to companies like Uber, Khan Academy, Airbnb, Quip, LinkedIn, and other smaller startups. There is no understanding of how to manage an individual engineer's career. They will promise you a lot when you join, but it will turn out to be a career graveyard.
- 4.0Great culture and remote work, but business uncertaintySoftware Engineer • Current EmployeeApril 25, 2026Pros: There is a good culture, full remote work, a modern tech stack, and friendly people.Cons: Edtech is at risk due to AI, with no clear way of how to grow the business.
- 5.0Remote work with good coworkers, but recent layoffs concernSoftware Engineer • Current EmployeeAugust 13, 2026Pros: It was remote, with good coworkers, and I liked the product.Cons: There were lots of recent changes and layoffs.
Coursera Interview Questions
