I had to take a programming test (around 4 hours) in a language of my choice. There were four assignments (implementation, debugging, changes to code etc). The test code base that I had to work with was reasonably complicated. It took some time to figure out what it was doing & what I was supposed to do. You are graded on completeness / correctness (whether you can get it to compile) / solution efficiency / approach / code readability etc. They checked on me a cpl times during the test to ask if I had questions & I was free to take breaks if/when needed. Internet access was provided.
I did not do well, even though I consider myself a decent programmer & I eventually got a hang of the overall logic in their test code.
In hindsight, I think a better approach would have been to split the overall test into multiple segments of an hour each: 1 programming assignment, a debugging session with a technical member of their team present ('pair' programming ...), a white boarding session to write algorithms/programs etc. etc. That is, multiple approaches to evaluate instead of giving the candidate several hours to work on assignments on a laptop by himself/herself ...
Other candidates may disagree ... or maybe I'm complaining too much & am technically 'challenged' :)
Regardless, the overall experience was good / interesting. The person I dealt with was very courteous.
N/A.
The following metrics were computed from 1 interview experience for the Check Point Software Software Engineer role in San Carlos, California.
Check Point Software's interview process for their Software Engineer roles in San Carlos, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Check Point Software's Software Engineer interview process in San Carlos, California.