4 exercises — structuring a 3-minute pitch, delivering an elevator pitch with evidence, responding to complexity objections, and adapting pitch depth for different audiences.
0 / 9 completed
1 / 9
You need to pitch a new internal monitoring tool to your manager in 3 minutes. Which structure is most effective?
Option B uses the Problem / Solution / Why Now / What I Need pitch structure:
1. Problem (specific): "40 minutes per incident manually correlating logs across five dashboards" — not "our monitoring is bad", but a specific, measurable cost 2. Root cause named: "current tooling surfaces noise, not the root signal" — shows you understand the cause, not just the symptom 3. Solution described functionally: "alert aggregation layer that correlates signals and ranks by impact" — tells the listener what it does, not how it's built 4. Why now (urgency): "three P1s in the last 30 days that exceeded SLA" — links the solution to a current, measurable business problem 5. What I need (bounded ask): "2 sprint cycles + one senior engineer review" — specific, scoped, easy to approve
Why A fails: "Has dashboards and alerts" is a feature list — no problem framing, no urgency, no ask
Why C fails: "Quite complex but I can explain it" signals lack of preparation; "aggregates things" is too vague to approve
Why D fails: Formal framing without content — this sounds like preamble, not a pitch
3-minute pitch formula: Problem (specific + measurable) → Solution (functional, not technical) → Why now (current business cost) → What I need (specific, bounded)
2 / 9
You built an internal code review automation tool that saves time. You need a 30-second elevator pitch. Which is best?
Option C is a strong elevator pitch because it follows the cost → insight → solution → proof pattern in 30 seconds:
1. Specific cost: "2.3 days average to close code reviews" — puts a number on the problem immediately 2. Diagnostic insight: "Half of that is formatting and boilerplate — things a machine can catch" — shows you understand the structure of the problem 3. Solution that solves the diagnosed problem: "automates those checks, surfaces only substantive feedback" — connects directly to the insight 4. Proof from a real pilot: "2.3 days to 0.8 days across three teams" — this is not a claim, it's evidence
Why A fails: "Python, AST parsing, CI integration" is a technology description, not a value proposition. The listener doesn't know why they should care
Why B fails: "Something every team needs" is a generalisation — it doesn't connect to a specific problem this organisation has
Why D fails: "Faster and better" without evidence — after hearing the pitch the listener still doesn't know what specifically changed
Elevator pitch formula: [Specific current cost] → [Insight about why] → [What your solution does about that] → [One piece of evidence from reality]
3 / 9
Your manager says: "This monitoring tool sounds interesting, but it sounds too complex to build given our current sprint load." How do you respond?
Option B uses the validate → decompose → checkpoint → bounded downside technique for handling a complexity objection:
1. Acknowledges the concern as legitimate: "The complexity concern is real" — not dismissing the objection 2. Reduces the risk with a minimal first milestone: "single-service prototype in one sprint" — transforms an overwhelming scope into a single bounded unit 3. Minimises integration risk: "doesn't require changes to the existing alert pipeline" — names the specific fear (breaking existing systems) and addresses it 4. Uses phased checkpoints: "go/no-go after each sprint" — turns an open-ended commitment into a series of small decisions 5. Names the bounded downside: "stop at the first milestone if it's not delivering value — sunk cost is one sprint" — the manager can now assess: is one sprint of risk acceptable? The answer is usually yes
Why A fails: "Not that complex actually" — dismisses your manager's concern and starts an argument about your assessment vs. theirs
Why C fails: "I can make it simpler" is a vague concession — simpler in what way? At what cost to the solution's value?
Why D fails: "The complexity is necessary" shuts down the conversation with no compromise path
Complexity objection formula: Validate → Smallest first milestone → Risk addressed → Phased checkpoints → Named bounded downside
4 / 9
You're presenting the same tool to three different people: a tech lead, a product manager, and a VP of Engineering. Which adapts the pitch most effectively?
Option C demonstrates audience-adaptive pitching — same product, three different value propositions:
Tech lead: Wants to know HOW it works and will have opinions about the implementation. The pitch invites their expertise: "What would you want in the rule set?" — turns evaluation into collaboration
Product manager: Doesn't care about AST parsing. Cares about outcomes. The pitch starts with the function ("automates mechanical review") then jumps to the business impact: "2.3 days to 0.8 days"
VP: Cares about engineering capacity and cost. "65% reduction in review cycle time" and "4 engineer-hours per sprint freed" are the metrics they track. "Runs on existing CI — no new vendor costs" removes a potential barrier before it's raised
Why A fails: One pitch for three audiences means one audience will be bored (VP hearing about AST), one will be confused (PM hearing about AST), and one will be underserved (tech lead who needs implementation details)
Why B fails: The PM version ("a thing that checks code") is dismissive and vague; the tech lead version is all implementation without context for why the problem matters
Why D fails: "Let them take what's relevant" is an audience-burden approach — it's the presenter's job to adapt the message, not the audience's job to filter it
Audience adaptation formula: Tech lead → HOW (mechanism) + invite their expertise PM → WHAT it does (function) + WHAT changed (business outcome) VP → IMPACT in their metrics + COST removed before it's raised as objection
5 / 9
Alex: 'I've noticed a recurring issue with the payment gateway integration. Users are intermittently reporting failed transactions.' As a senior developer, which of the following Slack messages would be most effective in escalating this problem and requesting immediate attention?
The best response quickly acknowledges the severity of the problem and initiates immediate action. Adding 'critical' emphasizes urgency, while requesting DevOps involvement demonstrates a proactive approach to mitigating potential downtime. Options A & B are too vague; C is far too slow for an intermittent payment issue. Option D implies immediate escalation without proper preparation.
6 / 9
Ben, a junior developer, submits a PR with a complex regular expression used to validate user input. The code review comment reads: 'This regex is overly complicated and difficult to understand. Can you simplify it?' Which of the following responses in the PR discussion would be most appropriate for Ben?
Ben needs to demonstrate understanding and willingness to improve his code. Acknowledging the comment positively (Excellent!) shows he's receptive to constructive criticism. Requesting an alternative demonstrates a desire to find a better solution while aligning with best practices for readability and maintainability. Option A is passive; B is active, and C avoids directly addressing the issue.
7 / 9
You're writing a PR description for a new API endpoint that returns user profile data. The API response is JSON formatted and includes fields like name, email, and profile_picture_url. Which of the following descriptions would be most effective?
A good PR description should clearly explain the purpose and functionality of the code. Describing the endpoint's function (fetching user profiles) and listing key fields provides context for reviewers and future developers. Option A is too brief; B is detailed, and C/D are overly simplistic or lack crucial information.
8 / 9
Chloe is giving a standup update on her progress. She says: 'I'm working on the new user authentication flow.' Which of the following additions would make this update more effective and provide valuable context to her team?
Adding specifics to Chloe's update provides valuable context and demonstrates her understanding of the task. Mentioning OAuth 2.0 shows she's employing a secure authentication method. Option A is vague; B adds detail, and C indicates uncertainty – which can be useful but doesn't provide much value in a standup.
9 / 9
David, a product manager, asks you: 'Can we integrate this new data visualization tool into our existing reporting dashboard?' You've built the tool and it connects to the database successfully. Which of the following responses would best address her request?
David needs to understand the next steps and how the new tool will fit into the existing reporting infrastructure. Acknowledging the connection and prompting discussion about data fields and design shows you're proactively addressing her requirements. Option A confirms only connectivity; B is collaborative and forward-thinking; C rushes the process, and D indicates a problem.
What will I practice in "Technical Pitch Language — Presentations English Exercises"?
This is a Technical Presentations exercise set. It walks through 9 scenario-based multiple-choice questions built around real usage of technical presentations terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 9 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the technical presentations vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Technical Presentations exercises?
See the Technical Presentations exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — technical presentations vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.