I had a fantastic interview experience with Wealthfront. I applied because I've been a very satisfied client of the firm and wanted to be a part of the action. I ended up declining the offer because I was fortunate with offers, but Wealthfront will likely be the only other company I consider for full-time.
It begins with a phone screen with one of my newfound favorite people on earth: Chris Marty. People complain that he doesn't know code and asks these obscure Java syntax questions, which is fair, but I have always felt that language familiarity is a good proxy for experience. I'm also a Java dev, so it played to my strengths. Then there are one or two technical phone screens. Classic coding questions.
The big push is the afternoon-long Google Hangout with coding, behavioral, and analytical questions. Very fun time and very smart questions by very smart employees. The final technical assessment is with Avery, the director of engineering, who asks a coding and math question. I bombed the math question and honestly felt it was simply irrelevant to my SE abilities, but they progressed me, so I'm not mad. It did indeed dig into my way of thinking.
The final step is an awesome, day-long on-site where you get to meet literally everyone and experience Wealthfront for the day. It's a fantastic opportunity. They're a killer team.
Random Java syntax questions. What's a TreeMap?
The following metrics were computed from 10 interview experiences for the Wealthfront Software Engineer role in Palo Alto, California.
Wealthfront's interview process for their Software Engineer roles in Palo Alto, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having good feelings for Wealthfront's Software Engineer interview process in Palo Alto, California.