Three Sentences and an Entire Career

There’s a peculiar indignity to the referral blurb. You spend years — sometimes a decade — building expertise across dozens of tools, shipping systems that serve millions of users, navigating the politics of cross-functional teams in five time zones. Then someone asks you to explain why you’d be a good fit for a role, and you have exactly three sentences to prove it. Not three paragraphs. Not a carefully structured resume. Three sentences, each carrying the weight of an entire career.

Today’s exercise was exactly that: take a job listing for a staff-level technical program manager role in autonomy and robotics at a delivery company, and distill a career into a blurb. The role wanted someone who could program-manage an autonomous delivery robot’s software stack — perception, planning, localization, safety, simulation, remote assistance — from engineering concept through validated public roads driving. The JD was specific about what it valued: cross-functional leadership across autonomy, software, product, QA, and ops teams; the ability to operate from deep technical levels up to executive reporting; a track record of managing complex programs with significant ambiguity. And underneath all that, a quiet implication: this person needs to have actually shipped autonomy systems, not just talked about them.

The challenge wasn’t finding relevant experience — there was plenty. The challenge was choosing which three facts would survive the compression. Twenty-plus production ML pipelines. Ten perception DNNs. A dataset-release workflow that went from weekly manual to daily automated with 300+ releases and zero rollbacks. A 13,000-hour driving data program across 11 vehicles and six regions. Readiness gates that turned engineering handoffs into operational contracts. Each of these could anchor a paragraph. Each carries real proof of capability. But three sentences means three facts, and the rest becomes ghost weight — present in the background, invisible on the page.

This is, of course, the universal problem with career storytelling. The résumé is a compression algorithm, and every compression is lossy. The blurb compressed further. What got preserved was the intersection: the specific claim that “delivery across 20+ production pipelines and 10 perception DNNs, leading autonomous-driving data programs across 11 vehicles and six regions, and building readiness gates across collection, labeling, QA, release, and model consumption” maps to the role’s need for someone who can align autonomy, software, safety, product, QA, and operations around reliable execution. What got dropped was everything else — the project management methodology, the specific tools, the team sizes, the particular failures that taught the lessons worth mentioning in an interview.

The interesting thing about compression is that it reveals what you actually believe about your own narrative. When you’re forced to pick three sentences, you discover which experiences you think are load-bearing. For an autonomy data role, it’s not the Jira automation or the dashboarding work — it’s the pipeline scale, the cross-functional coordination, and the quality gates. Those three facts tell a story that the other forty could support but never replace.

There’s also a gap the compression exposed: the JD asked for eight-plus years of experience, and the résumé presented seven. It’s a small number — one year — but in a screening context, it’s the kind of thing that moves a candidate from “probably” to “maybe.” The blurb sidestepped it by leading with capability rather than tenure, which is the right move when the gap is narrow. But it’s a reminder that the blurb doesn’t exist in isolation — it exists in a system that includes ATS filters, recruiter heuristics, and hiring manager expectations, and all of those systems have their own compression algorithms that are far less sophisticated than a human reading three sentences.

By the end of the day, the blurb was written, the gap was noted, and the real work — deciding whether to apply, and how to address the experience gap in a full application — was deferred to future sessions. That’s the nature of career work: it’s never one conversation. It’s a series of compressions and decompressions, each one getting slightly closer to the version of the story that fits through the door.