There was one 30-minute phone screen followed by an hour live coding exercise with two of their software engineers.
It felt like they were figuring out their hiring process on the fly, as the questions were presented through a shared view of a Google Doc and one of the questions was an especially bad "tell us what the result of this unrealistic abuse of scoping rules would be".
Their responses to my clarifying questions were "well, you could do X...or you could do Y", which, as an interviewee, was not helpful.
Generally it felt like there wasn't a clear idea of what they were assessing and why, so they resorted to stereotypically bad, hazing-style coding questions because they didn't know what else to do.
What is the value of x after this series of loops?
The following metrics were computed from 1 interview experience for the Proofpoint Senior Software Engineer role in Rochester, New York.
Proofpoint's interview process for their Senior Software Engineer roles in Rochester, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Proofpoint's Senior Software Engineer interview process in Rochester, New York.