Interview Questions

Dhruv M. - "During my internship at Lumora Analytics, I was tasked with creating a dashboard to track supplier performance using real-time data. Midway through the project, I hit a roadblock when one of the key data sources was delayed due to access issues with the external vendor’s system. Despite the delay, I had to ensure that the dashboard development stayed on schedule so it could be presented to leadership by the end of the week. Instead of waiting passively, I immediately informed my supervisor and o"See full answer

Anonymous Stork - "AWS"See full answer

Vineet S. - "This is phased approach and would consist below steps Initiation - Identify Business Goals and Drivers, Perform TCO Analysis, Compliance Assessment and then formulating strategy Prepare: Develop Require Skill sets and roles and Technical Cultural Training through CoE, Collaboration with partners and internal stakeholders Assess: Conduct workshops, understand Application Realms and identify the cloud candidates OKRs and App Roadmap Execute: Learn, Design, Implement, Document, Depl"See full answer

Manu S. - " Attributes of a good Product strategy: Good product strategy builds upon the company’s existing advantages (companion products, distribution channels, partner relationships, etc.). Good product strategy clearly identifies target customer segments and non-target segments. Good product strategy identifies leading and lagging indicators of success, whether they are metrics or milestones. Take both top down and bottom-up approach to formulate your strategy. Use top down to bring alignme"See full answer

Bit P. - "Testing"See full answer

Shivam S. - "Conduct a competitive analysis: Research the competitive landscape to identify gaps and opportunities that your product can capitalize on. Develop a business case: Document the value of your product, including projected growth, expected return on investment, and potential risk factors. Establish partnerships: Develop relationships with key stakeholders and partners who can help provide resources and funding for your product. Secure executive support: Present yo"See full answer

Shivam S. - "I. Understanding Customer Needs & Requirements II. Developing a Project Timeline III. Defining the Problem Statement IV. Identifying Product Features, Benefits & Requirements V. Defining Project Objectives & Success Criteria VI. Identifying Stakeholders Associated with the Project VII. Determining Resources Needed to Complete the Project & Potential Risks"See full answer

Shivam S. - "I use a combination of quantitative and qualitative methods to gain a comprehensive understanding of the target market. Quantitative Methods: • Conducting surveys • Utilizing data analysis techniques such as segmentation Qualitative Methods: • Focus groups • Interviews with current and potential customers Additional Considerations: • Competitive landscape • Industry trends to ensure that my research is relevant and actionable."See full answer

Shivam S. - "We utilized AI and ML to improve the product’s accuracy and performance and to generate insights from customer data. We also leveraged the cloud to store and manage customer data securely. Additionally, we implemented smart assistants to automate customer support and help customers quickly resolve inquiries."See full answer

Scott S. - " Situation In the derivatives trading domain, timely and accurate data is crucial for making informed trading decisions. Our existing data processing system was facing challenges with latency and scalability, which hindered our ability to react swiftly to market changes. To address these issues, we designed a new real-time market data processing platform. Task The task was to develop a low-latency data processing platform that could handle real-time market data ingestion, processing, an"See full answer

Chandru S. - "Roles, Events, Artifacts, Roles: PO, Scrum Master, Developer Events: Sprint, Sprint Planning, Daily Standup, Review, Retrospective Artifacts: Product Backlog, Sprint Backlog, Increment"See full answer

Ridhima R. - "This cannot be answered as a black and white question. It has to be a careful mix of both. If we are delivering a product that is time-sensitive, and we have customers waiting for it, we would rather ship a product quickly with lesser features (MVP) and keep building on it later. But if we can delay our product release to the market by a couple of weeks, then we rather work on getting all the features right and delivering it."See full answer

Rahul J. - "Target market and pain points to be solved Impact of solving the problem: TAM Existing solutions and their problems Value proposition of my product Costs and resources required in building and maintaining"See full answer

Sudhansu T. - "There are few points which we need to understand while advising engineering team. Risk assessments. Cost Benefit Analysis Vendor relationship Vendor Lock in."See full answer

Hemanth M. - "Start by giving a brief overview of the technical stacks used in our product. Highlight the key technologies, frameworks, languages, and tools employed. This sets the stage for a more detailed discussion. In choosing our technical stack, we prioritized scalability, opting for micro-services architecture to ensure flexibility and ease of scaling components independently. This decision enables us to handle increased user loads while maintaining optimal performance. One trade-off we made was favo"See full answer

Affreen M. - "Product Vision, Product Roadmap, Product Requirements (User-stories), Metric analysis, Market/user research"See full answer