Frontend Web Developer Interview Experience - San Francisco, California
Process
Applied via LinkedIn. Had an initial chat with the recruiter, then got sent a take-home test. The recruiter told me the take-home test is very full-stack focused, even though the position is for a primarily front-end role. The test itself continued to state, "This is heavily focused on full-stack, even though the position we're hiring for is front-end..." Spent maybe 20 hours on this assignment because, as a FRONTEND engineer, I don't have any experience with Ruby. Even then, I got pretty much 95% of the tasks they asked for done. I spent so much time on this take-home test, and why the hell are they testing me on full-stack if the role is for front-end and even say that to me multiple times? Then hire a full-stack
Questions
Take-home test: full-stack application.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Wealthfront Frontend Web Developer role in San Francisco, California.
Success Rate
Wealthfront's interview process for their Frontend Web Developer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for Wealthfront's Frontend Web Developer interview process in San Francisco, California.
Wealthfront Work Experiences
- 5.0Data Engineer ExperienceData Engineer • Current EmployeeNovember 9, 2025Pros: Working at [Financial Company Name] is good.Cons: I don't find any difficulties while working at Wealthfront.
- 4.0Great place to work with a strong remote cultureAndroid Engineer • Current EmployeePalo Alto, California, United StatesNovember 3, 2025Pros: Good compensation, particularly if you are working remote in a low cost of living area.Cons: Engineering on-call rotations can be brutal. Firings based on performance are common and occur randomly.
- 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.
