Software Engineer Interview Experience - Redwood City, California
Process
There was a one-hour technical interview where you do a problem in a shared editor.
The onsite interview consists of doing one hour of actual coding on a laptop with one of their engineers, followed by a whiteboard problem, and then a couple rounds of more casual chats about past behavior, experience, and team fit.
Everyone was very friendly. My only complaint is that I did really well on the actual coding, and they liked me personally, but I didn't do well on the whiteboard brain-teaser, and that is what got me flushed. This is based on how I felt the interview went, as well as the feedback they gave me. It's just frustrating that I can clearly code, and they liked me, and I wanted to work there, but that was not enough to get the job.
I do appreciate that they took the time to give me actual personal feedback.
Questions
The phone interview involved extracting a solution from a series of "in" values. It was a good question because there is a brute-force O(n^2) solution, and then you can drill down to better and better answers from there.
The laptop interview involved implementing some Java 8 object stream features.
The whiteboard question involved maximizing the values of nodes in a tree.
Was this helpful?
Interview Statistics
The following metrics were computed from 5 interview experiences for the Wealthfront Software Engineer role in Redwood City, California.
Success Rate
Wealthfront's interview process for their Software Engineer roles in Redwood City, California is very selective, failing most engineers who go through it.
Experience Rating
Candidates reported having very good feelings for Wealthfront's Software Engineer interview process in Redwood City, California.
Wealthfront Work Experiences
- 2.0Once a promising star past its primeSoftware Engineer • Former EmployeeRedwood City, California, United StatesJuly 13, 2018Pros: The development environment is the engineers' heaven. The code is well-architected and thoroughly tested, and you can run everything offline. TDD and CI/CD make you super productive. You can basically write the tests, implement your code, run tests locally to make sure it behaves as expected, submit your PR, get it approved, and let the systems do the rest. If everything goes well, your code will be in production in 30 minutes. Most of the engineers are from top schools. If you are a new graduate, you will learn a lot in the first few years.Cons: The production environment is so outdated. Most of the services, except data infrastructure (which is the only cloud-native one), run on dedicated servers, so you can't use anything AWS or GCP. On-call is a nightmare. On average, you get paged once or twice a day, no matter if it is office hours, midnights, or weekends. You are expected to fix it immediately since these issues are either user-facing or money-related. If you are an experienced engineer, you join as E4. This is basically the top of the ladder, since E5 or above is only for old-timers or insiders. The leadership team created some guidelines and rules, for example, promotion criteria and expected tenure in each level. However, you also keep seeing exceptions. When these exceptions don't happen to you, you know you are not among the insiders.
- 4.0Good Perks, Tough BusinessSoftware Engineer • Current EmployeeRedwood City, California, United StatesDecember 2, 2016Pros: Good location, nice building, and snacks.Cons: Too many moving parts and a tough business.
- 5.0Nice people and great engineering cultureSoftware Engineer • Current EmployeeNew York, New York, United StatesApril 26, 2025Pros: Strong engineering culture. Clean and consistent codebase. Nice people. Company is doing really well and is profitable.Cons: There may be a lack of really difficult engineering problems or a lack of scale. Compensation could be higher at non-entry levels.
