The case for going to tech meetups as a non-technical person

I'm not technical. I work in operations at a software company. My job involves spreadsheets, contracts, vendor management, a little bit of project work. I have never written a line of production code in my life and I don't plan to start.

I go to roughly two tech meetups a month. They are some of the most useful evenings I have in my calendar. People keep telling me they wouldn't feel comfortable doing this and I think they're wrong, so here's my pitch.

What you think happens at a tech meetup

If you don't go to tech meetups, here's what you probably picture. A room of engineers in branded hoodies. Pizza. Someone stands up and talks for 40 minutes about something with the word "Kubernetes" in it. Everyone else asks questions you don't understand. You stand awkwardly with a beer for an hour and leave early.

I will be honest, this is what some tech meetups are. The deeply technical ones — the Postgres meetup, the Rust London meetup, the kernel debugging one — are exactly that, and you would feel out of place at them. Don't go to those.

What actually happens at the others

Most London tech meetups are not those. The AI meetups, the product meetups, the design meetups, the startup community ones, the company-hosted "we want to look outward" events — these are mostly accessible. The talks are aimed at a mixed audience. The Q&A is welcoming. The networking is genuinly mixed: founders, recruiters, ops people, designers, salespeople, finance people, the occasional curious civil servant. It is not a homogeneous room of senior engineers.

If you turn up at one of these, the worst thing that happens is you have a slightly awkward forty minutes and leave knowing more than you did. The best thing is you meet five people who are useful to you over the next year.

Why non-technical people benefit more, not less

Here's the contrarian bit. Non-technical people probably get more out of tech meetups than technical people do.

Engineers go to meetups for the talk. They're evaluating whether the speaker knows what they're talking about. The networking is incidental.

Non-technical people go to meetups for the room. The talk is incidental. You're there to meet the founders, the operators, the recruiters, the people who will hire you for your next role or work with you on your next project. The signal density of the room is high — these are people who have shown up midweek to learn, which is itself a useful filter.

The technical content washes over you. You'll catch enough to be conversational about it later — "the Anthropic London office has been doing some interesting evals work" is not a sentence you need to be technical to say. You'll learn the vocabulary by exposure.

Vocabulary as a skill

This is the underrated thing. The reason non-technical people are intimidated by tech meetups is mostly vocabulary. There's a glossary of words and acronyms (RAG, fine-tuning, embeddings, MCP, agents, eval, latency, throughput) that you don't need to deeply understand but you do need to recognise when they're said.

You will pick this up at meetups faster than you would by reading. The reason is partly social pressure — you sit through enough talks where someone says "we did this with embeddings" and you will look up what embeddings are, and the looking-up sticks because it has a context. Reading the same definition online is much harder to retain.

After three months of going to one meetup a week you will have most of the working vocabulary of a junior product manager at an AI company. This is genuinely valuable in a non-technical career and there is almost no other equivalently efficient way to acquire it.

The hiring layer

The non-technical roles at most growing tech companies — operations, marketing, sales, partnerships, finance, people — are heavily hired through warm introduction. The job postings exist but the actual hiring conversations start with "do you know anyone who would be good for this." If you're not in the rooms where those conversations happen, you're not in the candidate pool, regardless of how good your CV is.

Meetups are where these rooms are. Specifically, the after-talk pub portion is where they are. You don't have to be at the meetup as a recruit — you have to be there as a person, and the network forms over twelve months of half-distracted post-work pints.

I have been hired into two of my last three roles via people I first met at meetups I went to as a non-technical person at a company nobody had heard of. Neither role was advertised. Neither company posted the vacancy publicly. The conversations happened in pubs.

The rooms that are friendliest

If you're going for the first time, pick one of these:

• An AI x product meetup (Newspeak House runs them often, the Conduit does some, various startup spaces do them)
• A "founders + ops" or "early stage" meetup
• A company-hosted public talk at one of the big AI labs' offices (occasional, free, well-mixed crowd)
• A design x technology night
• A women in tech or non-traditional-route-to-tech event if either applies to you

What I'd skip on day one — anything with "Engineering" in the title, anything with a deeply specific technology in the title, anything advertised as "for technical professionals."

The rules of going as a non-technical person

A few practical things from many years of doing this.

First — be honest about what you do. Don't pretend to be technical. The rooms are friendlier when you're not pretending. "I do operations at a software company" is a perfectly fine sentence and starts more conversations than it ends.

Second — ask the bad questions in the Q&A. The room is silently grateful when someone asks the basic thing. The speakers genuinly prefer it. The other half of the room is wondering the same thing and didn't want to ask.

Third — go to the pub after. The pub after is where the networking happens. The talk is the entry fee.

Fourth — go to the same meetup twice. The second time you go, you'll recognise four people, and four becomes eight and so on. The marginal value of attending compounds heavily over the first six months.

Fifth — do not pitch anyone at the talk. The vibe doesn't work. Have a conversation, swap details, message later. Pitching at the meetup itself is a faux pas in a way that doesn't apply at most networking events.

The closing pitch

If you're non-technical and curious, you're leaving value on the table by not going to two meetups a month. The cost is one hour of your time and zero pounds. The upside is vocabulary, network, occasional jobs, and the slow shift from "I work near tech but don't feel part of it" to "I am part of this scene, I know how it works, I know who's who."

Pick one this week. The free London tech meetups list on Rifio is a fine starting point — filter by free, pick something that doesn't have an acronym you don't recognise in the title, RSVP, turn up. You will not regret it. You might, six months in, wonder why you didn't start sooner.