First, a standard recruiter phone screen, then an online coding exercise, which was very easy. The on-site was much more difficult, done in three stages with two interviewers in each stage: coding on a computer, a whiteboard problem, then a behavioral interview.
On their part, I got an interesting impression of both strict process and weird unpreparedness. It's obvious this is a bigger, more structured startup, and that they had all given this same interview many, many times. But they admitted that they hadn't actually prepared any Android-specific questions, instead giving a backend Java problem and tagging five minutes of Android trivia questions on at the end. The behavioral section was outright strange, with me being asked things like, "Without using specific examples, how would you test something?" In general, the interviewers were very good at the "impassively staring with no expression that might give away if you are giving the right answer or we think you're a complete idiot," which made sense on the whiteboard problem but was a bit more awkward with supposedly subjective personality match type questions.
IMO, I ended up acing the computer coding, flunking the whiteboard, and being very confused after the behavioral bit. I did not receive an offer and was disappointed, but it really didn't seem like a great fit anyways.
Given a binary tree of numbers, find the node matching various constraints (max, min, etc.).
Here is a skeleton of some Java 1.8 code using lambdas; implement these hooks.
How would you test something? Not a specific thing, just a thing.
The following metrics were computed from 1 interview experience for the Wealthfront Android Engineer role in Palo Alto, California.
Wealthfront's interview process for their Android Engineer roles in Palo Alto, California is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Wealthfront's Android Engineer interview process in Palo Alto, California.