The process is straightforward, nothing out of the ordinary.
The interview itself was of average/easy difficulty, but the problem is that this is the kind of company that looks for nitpicky reasons to not hire you.
I wrapped up the coding questions in half the time and all of their follow-up questions, yet later on they said I did not pass because I omitted something. I clearly stated that, because of the nature of the problem space, it did not account for these cases, and the interviewer agreed.
If I had known they were going to dock me for not doing something I explicitly asked them if it was okay not to do because of the specificity of the problem, I would've gladly done that. It was not a problem at all. Yet the interviewer failed me because of it. Thanks.
I was also told I talked too much? What kind of feedback is that. I answered behavioral questions in 30 seconds to 1 minute tops. I don't know how much shorter they were expecting, unless they were looking for simply "yes"/"no" responses.
Overall, this company does not understand how to interview or what they're looking for. I have a sense their criteria are absolutely not standardized and are just whether they like you or not.
Standard LeetCode stuff.
Behavioral questions (tell me about a time...)
The following metrics were computed from 12 interview experiences for the Chime Software Engineer role in San Francisco, California.
Chime'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 Chime's Software Engineer interview process in San Francisco, California.