ID.me Interview Questions
& Process

The whole thing took about two weeks: First there was an initial call with HR, then a call with the hiring manager. After that, there was a loop of three separate calls that were technical/coding focused (SQL/Python). Finally, there was a final call to make the decision and offer.

The recruiter was super enthusiastic on the phone but then ghosted me or took days to reply when I actually had questions. The process felt like overkill for a company that isn't that well-known. It started with an initial screening, followed by a 30-minute chat with my potential direct supervisor. Then, there was a take-home assignment to solve a current company problem. After that, I had three more 30-minute interviews with leaders in related roles – which honestly could have been a panel. Two of those leaders were great to talk to and offered good insights, but the program manager with initials A.C. was really unwelcoming. The recruiter said they'd get back to me within a week, but it took almost three weeks for a formal rejection. They didn't even hire anyone from the first round because they reposted the job. They seem to have a pattern of negative reviews, so it's probably not worth applying.

The interview process was quite a journey, starting with a recruiter screening call, then a 30-minute chat with the hiring manager. Next up was a psych leadership exam to gauge my complex problem-solving skills and ability to execute. After that, a portfolio review where I presented 2-3 case studies and fielded questions for about an hour. This was followed by executive interviews and a design exercise, which they described as a chance to see what it's like working with me, encouraging me to ask a lot of questions and conduct a workshop using Miro. The whole experience had long delays in scheduling, sometimes 3 months, and then sudden interview requests, like being asked in the morning for an interview that afternoon. The psych evaluation was particularly odd, asking about my political views and the specific year I graduated.

It started with a recruiter call. Then there was a call with an engineering leader. After that, there was a coding interview, a system design interview, and a managerial interview. Finally, there were two behavioral interviews. My recruiter was good with communication. They told me for the coding interview to write pseudocode since it's a managerial position, but in the actual interview, they wanted real code. They were fine with pseudocode after I mentioned it, so there was a slight miscommunication there. For system design, instead of designing a system, they asked how the internet works and about byte flow through TCP/IP and its protocols. This was unexpected, as there are so many CS concepts, and I'm not sure how they expect us to know everything in detail, like specific protocols (TCP, UDP, SHA2).