5 exercises — learn to craft compelling 30-second and 2-minute pitches. Understand what to include, what to cut, and how to open a conversation worth having.
0 / 5 completed
Elevator pitch templates for developers
"I help [audience] achieve [outcome] by [your specific method or skill]."
"I'm a [role] specialising in [niche]. At [company], I [specific achievement with a number]."
"I'm currently looking for [type of role/challenge] — which is what drew me to [this company/event]."
"Are you dealing with [relevant problem]? That's exactly the kind of challenge I've been solving."
"Tell me about yourself" → Present (current role + focus) → Past (key achievement) → Future (what you're seeking).
1 / 5
You have 30 seconds in a lift with a CTO you want to impress. Which elevator pitch is most effective?
Option B is the model elevator pitch. It has the three essential components: (1) role identity with a specific angle ("backend engineer who specialises in reducing infrastructure costs"), (2) proof with a concrete result ("cut cloud spend by 40%"), (3) intent — what you're looking for ("roles where I can do this at scale"). Option A is an identity statement with no value signal — it could describe anyone. Option C lists technologies and experience chronologically — this is a resume recitation, not a pitch. It also starts with "I" followed by job title, which is weak. Option D uses vague positive qualities ("passionate about clean code") that every developer claims — this provides no differentiation. Rule: a good pitch answers "What's your specific superpower and what have you done with it?"
2 / 5
For a 2-minute pitch at a startup event, which structure is most effective?
Option B is the correct structure for a 2-minute pitch. Let's break down why: (1) "Who you are" — brief identity, 10 seconds, (2) "specific problem you solve" — your unique angle, not just your job title, (3) "evidence of impact" — one or two specific numbers or outcomes, (4) "what you're looking for and why this audience is relevant" — shows you've targeted this pitch to the listener, not just broadcast your CV. Option A is the resume-reading structure — it answers "what have you done?" not "why should I care?" Option C leads with institutional identity (company/education) — appropriate for formal introductions but not engaging pitches. Option D starts with a personal story, which can work in a pitch competition but is risky in 2 minutes — it eats time before the value proposition.
3 / 5
Which phrase best opens a developer elevator pitch at a job fair?
Option B opens with the value proposition first — a powerful technique borrowed from product marketing. Instead of starting with who you are, you start with what problem you solve and what result you deliver. The structure is: "I help [audience] do [outcome] by [method]." This immediately communicates your value to any listener. Option A is weak and creates a passive impression. Option C is a skills laundry list — technology stacks alone don't differentiate you; every developer has a stack. Option D is too generic and emotional rather than professional. You can follow Option B with your name and current role, but leading with value is far more memorable. Tip: if you don't know your specific value yet, ask yourself: "What problem does my manager come to me for?"
4 / 5
What should the closing line of a developer elevator pitch accomplish?
Option B is correct. A pitch without a close is like an API endpoint with no return value. The close should do one of three things: (1) propose a next step ("I'd love to find 15 minutes to show you the dashboard I built"), (2) ask a relevant question to open dialogue ("Are you dealing with similar scaling challenges at [Company]?"), or (3) express a specific interest that invites response ("I noticed you're hiring for platform engineering — is that an area you're growing?"). Option A is polite but ends the interaction. Option C is repetition — you only have 30-120 seconds; don't waste them summarising. Option D is pleasant but generic — enthusiasm without a hook gives the listener no reason to continue the conversation. The best pitches end with a question or invitation, not a full stop.
5 / 5
A recruiter asks "Tell me about yourself" at the start of a phone screen. Which 30-second response is most effective?
Option B is the professional standard for "Tell me about yourself." It follows the Present-Past-Future structure: (1) Present — current role and specific focus ("senior backend developer, distributed systems"), (2) Past — what you've built, with scale ("10 million events per day"), (3) Future — what you're seeking and why this role fits ("more greenfield architecture work"). Option A is the chronological life story — it answers "what happened to you?" not "why are you here?" Option C lists soft skills and generic qualities — these are expected of every candidate and carry no information. Option D stalls with a filler phrase ("That's a great question") and then says nothing concrete. In interviews, "Tell me about yourself" is your pitch slot — use the Present-Past-Future framework every time.