Robinhood Behavioral Interview Questions

Sreenisha S. - "Let me tell you about a time where a website I managed suddenly showed slow performance and the mistake on our side was it was unnoticed until a user reported the issue to management. As a PM for that project, I took full responsibility of the situation and worked with the engineering team to quickly resolve it. This mistake taught me the importance of focusing and monitoring non functional requirements as well in addition to new feature development /adoption where I was mostly spending my time"See full answer

Catherine I. - "I always ask to clarify if this is a brand new team. If so, then I focus on bringing in people with strong technical aptitudes(since I'm hiring for software engineering), but also team members that have experience mentoring and good communication is a must. I look for people who have leadership qualities. I emphasize that building a brand new team isn't something I can do on my own, so the initial hires of that team are very important to help me expand it."See full answer

George A. - "strengths- Working with engineering, working with metrics, execution Weakness- ideation and visioning, working with design"See full answer

Vinay P. - "Fintechs are providing ready solutions for various financial operations of banks with customer-centric UI which are easy to integrate with various platforms and cost-effective."See full answer

Scott S. - "As engineering managers, it’s our obligation to prioritize and manage technical debt properly. However, achieving the correct mix between reducing technical debt and providing new features while meeting deadlines can be fairly tough.To manage technical debt efficiently, it’s vital to first understand how to detect it inside your projects. One way to do this is by doing regular code reviews and encouraging your team to share any concerns or areas where they feel the codebase may be improved. This"See full answer

Coco H. - "These works often aren't comparable, so that I'd use a balanced portfolio of 20%-30% engineering needs and 70%-80% user needs to satisfy both sides. However, this is only a starting point, if engineering requests more than this baseline then I would use ROI to prioritize."See full answer