"This happened in my previous job in [company X]. I was the Single threaded Owner for a new business growth initiative from this company to launch a new eCommerce supply chain solution that X was planning to experiment.
Being the single threaded owner, I was accountable for researching the customer problems and coming up with business goals and requirements, including identifying the engineering headcount needed to solve the customer pain point and eventually execute it across 11 different produ"
VictorSage - "This happened in my previous job in [company X]. I was the Single threaded Owner for a new business growth initiative from this company to launch a new eCommerce supply chain solution that X was planning to experiment.
Being the single threaded owner, I was accountable for researching the customer problems and coming up with business goals and requirements, including identifying the engineering headcount needed to solve the customer pain point and eventually execute it across 11 different produ"See full answer
"Situation: This is an example from 2019 where I worked as a TPM in a leading company in the Tax, Accounting and Audit software biz in N. America. All our engineering teams had adopted agile ways of working and utilizing Scrum. Our teams had been at this for a while and were pretty good at planning and executing sprints. We would have quarterly releases to Production but we strived to have Production ready increments each Sprint. Since the software was in use for years , we would often get Pr"
Adib M. - "Situation: This is an example from 2019 where I worked as a TPM in a leading company in the Tax, Accounting and Audit software biz in N. America. All our engineering teams had adopted agile ways of working and utilizing Scrum. Our teams had been at this for a while and were pretty good at planning and executing sprints. We would have quarterly releases to Production but we strived to have Production ready increments each Sprint. Since the software was in use for years , we would often get Pr"See full answer
"I talked about how I request filtered using data and friendly escalated to keep the program on track. Also, delved deep into the tech stack to identify the areas where we need extra coverage and negotiated resources to handle those areas."
Rajesh P. - "I talked about how I request filtered using data and friendly escalated to keep the program on track. Also, delved deep into the tech stack to identify the areas where we need extra coverage and negotiated resources to handle those areas."See full answer
"My mistake: gave a very generic project management approach and didn't properly address how to get value out of it sooner
Expected: being able to structure a project in a way that delivers value at incremental steps along the way"
Praniti S. - "My mistake: gave a very generic project management approach and didn't properly address how to get value out of it sooner
Expected: being able to structure a project in a way that delivers value at incremental steps along the way"See full answer
"Product planning requires a strategic approach that balances customer needs, market trends, and business objectives. Here's a structured framework I recommend:
Discovery:Understand the Market: Conduct in-depth market research to identify customer needs, pain points, and competitive landscape.
Define User Personas: Create detailed user personas to understand your target audience's behaviors, goals, and challenges.
Analyze the Problem: Clearly articulate the core problem your product aims to"
Chozhls - "Product planning requires a strategic approach that balances customer needs, market trends, and business objectives. Here's a structured framework I recommend:
Discovery:Understand the Market: Conduct in-depth market research to identify customer needs, pain points, and competitive landscape.
Define User Personas: Create detailed user personas to understand your target audience's behaviors, goals, and challenges.
Analyze the Problem: Clearly articulate the core problem your product aims to"See full answer
"The other team was depending on the outcome of the release we were working on, since the service end points could not be established, the other team had to reshuffle their plans, and had to plan for uncertainity."
Anonymous Shark - "The other team was depending on the outcome of the release we were working on, since the service end points could not be established, the other team had to reshuffle their plans, and had to plan for uncertainity."See full answer
"The Reason I want to work as a project manager at Rivian is because I've worked as a team at GFS to throw the garbage and recycling out in the garbage and we were able to dump all the garbage as a team and we got the job done."
Amparo L. - "The Reason I want to work as a project manager at Rivian is because I've worked as a team at GFS to throw the garbage and recycling out in the garbage and we were able to dump all the garbage as a team and we got the job done."See full answer
"I don't have relevant experience so I gave an approach according to my understanding.
feedback: understanding how to define a semantic model. ( My answer and approach mentioned didn't indicate that)
i am working on all the constructive feedback provided. hoping this feedback helps someone else"
Praniti S. - "I don't have relevant experience so I gave an approach according to my understanding.
feedback: understanding how to define a semantic model. ( My answer and approach mentioned didn't indicate that)
i am working on all the constructive feedback provided. hoping this feedback helps someone else"See full answer
"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"
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
"My mistake: I seemed to immediately suggest tools I am familiar with rather than walking through the process of identifying candidate tool sets and prototyping each one"
Praniti S. - "My mistake: I seemed to immediately suggest tools I am familiar with rather than walking through the process of identifying candidate tool sets and prototyping each one"See full answer