Recruiter phone screen, take-home coding challenge, and onsite interviews. Onsite interviews consist of engineering values, two 'pair' programming sessions, engineering system design interview. A recruiter will call you back about the final decision. The conversations about their engineering culture were positive. I was able to ask questions to understand how the product engineering works, and everyone seems to really enjoy working at Policy Genius. I basically passed all the 'cultural and engineering values interviews', except the technical part... for the 'pair' programming session, I thought I performed okay since I was able to get to the end of the problem with the expected outcome, but ended up having the recruiter saying that the feedback says there were too many red flags in regards to my technical ability. First of all, it wasn't a pair programming session, not much interaction was going on during the interview, and I really didn't know what to expect from it or how I was expected to perform within such short period of time. It was just me trying to explain my code, figuring the solution, and code my way through. Since the wording of the problem was also ambiguous, I wasn't getting the right outcome even though my solution was right. Of the four engineers I 'pair-programmed' with, only one of them eventually helped to clarify the ambiguous part. I feel like I was being judged unfairly for my coding ability, and I really wish they could have provided more visibility about what to expect from an interviewee for the 'pair programming session', so I know what to expect and focus on while preparing for the interview. After the onsite interview, I emailed to ask for the status of my candidacy. There was no response. I had to email again after a few days to have the recruiter reply to ask for a 10 mins chat. I gave him my availability, but he didn't reply until the end of the next day. I did not feel respected about my time at all, I was left hanging the entire time. It could have been an easy email rejection, with feedback, and an option to call for additional feedback.

Started with a short video interview, then a code challenge (not timed) in any language I wanted, followed by an onsite interview. The onsite was a long day, with 7 different sessions - standard interview questions, pair programming, etc, varying 1-2 people per session. I was able to get a good sense of the company and the engineering department. Overall, I never felt like they intentionally asked anything that was too hard or unrealistic. It was more about seeing if my strengths and personality were a right fit for the company.