Crafting an Elevator Pitch: Summarizing Your Value Proposition in 60 Seconds
A good elevator pitch does not need to sound clever. It needs to help another person understand you quickly. In practice, that means giving a short introduction that explains who you are, what kind of work or problems you are best suited for, and what you want next. Career centers generally frame the pitch as a 30 to 60 second summary for networking, career fairs, and informational conversations, not a memorized speech for impressing strangers.[1][2]
Start with the problem space, not your full life story
One reason elevator pitches fall flat is that they try to cover everything. A stronger approach is to anchor the pitch in the kind of problem space you work in.
For a backend engineer, that might be reliable systems or API performance. For a product analyst, it might be turning messy behavioral data into decisions. The listener does not need your whole resume. They need a clean answer to, "What kind of value do you usually create?"
UNC's career guidance uses a present-past-future structure for this kind of introduction: who you are now, what relevant background supports that, and what direction you want next.[1] That structure works well because it forces prioritization.
Name the few strengths that actually differentiate you
After the problem space, move to the specific strengths that make you useful in that space.
This is where many people drift into vague language like "hardworking," "passionate," or "great communicator." Harvard's resume guidance pushes candidates toward specific, fact-based language and away from generic claims, which is just as useful in spoken introductions.[3] If the phrase could describe almost everyone in the room, cut it.
Instead, pick one or two strengths tied to evidence, such as a technical skill, a repeatable outcome, or a cross-functional advantage.
For example, compare these two versions:
- "I'm a software engineer with strong problem-solving skills."
- "I'm a software engineer focused on backend systems, and I do my best work on reliability and developer tooling problems that reduce friction for teams shipping fast."
The second version is more memorable because it gives shape to your value.
Santa Clara's career center recommends including your relevant strengths, target role, and what kinds of opportunities interest you.[2] That does not mean listing everything. It means choosing the details that create signal.
End with direction
A pitch feels complete when the listener knows where you are trying to go.
That goal can be immediate or exploratory. You might be looking for senior frontend roles or trying to move from QA into DevOps. Cal Poly Pomona explicitly suggests tailoring your pitch to different employers or industries, which is a useful reminder that "what I want next" should change with context.[4]
A compact formula looks like this:
Present: who you are now
Proof: the strengths or experience that matter most
Direction: the kind of role, team, or problem you want next
That might sound like:
"I'm a data analyst in B2B SaaS, and lately I've been focused on turning product usage data into retention insights for customer success and product teams. I'm at my best when I can connect the numbers to a clear business decision, and right now I'm exploring senior analytics roles where that mix of analysis and stakeholder communication matters."
That gives the listener your role, problem space, differentiation, and direction in under a minute, which is usually all you need.
Tailor the same core pitch for interviews, networking, and conferences
You do not need a different identity for every room. You need one core pitch and a few variations.
At a networking event, the goal is to open a conversation. Yale describes networking as a way to gather information, build professional connections, and uncover opportunities.[5] In that setting, your pitch should feel curious and easy to engage with.
In an interview, the same pitch can be tighter and more role-specific. At a conference, it can be broader and more idea-oriented, especially if you are meeting peers rather than hiring teams.
A useful test is this: after hearing your pitch, could the other person reasonably know what kinds of roles, teams, or conversations to point you toward? If not, it is probably too abstract.
A few example versions make the difference clearer:
- Software engineer at a networking event: "I'm a backend engineer working mostly on API and reliability problems for SaaS products. A lot of my recent work has been around making internal tooling easier for other engineers to use, and I'm especially interested in teams where developer experience is treated like a product."
- Career switcher in an interview: "I started in customer support, then moved into operations analytics because I kept gravitating toward process and data problems. Over the past year I've been building SQL, dashboarding, and reporting skills, and now I'm targeting junior analyst roles where I can combine customer context with hands-on analysis."
- Product marketer at a conference: "I work in product marketing for B2B software, usually at the point where positioning, launch strategy, and customer research need to line up. I'm especially interested in how technical products get explained clearly, so I always like talking with people who sit close to product and sales."
Each example stays short, but each also gives the listener something useful to work with: your lane, your evidence, and the direction you are moving.
Practice until it sounds natural
You are not trying to memorize a monologue. You are trying to make the introduction easier to deliver.
Cal Poly Pomona recommends practicing out loud and getting feedback from other people.[4] Santa Clara likewise notes that practice helps you feel comfortable enough to introduce yourself clearly in different settings.[2] That is the right standard. You want fluency, not theater.
A simple practice routine works well:
- write a version that is about 80 to 100 words
- say it out loud and remove any phrase that feels unnatural
- create a shorter 40 second version and a slightly fuller 60 second version
- test it with a friend and ask what they remembered two minutes later
If people only remember your job title, the pitch is too generic. If they remember the kind of problems you solve and where you want to grow, it is working.
Keep your spoken pitch aligned with your written materials. If your resume says one thing, your LinkedIn says another, and your introduction points in a third direction, people notice. Tools like CoreCV.ai can help you keep tailored resume versions consistent with the story you tell live, but the principle matters more than the tool.
A strong pitch is just clear positioning
You are not trying to perform. You are trying to make it easy for the right people to understand where you fit. Start with the problem space, name the few strengths that truly differentiate you, and end with a clear direction. Then practice until it sounds like you on a good day.
Sources
1. University of North Carolina Career Center, How to Craft an Elevator Pitch: https://careers.unc.edu/resource/how-to-craft-an-elevator-pitch/
2. Santa Clara University Career Center, Elevator Speech: https://www.scu.edu/careercenter/toolkit/networking/elevatorspeech/
3. Harvard FAS Mignone Center for Career Success, Create a Strong Resume: https://careerservices.fas.harvard.edu/resources/create-a-strong-resume/
4. Cal Poly Pomona Career Center, Elevator Pitch: https://careercenter.cpp.edu/channels/elevator-pitch/
5. Yale Office of Career Strategy, Networking: https://ocs.yale.edu/channels/networking/
Disclosure: This article is authored by the CoreCV team. While we mention CoreCV.ai, the strategies and advice presented apply broadly to modern job searching and career development.