Crafting an Elevator Pitch for Tech Roles

An elevator pitch for tech roles is your answer to "so, what do you do?" or "tell me about yourself", delivered in the time it takes to ride a lift. Its job is not to tell your whole story. It is to make the listener curious enough to ask a follow-up question, about a project, a result or what you are looking for.

The structure career services teach

MIT's career office suggests describing what you do with a focus on your strengths, interests and recent accomplishments, after researching the person or organisation so you can stress the experience that best fits (MIT CAPD: elevator pitch). For tech and data roles, that becomes four parts:

1. Who you are: your current role or study, in one phrase.
2. What you do well, with evidence: one specific project or result.
3. What you are looking for: the type of role and, if relevant, domain.
4. A bridge to them: why you are interested in this person or company, often as a question.

The second part is where most pitches fail. "I'm passionate about data" says nothing; "I built a dashboard that cut a weekly report from two days to two hours" gives the listener something to ask about.

Three lengths for three situations

Harvard's career centre suggests a 15-second version for job fairs, a 30-second version for networking events and a 60 to 90-second version to open an informational meeting (Harvard: building your network). The same four parts work at every length; only the detail changes.

15 seconds: the hook

"I'm a final-year statistics student. I recently built a demand forecast for a local grocery chain that beat their spreadsheet method, and I'm looking for analyst roles in retail."

30 seconds: the networking version

"I'm a data analyst with two years in logistics. Most of my work is SQL and Power BI; my favourite project automated our delivery-delay report, so the operations team now sees problems the same morning instead of a week later. I'm looking to move into analytics engineering, building the models behind dashboards. I saw your team uses dbt; how did you start using it?"

60 to 90 seconds: the meeting or interview opener

This version adds a little background, a second piece of evidence, and a clearer reason for this company. It works as the opening answer to "tell me about yourself" in an interview, before the interviewer moves to their own questions. Keep it under 90 seconds; interviewers want a summary they can dig into, not a biography.

Examples for different starting points

Fresher: "I've just finished a B.Tech in computer science. My final-year project was a pipeline that pulls public air-quality data every hour, cleans it and flags unusual readings on a dashboard. I'm looking for a junior data engineering role where I can work on production pipelines."

Career switcher: "I've spent six years in accounts payable, and for the last year I've been automating our reconciliation reports with SQL and Python, which saved my team about a day a month. I'm now looking for a finance analytics role where my accounting background is an advantage, not something to explain away."

Experienced professional: "I'm a senior data engineer at a payments company, where I led the move of our batch pipelines to a lakehouse and cut daily processing time by about half. I'm interested in platform roles with more ownership of data quality, which is why your team's work on data contracts caught my attention."

Each one names a role, gives one concrete piece of evidence, says what they want, and ends somewhere the listener can respond.

How to practise

• Write it, then cut it. First drafts are usually twice too long. Remove adjectives and anything the listener would not ask about.
• Say it out loud and time it. MIT recommends practising alone, with a friend or mentor, or with a career counsellor. Record yourself once; you will hear filler words immediately.
• Make it sound like you. Learn the structure, not a script. A memorised pitch sounds memorised.
• Prepare the follow-ups. Whatever evidence you mention, be ready for "how did you do that?" with a two-minute story.

Adapting it

Change the evidence for the audience: a technical example for an engineer, a business result for a manager or recruiter. Change the ending for the situation: a question about their team at a meetup, a request for advice in an informational call, and a link to the role in an interview. The portfolio project you are proudest of is usually the best evidence to use.

If speaking about yourself makes you uncomfortable, networking for introverts and building confidence for technical interviews may help.

Projects that give your pitch concrete evidence are part of the Data Analytics course.

Sources

• Develop your elevator pitch (MIT Career Advising and Professional Development) — MIT CAPD
• Harvard Extension School Guide to Building your Network (Harvard Mignone Center for Career Success) — Harvard FAS Mignone Center for Career Success