Real, anonymous reports from people who interviewed for Frontend Engineer at Wealthfront, newest first and distilled into what to expect across the loop.
Get your personalized Wealthfront Frontend Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I went through a longer onsite-style sequence where I was mostly doing technical interviews, including multiple Java and OOP questions. The format was group-based, with me solving three questions across different groups of interviewers, and there was a lunch break built into the super-day pace. There was also a behavioral component mixed in, but the day mostly felt like it was testing how I performed through several rounds of technical work.
In that same kind of interview flow, I remember the onsite being structured similarly—several phone or initial screens leading into whiteboard-style questions with different people. Even though some of it was challenging, I did like talking with everyone I met, and I got opportunities to ask questions about culture. Overall, it felt like a serious, effort-heavy onsite where the technical parts were the center of gravity, and while I didn’t end up with an offer, the day itself was at least organized around substantive discussions rather than surprises.
> 1 year
Average Negative United States
After a recruiter chat, I was sent a take-home test. The recruiter framed it as very full-stack focused even though the role itself was primarily front end, and that mismatch showed up again in the instructions—repeatedly pointing to full-stack expectations despite the job being framed as frontend. I ended up spending around 20 hours on it, and it was frustrating to be forced into areas I hadn’t really used before; I ran into the extra learning curve because I didn’t have Ruby experience.
Later, I also had a different manager-led conversation where I was able to ask about the role and work environment, and I received a take-home project afterward. That one ended up feeling excessively time-consuming and tedious, and what really bothered me was the expectation that I’d learn an entirely new framework just to complete the take-home work. Overall, the assignments drove most of the experience, and both times the take-home felt disproportionately demanding relative to what the role was supposed to be focused on.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
