## Tell me about a time you had to juggle multiple high priority projects, how did you deal with that? In one of my previous roles, I was responsible for managing three different projects simultaneously, all with tight deadlines. To manage these competing priorities, I first made a comprehensive list of all the tasks that needed to be completed for each project and then prioritized them based on urgency and importance. I then created a schedule that allowed me to work on each project for a certain amount of time each day, ensuring that I made steady progress on all of them. I also communicated regularly with my team and stakeholders to keep everyone informed of my progress and to ensure that we were all aligned on priorities. ## How do you prioritize features? Prioritizing features involves considering a range of factors, including customer needs, business goals, technical feasibility, and the potential impact on the product. I typically use a prioritization framework, such as the Kano model or the MoSCoW method, to help me determine which features should be prioritized. I also gather feedback from customers and other stakeholders to ensure that we are meeting their needs and expectations. ## How would you define tech debt? Tech debt refers to the accumulated cost of maintaining and updating software or technology that has been built with shortcuts or compromises. It can arise from a variety of factors, including time constraints, lack of resources, or changing requirements. Tech debt can slow down development and make it more difficult to maintain or update software over time. ## How do you view tech debt in the overall planning process? Tech debt is an important consideration in the overall planning process because it can have a significant impact on the long-term success of a product or project. While it may be tempting to prioritize short-term gains over long-term sustainability, it's important to address tech debt in a timely manner to ensure that it doesn't become a major obstacle down the road. By factoring in tech debt when making decisions about feature prioritization and resource allocation, product managers can help ensure that they are building a sustainable and scalable product. ## How do you prioritize tech debt against other features? Prioritizing tech debt against other features involves weighing the short-term benefits of adding new features against the long-term benefits of addressing tech debt. In general, I prioritize tech debt when it poses a significant risk to the product's stability, scalability, or maintainability. For example, if there are critical bugs that are impacting the user experience, I would prioritize addressing those over adding new features. However, if the tech debt is relatively minor and the impact on the user experience is minimal, I might prioritize adding new features instead. ## Tell me about a time you had to deal with tech debt, and what approach you took. In a previous role, I inherited a codebase that had significant tech debt. The code was difficult to maintain and update, and there were a number of critical bugs that were impacting the user experience. To address this, I worked with the development team to prioritize the most critical tech debt issues and develop a plan to address them over time. We also implemented a process for addressing tech debt during each sprint, allocating a certain amount of time to fixing bugs and updating the codebase. This approach helped us make steady progress on addressing the tech debt while still delivering new features and functionality to our users. ## How would you manage a sudden shift in priorities? Managing a sudden shift in priorities requires a flexible and adaptable approach. First, I would work with the team and stakeholders to understand the reasons for the shift and the implications for the project. I would then prioritize the new tasks and re-allocate resources as needed to ensure that we could meet the new deadlines or requirements. Communication is key in these situations, so I would make sure to keep everyone informed of the changes and adjust our plans as necessary to stay on track. Finally, I would also take the opportunity to re-evaluate our overall project plan and make any necessary adjustments to ensure that we were still on track to meet our goals.