I applied at the career fair and was given a relatively simple coding challenge on the back of my resume, which I completed.
I was later emailed that they would like to interview me on campus.
After chatting for a bit, the two engineers interviewing me had me do a couple of coding problems on a computer, all of which built off of each other. I solved all of them, perhaps taking a bit longer on the last one than I should have.
I was later emailed that I had positive reviews from my interview and they were still deciding.
The next week, they emailed me that they could not offer me a position, but they encouraged me to apply again and had added my name to a list of people they were interested in for the future.
Being a sophomore, I can't have too many complaints.
First, I wrote a method that generated license plate numbers by taking certain formatted strings and converting certain numbers into letters.
Next, I wrote a method that used the first method to check if certain strings were valid license plates.
Finally, I wrote a method that generated all possible correctly formatted license plates.
I was also asked about hypothetical ways to improve the solutions, although I was told not to worry too much about efficiency.
The following metrics were computed from 4 interview experiences for the Guidewire Software Engineering role in United States.
Guidewire's interview process for their Software Engineering roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Guidewire's Software Engineering interview process in United States.