Question 1

Tell me about yourself and your journey to becoming a Project Manager.

Accepted Answer

Present-Past-Future: Current role -> Key experiences -> Next goals. Don't recite your CV. Tell a story with a clear thread - where you started, what turning point brought you to PM, and why you chose this path. For example, someone who was a developer for 3 years, realized they preferred coordinating over coding, transitioned through BA to PM - that's compelling because it shows both technical and management understanding. Focus on 1-2 standout projects with specific numbers (team size, duration, budget). End with why you want this role and connect it to the company's direction.

Question 2

How do you decide between Agile and Waterfall for a project? Share a real situation where you chose the wrong methodology and what you learned.

Accepted Answer

Criteria-based Decision -> Failure example -> Specific lesson learned. Nobody wants to hear you recite a textbook on Agile vs Waterfall. This question tests real-world judgment. Good PMs know no methodology is 100% right - some outsourcing projects for Japanese clients with rigid requirements suit Waterfall better. Conversely, internal product work with constant changes fits Scrum. Huge bonus if you admit to choosing wrong - like forcing Scrum on a fixed-price project where the client refused scope changes, causing constant conflicts. The lesson learned is what I value most.

Question 3

Tell me about the biggest risk you encountered in a project - how did you identify, assess, and handle it?

Accepted Answer

STAR + PMI Risk Process: Identify -> Analyze (probability x impact) -> Response strategy -> Monitor. I'm not asking about risk matrix theory - I want a real story. One PM told me: mid-project, the lead developer quit suddenly, taking all domain knowledge. They had identified the risk early (noticed the dev updating LinkedIn), prepared a backup through pair programming and knowledge documentation. When the risk materialized, the team kept running. That's real risk management - not a beautiful risk register on Confluence that nobody reads. Be clear about which strategy you used (mitigate, transfer, avoid, accept) and why.

Question 4

The client keeps requesting features outside the original scope without wanting to increase budget or timeline. How do you handle it?

Accepted Answer

Acknowledge -> Assess impact -> Negotiate with data -> Propose options -> Document. This is a classic outsourcing problem in Vietnam - clients say 'just a small addition' but cumulatively scope inflates 30-40%. Junior PMs either say Yes to everything (team burns out) or say rigid No (lose the client). Good PMs: (1) acknowledge the request with empathy - 'I understand this feature is important for your business'; (2) assess impact with specific data - adds 2 sprints, needs 1 more dev; (3) offer options - swap a lower-priority feature or defer to phase 2; (4) EVERYTHING must be documented via email/CR. Share a real case where you negotiated successfully.

Question 5

How do you manage communication when working simultaneously with foreign clients, local dev teams, and internal C-level executives?

Accepted Answer

Stakeholder mapping -> Communication plan (frequency, channel, content) -> Conflict resolution example. Vietnam outsourcing is unique because you speak three different languages to three groups. With Japanese/Korean/US clients - they want concise, timely status updates focused on risk and progress. With dev teams - you need to translate business requirements into clear technical tasks, not vague 'client wants it prettier'. With C-level - they only care about revenue, margin, and resource utilization. Good PMs don't just relay information, they transform it for each audience. Share an example of handling conflicting expectations - client wants more features, dev says no time, boss wants to keep the client.

Question 6

How do you estimate effort and create a resource plan for a new project? What is your typical estimation accuracy?

Accepted Answer

Estimation method (Analogy/3-point/Planning Poker) -> Buffer strategy -> Track record with accuracy numbers. Bad estimation equals project burnout. I want to know your technique - top-down (analogous from past projects), bottom-up (break WBS then estimate each task), or 3-point (optimistic/most likely/pessimistic). Experienced PMs usually combine: analogous to validate totals, bottom-up for details, then add 15-20% buffer for risk. The most important question: do you track actual vs estimate? Good PMs know their accuracy rate - like 'last project estimated 800 man-days, actual 850, off by 6.25%'. If you say 'always 100% accurate', I know you haven't handled complex projects.

Question 7

Explain Earned Value Management through a real project. If CPI = 0.85 and SPI = 1.1, what is the project status and what would you do?

Accepted Answer

Explain EVM metrics -> Analyze scenario -> Specific action plan. CPI = 0.85 means for every dollar budgeted, you're only producing $0.85 of value - you're over budget. SPI = 1.1 means you're 10% ahead of schedule. Combined: the project runs faster than planned but burns money excessively. Common cause in Vietnam outsourcing: adding people to meet deadlines without optimization, or using senior resources for junior-level tasks. Action: review resource allocation, check if you can slow down slightly (reduce SPI) to optimize cost, renegotiate if needed. Junior PMs see SPI > 1 and celebrate, missing that CPI is bleeding cash.

Question 8

Have you managed projects using offshore/onsite/hybrid models? Share your biggest challenge and how you resolved it.

Accepted Answer

Model description -> Challenge (timezone, culture, communication) -> Solution -> Outcome. This is a Vietnam outsourcing-specific question - most FPT, KMS, NashTech projects have an offshore component. Classic challenges: timezone gap with US/EU clients (only 2-3 hours overlap), Vietnamese devs' culture of 'afraid to say no' making clients think everything's fine while there are actual blockers, or poor knowledge transfer during member rotation. Good PMs describe their communication cadence - daily async updates via Slack, weekly sync calls, bi-weekly demos. Or how they handled when the bridge SE quit suddenly and the client lost visibility. Big bonus if you know the BOT (Build-Operate-Transfer) model trending in Vietnam 2026.

Question 9

How do you set up Jira workflow and Confluence space for a new project? Give specific examples of board configuration and documentation structure.

Accepted Answer

Workflow design (statuses, transitions, rules) -> Board config -> Confluence template -> Integration. Any PM can say 'I use Jira'. I want specifics. How many statuses in your workflow? To Do -> In Progress -> Code Review -> QA -> Done or more complex? Do you set transition rules - like blocking move to Done without test evidence? Scrum or Kanban board, swimlanes grouped by what? How do you organize Confluence - separate spaces for Meeting Notes, Decision Log, Technical Docs? Senior PMs usually have their own templates they carry between projects. Bonus if you mention automation rules (like auto-assigning reviewer when PR is linked).

Question 10

Two senior developers in your team disagree on system architecture, impacting progress. How would you resolve this?

Accepted Answer

Listen both sides -> Facilitate structured discussion -> Decision framework -> Follow-up. Conflict between senior devs is very common - and many PMs handle it wrong by either picking sides or immediately escalating to CTO without trying to resolve it. What I recommend: (1) listen to each person separately to understand root cause - sometimes it's not technical but ego; (2) organize a structured meeting - each person presents their solution for 15 minutes, evaluated against clear criteria (scalability, timeline, team capability); (3) if still unresolved, use a decision matrix or invite an external Tech Lead/Architect to review; (4) most importantly - after the decision, both must commit. PMs don't need to code, but they must facilitate technical discussions and keep the team healthy.

Question 11

You're assigned to a burning project - 2 months behind schedule, client escalating, team demotivated. What do you do in the first 2 weeks?

Accepted Answer

Week 1: Assess (data, people, client) -> Week 2: Stabilize (quick wins, re-plan, rebuild trust). Project rescue is the pinnacle of PM skills. Common mistake: jumping in and changing everything in week one. Good PMs: Week 1 - only assess. Talk 1:1 with each member to understand real morale and blockers, review Jira/Git to see actual velocity, meet with client to reset expectations. Week 2 - pick 2-3 quick wins for momentum (fix a long-standing bug client complained about, deliver a near-complete feature), re-plan with realistic timeline and present to client with data. Real case: a PM took over a burning project, discovered the team was micromanaged by the previous PM causing low motivation. Simply giving the team more autonomy increased velocity by 40% without adding headcount.

Question 12

A client sends an RFP for a 12-month project. How do you prepare the proposal and estimation to be both competitive and profitable?

Accepted Answer

Requirement analysis -> Team composition -> Estimation (with contingency) -> Pricing strategy -> Proposal structure. This is the survival equation of outsourcing - bid low and win but lose money, bid high and lose the deal. PMs need to: (1) analyze the RFP thoroughly - which requirements are clear, which are ambiguous (ambiguous = risk = buffer); (2) propose a realistic team composition - don't stuff it with seniors just to impress then swap later; (3) include 10-15% contingency but present it smartly - divide into phases, phase 1 fixed price for client confidence, phase 2 T&M for flexibility; (4) highlight differentiators - domain expertise, tech stack match, similar case studies. Experienced PMs know the trick: read between the lines of the RFP to understand what the client truly needs, not just what they wrote.

Question 13

Do you have PMP certification or PMI knowledge? Among PMBOK's 10 knowledge areas, which do you think is most undervalued in Vietnam and why?

Accepted Answer

Certification status -> Knowledge area analysis -> Vietnam context -> Practical improvement. You don't need PMP to answer this, but senior PMs should understand the framework. 10 knowledge areas: Integration, Scope, Schedule, Cost, Quality, Resource, Communications, Risk, Procurement, Stakeholder. In Vietnam, the most overlooked areas are typically Procurement Management (few outsourcing PMs manage vendor/subcontractor procurement) and Quality Management (QA is often an afterthought, not a built-in process). You could also argue Stakeholder Management - many Vietnamese PMs excel technically but lack client-facing soft skills. The best answer names an area, explains why it's undervalued, and shares how you improved it on your team.

Question 14

In the final sprint before release, QA finds a critical bug affecting a core feature. The release deadline is hard - cannot be moved. What's your decision?

Accepted Answer

Assess severity -> Stakeholder communication -> Decision options -> Risk acceptance criteria. This tests decision-making under pressure - there's no single right answer. Options: (1) hotfix immediately if the bug can be fixed within remaining timeline - but assess regression risk; (2) release with known issue + workaround if the bug doesn't block the main user flow - document clearly and plan a patch release; (3) partial release - deploy stable features, disable the bugged feature; (4) escalate and propose delay if the bug is too critical (data loss, security). PMs need to communicate transparently with clients: 'We have 3 options, each with these tradeoffs...'. I've seen PMs push a release with a bug out of fear of missing the deadline, and the resulting production incident was far worse than a 2-day delay.

Question 15

Why did you choose PM over continuing a technical career? What keeps you in this role?

Accepted Answer

Core motivation -> Value PM brings -> Long-term vision. A simple question that reveals a lot about who you are. Bad answer: 'Because PM pays more than dev'. Good answer: tell me about a moment you realized you wanted broader impact - as a dev, you coded one feature, but as a PM you define the entire product direction. Or you realized you're good at connecting people - bringing designers, devs, and clients onto the same page. What keeps you in PM might be the satisfaction of successful delivery, seeing team members grow, or resolving seemingly impossible conflicts. I'm looking for genuine passion, not someone who chose PM because they 'ran out of coding runway'.

Question 16

What is your expected salary for this position?

Accepted Answer

Research market -> State range (not single number) -> Justify with value -> Show flexibility. Don't shy away from talking money - but don't throw out random numbers either. Vietnam market reference as of August 2026: Junior PM (1-3 years) around 15-25M VND/month, Mid PM (3-5 years) around 25-50M, Senior PM (5-10 years) around 45-80M, PM Director/Head of PMO from 70-120M. Outsourcing typically pays 10-15% less than product companies but compensates with other benefits. State a range instead of a single number - like '35-42M' - and explain why: years of experience, certifications (PMP, CSM), domain expertise. Important: ask about total compensation - bonus, review cycle, training budget. A PM who can negotiate for themselves can negotiate well for their projects.

*Note: Salary ranges above are references from Vietnam recruitment market data as of August 2026 (VietnamWorks, ITviec, Glassdoor). Actual figures may vary by company, industry, and location.*

Question 17

Do you have any questions for us?

Accepted Answer

2-3 smart questions: about team/project, culture, and growth path. The questions you ask reveal more about you than your answers. Bad questions: 'Does the company have team building?' or 'What time can I leave?'. Good questions: (1) About the project - 'What phase is the project I'd join? Team size? Tech stack?'; (2) About challenges - 'What's the biggest challenge the PMO is currently facing?'; (3) About growth - 'What's the career path for PMs here? Is PMP certification supported?'; (4) About culture - 'Do PMs have authority over resource allocation or does it go through department heads?'. These questions show you've researched the company, you're serious about the role, and you're evaluating whether the company fits you - not just whether you fit the company.