Project manager Interview Questions

I looked a this time to reflect and to regroup and research opportunities further my career aspirations.

There could be very personal reasons for a break like that. It may have nothing to do with career or traveling, it may just be something personal. In other words: it may be nobody's business. Good questions to ask in reply are: "Why do y ou want to know? How will it help you to know that? Did you stop to consider that there might be a reason I didn't include it in my CV?"

Maternity leave

Answered honestly and had nothnig to hide but strange they asked on every role I'd done for 15 years.

That means opportunity to widens once knowlegde on the field of specialiaziation. Improve onces wider skill, having uncommon non-localised ability .

Being a skilled estimator is a crucial part of setting schedules, establishing budgets, managing resources and running a thriving team and business. Using the best online project management software for the job is a huge help, but knowing the methods and learning how to do them well is how you become a great estimator. There are a number of estimation methodologies to choose from—and here we’re going to look at five tried-and-trusted ones that work for all types of projects. 1. Expert judgment This is probably the most common way people get an estimate. Talk to the men and women with the best hands-on experience and understanding of the project requirements. Just make sure that everyone has the same understanding of what needs to be delivered. And try to find experts who will actually be working on the project. 2. Comparative or analogous estimation If your current project is similar to past ones, take the data from previous work and extrapolate it to provide your estimates for the new job. Before proceeding, make sure to check whether those projects were successful! 3. Top-down Using a high-level work breakdown structure and data from previous projects, you can add estimates for each project work item to determine the overall effort and cost. The top-down method lacks detailed analysis, which makes it best suited for a quick first-pass at a prospective project to assess its viability. 4. Bottom-up This method uses a detailed work breakdown structure, and is best for projects you’re committed to. Each task is estimated individually, and then those estimates are rolled up to give the higher-level numbers. (If you use the right project management software, it will roll up the estimates for you). This process makes you think about what’s required in order to take a step back to see if the big picture still makes sense. You’ll receive more accurate results than the top-down method, but it’s also a greater investment of time. 5. Parametric model estimating This is a more scientific method that essentially auto-calculates estimates using detailed data from previous activities. Let’s say you have data from your last three office network installation projects. You can use this to get a days-per-workstation value or something similar. You then plug in the number of workstations for your new installation and out pop the estimates. This can be a quick method but needs robust data to feed it. And because it’s all about the math, it’s hard to adjust for the environmental, political and cultural differences between projects.

In fact, there are ore than just three. Being a skilled estimator is a crucial part of setting schedules, establishing budgets, managing resources and running a thriving team and business. Using the best online project management software for the job is a huge help, but knowing the methods and learning how to do them well is how you become a great estimator. There are a number of estimation methodologies to choose from—and here we’re going to look at five tried-and-trusted ones that work for all types of projects. 1. Expert judgment This is probably the most common way people get an estimate. Talk to the men and women with the best hands-on experience and understanding of the project requirements. Just make sure that everyone has the same understanding of what needs to be delivered. And try to find experts who will actually be working on the project. 2. Comparative or analogous estimation If your current project is similar to past ones, take the data from previous work and extrapolate it to provide your estimates for the new job. Before proceeding, make sure to check whether those projects were successful! 3. Top-down Using a high-level work breakdown structure and data from previous projects, you can add estimates for each project work item to determine the overall effort and cost. The top-down method lacks detailed analysis, which makes it best suited for a quick first-pass at a prospective project to assess its viability. 4. Bottom-up This method uses a detailed work breakdown structure, and is best for projects you’re committed to. Each task is estimated individually, and then those estimates are rolled up to give the higher-level numbers. (If you use the right project management software, it will roll up the estimates for you). This process makes you think about what’s required in order to take a step back to see if the big picture still makes sense. You’ll receive more accurate results than the top-down method, but it’s also a greater investment of time. 5. Parametric model estimating This is a more scientific method that essentially auto-calculates estimates using detailed data from previous activities. Let’s say you have data from your last three office network installation projects. You can use this to get a days-per-workstation value or something similar. You then plug in the number of workstations for your new installation and out pop the estimates. This can be a quick method but needs robust data to feed it. And because it’s all about the math, it’s hard to adjust for the environmental, political and cultural differences between projects.

5 years

Still i am working in same field

From my perspective, project success criteria is specific to each project, and has to be something the stakeholders involved can understand and get behind. Different teams will have different criteria for success because different people are involved. So it's a tough question to answer.

Each project has project-specific success criteria; however, the general success criteria for any project would be project completion on time, on budget, according to expected quality standards (classic triangle), plus customer satisfaction being the most important one.

I manage risks by identifying all possible risk factors and make sure all of them are addressed while the project is being completed.

I like to make sure that my work is perfect, so I tend to perhaps spend a little too much time checking it. However, I've come to a good balance by setting up a system to ensure everything is well-prepared and done correctly the first time.

Not to be very aggressive