[Welcome to I Want Her Job's second Women at Microsoft Week! We're celebrating the female force behind the company as we join the Grace Hopper Celebration of Women in Computing Conference, happening now in Phoenix. If you're going to be there be sure to tweet us @iwantherjob. Today's article is the latest in a series of four that will help you find out what it's like—and how you can—land your dream job at one of the biggest companies changing the face of business.]
Dona Sarkar grew up in downtown Detroit and attended a middle school that she says is now, “a crack den hole in the ground. It doesn’t exist anymore.” But Dona didn’t know of her surroundings at the time. All she knew was that she loved reading; loved it so much she’d often get in trouble for reading too much. And she had another love: a computer class that had one computer. In that class, she was learning to use a keyboard. “Now, looking back, I realize how groundbreaking that really was for that school,” Dona says.
Then, in early high school, both of her parents who were working and attending school while taking care of Dona and her sister, decided to move the family to the Detroit suburb of Novi. “I’m so different from everyone else,” Dona says. “I always have been, and I was determined to be better than that circumstance. My parents did a fantastic job given what they had. I secretly had a huge goal to one day walk into a Macy’s store and buy something without looking at the price tag. I couldn’t wait for an opportunity to grow up and not be bound by downtown Detroit.”
Dona found that opportunity in tech after falling in love with her first computer science class; one she took at a community college while she was a junior in high school. And now, as a principal engineering lead for Microsoft, Dona takes her role as female tech ambassador very seriously. Whenever she’s not working at the tech giant on projects so cool she can’t always talk about them, designing clothing (she makes her own dresses) or writing her next book (set for release next year and titled, You Had Me At Hello, World!). she’s mentoring other women via Skype and answering emails with advice on how they, too, can enter the world of tech. “I realized that tech is the greatest get rich scheme in the world,” Dona says. “You get a four-year degree and you make all this money. You don’t need a master’s or a doctorate. You just start working at a great company.”
Find out how Dona inspires other women, designs the next great thing for Microsoft products and how she didn’t let a failing grade in computer science stop her. But wait, that’s a spoiler alert! Her story is so amazing, we broke it into two parts. Catch part one today to learn how she got into tech, then come back tomorrow to learn why Dona is Microsoft’s hidden threat—and the next greatest female tech rock star.
How did you first discover tech?
I was in high school in the mid-90s when technology was becoming a big thing. I kept coming across articles about young people who were launching their own startups and were the CEO of their own company. I would tell my dad about it. He's a total feminist, and he told me, "There's no reason you can't get into this and be very successful." "But I know nothing," I responded. "Well, then you should learn it. Do your research," he said.
I did my research. It turns out if you're good at math and logic, then you're good at programming. I used to love playing Oregon Trail, and more than anything, I wanted to make a game like that. Growing up in underprivileged downtown Detroit, we were fortunate to have one computer and a very basic computer class. I went to this computer class after school and found myself in front of five guys who were in there. They said, "The French Club is down the hallway." "I'm actually in French Club, but I'm here to program a game," I responded. They started laughing.
After two sessions with this group of guys, they still wouldn't talk to me or collaborate with me. I no longer wanted to be there; it wasn't something I looked forward to. I went home and told my dad it just wasn't going to work out.
"Is this what you want?" he asked me. "Yes, I want to give this a shot," I said. So, together we looked at different options. We found a class offered by a community college near us. My dad said he'd come to community college and take an English composition class while I took a computer programming class. This class is where I realized tech had me at, "Hello, world!" I loved how in this class there was always a right answer. I immediately knew whether my code was working or not. Did it compile? Did it run and do what I expected? Coding isn't mysterious at all. It's definitive.
During that class, my project was to create a real estate website. It required a very basic user interface, but I made it by myself. It wasn't the most fun thing in the world to make, but learning the skills and how to make this website was huge to me. So, the lesson here is that even when though those nerds shunned me from their club, I still figured it out.
Wow! It's hard to believe you were a junior in high school taking community college computer science classes. Take that, boys! After you graduated high school, what were the next steps you took to pursue a career in tech?
I went to college at the University of Michigan and enrolled in EECS 100, Introduction to Programming. When I arrived at the University of Michigan, I realized what a big deal it was, so I spent my life studying.
When I was still in high school, my favorite thing to do was calculus, even when I was too young for it. I entered college with a perfect GPA and good ACT and SAT scores. Because college was all on scholarships and student loans, my parents helped as much as they could. I wanted to take it seriously and show them this was the best investment they ever made. I was a college student who wanted to study.
What was your first college computer science class like?
I entered computer science class thinking it would make sense, based on my previous community college experience. Instead, it was all about bits and gates. I didn't understand it at all. Then we quickly moved on to binary programming and then assembly programming. I didn't know what was going on. I was not doing well.
At the end of the semester after finals one day, I went to my mailbox and saw my grade card. I went up to my room. I sat down. English—A. Math—A. Something else—B. Computer science—E. In my school, an "E" meant I got a "F". I failed my first programming class. It was the most devastating moment I've ever had. I sat there alone in shock thinking, "This can't be right. This is what I was going to do. This is what I was going to become. Those nerds were right. I can't believe those nerds were right.
I emailed my professor, then I sat there for hours. It grew dark outside. I had to call my parents and tell them. I told my dad and he was in shock, like me, because I'd never failed at anything before. Ever. I kept thinking, "How can this be?"
To move on, I started researching other majors. I thought about applying to business school, but at the end of winter break, I still wanted to be a computer scientist. I just liked it. So, with my dad's support, I took the computer science class again.
The class was still hard the second time, but I got it. I knew what was coming. I went to see the teacher's assistants many times—making sure I understood each section. And I ended up getting a "B" after that second class. Sure, it might have taken me longer than it took other people, but I didn't give up because this is what I wanted to do.
For so many other kids in my classes in college, the introduction to computer science was not new to them. They'd studied it for years. I learned that in other high schools, the students had the option to take something called AP Computer Science, which was pretty much the same content I'd been surprised by first semester. My school hadn't had it. When I understood that's what I was up against, I realized I was doing pretty well.
How did you parlay your college experience into your first internship?
I was looking for an internship during the tech bubble, when companies started to take off and then crash. I really wanted an internship, because I knew this was the only way I was going to get a job. The word around campus was that companies were only hiring juniors—if anyone —for their internships. I was only a sophomore.
I've always loved fashion and I remember reading an article that said to dress for the role you want. So I thought, "I can do that. I'm going to dress like I'm going to an internship every day." I woke up every morning, put on a suit and proceeded to the engineering library where all the interviews were taking place. This is where I would create all of my projects, write all my code and play games.
One week in November, I walked in and saw a guy who was clearly a recruiter. He was walking around looking lost. I walked up to him and asked if I could help. He said, "I'm from Autodesk and I was wondering if you know where the interview rooms are. I assume you're headed there." He gestured to what I was wearing. We walked there together and talked. He asked me how busy I was with interviewing season and what I was working on. I told him I just made a game and was looking into operating systems. He asked if I was interviewing at Autodesk. I told him no, because I didn't think our schedules aligned.
When we reached the interview room he told me about an opening in his schedule. He was originally going to call into a meeting, but he said because I was so helpful, he'd rather interview me. I couldn't believe it. My moment arrived. I ran back to my workstation and immediately started preparing for my first-ever technical interview. I did nothing for hours but take deep breaths and study.
A few hours later, I went in for my Autodesk interview. This is the company that makes AutoCAD, which is a really big deal. My parents both worked for car companies, so I had learned about this program. As we were talking, I drew on that experience and told him that I understood the AutoCAD customer, because they were people like my parents. Then, as in all technical interviews, I did some coding. The interview ended, I sent him a thank you email and some pointers for places to grab lunch because I realized he missed his lunch by interviewing me. Then, I resumed my actual work. I had quizzes coming up, after all!
Two weeks later, Autodesk offered me an internship.
That's the power of presenting yourself as you want to be perceived. People want to work with people they like. That guy thought I was helpful. He thought, "I want someone like you at my company." Now that I hire lots of people, I know that the ability to communicate, learn, deal with ambiguity and radiate ambition is key. The person who checks those boxes is the person I want on my team, because they can figure things out. Be this person. You'll be amazed how many doors it can open for you.
What happened after your internship at Autodesk?
The following summer I had another internship; this time at Intel. This meant I had to move far away from home in Michigan to Portland, Ore. During my internship, Intel had a hiring freeze, which meant they wouldn't be giving their interns, including me, any offers.
I started applying for jobs everywhere I could, except for Microsoft—it seemed too big to me. I didn't think I was worthy of a company that created the most-used software in the world. I had offers from three companies when I graduated. One was with the NSA. I didn't want to go to have my eyes scanned through a laser just to get into work every day, so that didn't feel like a fit for me. I also had an offer from the Goodyear Tire Factory in Akron, Ohio, but after growing up in the Midwest I wanted a West Coast job. I wanted to be where tech was happening. I ended up taking a job as a software engineer with Siebel Systems in downtown Bellevue working on their handheld client. I didn't know anyone in the city; I was a 21-year-old who had never lived away from home. But as soon as I started working as a developer on the sync engine between the Palm Pilot and its database backend, I loved it.
Then one day, after being at the company for about a year, something happened that changed my life. I was sitting in my cube and my manager came down the hallway. He asked if I had a passport. They needed me to travel to Budapest to work with British American Tobacco. The company’s sales team was experiencing problems with uploading data. Siebel needed to send an engineer from our team to debug this blocking customer issue.
My manager said to me, "You present yourself well, so we figure you'll do great in front of customers." I'm telling you this because the things I thought would hold me back in tech—being a woman, being a nice and friendly person and dressing well—were not really holding me back. These things were actually giving me opportunities. I related to people first and foremost. I was trying to figure out how to make things better for people.
Before I knew it, I was on a plane to Budapest on my first-ever business trip. I stayed in my first hotel room by myself. I took my first towncar to the office. It was amazing. I showed up at British American Tobacco with my laptop ready to go. I asked the sales team to let me follow them for a day in their life to see what was going on.
We went into a tobacco shop. The sales person introduced me as a consultant from headquarters and then wrote down the inventory the shop needed. There were two buttons on the device—Save and Commit. Save would be a temporary save and Commit meant upload to the database. After a while, Save deleted the data. I noticed that when the sales person entered his inventory, he kept hitting Save and he never hit Commit. He didn't know he had to. When he hit Save he thought it meant it would save to the database. It was so stupid that as developers of this product, we never walked in the customer's shoes.
I ran back and called my manager. "The problem is UI-based," I said. That moment changed my life forever. It ingrained in me that it's always about people. Technology is simple. It's people who are complicated. I realized I wanted a job where I can see how customers are using technology.
After your "ah-ha" moment, how did you take that next step and find your dream job at Microsoft?
I was still scared of Microsoft. It's the best tech company in the world. But, as scared as I was, I applied. I really wanted a job where I could interact with customers. And I got that job at Microsoft. Here, I get to talk to customers and do validation and testing based on how they use products, not just through code.
With such an amazing job, how do you organize your day?
Every day is completely different. Across Microsoft, there are a lot of people who have jobs similar to mine. I work with our researchers and analytics people and they're located all around campus. So, earlier in the day, I try to schedule and attend all of my meetings I have with people who aren't on my team. That way, I can talk to my team about what I learned in those meetings later on in the day.
Every afternoon, I schedule my day around my team, then this time is spent working with them. I also find that my workday finds its way into my mind as I drive home each evening. I'll have thoughts like, "I want to do this... and this... and we could go get a 3D printer and do this." When I get home, the first thing I do is tell my husband. He's used to my tendency to plot the next day's activities on my drive home each day.
During the evening, I love to spend time researching trends and things happening in our industry. I also have a lot of mentees around the company and industry, so during the evening is when I find time to email them back and forth or have a Skype session with people not based in Seattle. Once that's done, I take time to do something else I love, like writing or sewing. It's never both. It's never everything. I really can only manage to accomplish three things in a day—work, spend time with my husband and then sewing or writing.
It sounds like you've figured out a plan for work/life balance. How does a job in tech allow for this?
You really only have three parts in a day: morning, afternoon and evening. I'm a big believer in work/life integration. Sometimes I'm at work and there are home matters that need taken care of during the day. When I was planning a wedding this summer, I'd have to call the caterer, for example, during my workday. But in the evening, you'd find me writing the first draft of a fun project with my team. And I enjoy doing that in the evening.
A technology job is so versatile. Tech is not just the greatest get-rich quick scheme in the world, but you can work anywhere with this degree. You can work in a penthouse in Paris or the desert in Mongolia. You can work at any company with a technical degree. I tell women all the time: if you have interests and passions in other industries, you should still get a technical degree. Start with even a minor in computer science. You have no idea where that will take you. Being the tech girl at a company can take you anywhere.
What challenges keep you awake at night?
We have to get the tech industry to not be so insular; meaning composed of people who are technical and people who are not technical. That's the divide, and it can be very intimidating to those who need to use technology in their job. But tech is not a groundbreaking thing. The very first switchboard operators were women. The first computer scientist was a woman. Computing—and technology—is totally women's work.
Think about Mad Men for a minute. All the guy characters in the show are too busy being the boss. They have their secretaries do all their math and correspondence for them. It's really the women who have all the power, because that's where the power is.
We have to remove this divide that technology is this special thing that "some" people get into. Technology should be just as ingrained in our lives as reading, writing and math. Everyone needs to work on a computer and most everyone has basic social media needs or even a need to build their own websites and maps. But, tech is still considered this seriously mysterious thing. It's not. They're just computers. There are developers out there who literally set up an app developer kit and just start building their own app. You don’t need to go to school for 12 years to do technology.
Another bonus is that the tech industry is everywhere, not just here on the West Coast. How great would it be to have a job that allows you to live anywhere you want? That's what technology does. That's the power of tech.
What would you say to a woman curious about a job in tech if she were sitting across the room?
It's pretty damn cool. It's a superpower people are impressed by. And, tech is fairly easy to get into. If you're a woman who knows nothing about tech and you're timid about getting into it, try an online course through Udacity. It's free. Just sit down, pay attention and focus. Do the course once, then do it again if you didn't quite get it the first time. Once you have a good grasp on it, get a computer science degree. You can do it either online or in person.
The barrier to entry in tech is quite low, because you can teach yourself much of it. Cities have all of these meet-up groups for people who are learning how to code. Just look up "coding meet up" for your city. I would highly recommend that you get involved. When you attend a meet up with other girls who code, it will build your confidence. When you have others around, you'll be surrounding yourself with people who know what they're doing. They're there to help.
There are literally millions of people like me in the world who want women in technology. You can't build products for half the world without half the world on your team. Women buy more technology and use social media more than men. Women are inherently social, yet we make up less than 10 percent of engineering staff. That can change—with you!