Bridget Kromhout

Ops Sundries

Four Interactions That Could Have Gone Better

I go to a lot of tech events, which means I meet a lot of people in tech. Most of you won’t be surprised to find out that many of them are dudes, and awesome dudes at that. And way more frequently than I’d like, I also find myself in the most tedious conversations.

If you’re wondering why women don’t attend the conferences, unconferences, meetups, or hackathons you enjoy, or why you don’t seem to make meaningful professional connections with the ones who are there, maybe they’ve been having these conversations often enough that they’re tired of it, and would rather spend their time doing anything else at all.

So, here are four recent real-life examples of opening lines that didn’t start off the interactions in the best way, followed by four ways I think they could have gone better. Not a comprehensive list, because none of us have that much time. :)


1. “Are you an engineer?”

Those were his introductory words after looking me down and up and down a couple of times, and my impulsive answer was to laugh aloud. Nope, not my most empathy-filled moment, and I don’t recommend that approach. I felt impatient to be fielding a question that sounded like an incredulous “what are you doing at this industry-company afterparty?”

“Why’s that so funny?” he wanted to know, honestly perplexed.

I looked at his badge and said, “It just is. <Name>, are you an engineer?”

“Um, yes.” He seemed a bit confused. To be fair, he couldn’t have been mistaken for anything but. He had a classic geek aesthetic, straight out of central casting. Nobody would ever question his plausibility in the role of Resident Computer Guy.

I pressed on. “Has anyone else at this conference asked you if you’re an engineer?”

“No…” And then he brightened, an idea occurring to him. “But you’re wearing a company t-shirt, and that usually means marketing or recruiter!”

I lifted my badge and pointed to the “Speaker” line. “Or an operations engineer wearing her company’s shirt the day she’s speaking at the conference.” Gently, with a smile, I then made polite small talk about him and his job until the bartender could give me the water I’d come to get. Although unintentionally hilarious, he seemed to be a nice enough guy, and we managed an okay chat of the Fight Club single-serving-friends sort. So I wasn’t offended, just eyerolly on the inside (and okay, a bit on the outside too).

And then I excused myself to go back to hanging out with Team Etsy, who don’t tend to ask such facepalm-inducing questions. I’m extroverted and I like meeting new people at conferences, but when I don’t have the energy to put up with possible negative interactions, I’ll trade variety for a known-good. I don’t enjoy interacting with peers who act like I am The Mysterious Other and Definitely Not One of Them. It’s tiresome every time it happens again. Still.

2. “Wanna go to the titty bar with us?”

On my way into a conference hotel one evening, I heard the word “devops” coming from the bar, so I walked in and said, “Hi! Sounds like you’re with the conference; heard you talking devops” to three guys in a conversation there. As opening salvos go, their response gets points for being direct (and succinct; they didn’t even introduce themselves). I noped my way out of that conversation right quick, saying, “no thanks; you gentlemen have fun”. (It’s possible there were detectable levels of snark, because what kind of question is that for someone you’ve just met? I don’t personally care what they got up to, but that’s rather awkward. I’ll leave it to the reader to judge or not judge their choices.) I then left the hotel bar and ran into a Twitter friend in the lobby, and while I was chatting with him, the three drunk attendees came lurching after me. (They were definitely with our conference; one was even wearing the conference t-shirt.)

They tried convincing both of us to join them, and (being sober) I made my saving throw to dodge an Axe Body Spray-scented attempted hug. I then excused myself and headed to my room, while apparently they kept following my Twitter friend and hassling him to go with them for a few more minutes.

(I’m all for #hugops, but personally I’d rather have learned your name or at least Twitter handle before we are #hugops buddies. And other women might feel very differently! You should have a verbal ACK that hugging is welcomed by an individual woman before you attempt it, or better yet, let her initiate any hugging. #hugops is a TCP-based not a UDP-based protocol.)

I never felt threatened or particularly alienated; I was heading up to bed anyhow. But if I’d wanted to stay there and keep interacting with other conference-goers, those dudes were a deterrent; if I were a different person with a different set of lived experiences, this could have hit me very differently. It seems they’d completely missed the point of the conference’s code of conduct; I’m pretty sure that wasn’t the kind of inclusiveness it encouraged. And sure, there are much worse things they could have said or done. But when one dude said and did this relatively minor stuff, his two buddies thought it was peachy-keen. Not a sign of good peer review there.

3. “Do you know who that obscure sci-fi character is, the one you used in your slide deck?”

I know a fair number of conference speakers. Some need to hide before and/or after speaking. Some head right to the bar afterwards. Some thrive in the spotlight of “office hours” after a talk, engaging one-to-one with all comers. Many of us seem to finish our slides on the plane if not the podium. I haven’t yet met one who puts stuff generated by /dev/random into a deck without being motivated by any context or reason.

If you want to talk about that TV show you love, don’t open with a line that sounds like you’re fake-geek-girling the speaker who just got off-stage. Because it’s entirely possible that she taped the entire run of that series on VHS, can recite key passages, and rewrote one of the tie-in novels because she didn’t like the ending.

Again, a nice guy. Probably meant well. But in those fraught moments right after public speaking, being asked if they understand their own slides is not a conversation opener that any presenter I know would enjoy.

4. “I didn’t understand most of that stuff you just said about AWS infrastructure tradeoffs. But could you design my app?”

Design is a fantastic skill that I do not even remotely possess. Seriously, I could design you something awesome… as long as I could do it with awk or sed, and you’re okay with it looking like nethack.

This isn’t even the first time I’ve been asked if I’m a designer. At least this guy didn’t insist that I must be, because I look “artistic” (by which I can only guess the previous guy saying that meant “female”). (Yes, I have brightly-colored plastic hair extensions. I hire a stylist with actual taste to help me with that!)

The important thing is, when a woman says, “nope, can’t design stuff for you; I’m an operations engineer”, you should believe her. Or, you know, stop assuming that every woman you meet is going to map to the roles held by women you’ve met in the past.

Also, I suspect nobody would claim to be in ops were it not true, since it would take about ten seconds to unravel such a deception; not to mention, most people don’t even know operations is a thing that exists in the world. Maybe we need our friends in design to help with some promo materials!


So, how could these interactions be better?

You are probably already pretty good at talking about tech and geeking out about the stuff you love. Hooray! Chances are decent that when you meet a woman at a tech event, she might be into tech too!

And hey, the above four examples could annoy people who aren’t women too. This isn’t specific to gender relations or intentional discrimination; it’s about making choices that limit (or enhance!) the quality of your potential interactions with your fellow techies.

So, here are four approaches to try instead:

1. Ask open-ended questions that don’t make assumptions.

Instead of asking her if she’s an engineer or assuming she’s a recruiter or in marketing, ask her, “What are you enjoying doing at Company X?”

She might have a hilarious table-flip anecdote about MongoDB or fresh insights into some Docker thing you’ve been wanting to try. Give her room to surprise you; open-ended questions lead to better conversational outcomes in most circumstances no matter who’s involved. And hey, most companies are hiring; if hers sounds cool, maybe you’ll be interested in talking to them. Or if she doesn’t sound like she’s having fun at her current gig, maybe your company can poach her!

2. Be as respectful as you would be to any person, regardless of their gender.

Please, thank you, not interrupting (or at least asking if it’s okay to page her out to disk!): you probably went to kindergarten; you know this stuff.

If you’re thinking, “I would never say something horrifyingly rude and sexist! I am unfailingly polite to women!”, you still might be making women uncomfortable.

If you don’t know a woman well enough to know how she feels about these things, I wouldn’t suggest pulling out a chair for her, kissing her hand, saying “ladies first”, offering to protect her from amorphous threats, commenting on her attractiveness, or calling her “madame”/“m’lady”. What reads as polite to some might read as condescending to others, and definitely could be seen as setting her apart from the men you consider to be your equals. Leave the chivalry at home.

One place you can help, though: like the gentlemen above who could have peer-reviewed their friend, you can say something to the guys around you, so that they’ll know that you value when they act respectful too. (Woman can say this stuff, but the guys who are less-aware are probably more likely to listen to other guys anyhow.)

3. Talk about the event you’re both at without challenging her right to be there or implying that she needs to provide bona fides.

Instead of asking why she’s attending or what she’s doing there, ask her, “What are you the most interested in learning at this conference? Are there particular speakers you’re looking forward to hearing?”

Tell her about something you’ve enjoyed at the event and ask her what she’s found interesting. (Yes, instead of first quizzing/judging her as to which track(s) she’s attended, offer her some kind of conversational hook. You know perfectly well that the hallway track is a valid track! And that goes doubly for the Werewolf track.) This will help you welcome any new attendees, not just the ones who identify as women.

4. Treat her as an individual.

Address her as “you” and ask her opinion, not the opinion of a hypothetical “someone like you”.

She may be there representing her organization, but she probably didn’t come prepared to represent 51% of the entire US population (or whatever the percentage breakdown is, where you are). Asking a woman you just met about Being A Woman places an unwelcome burden on her, one where she needs to play the role of “Representative Woman In Tech” for the 10,000th time instead of being seen as a person in her own right.

It would be pretty strange if every guy in tech you met were exactly the same as all the others. And that goes for women as well! Giving people space to be themselves allows you the chance to get to know them, which is awesome.

(And it’s possible she doesn’t want to be described with the noun “a female”, which evokes a Discovery-channel-like narrative of the female of the species approaching the watering hole, her calf hidden safely in the underbrush. Go with “woman” if you feel the need to point out the obvious.)


If you’re recognizing your own past behaviour in any of the above, congrats! That means that you have enough self-awareness to realize that you might have inadvertently made a woman in tech feel like you don’t see her as a peer. Awareness is the first step towards change, whether you become aware during an interaction or while reading a blog post. (The next step is trying out the improved interactions. Iteration is a thing! Perhaps you’ll see better results!)

I love working in tech, and I want to be able to encourage other women in tech without a bajillion caveats about all the things they’ll deal with constantly. Plus, if you create a positive culture that welcomes new, different, or marginalized individuals, everyone will want to work at your org. Which is probably hiring. Win!