The situation described at the tradeshow in this article has also happened to me, repeatedly and consistently. The difference? I AM technical. I just also happen to be a woman.
I love the tech industry. I've been in it professionally since 1997, and I've run tech startups as a CEO for the past 13 years. And if there's one thing I can count on, it's the consistent, pervasive assumption that I'm not technical.
I hate going to tech events with my fiance (or for that matter, any man), because people will come up to us, acknowledge me, and then ask him brightly: "So why are you here?"
I once thought it would be funny to time it and see how long another person could go talking to only him and not making eye contact with me, even when he mentioned that he was at the event because of me. Current record? 13 minutes. 13 minutes of not looking at me, saying a word, or acknowledging that I was there.
Every male that I've ever told this story to can't believe it until they go to parties and see it in action. It's so consistent, yet it's unbelievable until you see it.
This is what it's like to be a woman in tech, even when you're a technical one. It's assumed that you're non-technical. But don't take that into account and lead with your credentials--whoops, no, that's "aggressive" and you shouldn't do that. Don't go to tech parties with a guy because you're assumed to be "the girlfriend." Don't go alone because you'll get hit on. But don't NOT go to tech parties, because that's where you'll meet investors and other potential contacts.
Being a woman in tech is like walking through a maze with minefields at every turn and never knowing which one you'll hit. I'm here because I love this industry and I couldn't imagine doing anything else. But I hate that my physical appearance and gender connotes so many (invalid and ridiculous) assumptions.
There seems to be a big horrible cycle here. I attended VMWorld last year in San Francisco and was shocked by how many booths were staffed by attractive women who where just hired as like, temps or something. They were aggressively friendly and seemed to have the single task of getting my contact information as a sales lead. Their knowledge of the products was generally no deeper than what was printed on the promotional fliers. I probably did tend to ignore women after a few interactions. So, I'm the kind of person you're complaining about, yet I don't like the situation either. Perhaps "booth babes" are part of a successful sales strategy and I'm an outlier. However, its possible that trade show sleaze is just a pattern propelled forward by inertia. Either way, we should speak out against it.
It did occur to me that a correcting mechanism for trade shows would be a gender balance in attendees. Maybe you're working different type of trade shows, but that was my recent experience.
Yeah, except when I do start a conversation with you, I'm hitting on you, and probably being "creepy".
I have to navigate a mental minefield of "don't say this" "don't say that too much" or "don't be overly aggressive", otherwise I get screamed about on twitter, labeled as a misogynist, and possibly fired from my job. (Uh-oh, I said dongle! Or...[1]meritocracy!)
I'm not saying women in tech don't have problems, they do, but I'm really sick of hearing this like it's a completely one-sided problem. The stupid evil men are holding the women down and keeping them from succeeding!
Gender dynamics are hard, for EVERYBODY. Men are having to deal with the fact that suddenly (or maybe not suddenly?) doing things like getting beer after conferences is bad, telling jokes to one another is bad, thinking certain thoughts is bad, using certain words[2] is bad.
I'm sorry if you come to a conference and I don't behave in the ultra-narrowly-defined way that you have determined makes me not part of the problem (although I recently found out that asking if I did it wrong makes me part of the problem).
I don't have a context for this! And it seems like everything I, and other men like me, try to do to make you feel included is WRONG, and we're BAD for doing it!
Invite you to beers after a conference? Hitting on you!
Compliment you on what you're wearing? Hitting on you! Objectifying you! Noticing that you are a partially-physical entity! THE HORROR!
Ask you about your projects? Flirting with you!
Make a suggestion about your project? Mansplaining at you!
Men have to navigate a constantly changing, and VERY hazardous minefield every time we talk to you. I'm really sorry (really, genuinely, that is not sarcasm) that sometimes we get it wrong, or sometimes we just forego trying at all and stay quite around you. A lot of it is really just because we don't want to mess it up and make you angry. Women have a LOT of power over men in these situations, and if we screw up even a tiny tiny bit, it can ruin our lives.
This is a good example of sexism. But also a hint of target marketing, a few things of note...
Since there are less women in tech, technical people assume they are boring most people with technical jargon including most women (probabilistically). I bet if you dropped some technical info early it would knock it out of that mode quickly. I know when a women knows or doesn't know about tech I do change how I talk but I do this with anyone that is technical/non-technical. The old Feynman tune it to your crowd when you educate/market type of steward.
Also since there are so few women in tech, men don't usually work with them during the day and aren't the most alpha, lots of them could be shy or even have difficulty with eye contact at all. If they are introverted even moreso like many programmers are. Many are also young and not married which leads to awkwardness at times with ladies.
I think there are lots of opportunities for really skilled women but these intricacies should be stated more often so people understand and correct their assumptions. People need examples like this to learn how subtle it can be because just hearing 'sexism' doesn't help educate, more women with more examples as it is eye opening and helps understanding of this problem.
My thought is that it's not because they mean to be rude. It's because they pattern match. I've noticed when folks see the same pattern over and over it's difficult to see outside it.
My friends wife is an F16 fighter pilot. I was surprised to find that out. Truth is I should not have been surprised, but it went against the patterns I'm used to seeing.
I've seen this happen as well. As a black male CEO of a VC-funded startup, I've also seen it happen to me in a slightly different way. I gotta hype up the nerdiness, the glasses, and casually name-drop my college degree just to help those around me not embarrass themselves by assuming "I'm not the guy writing the code". Unfortunately, I'm quite used to this though and rarely think to share this experience with anyone because this has been My Whole Life.
You have a kid, you look for a nanny to look after him. You put it on news-paper, there's a 45 year old dude who comes offering his services to look after your kid.
Now tell me that you're so awesome that you'll not think what you are thinking right now.
Exactly.
People use stereotypes to save time. Many stereotypes are wrong, because you'll get them from CNN or Fox. People don't get on the news for being normal.
When you're in a hurry, you don't want to change. You don't have that luxury because you want the result now. You're not in "experimenting, expanding comfort zone, increasing awareness" mode. You're in "Getting it done" mode with as few new parameters.
Usual is better than confusing.
Besides, some stereotypes are true so one can understand people behaviour.
Black people go to jail more, geeks don't do well with girls, etc.
And I know that some people will be butt-hurt and cry foul and it's 2014 and how it's a stone age thinking, but the stats are there.
(I don't have stats on the sex life of geeks, though).
Someone might be offended at first, but there's a reason for these stereotypes to have had such a long, established life: If they don't represent the truth, they at least reflect it in some distorted way.
The person coming to a booth has probably had a long life where, comparatively, he's met really fewer females in tech and come on, it's not like us humans are so pure that we'll go: Hmm, this is the first time I meet a female in tech. I'll speak to her in spite of being in a hurry, in spite of my question being complex, in spite of being used to talk with dudes all my life and this one comes out now.
When you're in a hurry, you don't want to change, you don't want surprises: Usual is better than confusing.
A lot of time, people won't deal with you simply because they don't like you. A lot of times, people won't deal with you simply because they don't know you.
People who'll talk to you and give you the benefit of the doubt are giving you the benefit of the doubt. Meaning it's a privilege they're granting you, so having an entiteled attitude about it goes against the meaning of the words.
Just a guess. May be they are trying not to appear to be hitting on you. Paraphrasing you ..."Being a man around women is like walking through a maze with minefields at every turn and never knowing which one you'll hit."
My skin color and gender both connote a number of invalid assumptions. This probably applies to most people at some point in their lives. It just doesn't bother me. I'm sorry if it bothers you and I sympathize with others who are annoyed. I just don't relate.
I'm inclined to agree with much of what you said, but I don't think sexism is always at fault here. If I were that person who struck up a conversation with your fiance, I know I would personally find it difficult to make the "first move" in initiating a conversation with you.
Is it because I'm sexist? No! I'm not a very extroverted or social person and I find it personally very difficult to make initial contact with anyone I don't already know. Given that I'm already talking to your fiance, we can infer that something or someone has broken the ice and hence we are engaged in a conversation.
If you were the person with whom the ice was broken with first, it would be your fiance who would be seemingly "snubbed" by me, unless introduced explicitly by yourself. Maybe non-extroverts, shy, or just socially awkward individuals need to wear a public service announcement or something to make this clear to everyone.
"Disclaimer: I'm not sexist; I'm just socially awkward. Please break the ice and say hello to me!"
I'd also like to add, for your consideration, that some people are better at one-on-ones than navigating the social jungle that is multi-person conversations. I have no idea how to engage multiple persons at once outside of the context of a formal or informal presentation of some sort. This could be that the topics of conversation that I usually engage in with others are not usually of the anecdotal variety, which I imagine are amenable to group conversation, where others can more easily "participate" passively.
Finally, I'd like to point out that I think your social party experiment as you framed it will always generate results that are biased toward your assumption. Just because a phenomena has been observed to exist (in this case the phenomena, according to your testimony, is "men in a technical environment are more inclined to strike up technical conversations with men to the exclusion of the women also present") does not actually tell us anything about -why- this is so.
You can come up with any number of anecdotally reasonable hypotheses, but until you actually test these hypotheses in a well defined and scientific manner with an experiment designed to eliminate all of the potential biases, your experiment is no better (rhetorically speaking) at proving anything than a sexist diatribe along the lines of "why my ex-{girlfriend or wife}'s {anecdotally negative conduct} proves women are {some universal claim about all women}".
I believe no matter if you are technical or not, you still can find certain correlation between person's sex and if he or she is technical or not. I understand that there are a lot of gals in tech, but it is less likely to happen to see couple where female party is technical and male - is not. It is just statistics. Just like it is more likely for gals to have longish hair and for guys - shorter one. It is just how current overall earth as large system evolved.
Just like everybody assumed I am boring when I was young and nerdish, same would happen to gals in tech. I bet that if instead of waiting for 13 minutes you would join conversation whoever approached you and your fiance would happily continue conversation with you two. Yes, his initial assumptions were incorrect, but they are based on current expectations. As soon as there will be close to 50/50 female/male ration in tech I bet these assumptions will disappear.
Don't try hard to find samples of sexism. Just join a conversation.
Erica, I don't know the particulars of your situation, but may I suggest that maybe you're reading too much into (some of) this?
I've seen the lack of eye contact problem happen many times, with a mix of genders/races/etc. Sometimes I'm the one being ignored (I'm male); sometimes I feel weird because the person talking is only looking at me and ignoring everyone else in the group. It feels random to me.
IMHO, it points more to a general lack of social skills than a sexist/racist thing. I try not to take it personally. And I try, in my own conversations, to always be very inclusive (e.g. eye contact with everyone, even if I'm answering one particular person's question) and encourage others to be inclusive as well (e.g. deliberately introducing people, asking questions, or simply giving others in the group eye contact even when I'm on the listening end). I think steps like these can go a long way.
I am a self-employed technical female as well but in my case I'm also a semi-recluse so my exposure to such things is greatly limited. Outside of being a developer I'm also known to occasionally fix my own cars and large appliances in lieu of taking them to be repaired.
In that context I have experienced similar issues but I chalk it up to people simply not being exposed enough to oddities like me. I am guilty of it too towards people I come across who break my mental image of how something "is."
For example, I live near Austin, Texas. I recently saw a really tall, very handsome black man wearing a cowboy hat and full-length duster. Certainly that's not the norm for me to see but not too incredibly odd either. That is until I heard him speak with the most refined British accent I'd ever heard in my life. I completely lost my composure and started viewing him if he were a novelty act. I have no doubt I was at least as much of an ass as the men you describe.
As other commenters have pondered, I wonder if these situations will actually start to decrease as the commonality of females in tech starts to increase.
I feel I have to apologize on behalf of all clueless men out there unfortunately we were brainwashed by the media that all women are non technical.
On the other hand i see nothing wrong with you being aggressive and it would be extremely hilarious if you were to go with your boyfriend to an event and just whisper in his ear what he needs to say every time he gets asked something technical he might not know.
I always enjoy playing on peoples assumptions and making them feel awkward for making them.
P.S. There's no gender neutral interactions so make the most of your gender's image and strengths.
If you want to be treated for who you are and not just a member of your gender you will have to show a strong personality and don't be afraid of being assertive or slightly aggressive sometimes. It gets you respect.
I'm not trying to be insulting here in any way, and I hope I come across correctly.
It's not your fault, and it's a horrible situation that many people would love to see changed. I love talking about technology, and it's unfortunate the culture is the way it is where it alienates part of the community for discussion.
However, with all such things -- while it is worthwhile to push for change -- they must be taken in stride and seen as obstacles to overcome.
Take what you think is a weakness in your situation: that you're underestimated, or maybe ignored, as your strength.
Lots of projection about why men are ignoring women. Maybe sometimes its nothing to do with assumptions about competence. Could be awkward unfamiliarity with what to do with a women in an admittedly male-filled industry.
I don't mean that you ought to shoulder the burden of conditioning all the males; or that its fair. Mostly the world isn't fair. But its the current state of affairs.
Find a field that has been woman-dominated for the last 50 years. Now put a man in that field, who is rather successful (like yourself in technology), and you will get the exact same result in the contexts you describe. I'm sick of this paradox where men and women are equal and yet men (and only men) are capable of making this mistake. It's simple pattern matching, and when the pattern tells you one thing and it's actually the other you're now a giant sexist pig. Now if a guy ignores you for more than a few seconds at one of these events then I agree, the guy needs to wake up, it's 2014.
Also complaining about getting hit on? Really? A person finds you attractive and wants to talk to you. What a monster.
"But I hate that my physical appearance and gender connotes so many (invalid and ridiculous) assumptions."
What is ridiculous about an assumption that is 95% correct in today's world? Perhaps it will be a ridiculous assumption in 5 years, and definitely 10, but it's not far-fetched to run into guys at these events who don't interact with women ever in their day-to-day work lives.
This pattern shows up in a great many industries. And not always in favor of engineers.
Almost always, the divide is right along the profit center/cost center line. In finance, traders are revered and engineers are their support staff. In the Air Force, pilots run the show all the way up the chain of command and engineers -- as critical to mission success as they may be -- are support. That's okay. Those jobs can be even more rewarding than working in "tech".
Remember, the same reason you might choose to work as an engineer in $awesome_field is why your ops/admin/qa team came to your company.
From the VBScript and complex spreadsheet wrangling required to perform analysis of key organizational metrics to mastery of numerous different specialized softwares and systems in order to perform basic functions of the job ranging from accounting to people operations, non-technical employees must have a bevy of technical skills at the ready every single day. In fact, I had to code a sample app using the company’s API to get my job as an operations manager — and I committed code to the frontend of the marketing site regularly. I’m not the exception.
That doesn't really sound like a non-technical employee to me. Maybe a question of terminology, or the primary focus of the person's role, but a person who is coding sample apps using the company's API sounds pretty damn technical.
That was my immediate thought, irregardless of the gender argument. I work with plenty of non-technical ops people, ALL of them REGARDLESS of intelligence, can not code out of a wet paper bag. I have at various points shown them all how to use basic excel formulas and they still use calculators that would not look out of place in a grade school.
Are they good at what they do? Yes.
Does what they do require that type of abstract thinking and computer skills? Not that I have seen, they seem effective at what they do, the lights are on, the place runs smoothly.
Maybe her argument is that she's less technical than the engineers (and therefore looked down upon unnecessarily, leading to this article), even if she has to be far more technical than the average person, just to get the job.
I'm the "non-technical" co-founder of my startup, and I used to program web server gateways in python. It just happens that our technical architecture that we're using isn't really my area of specalisation (it's my partner's) so I ended up doing most of the business dev, ops, sales/marketing instead of programming.
I think all this really depends on the where the startup is in timeframe. A larger company will have more specialised employees who do only one thing, but a smaller one would have a single employee doing multiple roles even if in both cases their titles were exactly the same.
A implies B does not necessarily mean that B implies A. She's just saying that it's possible for a person to have skills beyond those required for their role. The examples you quoted aren't listed as what should be expectations of her role, they're examples of how she often pulls in her not-in-the-job-req skills in the service of her official duties.
Taking aside the blatant sexism (kudos - we need more people raising this issue), there is a significant 'rolism' in the tech community. I have worked on the business/product side of tech for more than 10 years. What you say is inherently true of too many 'developers' and their views.
It harks back to a belief of "Build it and they will come" that pervades the industry (and yes, I do know the actual quote is "Build it, and HE will come"). There are many successful products that solve a problem or do something. If no-one ever knows about it or works out how to pay you for it, then the business will never be a success. You need all parts of a business (selling, marketing, ops, banking the cheques, making payroll, taking out the garbage) for it to work ... the naivety of some devs about the processes that go on to make that work and their lack of engagement in the wider business is a wake-up call many need to hear.
I agree with you to a point, devs would benefit with understanding "the other side of the house" and that sales, marketing, and administration are all important aspects of building a healthy business.
We have different roles to play in the success of an organization; at different times each role has different values, but as people we're all valuable.
Of course your side of the house is always out of the office by 5p =)
given how many "product driven" companies fail for lack of marketing or customers, you'd think they'd catch on. but apparently that kind of pattern matching doesn't work for them.
--You only take a job in business operations if you aren’t smart enough to be an engineer (or designer, or product manager, or…)
--If your role isn’t technical, you don’t actually understand the product.
I don't think many people actually say or believe this. Maybe these were common thoughts in 1999, but as an SF-based ops guy, I've never heard this.
In fact, I would argue that good business operators have it just as good, if not better, than most engineers right now. Startups like Uber, Postmates, Airbnb, Dropbox, etc. are killing it, and they all have really talented (and highly paid) people in sales, ops, marketing, support, etc.
I think most of us are aware that it takes more than engineers to build a company:
Very well written article. Operations people are driving a new wave of real world/tech hybrid companies and I think they need a lot more respect for their contributions.
One nit, you admonish (rightly) people for thinking just because you are a nontechy that you don't understand the product. But then you make a similar mistake by accusing the young nerdy male engineer who is devouring the beef jerky of not being street wise enough to be able to order lunch.
Simpler explanation: you've set up the expectation that he can eat on the company dime so he's going to take full advantage of that. He can order lunch just fine he just doesn't want to pay for it.
Give him the company credit card (or a company seamless account) and 'problem solved'. Except it's not really a problem since it's better for the company if you can have him working around the company catering times.
I was fortunate enough to work with the author at the startup she mentions. And I don't use the word "fortunate" lightly; she was absolutely a key player on the team. I'm happy to see that she had a positive experience with the rest of the (male) team!
Maintaining a good company culture™ was very important to me and the other founders and we were very aware of how much our early hires would contribute to it. An important part of that culture was only hiring the best and smartest people (yes, it's cliché, I know). It did not even cross our minds to hire an operations manager (or any other role) who could not understand and comfortably explain our product, for instance. I think that did a lot to set a tone that no one should have lower expectations set for them nor was somehow in a "second-class" role.
TL:DR - You pure development guys are more likely to have success if you realise you have a need for people with other complimentary skills, and you need to have respect for them, their intelligence and their role.
I've seen this so many times its tragic, and it comes down to largely one thing IMHO... the arrogance of extremely intelligent people with specialties in maths/physics or other numeracy focused backgrounds over other people.
How about an office move where developers sat around and bitched because network cables hadn't been moved across yet? Young office admin girl shows initiative and drives to old office and gets all the network cables. They now see her as their runner as they know that she's paid less so therefore its optimal.
Its crunch time and a ScrumMaster who goes and gets coffee for the team before a release so they stick to working is then perpetually told "We're busy, coffee needed", and is slowly reduced to Team Mom, or worse Janitor.
A startup's CTO and part shareholder overrules the Head of Marketing and lead designers on their design choice because he's read an article saying how Arial is optimal for reading, and then gets involved in every decision. Only once the CTO is moved on does the sales and marketing team really start performing and the company is saved.
I've seen numerous friends who are extremely technically capable Java developers create excellent technical solutions in the finance space to problems that people won't pay for, or don't need solving, or that they don't know how to market or keep running 24/7. They see MBA's as a waste despite their MBA friend saying "Look at the market segmentation, and consider your positioning to see if you can compete" - A valid point that could have answered the question before the £80K in lost wages.
I've had conversations where I've quoted a previous stand-in lecturer who was worth £110m from 3 different startups who told of the importance of a well rounded team including sales, finance etc. to young developers who think that DHH is basically a prophet, they only need tech guys and if you build it they will come, and their answers to me were words to the effect of "I disagree because HN said so".
I'd rather put £1000 of investment money in the hands of a proven sales guy's startup than a proven back-end developer, as I've seen first hand that a great sales guy can sell crap and make money.
I guess I've mainly worked in environments where it's "operations manager" and an entire ops team, and where they handle things related to revenue or technology (logistics, travel, facilities, equipment, security, etc.), but I've never really seen the operations role as female. Probably less female than any other department with the possible exception of some parts of engineering.
(In my experience, HR is the vastly-female role, and always-useless to employee; sometimes useful to companies for compliance reasons, but rarely. HR's worthlessness has nothing to do with female employees; in dev and product roles where some companies have 20-30% females, they're generally in the upper half of contributors, and in design, which is often somewhat majority female, they're often the key to a company's success. Actual receptionists are also usually female, but rarely do I see those in <100 person tech companies, unless provided by the building management.)
Generally I've just seen founders handle most of these things (taking out trash, ordering lunch, etc.) at the early stage, and then contract it out entirely (use a meal delivery service, office cleaners, etc.) This might be specific to silicon valley tech startups; the other environment I know about, USG/DOD/DOE, has 10x as many people for any role in general, and a clear hierarchy for who does what, but it's based on overt rank or grade, and not gender, age, whatever.
QA, design and management is where I've noticed a greater proportion of women outside of HR. What is it about those roles which makes them amenable to women but not tech?
Technical people are hard to find, whereas I can get about 100 non-technical ops resumes in 5 minutes from liberal arts majors at top ten schools, who will kick ass at ops.
There are a lot of smart people you can groom into good ops people. There are also a lot of seasoned ops people looking for jobs, if you look outside silicon valley and bring someone here from a business in another city.
Whereas, we can't for the fucking life of us get good mobile developers, programmers with machine learning experience, or robotics experience ... unless we pay large sums and offer great perks.
That's why nobody talks much about, or pays much attention to Ops.
This related post "Tech companies, stop hiring women to be the Office Mom" describes "empathy work" and how it has almost always been significantly underpaid.
I like the reference to the fact that for a large part of history, many women worked completely without pay doing empathy & ops work full time (mothering families and running ops for households and community groups). As a culture maybe we have some residual beliefs about this type of work (and women's time) being basically free/cheap.
> I was repeatedly asked if an engineer was around to explain the product before I had a chance to say more than hello.
> let's focus on the other assumption: that because a person has a non-technical role, she is fundamentally incapable of assessing whether she is able to answer your question.
> While we’re at it, I’d like to dispel the notion that people in non-technical roles don’t have technical skills. From the VBScript and complex spreadsheet wrangling required to perform analysis of key organizational metrics to mastery of numerous different specialized softwares and systems in order to perform basic functions of the job ranging from accounting to people operations, non-technical employees must have a bevy of technical skills at the ready every single day.
It's difficult to recognize what you don't know. As an engineer, I feel like I didn't understand jack a year ago. A year from now, I'll feel the same way about my current level of understanding & skill. Between now and then, I'll speak with confidence about topics I think I understand but probably don't fully grok.
Earlier in my career, I was "semi-technical" with more [technical] experience than the OP. Looking back, I really didn't understand the product to the extent I thought I did.
"Yet the myths we hold so dear — the noble engineer, sleeping under his desk to get the product out on time; the company that cares for its employees’ every need — exclude and marginalize an entire class of people whose contributions to these startups make their success possible."
I'm not sure I can empathize with this. People within the company should be grateful for the work being done by office managers, but why would anyone outside the company be particularly concerned about it? Some work is glamorous. Some isn't. That's life.
The problems described here aren't just limited to startups: Support personnel is often neglected in large companies too. A couple of years ago, I was working at a very large company that was also suffering from high turnover. Calls were made first by business analysts, who really didn't understand what the heck was going on, and implemented in some fashion or another by developers like me, who were far removed from the realities of the software. With all that turnover, nobody that was actually working on the software understood what the real use cases were, so if a decision actually matched what a user wanted, it was probably by accident.
Having worked at better shops, I realized this was only going to lead to dismal failure, so I started asking around for real information on what was going on. And guess what: There was a support team, 90% female, who nobody actually consulted for anything, and was paid peanuts. And yet, they actually had more information about the practical uses of the application, and where to take it, than the PhD totting analysts. After a few weeks talking to said support team, and explaining how to actually make sense of what we were doing, I was seen as some kind of Messiah by management, when all I actually did was actually pay attention to the people that had the actual knowledge.
As far as sexism, yes, it's very sad that most of us view so few females that are even put in a position to succeed that it's easy to make assumptions about people's knowledge. I've been lucky to have worked with a couple of extremely good female programmers, and about a dozen women doing support work, so that I am at least not astounded when a woman at a user group isn't just a recruiter. But that doesn't mean I won't make wrong assumptions. The best most of us can do is recover quickly, and remember that while there are few women in the industry, their skill and knowledge is no different than the one of men.
I think the author has mistaken what her role in the company is. If you want to answer technical questions than become a tech employee. The same way you don't want a random tech employee trying to handle the complicated operations pieces, you should let the tech employee's answer the tech questions.
I co-founded an engineering startup that works on high-heat machinery. I have degrees in mathematics and information analysis, I fully understand the technical aspect as I contributed to a lot of the work, yet I refuse to answer tech questions. I serve in an operations role right now and don't spend my entire day developing the technology; thus I am not the best qualified to answer any tech questions.
You are right that tech companies can only afford to hire the smartest, but that doesn't mean you have to be a jack-of-all-trades - that applies to co-founders. Do the job you were hired to do and do it better then any one else can.
I don't know how people put up with this kinda stuff, I hear a C-suite say something heteronormative and I'm already pretty much on my way out the door.
Then I'm going to ask the programmer/engineer to flip the model around and ask that they look at Operations in the same way they wish management see them.
Understanding your company's product, marketing, financials, hiring, and business strategy makes you an _incredibly_ valuable employee (though perhaps difficult to describe with a job title).
An employee like that shouldn't be spending much time ordering food and cleaning. Those things can be outsourced to people who can do them at scale for many companies at once, at a much lower rate.
At my startup we've used ZeroCater (Food for events),
HomeJoy (Cleaning),
TaskRabbit (Odd tasks),
Zirtual (Scheduling meetings, booking flights), and
Advsor (Accounting & Billing).
We also have a full time remote assistant that does things like coordinating team outings, ordering new tshirts, researching stuff, spreadsheet jocky-ing, etc, etc. They would also order food for us if we didn't have it provided at our co-working space.
I hope this comment was helpful and not condescending. I do some business ops work myself in addition to writing code and consulting. As the longtime only-female, I too had to deal with the assumptions about my role (outside the company, not inside).
All of these tasks are important and need to happen for a company to run successfully, but they don't all need to be done by an "Office Manager" just because that's how it works at some startups.
People are resistant to change. But change is in the air - self awareness of this issue is growing. The people who are aware, men and women, will rise in rank and create new cultures / new companies with friendlier atmospheres.
It's only a matter of time until the tech industry is a much more women-friendly place. And frankly I can't wait - there's a lot of pain in the world, and we need the brightest minds on them.
[+] [-] ericabiz|12 years ago|reply
I love the tech industry. I've been in it professionally since 1997, and I've run tech startups as a CEO for the past 13 years. And if there's one thing I can count on, it's the consistent, pervasive assumption that I'm not technical.
I hate going to tech events with my fiance (or for that matter, any man), because people will come up to us, acknowledge me, and then ask him brightly: "So why are you here?"
I once thought it would be funny to time it and see how long another person could go talking to only him and not making eye contact with me, even when he mentioned that he was at the event because of me. Current record? 13 minutes. 13 minutes of not looking at me, saying a word, or acknowledging that I was there.
Every male that I've ever told this story to can't believe it until they go to parties and see it in action. It's so consistent, yet it's unbelievable until you see it.
This is what it's like to be a woman in tech, even when you're a technical one. It's assumed that you're non-technical. But don't take that into account and lead with your credentials--whoops, no, that's "aggressive" and you shouldn't do that. Don't go to tech parties with a guy because you're assumed to be "the girlfriend." Don't go alone because you'll get hit on. But don't NOT go to tech parties, because that's where you'll meet investors and other potential contacts.
Being a woman in tech is like walking through a maze with minefields at every turn and never knowing which one you'll hit. I'm here because I love this industry and I couldn't imagine doing anything else. But I hate that my physical appearance and gender connotes so many (invalid and ridiculous) assumptions.
[+] [-] galago|12 years ago|reply
It did occur to me that a correcting mechanism for trade shows would be a gender balance in attendees. Maybe you're working different type of trade shows, but that was my recent experience.
[+] [-] your_throwaway|12 years ago|reply
I have to navigate a mental minefield of "don't say this" "don't say that too much" or "don't be overly aggressive", otherwise I get screamed about on twitter, labeled as a misogynist, and possibly fired from my job. (Uh-oh, I said dongle! Or...[1]meritocracy!)
I'm not saying women in tech don't have problems, they do, but I'm really sick of hearing this like it's a completely one-sided problem. The stupid evil men are holding the women down and keeping them from succeeding!
Gender dynamics are hard, for EVERYBODY. Men are having to deal with the fact that suddenly (or maybe not suddenly?) doing things like getting beer after conferences is bad, telling jokes to one another is bad, thinking certain thoughts is bad, using certain words[2] is bad.
I'm sorry if you come to a conference and I don't behave in the ultra-narrowly-defined way that you have determined makes me not part of the problem (although I recently found out that asking if I did it wrong makes me part of the problem).
I don't have a context for this! And it seems like everything I, and other men like me, try to do to make you feel included is WRONG, and we're BAD for doing it!
Invite you to beers after a conference? Hitting on you!
Compliment you on what you're wearing? Hitting on you! Objectifying you! Noticing that you are a partially-physical entity! THE HORROR!
Ask you about your projects? Flirting with you!
Make a suggestion about your project? Mansplaining at you!
Men have to navigate a constantly changing, and VERY hazardous minefield every time we talk to you. I'm really sorry (really, genuinely, that is not sarcasm) that sometimes we get it wrong, or sometimes we just forego trying at all and stay quite around you. A lot of it is really just because we don't want to mess it up and make you angry. Women have a LOT of power over men in these situations, and if we screw up even a tiny tiny bit, it can ruin our lives.
[1]:http://readwrite.com/2014/01/24/github-meritocracy-rug#awesm...
[2]:http://banbossy.com
[+] [-] drawkbox|12 years ago|reply
Since there are less women in tech, technical people assume they are boring most people with technical jargon including most women (probabilistically). I bet if you dropped some technical info early it would knock it out of that mode quickly. I know when a women knows or doesn't know about tech I do change how I talk but I do this with anyone that is technical/non-technical. The old Feynman tune it to your crowd when you educate/market type of steward.
Also since there are so few women in tech, men don't usually work with them during the day and aren't the most alpha, lots of them could be shy or even have difficulty with eye contact at all. If they are introverted even moreso like many programmers are. Many are also young and not married which leads to awkwardness at times with ladies.
I think there are lots of opportunities for really skilled women but these intricacies should be stated more often so people understand and correct their assumptions. People need examples like this to learn how subtle it can be because just hearing 'sexism' doesn't help educate, more women with more examples as it is eye opening and helps understanding of this problem.
[+] [-] jv22222|12 years ago|reply
My friends wife is an F16 fighter pilot. I was surprised to find that out. Truth is I should not have been surprised, but it went against the patterns I'm used to seeing.
I wonder if that's at play here?
[+] [-] jtfrench|12 years ago|reply
[+] [-] Jugurtha|12 years ago|reply
Now tell me that you're so awesome that you'll not think what you are thinking right now.
Exactly.
People use stereotypes to save time. Many stereotypes are wrong, because you'll get them from CNN or Fox. People don't get on the news for being normal.
When you're in a hurry, you don't want to change. You don't have that luxury because you want the result now. You're not in "experimenting, expanding comfort zone, increasing awareness" mode. You're in "Getting it done" mode with as few new parameters.
Usual is better than confusing.
Besides, some stereotypes are true so one can understand people behaviour.
Black people go to jail more, geeks don't do well with girls, etc.
And I know that some people will be butt-hurt and cry foul and it's 2014 and how it's a stone age thinking, but the stats are there.
http://www.naacp.org/pages/criminal-justice-fact-sheet
(I don't have stats on the sex life of geeks, though).
Someone might be offended at first, but there's a reason for these stereotypes to have had such a long, established life: If they don't represent the truth, they at least reflect it in some distorted way.
The person coming to a booth has probably had a long life where, comparatively, he's met really fewer females in tech and come on, it's not like us humans are so pure that we'll go: Hmm, this is the first time I meet a female in tech. I'll speak to her in spite of being in a hurry, in spite of my question being complex, in spite of being used to talk with dudes all my life and this one comes out now.
When you're in a hurry, you don't want to change, you don't want surprises: Usual is better than confusing.
A lot of time, people won't deal with you simply because they don't like you. A lot of times, people won't deal with you simply because they don't know you.
People who'll talk to you and give you the benefit of the doubt are giving you the benefit of the doubt. Meaning it's a privilege they're granting you, so having an entiteled attitude about it goes against the meaning of the words.
[+] [-] huherto|12 years ago|reply
[+] [-] AgathaTheWitch|12 years ago|reply
[+] [-] adrianm|12 years ago|reply
Is it because I'm sexist? No! I'm not a very extroverted or social person and I find it personally very difficult to make initial contact with anyone I don't already know. Given that I'm already talking to your fiance, we can infer that something or someone has broken the ice and hence we are engaged in a conversation.
If you were the person with whom the ice was broken with first, it would be your fiance who would be seemingly "snubbed" by me, unless introduced explicitly by yourself. Maybe non-extroverts, shy, or just socially awkward individuals need to wear a public service announcement or something to make this clear to everyone.
"Disclaimer: I'm not sexist; I'm just socially awkward. Please break the ice and say hello to me!"
I'd also like to add, for your consideration, that some people are better at one-on-ones than navigating the social jungle that is multi-person conversations. I have no idea how to engage multiple persons at once outside of the context of a formal or informal presentation of some sort. This could be that the topics of conversation that I usually engage in with others are not usually of the anecdotal variety, which I imagine are amenable to group conversation, where others can more easily "participate" passively.
Finally, I'd like to point out that I think your social party experiment as you framed it will always generate results that are biased toward your assumption. Just because a phenomena has been observed to exist (in this case the phenomena, according to your testimony, is "men in a technical environment are more inclined to strike up technical conversations with men to the exclusion of the women also present") does not actually tell us anything about -why- this is so.
You can come up with any number of anecdotally reasonable hypotheses, but until you actually test these hypotheses in a well defined and scientific manner with an experiment designed to eliminate all of the potential biases, your experiment is no better (rhetorically speaking) at proving anything than a sexist diatribe along the lines of "why my ex-{girlfriend or wife}'s {anecdotally negative conduct} proves women are {some universal claim about all women}".
[+] [-] hippich|12 years ago|reply
Just like everybody assumed I am boring when I was young and nerdish, same would happen to gals in tech. I bet that if instead of waiting for 13 minutes you would join conversation whoever approached you and your fiance would happily continue conversation with you two. Yes, his initial assumptions were incorrect, but they are based on current expectations. As soon as there will be close to 50/50 female/male ration in tech I bet these assumptions will disappear.
Don't try hard to find samples of sexism. Just join a conversation.
[+] [-] ipince|12 years ago|reply
I've seen the lack of eye contact problem happen many times, with a mix of genders/races/etc. Sometimes I'm the one being ignored (I'm male); sometimes I feel weird because the person talking is only looking at me and ignoring everyone else in the group. It feels random to me.
IMHO, it points more to a general lack of social skills than a sexist/racist thing. I try not to take it personally. And I try, in my own conversations, to always be very inclusive (e.g. eye contact with everyone, even if I'm answering one particular person's question) and encourage others to be inclusive as well (e.g. deliberately introducing people, asking questions, or simply giving others in the group eye contact even when I'm on the listening end). I think steps like these can go a long way.
[+] [-] NicheDiver|12 years ago|reply
In that context I have experienced similar issues but I chalk it up to people simply not being exposed enough to oddities like me. I am guilty of it too towards people I come across who break my mental image of how something "is."
For example, I live near Austin, Texas. I recently saw a really tall, very handsome black man wearing a cowboy hat and full-length duster. Certainly that's not the norm for me to see but not too incredibly odd either. That is until I heard him speak with the most refined British accent I'd ever heard in my life. I completely lost my composure and started viewing him if he were a novelty act. I have no doubt I was at least as much of an ass as the men you describe.
As other commenters have pondered, I wonder if these situations will actually start to decrease as the commonality of females in tech starts to increase.
[+] [-] Fuxy|12 years ago|reply
On the other hand i see nothing wrong with you being aggressive and it would be extremely hilarious if you were to go with your boyfriend to an event and just whisper in his ear what he needs to say every time he gets asked something technical he might not know.
I always enjoy playing on peoples assumptions and making them feel awkward for making them.
P.S. There's no gender neutral interactions so make the most of your gender's image and strengths.
If you want to be treated for who you are and not just a member of your gender you will have to show a strong personality and don't be afraid of being assertive or slightly aggressive sometimes. It gets you respect.
[+] [-] odonnellryan|12 years ago|reply
It's not your fault, and it's a horrible situation that many people would love to see changed. I love talking about technology, and it's unfortunate the culture is the way it is where it alienates part of the community for discussion.
However, with all such things -- while it is worthwhile to push for change -- they must be taken in stride and seen as obstacles to overcome.
Take what you think is a weakness in your situation: that you're underestimated, or maybe ignored, as your strength.
[+] [-] unknown|12 years ago|reply
[deleted]
[+] [-] JoeAltmaier|12 years ago|reply
I don't mean that you ought to shoulder the burden of conditioning all the males; or that its fair. Mostly the world isn't fair. But its the current state of affairs.
[+] [-] mathattack|12 years ago|reply
[+] [-] rodly|12 years ago|reply
Also complaining about getting hit on? Really? A person finds you attractive and wants to talk to you. What a monster.
"But I hate that my physical appearance and gender connotes so many (invalid and ridiculous) assumptions."
What is ridiculous about an assumption that is 95% correct in today's world? Perhaps it will be a ridiculous assumption in 5 years, and definitely 10, but it's not far-fetched to run into guys at these events who don't interact with women ever in their day-to-day work lives.
[+] [-] Pherdnut|12 years ago|reply
[+] [-] citadelgrad|12 years ago|reply
[+] [-] unknown|12 years ago|reply
[deleted]
[+] [-] hmason|12 years ago|reply
[+] [-] johnhess|12 years ago|reply
Almost always, the divide is right along the profit center/cost center line. In finance, traders are revered and engineers are their support staff. In the Air Force, pilots run the show all the way up the chain of command and engineers -- as critical to mission success as they may be -- are support. That's okay. Those jobs can be even more rewarding than working in "tech".
Remember, the same reason you might choose to work as an engineer in $awesome_field is why your ops/admin/qa team came to your company.
[+] [-] lxt|12 years ago|reply
[+] [-] theorique|12 years ago|reply
That doesn't really sound like a non-technical employee to me. Maybe a question of terminology, or the primary focus of the person's role, but a person who is coding sample apps using the company's API sounds pretty damn technical.
[+] [-] hobs|12 years ago|reply
Are they good at what they do? Yes. Does what they do require that type of abstract thinking and computer skills? Not that I have seen, they seem effective at what they do, the lights are on, the place runs smoothly.
[+] [-] stephenaturner|12 years ago|reply
[+] [-] rachellaw|12 years ago|reply
I think all this really depends on the where the startup is in timeframe. A larger company will have more specialised employees who do only one thing, but a smaller one would have a single employee doing multiple roles even if in both cases their titles were exactly the same.
[+] [-] benjamincburns|12 years ago|reply
That one.
A implies B does not necessarily mean that B implies A. She's just saying that it's possible for a person to have skills beyond those required for their role. The examples you quoted aren't listed as what should be expectations of her role, they're examples of how she often pulls in her not-in-the-job-req skills in the service of her official duties.
[+] [-] asharpe|12 years ago|reply
It harks back to a belief of "Build it and they will come" that pervades the industry (and yes, I do know the actual quote is "Build it, and HE will come"). There are many successful products that solve a problem or do something. If no-one ever knows about it or works out how to pay you for it, then the business will never be a success. You need all parts of a business (selling, marketing, ops, banking the cheques, making payroll, taking out the garbage) for it to work ... the naivety of some devs about the processes that go on to make that work and their lack of engagement in the wider business is a wake-up call many need to hear.
[+] [-] balls187|12 years ago|reply
We have different roles to play in the success of an organization; at different times each role has different values, but as people we're all valuable.
Of course your side of the house is always out of the office by 5p =)
[+] [-] melindajb|12 years ago|reply
[+] [-] gatsby|12 years ago|reply
--You only take a job in business operations if you aren’t smart enough to be an engineer (or designer, or product manager, or…)
--If your role isn’t technical, you don’t actually understand the product.
I don't think many people actually say or believe this. Maybe these were common thoughts in 1999, but as an SF-based ops guy, I've never heard this.
In fact, I would argue that good business operators have it just as good, if not better, than most engineers right now. Startups like Uber, Postmates, Airbnb, Dropbox, etc. are killing it, and they all have really talented (and highly paid) people in sales, ops, marketing, support, etc.
I think most of us are aware that it takes more than engineers to build a company:
http://blog.42floors.com/year-operations-startups/
http://www.cdixon.org/2014/03/15/full-stack-startups/
http://justinkan.com/exec-errands-post-mortem
[+] [-] jacquesc|12 years ago|reply
One nit, you admonish (rightly) people for thinking just because you are a nontechy that you don't understand the product. But then you make a similar mistake by accusing the young nerdy male engineer who is devouring the beef jerky of not being street wise enough to be able to order lunch.
Simpler explanation: you've set up the expectation that he can eat on the company dime so he's going to take full advantage of that. He can order lunch just fine he just doesn't want to pay for it.
Give him the company credit card (or a company seamless account) and 'problem solved'. Except it's not really a problem since it's better for the company if you can have him working around the company catering times.
[+] [-] mattlong|12 years ago|reply
Maintaining a good company culture™ was very important to me and the other founders and we were very aware of how much our early hires would contribute to it. An important part of that culture was only hiring the best and smartest people (yes, it's cliché, I know). It did not even cross our minds to hire an operations manager (or any other role) who could not understand and comfortably explain our product, for instance. I think that did a lot to set a tone that no one should have lower expectations set for them nor was somehow in a "second-class" role.
P.S. In my defense, it was darn good beef jerky.
EDIT: English is hard.
[+] [-] richliss|12 years ago|reply
I've seen this so many times its tragic, and it comes down to largely one thing IMHO... the arrogance of extremely intelligent people with specialties in maths/physics or other numeracy focused backgrounds over other people.
How about an office move where developers sat around and bitched because network cables hadn't been moved across yet? Young office admin girl shows initiative and drives to old office and gets all the network cables. They now see her as their runner as they know that she's paid less so therefore its optimal.
Its crunch time and a ScrumMaster who goes and gets coffee for the team before a release so they stick to working is then perpetually told "We're busy, coffee needed", and is slowly reduced to Team Mom, or worse Janitor.
A startup's CTO and part shareholder overrules the Head of Marketing and lead designers on their design choice because he's read an article saying how Arial is optimal for reading, and then gets involved in every decision. Only once the CTO is moved on does the sales and marketing team really start performing and the company is saved.
I've seen numerous friends who are extremely technically capable Java developers create excellent technical solutions in the finance space to problems that people won't pay for, or don't need solving, or that they don't know how to market or keep running 24/7. They see MBA's as a waste despite their MBA friend saying "Look at the market segmentation, and consider your positioning to see if you can compete" - A valid point that could have answered the question before the £80K in lost wages.
I've had conversations where I've quoted a previous stand-in lecturer who was worth £110m from 3 different startups who told of the importance of a well rounded team including sales, finance etc. to young developers who think that DHH is basically a prophet, they only need tech guys and if you build it they will come, and their answers to me were words to the effect of "I disagree because HN said so".
I'd rather put £1000 of investment money in the hands of a proven sales guy's startup than a proven back-end developer, as I've seen first hand that a great sales guy can sell crap and make money.
[+] [-] rdl|12 years ago|reply
(In my experience, HR is the vastly-female role, and always-useless to employee; sometimes useful to companies for compliance reasons, but rarely. HR's worthlessness has nothing to do with female employees; in dev and product roles where some companies have 20-30% females, they're generally in the upper half of contributors, and in design, which is often somewhat majority female, they're often the key to a company's success. Actual receptionists are also usually female, but rarely do I see those in <100 person tech companies, unless provided by the building management.)
Generally I've just seen founders handle most of these things (taking out trash, ordering lunch, etc.) at the early stage, and then contract it out entirely (use a meal delivery service, office cleaners, etc.) This might be specific to silicon valley tech startups; the other environment I know about, USG/DOD/DOE, has 10x as many people for any role in general, and a clear hierarchy for who does what, but it's based on overt rank or grade, and not gender, age, whatever.
[+] [-] test1235|12 years ago|reply
[+] [-] TheMagicHorsey|12 years ago|reply
There are a lot of smart people you can groom into good ops people. There are also a lot of seasoned ops people looking for jobs, if you look outside silicon valley and bring someone here from a business in another city.
Whereas, we can't for the fucking life of us get good mobile developers, programmers with machine learning experience, or robotics experience ... unless we pay large sums and offer great perks.
That's why nobody talks much about, or pays much attention to Ops.
I've been an Ops guy.
[+] [-] mwetzler|12 years ago|reply
http://qz.com/47154/tech-companies-stop-hiring-women-to-be-t...
I like the reference to the fact that for a large part of history, many women worked completely without pay doing empathy & ops work full time (mothering families and running ops for households and community groups). As a culture maybe we have some residual beliefs about this type of work (and women's time) being basically free/cheap.
[+] [-] doktrin|12 years ago|reply
> let's focus on the other assumption: that because a person has a non-technical role, she is fundamentally incapable of assessing whether she is able to answer your question.
> While we’re at it, I’d like to dispel the notion that people in non-technical roles don’t have technical skills. From the VBScript and complex spreadsheet wrangling required to perform analysis of key organizational metrics to mastery of numerous different specialized softwares and systems in order to perform basic functions of the job ranging from accounting to people operations, non-technical employees must have a bevy of technical skills at the ready every single day.
It's difficult to recognize what you don't know. As an engineer, I feel like I didn't understand jack a year ago. A year from now, I'll feel the same way about my current level of understanding & skill. Between now and then, I'll speak with confidence about topics I think I understand but probably don't fully grok.
Earlier in my career, I was "semi-technical" with more [technical] experience than the OP. Looking back, I really didn't understand the product to the extent I thought I did.
A little knowledge can be dangerous. YMMV.
edit : if you down voted, care to explain?
[+] [-] natrius|12 years ago|reply
I'm not sure I can empathize with this. People within the company should be grateful for the work being done by office managers, but why would anyone outside the company be particularly concerned about it? Some work is glamorous. Some isn't. That's life.
[+] [-] hibikir|12 years ago|reply
Having worked at better shops, I realized this was only going to lead to dismal failure, so I started asking around for real information on what was going on. And guess what: There was a support team, 90% female, who nobody actually consulted for anything, and was paid peanuts. And yet, they actually had more information about the practical uses of the application, and where to take it, than the PhD totting analysts. After a few weeks talking to said support team, and explaining how to actually make sense of what we were doing, I was seen as some kind of Messiah by management, when all I actually did was actually pay attention to the people that had the actual knowledge.
As far as sexism, yes, it's very sad that most of us view so few females that are even put in a position to succeed that it's easy to make assumptions about people's knowledge. I've been lucky to have worked with a couple of extremely good female programmers, and about a dozen women doing support work, so that I am at least not astounded when a woman at a user group isn't just a recruiter. But that doesn't mean I won't make wrong assumptions. The best most of us can do is recover quickly, and remember that while there are few women in the industry, their skill and knowledge is no different than the one of men.
[+] [-] jonwachob91|12 years ago|reply
I co-founded an engineering startup that works on high-heat machinery. I have degrees in mathematics and information analysis, I fully understand the technical aspect as I contributed to a lot of the work, yet I refuse to answer tech questions. I serve in an operations role right now and don't spend my entire day developing the technology; thus I am not the best qualified to answer any tech questions.
You are right that tech companies can only afford to hire the smartest, but that doesn't mean you have to be a jack-of-all-trades - that applies to co-founders. Do the job you were hired to do and do it better then any one else can.
[+] [-] fleitz|12 years ago|reply
[+] [-] chris_mahan|12 years ago|reply
http://programmer.97things.oreilly.com/wiki/index.php/Don%27...
Then I'm going to ask the programmer/engineer to flip the model around and ask that they look at Operations in the same way they wish management see them.
[+] [-] mwetzler|12 years ago|reply
An employee like that shouldn't be spending much time ordering food and cleaning. Those things can be outsourced to people who can do them at scale for many companies at once, at a much lower rate.
At my startup we've used ZeroCater (Food for events), HomeJoy (Cleaning), TaskRabbit (Odd tasks), Zirtual (Scheduling meetings, booking flights), and Advsor (Accounting & Billing).
We also have a full time remote assistant that does things like coordinating team outings, ordering new tshirts, researching stuff, spreadsheet jocky-ing, etc, etc. They would also order food for us if we didn't have it provided at our co-working space.
I hope this comment was helpful and not condescending. I do some business ops work myself in addition to writing code and consulting. As the longtime only-female, I too had to deal with the assumptions about my role (outside the company, not inside).
All of these tasks are important and need to happen for a company to run successfully, but they don't all need to be done by an "Office Manager" just because that's how it works at some startups.
[+] [-] xivzgrev|12 years ago|reply
It's only a matter of time until the tech industry is a much more women-friendly place. And frankly I can't wait - there's a lot of pain in the world, and we need the brightest minds on them.
[+] [-] jmduke|12 years ago|reply
http://alexisohanian.com/on-being-a-proud-non-technical-foun...