by sachitgupta on 3/17/14, 10:37 PM with 243 comments
by ericabiz on 3/17/14, 11:50 PM
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.
by johnhess on 3/17/14, 11:45 PM
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.
by theorique on 3/17/14, 11:23 PM
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.
by asharpe on 3/18/14, 12:10 AM
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.
by gatsby on 3/18/14, 12:03 AM
--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/
by jacquesc on 3/18/14, 1:33 AM
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.
by mattlong on 3/18/14, 4:08 AM
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.
by richliss on 3/18/14, 10:13 AM
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.
by rdl on 3/17/14, 11:31 PM
(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.
by TheMagicHorsey on 3/18/14, 4:24 AM
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.
by mwetzler on 3/18/14, 12:53 AM
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.
by doktrin on 3/18/14, 1:36 AM
> 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?
by natrius on 3/17/14, 11:13 PM
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.
by hibikir on 3/18/14, 12:24 AM
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.
by jonwachob91 on 3/18/14, 1:17 PM
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.
by fleitz on 3/17/14, 11:05 PM
by chris_mahan on 3/18/14, 1:54 AM
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.
by mwetzler on 3/18/14, 1:40 AM
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.
by xivzgrev on 3/18/14, 12:07 AM
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.
by jmduke on 3/18/14, 12:00 AM
http://alexisohanian.com/on-being-a-proud-non-technical-foun...
by distracteddev90 on 3/17/14, 11:08 PM
by antonapa on 3/18/14, 2:02 PM
by mw67 on 3/17/14, 11:58 PM
If your role isn’t technical, you don’t actually understand the product.
We should remember that some great founders like Steve Jobs were also not writing any code and still added lots of value. IMHO understanding the product mostly mean understanding how users interact with it, not understanding how to code it.
by rainmaking on 3/18/14, 8:45 AM
by dleskov on 3/19/14, 2:17 AM
As far a job titles go, I read an article a day ago where the author suggested that when it comes to salary negotiation and you are not quite happy with the monetary part of the offer, you should at least demand a title that would show progress when put on your resume.
by hifier on 3/18/14, 12:38 PM
by ameister14 on 3/17/14, 11:36 PM
I'm sorry that they haven't captivated people the way a rogue engineer can, but an ops or HR person isn't likely to start a company from a dorm room, garage or basement that makes its way to a multi billion dollar IPO.
As to the office mom thing; I haven't encountered that much, maybe it varies from office to office. I don't doubt it exists, I've just never seen it personally. Anyone know if that's a really common thing?
by anauleau on 3/18/14, 3:06 AM
by h1karu on 3/17/14, 11:49 PM
by spiralpolitik on 3/17/14, 11:56 PM
Ask yourself this question. Do you really want to be the one that has to call the building manager every time the toilet gets blocked ?
by mooreds on 3/18/14, 4:15 AM
Even though it is everybody putting their shoulder to the grindstone every day that really moves the company forward.
by cyphunk on 3/18/14, 1:32 AM
by stbarnes on 3/18/14, 2:43 AM
The article claims that this is false. But in fact, it's pretty obvious that the average non-engineer is less intelligent than the average engineer. See for instance this table of IQ by college major: http://www.statisticbrain.com/iq-estimates-by-intended-colle...
(And, yes, IQ tests do quite accurately capture what is meant by "intelligence".)