Engineering-Product Collaboration: Phrases for Working with PMs
5 exercises on key phrases for working with product managers. Choose the most natural and professional option.
0 / 10 completed
1 / 10
A PM proposes a feature and you want to explain the technical implications. How do you frame your input?
TECHNICAL PERSPECTIVE FRAMING: "From a technical perspective..." signals that you're contributing domain expertise, not blocking the idea. It opens the door to alternatives rather than shutting down the conversation. Examples: "From a technical perspective, adding real-time sync here would require WebSockets — which is doable but adds infrastructure complexity." / "From a technical perspective, the simplest path is reusing the existing export module — no new service needed." / "From a technical perspective, this touches the payment flow, so we'd need a security review before releasing." Options A/B/D are blunt rejections or condescending — none of which advance the collaboration.
2 / 10
The PM asks why a feature is taking longer than estimated. How do you explain professionally?
EXPLAINING TECHNICAL DELAYS: "This will take longer than expected because..." followed by a specific, non-jargon reason respects the PM's need to understand and re-plan. Examples: "This will take longer than expected because the database schema needs migration before we can store this data type." / "This will take longer because we discovered a third-party API rate limit that requires us to build a queue." / "This will take longer than expected because the mobile and web codebases diverged here — we need to align them first." Options B/C/D are evasive, too brief, or dismissive — none of them give the PM what they need to manage expectations upward.
3 / 10
The feature scope is growing and you want to propose a smaller version. How do you phrase it?
PROPOSING SCOPE SIMPLIFICATION: "Could we simplify the requirements to [core scope] and defer [non-core] to v2?" is the professional way to propose a phased approach. It acknowledges the full vision while making a case for sequencing. Examples: "Could we simplify to just the CSV export for now, and add the PDF option in the next sprint?" / "Could we scope this to domestic users initially, and handle international edge cases in phase 2?" / "Could we simplify requirements to the happy path for launch, with edge case handling coming in the week after?" Options A/B/C are blunt refusals with no constructive alternative.
4 / 10
A PM asks you to include a feature that conflicts with an existing system constraint. How do you communicate this?
NAMING TECHNICAL CONSTRAINTS: "There's a technical constraint here..." gives the PM specific, actionable information. Naming the constraint — and optionally the path to resolve it — is far more useful than a flat "no". Examples: "There's a technical constraint — the mobile app doesn't have push notification permissions in the current build; adding them requires an app store review." / "There's a constraint: our CDN doesn't support server-side rendering, so this dynamic feature needs a different delivery approach." / "There's a technical constraint here — the API is rate-limited to 100 requests per minute, which won't scale to this use case without caching." Options A/C/D give the PM no information to work with.
5 / 10
The PM has given a very aggressive timeline. How do you push back professionally?
PROFESSIONAL TIMELINE PUSHBACK: "I'd push back on the timeline" paired with an alternative and the conditions for the original is the mature engineering response to unrealistic timelines. It is direct without being dismissive. Examples: "I'd push back on the one-sprint timeline — the database migration alone needs thorough testing. Can we negotiate two sprints?" / "I'd push back on the August deadline — we're still in discovery. September with full scope, or August with a reduced feature set." / "I'd push back on this — if we rush, we risk introducing tech debt that will cost more later. Can we take the extra week?" Options A/B are too blunt, D is passive and uncommitted — it doesn't help the PM make a real decision.
6 / 10
Context: You're reviewing a PR for a new user authentication flow. The PM, Sarah, comments on the code saying, 'This looks good but can you add logging around the token generation? It would be helpful to debug any issues.' What's the best response to Sarah in your code review comment?
A) 'Sure, I'll add it.' (No further explanation) B) 'Adding logging here will significantly impact performance. Can we discuss alternatives?' C) 'Okay, I've added logging around token generation as requested.' D) 'I don't think logging is necessary for this flow.'
The best response acknowledges the PM's request while also raising a valid technical concern. Option B demonstrates proactive communication and encourages a discussion about potential trade-offs. Options A and D are insufficient – they don't address the performance implications or fulfill the request directly. Option C is technically correct but lacks the crucial dialogue needed for effective collaboration.
7 / 10
Context: During a daily standup, your team lead asks you about the progress on integrating with the new payment gateway. You've encountered an unexpected API response format and are still investigating. How do you update him?
A) 'It's going fine.' B) 'I'm working on it; I'm facing some issues with the API response – it's not what we expected.' C) 'The integration is complete, and everything is running smoothly.' D) 'I haven't started yet.'
This scenario requires clear and concise communication. Option B directly addresses the issue without downplaying its importance. It provides a brief explanation of the problem, which allows the team lead to understand the situation and potentially offer assistance. The other options are vague or misleading and don't provide useful information.
8 / 10
Context: You're writing a PR description for a new feature that allows users to upload profile pictures. The PM asks if you can include a progress bar during the upload process. What should you write in the PR description?
A) 'Implemented user profile picture uploading.' B) 'Added a progress bar to the file upload flow, improving the user experience.' C) 'Uploaded images and added some code.' D) 'Fixed a bug in the image handling.'
A good PR description should clearly articulate the changes made and their purpose. Option B specifically describes the new feature (progress bar) and its benefit (improved user experience). This provides context for reviewers and helps them understand the value of the change. The other options are too vague or focus on technical details without explaining the broader impact.
9 / 10
Context: A PM informs you that a new user onboarding flow is needed. However, it requires integrating with a legacy system that's known to be unstable and has limited documentation. How do you respond?
A) 'Sounds good! Let's start working on it.' B) 'Integrating with the legacy system presents significant challenges due to its instability and lack of documentation; we should explore alternative approaches.' C) 'I can handle this alone.' D) 'Let's prioritize this feature.'
This situation demands a realistic assessment. Option B acknowledges the potential difficulties and proposes a proactive discussion about alternative solutions. It highlights the risks associated with the legacy system without dismissing the requirement outright. The other options are either overly optimistic or fail to address the core problem.
10 / 10
Context: The Product Manager asks you to add a 'dark mode' toggle to an existing mobile app. You realize this would require significant refactoring of the UI and potentially impact performance. How do you respond?
A) 'Okay, let's do it.' B) 'Adding dark mode will necessitate a substantial overhaul of the UI codebase and could negatively affect app performance; can we discuss a phased approach?' C) 'It's a simple toggle. I'll get started.' D) 'Dark mode is already popular – let's implement it!'
This question tests your ability to manage scope and expectations. Option B clearly articulates the potential impact of the change, prompting a discussion about a more manageable solution. It's crucial to raise concerns early on before committing to a large-scale refactor. The other options are either dismissive or fail to acknowledge the technical complexity.
What will I practise in "Engineering-Product Collaboration: Phrases for Working with PMs"?
This module focuses on Phrasebook — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Phrasebook exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasebook — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Phrasebook exercises?
See the Phrasebook hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.