Most referral advice starts too late, with the wording of the message. The harder problem is deciding what you are reasonably asking another person to support. A former teammate can discuss work they saw. An alumnus you met once cannot. Your request should make that difference visible instead of pressuring every contact to act like a close colleague.
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]
A tech career pivot usually fails for a simple reason: the story looks wider than the evidence. Harvard and MIT both advise candidates to tailor resumes so relevant skills and accomplishments are visible immediately rather than buried in a generic work history.[1][2] If you want to move from developer to product manager, or from QA to DevOps, the goal is not to pretend you already held the new title. It is to make the overlap legible.
Networking is the practice of building enough trust and shared context that opportunities, advice, and collaboration can move faster in both directions.