In partnership with
Build Better Relationships with Your Product Manager
Hey Junior Engineers! One of the biggest adjustments when joining your first cross-functional team is learning to work effectively with product managers. Let's explore how to build strong PM relationships that benefit both your projects and your career growth.
Core Concept: Understanding the PM-Engineer Partnership
Product managers and engineers are natural allies, not adversaries. While engineers focus on how to build solutions, PMs focus on what to build and why. This complementary relationship works best when both sides understand each other's perspectives and constraints.
Research from Harvard Business Review shows that high-performing product teams have 2x better communication between PMs and engineers compared to struggling teams. Here are key strategies to strengthen this partnership:
Schedule regular one-on-ones with your PM beyond sprint planning meetings
Ask clarifying questions about user impact and business goals, not just technical requirements
Share your technical insights early when PMs are exploring solutions
Provide realistic effort estimates and explain the reasoning behind them
Communicate blockers and risks proactively rather than during standups
Career Growth Tip: Master the Art of Technical Translation
One of the most valuable skills you can develop is translating technical concepts into business impact. When discussing technical debt, performance improvements, or architectural decisions, frame them in terms PMs care about: user experience, business metrics, and delivery timelines. This skill will serve you throughout your entire career, especially as you advance into senior roles.
Resource Spotlight
Here are three essential resources for improving PM-engineer collaboration:
First Principles of Product Management - Understand how PMs think about product decisions and user needs
Engineering-PM Communication Framework - Structured approaches for technical discussions with non-technical stakeholders
Requirements Gathering Template - Framework for asking better questions during feature discussions
Junior Dev Q&A
Q: "My PM keeps changing requirements mid-sprint. How do I handle this professionally without seeming difficult?"
A: Frame requirement changes as a learning opportunity. Ask questions like: "Help me understand what new information led to this change?" and "What would you prioritize if we need to adjust scope?" This positions you as a collaborative problem-solver rather than someone resistant to change. Also, document these conversations to build better estimation skills for future projects with similar uncertainty.
Ready to strengthen your PM relationships? Reply with your biggest challenge working with product managers, and I'll share specific strategies in an upcoming edition.
Sponsors!
Smart starts here.
You don't have to read everything — just the right thing. 1440's daily newsletter distills the day's biggest stories from 100+ sources into one quick, 5-minute read. It's the fastest way to stay sharp, sound informed, and actually understand what's happening in the world. Join 4.5 million readers who start their day the smart way.
