My interview experience with Palo Alto was unprofessional. The interviewer didn't introduce themselves and immediately sent a Codility coding challenge.
They insisted on Python, even though I'm primarily a Java developer. The challenge involved encoding strings like this:
['a', 'a', 'b', 'b', 'c', 'c', 'c'] -> ['a', '2', 'b', '2', 'c', '3'].
If the input is chars = ["a","a","b","b","c","c","c"], the output should be output = ["a","2","b","2","c","3"].
If the input is chars = ["a","b","b","c","c","c"], the output should be output = ["a","b","2","c","3"].
If the input is chars = ["a","b","b","c","c","c","c","c","c","c","c","c","c","c","c"], the output should be output = ["a","b","2","c","1","2"].
Do not use any data structures.
The following metrics were computed from 2 interview experiences for the Palo Alto Networks Principal Software Engineer In Test role in Santa Clara, California.
Palo Alto Networks's interview process for their Principal Software Engineer In Test roles in Santa Clara, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Palo Alto Networks's Principal Software Engineer In Test interview process in Santa Clara, California.