The initial phone screening, lasting 10 minutes, did not involve questions. Instead, it consisted of a briefing on the company structure, followed by the recruiter introducing the coding challenge.
The coding task was to build a frontend interface for a provided API. The recruiter stated it should take 2-6 hours to complete, encouraging creativity. The email containing the coding challenge mentioned a desire to move away from whiteboarding, opting instead for a more relevant discussion during the subsequent onsite interview.
Two weeks later, at the onsite interview, I met with five people and the technical recruiter. The first interviewer asked me to solve a problem on the whiteboard. I mentioned that while I had no issue with whiteboarding, the prior email instructions indicated it wouldn't be part of the process. He then requested I solve it on my laptop using jsfiddle. The problem required a specific solution I hadn't encountered before, so I asked to look it up. While I found documentation on MDN, the interviewer deemed it "too good" and prohibited its use. Consequently, I attempted the problem without any resources, which significantly slowed down my progress.
The next interviewer greeted me and handed me a paper with a coding challenge, instructing me to solve it in any way I preferred. I began working on it while she used her phone. This was the most awkward part of the entire interview process. I attempted to explain my approach but felt I was disturbing her. She also didn't notice that the cable for the external screen had become unplugged, preventing her from seeing my work.
The subsequent three interviews were with more senior staff and proceeded well.
A week later, I received an email stating I had been rejected. Five days after that, I received a new coding challenge on Hackerrank. I emailed the recruiter for clarification, and a few hours later, the recruiting team sent an email asking me to ignore the new challenge.
In conclusion, the people were friendly (with one exception), but the interview process was highly unorganized and unprofessional. I am disappointed because the preparation instructions provided for the onsite interview did not align with the actual experience, leaving me feeling unprepared.
Had to sign an NDA, but there were JS, HTML, and CSS involved.
Lots of cultural fit questions:
The following metrics were computed from 14 interview experiences for the Coursera Software Engineer role in Mountain View, California.
Coursera's interview process for their Software Engineer roles in Mountain View, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Coursera's Software Engineer interview process in Mountain View, California.