How do you network at a tech conference for a job?

Why is a tech conference a better job-search channel than a job board?

Treat a conference as a hiring channel rather than a learning holiday and it will beat a month of cold applications. The organisers' founder's guide to TechCrunch Disrupt 2026 — running October 13–15 at Moscone West in San Francisco — frames all three days around one question: how do you build an enduring company in the AI era? Read that as a job seeker and the subtext is hard to miss. More than 10,000 founders, investors and operators in one building, over 300 startup booths in the Expo Hall, six curated stages and the Startup Battlefield 200 for pre-Series A teams. The guide even tells scaling founders to use the event's networking tools to find talent. That talent could be you.

Compare the two funnels honestly. A posted role at a well-funded AI startup collects applications from every time zone within hours, and most of them are read by software before a human ever opens the file. At a booth, you're one of maybe forty people who speak to that company all day, and perhaps five who ask something intelligent about the product. The conversation isn't scored against a keyword list — it's scored on whether you were interesting. That's a completely different game, and it's one where a mid-career engineer, a career changer or a strong junior can win on curiosity and preparation rather than on pedigree alone.

Here's the catch nobody warns you about. Good conference conversations don't end with an interview; they end with "send me your CV tonight." That's a window measured in hours, not days, and it closes while the person is still buzzing from a conversation they'll have twenty more of before Thursday. If your CV is a two-year-old file with the wrong job title at the top, you've converted a warm referral into a cold attachment. Everything that follows in this article exists to protect that handoff: the research that earns the request, the intro that makes it specific, and the same-day turnaround that makes you look like someone who ships.

How do you pick 15 target companies before you go?

Cap your list at 15 companies and build it two weeks out, straight from the exhibitor directory and the Startup Battlefield 200 roster. Fifteen is the number because it's roughly what one person can research properly and still cover across three days of walking. Sort them into three tiers: five companies you'd accept an offer from tomorrow, five adjacent bets where your skills clearly transfer, and five wildcards — pre-seed teams whose booth nobody else will bother visiting. The wildcards convert best, and that's my contrarian position. A pre-Series A founder working their own booth is the hiring manager, the recruiter and the final decision-maker in one body, with no queue in front of them.

For each company, spend fifteen minutes and write five lines in one document: what they actually sell, their funding stage, which roles are open right now, the name of whoever runs the function you'd join, and one genuine question about the product. That last line does most of the work. "How are you handling evaluation for the agent workflows?" lands differently from "Are you hiring?" — the first marks you as a peer, the second as traffic. Cross-check the agenda as well: if someone from your list is speaking on the Builders or AI stage, go to the session. You'll walk up afterwards with a legitimate opening instead of a cold approach.

Then plan the clock, because the Expo Hall has a rhythm. Doors run 9:00 to 5:00 Pacific, and booths are quietest in the first forty-five minutes and while a headline keynote is pulling the crowd — exactly when a founder has ten unhurried minutes. Hit your top five then, not at 2pm when the aisle is three deep. Side Events running across the Bay Area during Disrupt week are the other unfair advantage: a smaller room, a drink in hand, and forty-five minutes with the same person you'd get ninety seconds with at a booth. Book two per evening and treat them as the main event, not the afterparty.

What do you say in 30 seconds so a hiring manager follows up?

Lead with the problem you solve, one number that proves it, and a specific reason you walked up to this booth — then stop talking and ask a question. Do not ask for a job in the first exchange. A usable version sounds like this: "I'm a backend engineer; I spent the last two years cutting inference costs on a recommendation service by about 40%. I came over because you're doing on-device models and I'm curious how you handle fallback when the connection drops." That's twenty seconds, it signals a specific competence, and it hands the conversation back instead of cornering someone.

The structure holds outside engineering too. A sales candidate says what they carried and closed; an operations lead says what process they rebuilt and what it saved; a career changer names the overlap rather than apologising for the gap — "I ran cohort data for 400 students a year, which is the same reporting problem your customer success team is solving." What kills the pitch every time is the chronological life story. Nobody standing at a booth has the patience for "so I graduated in 2017, then I joined…" Give them the headline, let them ask for the detail, and keep your answers shorter than theirs.

Close the loop before you walk away, because this is where most people fluff it. Ask one of two questions: "Who owns hiring for that team?" or "Is it worth me sending you something tonight?" Both make the next step concrete and both are easy to say yes to. Then write the person's name, their company, and the one detail you'll quote back — in your phone, immediately, before the next conversation overwrites it. Two more rules: don't hover around speakers and investors who are already surrounded, and don't collect swag at a booth where you want to be taken seriously as a candidate.

What should you carry instead of printed CVs?

Leave the printed CVs at home. They're dead weight, they go straight into a tote bag with forty flyers, and the version you printed on Monday can't be tailored to the conversation you had on Wednesday. Carry three things instead: a CV as a PDF you can send from your phone in under a minute, your badge for scanning, and a battery pack, because a dead phone at 3pm costs you the whole afternoon's follow-up. If you want something physical, a plain card with your name, role and contact details is enough — founders still pocket those, and it costs you nothing to have ten.

The digital kit matters more than people think. Keep one clean PDF in your phone's files and a second copy in a cloud folder with a short shareable link, so you can send it on the spot when someone says "actually, send it now." Put your LinkedIn QR code one tap from your lock screen. Keep a running note titled with the conference name where every entry follows the same shape: name, company, what we discussed, what I promised, deadline. By the end of day two you'll have twenty entries, and that note is the only reason you'll remember which founder cared about test coverage.

One more piece of prep that pays for itself: know what your CV scores before you walk in, because you won't have time to find out on the night. A free CV analysis gives you a score out of 100, five category scores covering experience, tech stack, impact and ownership, clarity and structure, and ATS compatibility, plus a visual layout check that flags the design choices that quietly break parsing. Fix the structural problems the week before. The conference is for conversations; it's a terrible time to discover your two-column template loses half your job titles in extraction.

How do you send the same-day email and the CV an early-stage startup actually reads?

Send it the same night, before you go to sleep, with a subject line that names the conversation: "Booth 214 — on-device fallback — backend engineer CV." Keep the body to five sentences. One line placing you ("we spoke at your booth this morning about evaluation for the agent workflows"), one line of proof tied to their problem, one sentence on what you want, the attachment, and a sign-off. Name the file properly — Firstname-Lastname-Backend-Engineer.pdf, never cv_final_v3.pdf. Ask for twenty minutes rather than "an opportunity." A specific, small request from someone they already liked is the easiest yes in a founder's inbox.

The attachment has to match the conversation, which is why the same-day turnaround is the hard part. Paste the job description — or the few lines the founder told you about the role — into an analysis and you get the missing skills called out plus ATS-friendly rewritten versions in six templates that mirror the job's own wording, which is a twenty-minute job instead of a two-hour one. If your current file needs rebuilding from scratch rather than tweaking, the chat-based CV builder takes an old CV or a plain description of your experience and exports to PDF or Word. Either way, send one tailored file per company. Never a single generic attachment blasted to eight people.

Keep a second variant ready for the pre-seed teams, because they screen differently. Many seed-stage companies run hiring out of a founder's inbox, a shared document, or a free or low-cost tracking tool; the heavyweight systems usually arrive later, once there's an actual recruiter and a real headcount plan. So there's often no keyword gate at all — but there's a harsher one: a founder reading on a phone between meetings, deciding in thirty seconds. Front-load scope, what you shipped, and what you owned end to end. Keep it one column and one page anyway, because the moment they forward you to a Series B friend, that file hits a parser after all.

Frequently asked questions