Elevator Pitch Examples: 15 Pitches, Organized by Situation

The best elevator pitch examples share one shape: a specific claim about what you do, one piece of evidence that makes the claim believable, and a small, concrete ask. Below are 15 examples — one person pitched five ways, seven career situations, and three rewrites of common failures — with notes on what each version deliberately cuts.

Every person below is an illustrative composite, and the numbers in their pitches show how evidence sounds out loud, not anyone's real results. Copy the structure, never the nouns.

The anatomy of a pitch: claim, evidence, ask

An elevator pitch is a spoken, 30-to-60-second answer to the question "so, what do you do?" that leaves the listener knowing what you're good at and what they could do next. MIT's career office recommends that same 30-to-60-second window. Almost every pitch that works has three moving parts, in this order.

The claim

The claim is one sentence about what you do, phrased as a result for someone rather than as a title you hold. "I'm a senior backend engineer" is a title. "I build the systems that decide whether your card payment goes through" is a claim. The test for a good claim is simple: could a thousand other people in your field say the exact same sentence? If yes, it's a category, not a claim.

The evidence

The evidence is a single, concrete thing you did that makes the claim believable: a project, a before-and-after, a problem you solved that the listener can picture. One piece is enough; three means the pitch has turned into a biography.

The ask

The ask is what you want to happen after you stop talking, anything from a question back to a request for an introduction. Most pitches that fail, fail here, for reasons worth a section of their own.

The length, in words rather than seconds

Career guides usually give the length as 30 to 60 seconds, which is hard to feel while you're drafting. Words are easier. The National Center for Voice and Speech puts average American conversational speech at about 150 words per minute, so a 30-second pitch is roughly 75 words and a 60-second pitch is about 150. The full examples below run roughly 45 to 85 words, short enough to survive an interruption.

Why most pitches fail on the ask, not the claim

People spend hours polishing the first sentence and almost no time on the last one. The result is a strong opener followed by "anyway, let me know if you hear of anything," which hands the listener a vague job with no deadline. Nobody acts on it, not because they don't want to help, but because there's nothing specific to do.

There's a well-documented reason people soften the ask. In a set of studies published in the Journal of Personality and Social Psychology in 2008, Francis Flynn and Vanessa Lake (now Vanessa Bohns) found that people underestimated by as much as 50% how likely others were to agree to a direct request for help. Help-seekers focused on how costly it would be for the other person to say yes, and underrated how uncomfortable it is to say no. The requests studied were everyday ones like borrowing a phone, not networking, but the pattern maps cleanly: we assume the ask is an imposition, so we blur it until it stops being one.

A good ask has four properties. It is small enough to say yes to on the spot, specific enough that the listener knows exactly what yes means, matched to their real reach, and easy to decline without awkwardness. Here are the asks that show up in the examples, from lightest to most direct:

• A question back. "What does your team work on?" Casual networking, where the goal is a second conversation.
• A qualifying question. "What level is this role scoped at?" Recruiters, where you're deciding together whether to keep talking.
• A follow-up call. "Would you be open to 20 minutes in the next couple of weeks?" When you share a specific interest.
• An introduction. "Do you know who runs the learning team there?" When the listener knows someone you don't.
• An opportunity. "Could we talk about whether I could lead that project next half?" When the listener controls what you want.

Not every pitch needs a hard ask. At a party, a question back is the correct ask. What matters is that the ending is a choice you made, not the moment you ran out of things to say.

One person, five pitches: what changes by situation

The same person needs materially different pitches for a networking event, a recruiter's call, a conference hallway, a meeting with their boss's boss, and the top of their LinkedIn About section. The tone barely changes between them. What changes is what gets cut, because each listener already knows different things and can do different things for you.

Meet Jordan, an illustrative senior backend engineer with six years on payments infrastructure at a mid-size fintech. Jordan recently led a migration that moved card authorization off a legacy system, and wants a staff-level role, either internally or somewhere else.

1. At a networking event

I build the systems that decide whether your card payment goes through — I'm a backend engineer at a fintech, mostly on payments infrastructure. The project I'm proudest of was moving card authorization off a fifteen-year-old system without any downtime. I'm starting to think about what's next, so I'm curious: what does your team work on?

Cut: the job title up front, the level, the job search details, the tech stack. The opener is a picture anyone understands; the ask is a question back.

2. When a recruiter calls cold

Sure. I'm a senior backend engineer, six years on payments infrastructure, mostly Go and Postgres at high transaction volume. I led the migration of our card-authorization service off a legacy monolith, and that's the scope I'm looking for as a baseline: staff-level roles on infrastructure or platform teams, remote or hybrid in Chicago. Before we go further, what level is this role scoped at, and which team is it on?

Cut: the friendly hook, the story, the curiosity. A recruiter is matching you to a requisition, so the pitch front-loads the facts they filter on, and the qualifying question saves you both a wasted call.

3. In a conference hallway, after someone's talk

Your point about retries being where money goes missing — we hit exactly that last year. I'm Jordan, I work on payments infrastructure at a fintech, and we ended up handling it with idempotency keys at the gateway instead of in each service. I'd love to compare notes on how you handled reconciliation. Would you be open to a 20-minute call in the next couple of weeks?

Cut: the career history and the job search, entirely. The pitch starts with their work, not yours, which is the only reason a speaker mobbed after a talk will keep listening.

4. In a skip-level meeting

Since the authorization migration wrapped, I've been looking at where our next reliability risk is, and I think it's settlement. It's still batch-based, and most of this quarter's incidents touched it. I'd like to own the design for moving it to event-driven processing, which is also the scope I'd need to make the case for staff. Is that on the roadmap for next half, and what would you want to see from me to lead it?

Cut: name, title, company, team — everything a director in your own org already knows. The claim becomes a problem you've spotted, and the ask is the most direct of the five, because this listener controls the opportunity.

5. As the LinkedIn About opener

I build payments infrastructure — the unglamorous systems that decide, between the tap and the beep, whether a card transaction is approved. For six years I've done that at a mid-size fintech, most recently leading the migration of card authorization off a legacy monolith with zero downtime.

Cut: the ask, or at least move it to the end of the section. On a profile, only the first few lines show before "see more," so the written version is pure claim and evidence. A job-search ask in the first line reads as needy in a way it doesn't in person.

Line the five up and the pattern is clear:

• Networking event: keep the picture, cut the logistics, ask a question back.
• Recruiter call: keep the logistics, cut the picture, ask a qualifying question.
• Conference hallway: cut yourself down to one sentence, lead with their work, ask for a call.
• Skip-level: cut everything they already know, lead with a problem, ask for the opportunity.
• LinkedIn About: cut the ask, keep claim and evidence, write for the preview.

Elevator pitch examples by career situation

Each situation below has a different structural problem to solve. The career changer has to make old evidence count for a new claim; the new graduate has no title to lean on; the person returning after a gap has to address it without apologizing for it. The pitches below are written for a networking conversation, the most common setting.

Career changer: teacher to instructional designer

For nine years I taught high school chemistry, which mostly means I spent nine years figuring out why people don't understand something and redesigning the lesson until they do. Over the last year I've moved that into instructional design. I finished a certificate and rebuilt a lab-safety onboarding module for a local biotech that roughly halved the time their trainers spend on it. I'm looking for my first full-time learning-and-development role. Do you know anyone on the L&D team at your company I could talk to?

Why it works: it translates the old job into the new job's verbs (diagnose, redesign) instead of listing it. The evidence comes from the new field, which answers the unspoken "but can you actually do it?" before it's asked. The ask is an introduction, because a career changer's real gap is contacts.

New graduate

I graduated in May with an industrial engineering degree, and the thing I keep coming back to is warehouses — specifically, why picking routes are still so inefficient. My senior capstone was with a regional grocery distributor: we re-slotted their fastest-moving items and shortened pick paths in a simulation they're now piloting on one shift. I'm applying for operations analyst roles in distribution. Your company runs its own distribution centers, right? What does the analyst team there actually spend its days on?

Why it works: with no title to hide behind, the claim is a specific interest, which is more memorable than "recent grad looking for opportunities." The capstone is real evidence of applied work. The closing question shows homework and gets the listener talking. For the setting where this pitch gets used most, see our guide to what to wear to a job fair.

Senior individual contributor

I'm a senior UX researcher. I run the studies that decide what our product team <em>doesn't</em> build. The most useful thing I did last year was a pricing-page study that convinced us to drop a feature tier before launch, which freed up about a quarter of engineering time. I've stayed an individual contributor on purpose — I want to keep doing research, not manage researchers. If you come across teams hiring hands-on research leads, I'd love to hear about them.

Why it works: senior ICs often face the silent question "why aren't you a manager yet?" This pitch answers it in one sentence and frames the choice as deliberate.

Freelancer

I'm a bookkeeper, but only for independent restaurants — usually one to three locations, with an owner doing the books at midnight. Restaurants have their own mess: tip pooling, delivery-app payouts that never match the deposits, food costs that swing week to week. I reconcile all of it monthly and send the owner a one-page summary they'll actually read. If you know a restaurant owner who's drowning in receipts, I'd be grateful for an introduction.

Why it works: the niche does the heavy lifting. "Bookkeeper" is forgettable; "bookkeeper for independent restaurants" is referable, because the listener can instantly think of one person to send your way.

Founder

I'm building scheduling software for home-health agencies. Most of them still schedule nurses with spreadsheets and phone calls, and when a visit gets missed, a patient goes without care and the agency has a compliance problem. We're live with four agencies, and every one of them has cut missed visits since switching. I'm looking for two or three more to pilot with. Do you work with any home-health operators who'd be open to a demo?

Why it works: this is the social version of a founder pitch, not the investor version. It names who has the problem, what it costs in terms a stranger can feel, and asks for what the company needs this month: pilot customers.

Returning after a career gap

I'm a marketing operations manager. For seven years I ran the systems behind campaigns: the CRM, the lead scoring, the reports that told sales which leads to call. I stepped away for three years to care for a family member, and over the last few months I've been getting current — I renewed my Salesforce admin certification and rebuilt lead routing for a nonprofit as a volunteer project. I'm looking to come back full-time. Who do you think is hiring for marketing ops right now?

Why it works: "I'm a marketing operations manager," present tense, not "I used to be." The gap gets one plain clause, no apology and no over-explanation, and then the pitch moves straight to current evidence, which is what the listener is actually wondering about.

Niche technical role

I'm an RF test engineer, which in plain terms means I make sure wireless devices pass the radio-emissions testing they need before they can legally be sold. Most recently I built an automated test rig for a smart-lock maker that took their pre-certification testing from weeks to days. I'm looking for a team shipping connected hardware at volume. Does anyone at your company own compliance testing for your devices?

Why it works: the "in plain terms" sentence is the whole trick. Most listeners are smart outsiders: translate the role into its consequence and save the jargon for the follow-up.

What not to do: the failure modes, with rewrites

Weak pitches rarely fail because the person has nothing to say. They fail in a handful of predictable ways, and each one has a recognizable sound. If you can hear yourself doing one of these, the fix is usually a cut, not an addition. Three come with rewrites; the other two are habits of structure and delivery, so they get a fix instead.

The job-title recitation

Before: "I'm a senior associate in the transaction advisory services group at a Big Four firm, focusing on the TMT sector." Accurate, but the listener has to decode four pieces of internal vocabulary to learn what you do.

I'm the person a buyer calls to find out whether a company's numbers are real before they buy it — mostly tech and media deals, at one of the big accounting firms.

The abstract-noun pitch

Before: "I'm a results-driven marketing leader passionate about driving growth and building high-performing teams." Results, growth, passion and teams are nouns with nothing inside them, and a competitor could say the same sentence word for word. This is the pitch version of the problem our personal brand statement examples spend most of their time fixing.

I run lifecycle email for a subscription meal-kit company — the emails that decide whether someone orders a second box. Last year we rewrote the first-week sequence, and the share of new customers who came back for that second box went up by about a tenth.

The ask that isn't an ask

Before: "Anyway, if you ever hear of anything, let me know!" It feels polite, but it asks the listener to remember you indefinitely and guess what "anything" means.

Would you be open to introducing me to whoever runs your data team? I'd keep it to 15 minutes.

The chronological biography

"So I started out in accounting, then I moved to…" signals a four-minute answer to a 30-second question. Start in the present and reach back only for the one piece of history that serves as evidence. The full chronology belongs in your resume or bio.

The audibly memorized delivery

Listeners can hear a recited pitch: an even, slightly sing-song rhythm, a speed that's faster than your normal speech, and a tell-tale restart from the top when you get interrupted. Recitation signals performance, which invites the listener to evaluate rather than engage. The fix is to memorize the skeleton, not the script: the first sentence word for word, then three bullet points (claim, evidence, ask) that you rebuild in fresh words every time.

How to build and practice your own

Writing a pitch in the order it's spoken is a big reason most drafts come out generic. Work backward instead: evidence first, because it's the part you can't fake, then the claim the evidence supports, then asks tailored to the rooms you'll actually be in over the next month. The whole process fits in an evening.

1. 1List three things you did that had a visible result. Pick the one a smart outsider would understand without a glossary.
2. 2Write the claim the evidence supports, phrased as what you do for someone. Run the thousand-people test and rewrite until it fails.
3. 3Write one ask per situation you expect in the next month: a question back for events, a qualifying question for recruiters, an introduction or a call for everyone else.
4. 4Assemble and cut to about 75 words. Read it aloud against a timer. If you breathe mid-sentence, the sentence is too long.
5. 5Memorize the first sentence and the skeleton only. Say it in different words each time you practice.
6. 6Test it on someone outside your field. Ask them to repeat back what you do. If they reach for your job title, your claim is still abstract.
7. 7Prepare the follow-up. A good pitch earns a question. Have the two-minute story behind your evidence ready, because that's where the real conversation starts.

Where your pitch lives in writing

The spoken pitch has written siblings, and they are not the same document. Each keeps the same core claim but cuts differently for its format and reader, so treat them as one set built from a single source. When your pitch changes, update all of them, or the version people read will contradict the one they heard.

• Personal brand statement: the claim alone, in one sentence, with no evidence and no ask. The personal brand statement guide linked above covers how to compress it that far.
• LinkedIn headline: the claim squeezed into 220 characters, with the first few words doing most of the work. See our LinkedIn headline examples for role-by-role versions.
• LinkedIn About section: the pitch minus the ask as the opener, then room to expand within the 2,600-character limit. Our LinkedIn About section examples pick up exactly where Jordan's opener above stops.
• Professional bio: the pitch in the third person, plus the history the spoken version cuts. The professional bio examples guide gives short, medium and long versions.
• Interview introduction: the pitch stretched to answer "tell me about yourself," with the ask replaced by why this role. Our guide on how to introduce yourself in an interview scripts the first 90 seconds.

One more thing travels with the written versions: your face. On LinkedIn, the About opener is read alongside your headline and profile photo, and the three either reinforce each other or quietly argue. A crisp claim next to a cropped vacation photo from years ago sends a mixed signal before anyone reaches "see more." Our guide on how often to update your LinkedIn photo gives the rule of thumb. The photo needs to be current, well lit, and cropped so your face is legible at thumbnail size, whether it comes from a photographer, a friend with a good phone, or an AI headshot generator.