Process took a couple weeks.
Talked with recruiter. Was given a HackerRank question to solve. 6 hours onsite including lunch (it was a bit draining, 4 hours of which were coding related).
Everyone was cordial but I didn't really get to even find out much about who they were or the company as a whole or much time to ask questions about "life at Mixpanel" or related as I would just get to coding right away via Coderpad.
A new person came in every hour, introduced themselves briefly and I started coding HackerRank-like questions. The interviewers primarily remained quiet throughout this time and just sort of watched me code. There was 1 hour of whiteboarding which I found a bit more refreshing as the interviewers engaged a bit more and was able to establish some sort of rapport.
It wasn't a negative experience but not a positive one. It just felt I didn't really need to be onsite or rather the entire 6 hours could've been done remotely.
I thought I did "okay" as I was close/on the path to a solution or got the solution for each question but left feeling I wasn't going to get an offer, which was true and I was okay with that.
Decipher the type of credit card a credit card number belongs to based on some conditions. The code should be extendable so that more cards or conditions could be added. (e.g. "cards starting with 4 and are 16 digits long are VISA")
The following metrics were computed from 10 interview experiences for the Mixpanel Software Engineer role in San Francisco, California.
Mixpanel's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Mixpanel's Software Engineer interview process in San Francisco, California.