When I was a college student, I heard about all these unbelievable perks at the Disneyland of all tech companies: Google. I heard about how they had these big storage cabinets, where someone would stock them up, fling the doors wide open, announce “FREE T-SHIRTS!” and there would be a free-for-all where you could grab as many brightly colored whimsically designed Google logo T-shirts as you wanted.
Fast-forward to my time as an actual employee at Google, and well, it didn’t quite work like that. But at certain points, it did feel like it was raining schwag. The free stuff would just keep coming, which IS as delightful as it sounds! Now I have enough T-shirts and hoodies for a whole “Silicon Valley engineer” wardrobe.
I also have other random things like this Android cookie cutter, which I immediately put to use that holiday season, but have since misplaced. Oops.
Anyways, back to the free T-shirts. It all began with the Noogler shirt when I first started at Google. Noogler stands for New Googler smashed into 1 word because we’re too lazy to say the 2 words. We also received a propeller cap, which this big guy at home wears now. Maybe I should see if the shirt fits him too.
At the end of my first day of orientation at Google, my mentor picked me up to go to my desk and that was when I found out I was joining the Android Apps team! Woohoo, it was my first choice, so I was on cloud 9. I was going to be working on the Android Market app as a software engineer. (The Android Market is the old school name for the Google Play Store app.) We had an incredibly ambitious plan, and the launch for the Honeycomb release of Android was brutal. So many late hours working, but at least we got these cool sweatshirts with our names hand-stitched on them at the end of it. Although, brown was never really my color.
Next up for the Ice Cream Sandwich release, I worked on the Contacts app – making it all prettyful. I learned the real meaning of pixel PERFECT. I was pushing things on the screen left 2 pixels, then right 4 pixels, up 16 pixels, etc… There was a method to the madness, I think. Our app did get mentioned during the keynote launch of Ice Cream Sandwich. 5 seconds of fame, hurrah!
Ice cream sandwich on a shirt
Ice cream sandwich on a truck
Ice cream sandwich in my hand
Then it was time to get back to work. Spring turned into Summer. Code was written. Summer turned into Fall. More code was written. We also got these jackets to keep us warm… but you know how I feel about the color brown. The jacket nearly envelops me, so I passed it onto my cousin. See! Enough schwag to clothe me and my family!
In the final weeks before JellyBean launch, I got shipped to London to help the Google Search team with their app. When I wasn’t stuffing my face with the amazing snacks in their microkitchen and drinking their freshly squeezed orange juice, I managed to fix a few bugs for the team. 😛 The launch celebration included a big Jellybean statue to display on our front lawn, to go with the other dessert statues. There were also many jellybeans eaten, or rather in my case, many popcorn jellybeans were eaten (my favorite flavor).
My next big project was creating the Google Keep Android app. There were ups and downs, pauses and restarts, redesigns and many rounds of iteration. But persistence paid off and we launched to the public on March 20, 2013. I remember that day like it was my birthday! We celebrated our launch in many ways, which included these extremely warm (and oversized) Google Keep hoodies. Our team also made a trip out to visit our counterparts in Sydney, where I got this Down Under shirt and learned how to do a proper Tim Tam slam. BAM!
From the Honeycomb release, to Ice Cream Sandwich, to JellyBean, and KitKat, it was a privilege to be able to witness the Android platform evolve and mature. I lived and breathed Android, and I loved it. Android stickers, squishables, collectibles, devices, I had it all. I also had friends with iOS devices, but those friendships were hanging by a thread. 😉 Kidding!
Buying ALL the Android KitKat bars at Walgreens
About 3 years into my time at Google, something inside me started to feel restless. I loved the people that I worked with, but I felt like my interests were calling me to a different type of work. I heard about a program to travel to Ghana for 3 weeks with a group of Googlers. It was a much-needed break to step back from the hectic schedule of my day job and figure out what I wanted next.
A team and I got to work with a nonprofit that was sharing lifesaving tips on pregnancy with expectant mothers in rural areas using SMS / voicemail messages. The experience cemented in me the amazing power of mobile phones and how much it could improve people’s lives. I realized that there was so much potential in training developers to build apps for their communities. I knew I wanted to be a part of that.
Upon returning home, I slowly made the transition over to the Developer Relations team to become a Developer Advocate (and collect more free T-shirts of course). Our aim was to train developers around the world on how to build Android apps. We tried to do it in scalable ways by creating videos. I still couldn’t get use to seeing myself on video. *Looks away and closes ears* It’s so weird!! Nevertheless, it felt like a surreal job, like I was getting paid to do something I would volunteer for. It felt like I had hit the career jackpot. We got to meet so many developers, startups, and got access to the coveted Google I/O conference, which was a big ol’ party of all the fun Google things in one place. Sleep was not a priority during those days.
During that time, our training team began to partner with Udacity to create free online courses. Even if you don’t have ANY programming experience, you can take the Android for Beginners course. Later we built out more courses, leading students through building a series of apps with a social impact angle. Along the way, we learned words from the Native American Miwok language (“yoowutis” means “Let’s go!” but I have more to learn..), filmed an earthquake scene with our terrible acting skills, and tried to steal a dog from the Silicon Valley Humane Society (we were building a pet shelter app and needed another subject matter expert).
On another random note, at Google there’s the usual Take Your Kids to Work Day, but ALSO a Take Your Parents to Work Day! Our team showed parents how to start building their own apps, and more importantly, how to do the happy dance after your code works. *Raise the roof*
Alas, another 3 years on the Developer Relations team zoomed by. As we wrapped up the final course, the same feeling of restlessness started to bubble up within me. As bittersweet and hard as it is to leave such a wonderful place, I felt like it was time for me to move on from Google. To find the next thing my mind wanted to learn. To find the next thing that my heart wanted to experience. I have yet to figure this out, but will be documenting the journey on this blog, so feel free to join me for one heck of a ride.
As I step back and look at this giant pile of T-shirts on the floor, I am filled with gratitude mixed with nostalgia. I grew up at Google. It sent me around the world and taught me more than I ever thought I could learn. (It also gave me an incredibly high standard for corporate cafeteria food.) While these T-shirts may get old and tattered, the people and experiences are things that I’ll always hold in my heart.
I’ll close here with a photo of my favorite Google T-shirt. I wear it the most.
And ironically, it’s the only one that I paid for.
Thanks for sharing it with us, it was great to know about our android mentor, and good luck.
I don’t know but your post is really very engaging to me, I’m your student learning android from udacity and I read your all post just because I also want to know what you find out.. well thanks for sharing this with us 🙂
So inspired by your mode of training for Android development. Best wishes in your future career Catherine.