Technical Project Manager Interview Prep Guide

Show structured negotiation skills. First, understand what drives the 8-sprint estimate by breaking down the work with the tech lead. Identify what can be descoped for an MVP that delivers core business value in 5 sprints. Present options to stakeholders: reduced scope delivered on time, full scope with a phased rollout, or additional resources with the tradeoff of onboarding overhead. Always present tradeoffs with data, not just opinions.

Discuss the strangler fig pattern where you incrementally extract services while keeping the monolith running. Explain how you would prioritize which services to extract first (bounded contexts with clearest boundaries), set up parallel running with feature flags, establish rollback procedures, and define success criteria for each extraction. Show that you understand this is a multi-quarter program that requires balancing migration work with ongoing feature development.

Demonstrate transparency and accountability. Explain how you identified the delay early through leading indicators (velocity trends, blocker accumulation), what you did before escalating (explored mitigation options), and how you framed the message constructively: here is where we are, here is why, here are our options with tradeoffs. Show that you did not wait until the last minute or try to hide the problem.

Discuss a practical framework: categorize tech debt by business impact (affects reliability, slows feature development, or creates security risk), track it visibly in the backlog with severity ratings, and negotiate a sustainable allocation with engineering leadership (typically 15-25% of sprint capacity). Give a specific example where you made a deliberate tech debt decision and how you planned for its eventual resolution.

Show a structured onboarding approach: Week 1, listen and observe (1:1s with every team member, review existing artifacts, attend standups without making changes). Week 2, assess and document (create a current state map, identify the top 3 blockers, document tribal knowledge). Weeks 3-4, stabilize and improve (address quick wins, establish lightweight processes, rebuild team confidence through small victories). Emphasize that you would not impose heavy process on a struggling team.

Discuss facilitation techniques for tense retros: set ground rules (focus on systems not people), use anonymous input gathering, apply the "5 Whys" to get past surface complaints to root causes, and ensure every identified issue gets an owner and a due date. Share a specific example where you turned a toxic retro into a productive one that led to measurable process improvement.

Discuss spike-based estimation: allocate a timeboxed spike (1-2 days) for the team to prototype the riskiest technical component. Use the spike results to calibrate estimates. Apply cone of uncertainty principles: give a range (best/likely/worst) rather than a single number, and refine as the team learns. Reference planning poker or t-shirt sizing for relative estimation with high-uncertainty work.

Focus on process improvements you identified and implemented: reducing meeting overhead, streamlining code review bottlenecks, automating repetitive tasks (CI/CD improvements, test automation), clarifying requirements upfront to reduce rework, or eliminating context switching. Provide specific before and after metrics and explain how you measured velocity consistently to validate the improvement was real and sustainable.