Coursera software engineer interviews, as candidates describe them, combine timed coding, practical frontend or async problems, and for senior roles code review and system design. Four reports, none ending in an offer.
$159K
Avg. Base Comp
$190K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Four candidates describe Coursera software engineering interviews, and all four ended without an offer. The reports cover different levels and formats, so treat them as separate experiences rather than one fixed process.
The coding bar comes up most. A senior candidate describes a screening round on hash maps and string manipulation, then a main round with a LeetCode-hard word wrap problem under a fixed time window. That candidate says going over time and asking clarifying questions both cost points, so practice timed problems and state your assumptions rather than pausing to ask if you are preparing for a similar format. An intern candidate describes two coding problems in about an hour on Zoom, the second a hard dynamic programming question, and says a friendly interviewer did not change the need for a complete solution.
A Software Engineer candidate reports a different flavor. The phone screen asked for sequential progress bars in vanilla HTML, CSS and JavaScript, using async/await and promises, even after React was first suggested. The technical round that followed included a Tribonacci problem plus questions on why Coursera and on LLMs. Refreshing frontend fundamentals and async patterns looks worthwhile for that kind of role.
The senior report also mentions a code review round, a system design round that extended a vaguely documented existing system, a deep dive on past work and a hiring manager discussion. For design, practice asking targeted questions and committing to assumptions quickly. One more candidate reached only a recruiter screen, which was disorganized and focused on current salary, so have a short, polite answer ready for that question. Only the senior candidate reports six rounds, so do not assume the same count for every level.
Synthesized from 4 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Coursera process.
The Coursera interview process started with a phone screening where I was asked to build a progress bar using vanilla HTML, CSS, and JavaScript. The interviewer initially suggested I could use React, but then walked that back and insisted on plain JavaScript. The challenge was to create multiple progress bars that would run sequentially — each one starting only after the previous one finished. I had to use async/await and promises to handle the timing correctly. It was a practical frontend problem, not a typical algorithmic challenge, and the constraint of avoiding a framework made it trickier than expected.
After the screening, I moved to the technical round with someone from the team. This is where things got less predictable. I was asked a Tribonacci sequence problem, which is a variation on the classic Fibonacci interview question but requires a bit more thinking about recursion or dynamic programming. The interviewer also threw in some behavioral and culture questions, including why I wanted to work at Coursera and what I thought about emerging technologies like LLMs. The questions felt somewhat scattered — less focused on the specific role or backend systems I'd be working with, and more about general technical knowledge and fit. The team is based in India, and the whole process had a conversational feel to it, though the lack of clarity around what they were actually looking for was a bit frustrating.
Overall, I didn't receive an offer. Looking back, I think the screening round was where things went sideways. The progress bar problem seemed straightforward in concept but required solid understanding of async patterns to nail the sequential execution piece. The follow-up questions in the technical round felt more like they were testing breadth of knowledge rather than depth in any specific area. If I were to interview here again, I'd spend more time on frontend fundamentals and async JavaScript patterns, and I'd ask clarifying questions upfront about the actual tech stack and problems I'd be solving day-to-day.
Prep tip from this candidate
Focus on async/await and promises for sequential task execution — the progress bar problem required solid async patterns, not just DOM manipulation. Also be ready to explain and code practical frontend problems without frameworks, even if they suggest you can use one.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Coursera
Describing a data project and its challenges
| Question | |
|---|---|
| Slow SQL Query | |
| Justify a Neural Network | |
| User Experience Percentage | |
| P-value to a Layman | |
| N-gram Dictionary | |
| Digital Classroom System Design | |
| Incorrect Packets | |
| Optimal Host | |
| Your Strengths and Weaknesses | |
| Why Do You Want to Work With Us | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Random SQL Sample | |
| Weighted Keys | |
| Flight Records | |
| Prime to N | |
| Largest Salary by Department |
Synthesized from candidate reports. Individual experiences may vary.
Two candidates describe a recruiter screen. One says it was mostly about where they saw themselves in the next few years. Another says the call was disorganized, with missed appointments and repeated questions about current salary. Prepare a calm answer on compensation and a list of role questions in case the screener lacks detail.
Candidates report timed coding at this stage. A senior candidate describes a hash map and string screen, an intern describes two problems in about an hour including a hard dynamic programming question, and another candidate describes a vanilla JavaScript sequential progress bar. Expect the format to vary by role and level.
The senior candidate reports a LeetCode-hard word wrap problem with strict timing, then a code review round where they reviewed code written by the interviewer. A Software Engineer candidate reports a team technical round with a Tribonacci problem and questions about motivation and LLMs. Practice finishing under time pressure and reviewing unfamiliar code.
The senior candidate describes a system design round extending an existing system with vague documentation, then a deep dive into past technical work and a hiring manager discussion covering technical depth and behavioral topics. This sequence is reported by a single candidate, so other levels may see something different. Prepare to ask targeted questions and make assumptions quickly.
