Prove Interview Questions
& Process

A recruiter reached out and asked me to apply online. Then came several interview rounds: first a recruiter screen, then interviews with the Hiring Manager, a System Design interview (tailored for SRE), a Coding interview, and finally a Panel interview. It felt like a lot of time and was a bit chaotic. Coming from a much larger company, I'm used to more structured interviews, so some of the inconsistencies here were noticeable. The Hiring Manager interview was mostly about seeing if my experience fit and if I was a good match. The System Design interview was the best part, the only one where the interviewer seemed prepared, engaged, and knew their stuff, and it felt like a real technical discussion. The Coding interview was a fairly easy LeetCode-style problem, but the interviewers seemed junior and didn't have much depth, making it hard to have a deep technical chat. The Panel interview was the worst: four interviewers who seemed unprepared and not really into it. They mostly went over my resume, asked repetitive and vague questions already covered with the Hiring Manager, and barely interacted. One of them just threw out a question about Kubernetes CRDs without any context, like a buzzword test. The vibe was tense, like they'd argued before coming in, which made it awkward. I followed up with the recruiter but just got a generic reply that they went with someone else. My guess is they have a super specific skill set in mind, and if so, it'd be better to filter that early instead of wasting everyone's time. This whole thing made me question their internal team dynamics and how they run interviews.

After an initial recruiter call, I had 3 main interview rounds. The first was with the Hiring Manager, where we discussed my past experience and some resume-based questions. This part felt pretty good. Right after that, I had two back-to-back coding interviews. I managed to finish the coding questions and pass the test cases, and also answered the follow-up questions correctly. Sadly, two days later, the recruiter let me know I didn't make it. The reason given was that I wasn't vocal enough about my thought process while coding, specifically not explaining my approach. This feedback was a bit surprising and disappointing, especially since I did respond to their follow-ups.

The interview process at Payfone was really thorough and spot on. It kicked off with a Phone Screen with the VP of HR, and then I had an onsite interview the very next day. The onsite was also led by the VP of HR. We went over my skills and experience, specifically focusing on my background in a startup environment and the transferable skills I could bring. They also asked why I was interested in Payfone and what I knew about their industry. Then, we dug deep into hiring metrics, process, strategy, handling ambiguity, and challenges. I also had to present my references and they asked about my earliest possible start date.

A couple of issues based on my lived experience with the Prove interview process: 1) The sales mgmt team (at least who I met) was young. My opinion is that older candidates may have a tougher road as opposed to younger candidates. There is more experience amongst the tenured reps but most new hires seem to be a younger demo. 2) Hiring down levelers. Candidates that. held mgmt/vp positions formerly are being hired as IC. It feels like a big win to get a candidate like that and bring them on board. But they are probably looking for their next VP gig and using the prove IC position as a bridge. Also...if you worked at Twilio...you may have the inside track here. Overall it was not an unpleasant experience. The interviewers were engaged, for the most part, and had really great energy. I just think there are some unforced errors happening that will resolve themselves in the long run.