In-Person Networking — How to Actually Do It

Most people attend events, talk to no one meaningful, and go home. Here's how to do it differently.

Before the Event

Prepare Your Context (5 min)

Know your 30-second answer to: "What are you working on?"

Bad: "I'm a student learning machine learning." Good: "I'm building ML competition solutions — just finished top 10% on a Kaggle NLP competition and now entering WorldQuant IQC. I'm looking to find teammates who know trading algorithms."

The difference: specific, signals competence, invites follow-up, states what you want.

Research Who's Attending

On Luma: RSVP first, then browse the attendee list. Find 3–5 people to talk to and check their LinkedIn/GitHub before going.
On Meetup: Browse the "Members attending" list. Find mutual interests.
On Eventbrite: Check the organizer's previous events — who speaks there regularly?

What to Bring

Phone with LinkedIn app ready for instant QR code sharing
A specific question about what you're building (people love helping)
Business card (optional — Luma/LinkedIn QR is faster in 2026)
1-sentence pitch about your most recent project

At the Event

The Opening Line That Works

Don't say "So what do you do?" — it's boring and generic.

Use context from the event:

"What brought you to this event specifically?"
"Have you been to one of these AI Tinkerers meetups before? What do you think of the demo format?"
"Are you working on anything with [the event's topic] right now?"

These open conversations naturally. People answer with detail, and now you have direction.

The Conversation Flow

1. Context opener (above)
2. Listen more than you talk (70/30 rule)
3. Find the overlap: "Oh interesting — I'm also working with [X]"
4. Offer something: a paper, a tool, a contact, a tip
5. End with clear next step: "Can I connect on LinkedIn? I'd love to follow what you're building"

Give Before You Take

The fastest way to be remembered: be genuinely useful to someone in the conversation.

"Oh you're struggling with [X]? I just dealt with that — here's what worked..."
"You're looking for teammates for a hackathon? I know someone who might be perfect."
"That paper you mentioned — I have a better one that covers the same idea more clearly."

Who to Talk To (Priority Order)

Speakers/presenters: They're approachable right after their talk. Start with a specific compliment: "That point about [X] was really interesting — how did you come to that conclusion?"
People standing alone: They want to be approached. Easiest conversation to start.
People whose work you've seen online: "Are you [name]? I read your Kaggle notebook on [X] — it was really helpful."
Organizers: Thank them genuinely. They know everyone in the room and will introduce you.

The 1 Rule for Hackathon Team Formation Events

Talk to people in the first 30 minutes before groups solidify. Ask directly: "Are you looking for a team? I have [X skill] and I'm looking for someone with [Y skill]." Directness is respected.

After the Event (Most Neglected Step)

Within 24 Hours — Non-Negotiable

Send LinkedIn connection requests to everyone you spoke to — include a short note referencing something from your conversation: "Great meeting you at AI Tinkerers — the point about [X] was really insightful."
Follow up on any promises: "I said I'd send you that paper — here it is: [link]"
Post on LinkedIn/Twitter: "Attended [event] tonight — here's what I learned: [3 points]." This gets you visibility AND shows up in the feeds of people you just met.

The Follow-Up System (2-Week Rule)

Week 1: Send connection request with personalized note
Week 2: Share something relevant to their work (paper, tool, article)
Month 1: Check in if you had a specific shared interest — "Did you end up trying [X]? I did and here's what happened."

This is not spam. This is relationship building. Most people drop off after step 1.

Building a Local Reputation

The Consistent Presence Strategy

Pick one local community (AI Tinkerers, GDG, or Meetup group) and show up every single month for 6 months. Don't hop between events — pick one and go deep.

After 3–4 meetups you'll be a "regular." Regulars get introduced by the organizer, get first-call for team opportunities, and are remembered by speakers.

Give a Talk

At month 3–4 of attending a local meetup, propose a 5-minute lightning talk on something you built or learned. Even a modest competition result makes a great talk: "How I got top 15% on my first Kaggle competition — what worked and what didn't."

Benefits:

Organizer owes you a favor
30+ people know your name after one night
LinkedIn post about your talk = content + credibility

Start a Study Group

Find 3–4 people from your local meetup who want to solve competitions together. Meet weekly (online or in-person). This becomes your permanent team pipeline.

Networking at Hackathons Specifically

Hackathons are the best networking events that exist because:

Everyone is in the same boat (stressed, building, problem-solving)
You have a shared context for conversation that lasts for days
You see people's actual skills and work ethic — not just their resume

How to Network During a Hackathon

Day 1, first hour: Walk the room. Introduce yourself to every team nearby. You'll naturally want to help each other with API issues, bugs, etc.
Mentor sessions: Go to every mentor session. Mentors are senior engineers — treat it as an interview.
Demo day: Watch every team's demo. Ask questions. The teams you respect become your future teammates or colleagues.
Post-hackathon: The people you built with over 48 hours become your strongest network nodes. Keep that group chat alive.