Maze(s) triggers PTSD in me. I was asked to write a code to generate one using a 100x100 grid in an Google interview in 40 min such that it was "fair". It was for L6/L7 (IC) position. I wrote a working code and the interviewer even acknowledged that I had atleast have a working code compared to others. The actual time I had was 30 min as 10 min included upfront discussion about what "fair" means and some time after-the-code discussion on improvements.
I was rejected with lean-no-hire (or weak-no-hire .. I don't remember the exact term but basically not a strong reject).
I like the definition proposed in the post - all possible mazes should be equally likely. A function could return the same maze each time and pass the criteria above.
Comments
Maze(s) triggers PTSD in me. I was asked to write a code to generate one using a 100x100 grid in an Google interview in 40 min such that it was "fair". It was for L6/L7 (IC) position. I wrote a working code and the interviewer even acknowledged that I had atleast have a working code compared to others. The actual time I had was 30 min as 10 min included upfront discussion about what "fair" means and some time after-the-code discussion on improvements.
I was rejected with lean-no-hire (or weak-no-hire .. I don't remember the exact term but basically not a strong reject).
what definition of "fair" was reached upon?
Under pressure, I suggested the following:
1. Only one solution (or path in this case) should exist
2. No loops (meaning the valid solution does not cross it-self)
3. The length of false path from correct path should not be more than 4
I like the definition proposed in the post - all possible mazes should be equally likely. A function could return the same maze each time and pass the criteria above.