Process
The interview focused on discussing React and Redux functionality.
The only verbal question I was asked was to describe React lifecycle methods (old syntax with componentDidMount, componentDidUpdate, etc.). The fact that I'm absolutely confident in all modern syntax and able to execute any code didn't interest the interviewer much; he wanted to hear about old lifecycle methods.
Then, in the remaining 40 minutes, I was given to do the following in TypeScript:
- Create a Codepen React project with the following:
- Fix several CSS bugs.
- Fetch data of random length via an external API.
- Render that data in a certain way.
- Sort it and perform actions so that components are reorganized based on user actions.
All of it was nearly done. The remaining piece was to build the Redux portion. The amount of work is insane. I didn't have a chance to get to the Redux portion due to lack of time.
Questions
The questions described above will ask you about some older React concepts.
Forget about hooks and RTK Query. He didn't even know what React Vite is.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Yahoo Sr. Frontend Engineer role in United States.
Success Rate
0%
Pass Rate
Yahoo's interview process for their Sr. Frontend Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Positive0%
Neutral0%
Negative100%
Candidates reported having very negative feelings for Yahoo's Sr. Frontend Engineer interview process in United States.
Yahoo Work Experiences
3.0
Little Work, Big Office
Web Deisgner • Current Employee
Central, United States
March 15, 2024
Pros: Work low, not much.
Work low, not much.
Cons: Office too big. Office too big.
4.0
I love my company
Director of Engineering • Current Employee
Sunnyvale, California, United States
April 5, 2019
Pros: Great place to work, with a very good 401K plan and health care benefits.
Cons: Remote management. Executive staff is on the East Coast.
3.0
Great People, Confusing Decisions
Software Engineer • Current Employee
London, England, United Kingdom
June 23, 2008
Pros: The best reason to work at Yahoo! is very simple: the people who work there. I haven't worked before at a place with so many bright, genuine, and good people. Many of them I now consider friends, some very close friends, and feel genuine loss when I see them leave.
The daily interactions with my co-workers are the primary reason I have stayed with Yahoo! so long.
In addition, the company offers a broad spectrum of products and projects, and allows a decent flexibility to switch between teams or projects. That is if one is inclined to do so.
It has definitely helped me broaden my scope of experience, while still feeling excited and engaged about new opportunities.
Cons: The organization still feels very convoluted, and there is little visibility into the decision-making process, at least in many teams. This is certainly not true for all.
In general, my experience has been that most decisions are made in and by the "Product" team, which also likes to call themselves "Product Owners." It has always struck me as odd to operate in such a way, since the company is striving to be an innovator.
It begs the question: shouldn't it be the talented people who work there who make the right product decisions?
The "Product Team" should be the sum of the people working on a project, with shared ownership and responsibilities. It is one of those details I have always found the most limiting and frustrating in delivering a great experience for the many Yahoo! users out there.
- 3.0Little Work, Big OfficeWeb Deisgner • Current EmployeeCentral, United StatesMarch 15, 2024Pros: Work low, not much. Work low, not much.Cons: Office too big. Office too big.
- 4.0I love my companyDirector of Engineering • Current EmployeeSunnyvale, California, United StatesApril 5, 2019Pros: Great place to work, with a very good 401K plan and health care benefits.Cons: Remote management. Executive staff is on the East Coast.
- 3.0Great People, Confusing DecisionsSoftware Engineer • Current EmployeeLondon, England, United KingdomJune 23, 2008Pros: The best reason to work at Yahoo! is very simple: the people who work there. I haven't worked before at a place with so many bright, genuine, and good people. Many of them I now consider friends, some very close friends, and feel genuine loss when I see them leave. The daily interactions with my co-workers are the primary reason I have stayed with Yahoo! so long. In addition, the company offers a broad spectrum of products and projects, and allows a decent flexibility to switch between teams or projects. That is if one is inclined to do so. It has definitely helped me broaden my scope of experience, while still feeling excited and engaged about new opportunities.Cons: The organization still feels very convoluted, and there is little visibility into the decision-making process, at least in many teams. This is certainly not true for all. In general, my experience has been that most decisions are made in and by the "Product" team, which also likes to call themselves "Product Owners." It has always struck me as odd to operate in such a way, since the company is striving to be an innovator. It begs the question: shouldn't it be the talented people who work there who make the right product decisions? The "Product Team" should be the sum of the people working on a project, with shared ownership and responsibilities. It is one of those details I have always found the most limiting and frustrating in delivering a great experience for the many Yahoo! users out there.
Yahoo Interview Questions
Explore Interview QuestionsTaro 75Google Interview QuestionsMeta Interview QuestionsAmazon Interview QuestionsApple Interview QuestionsNetflix Interview Questions
Explore Interview ExperiencesOpenAI Interview ExperiencesAnthropic Interview ExperiencesPerplexity Interview ExperiencesWindsurf Interview ExperiencesMistral AI Interview Experiences
