Here's what we're reading at MongoDB:
Intern Spotlight: Jason Hu
This year, MongoDB welcomed 33 university students to our intern program in Engineering, Marketing, and Education. In this series, we'll introduce you to the talented students who are helping us transform development and operations for how we run applications today. I had the chance to sit down with Jason Hu who spent the summer in our Palo Alto office working with the CAP team! Where do you go to school, what is your major, and what year are you in? I'm a rising senior at Brown University, where I study computer science. What is your role at MongoDB? I’m a software engineering intern on the CAP team. How did you find out about the internship program at MongoDB? Why did you choose to come to MongoDB? I actually started computer science a year late, so I didn’t really know about tech companies, let alone MongoDB until late in college. As I did more CS I learned from upperclassmen and recent graduates about the company, and it seemed like a cool mix of technical challenges that thought big. What’s your hometown? I actually grew up in the Silicon Valley—I’m from Los Altos, California. My friends and I would walk by Facebook when it was still a small startup in Palo Alto. Did you have previous experience using MongoDB before you arrived? If so, how are things different now that you work at MongoDB? If not, how did you learn MongoDB and how was the education process? I had no experience whatsoever. To be honest, databases had been a huge, intimidating block of computer science and software engineering that I haven’t really touched before. I figured throwing myself in the deep end would be the best way to learn, and after one week of orientation I definitely learned more than an entire semester. All the on-boarding staff and mentors were terrific—they should consider becoming professors, after they retire. Working on actual projects has also taught me loads about databases—not just how to use them, but how to think about them in the larger picture of an enterprise or business. Bike or public transportation to work? I drive, actually. One of the perks of being at home, I suppose, is having my old car. What’s a typical day (or week) for you? Well, it’s really hard to say since every week I’ve had has been so different. Some days will be very focused, where I can put on some ear-buds and crank out code. Other days will be back-to-back meetings or presentations, where I’ll be learning about MongoDB’s history or theoretical concepts about databases or road mapping my project for the next week. And I can’t forget the fun! A typical week always has a bunch of great events, from smaller game nights to larger company outings, such as to indoor skydiving, Giants games, or go-karting. The intern coordinators really out-do themselves. What do you love most about MongoDB? Definitely how much I’ve learned. I can say without exaggeration that I learned more about databases during onboarding than an entire semester of the class. But it’s more than just coding chops: Watching the ins-and-outs of a startup has been fascinating. For me, it’s easy at school to be stuck in a narrow path of problem solving—improving runtimes, cleaning code, etc.—but the challenges outside of code are usually not so neat and controlled. Hearing about the problems of marketing, finance, design, and HR has been incredibly illuminating for so much work we take for granted. What’s the most challenging aspect of your job? Adapting and learning on the fly is definitely something I need to work on more. In school, we have a general sense that a right answer exists, and what it should look like. In engineering in the real world, however, there aren’t necessarily the right answers in the back of the book. Now as an engineering intern, my main challenge isn’t finding the right answer, but rather figuring out whether a problem is feasible, what the solution looks like, and whether it’s worth my time. And this isn’t an easy process. During the course of the summer, as I learned and tested different languages and programs, my project had to change and sometimes backtrack as I adapted. What’s do you hope to accomplish while you’re here? The cool thing about Cluster Bingo was that I got the start it from scratch—decisions for structuring the code, as well as library and language decisions, were all mine. So my goal wasn’t necessarily to rush out a fully functional version. Instead I wanted to think about what are its long-term goals, and how to design it in such away that enabled the growth and continuation of the project after I leave. What’s your favorite Seamless lunch order? Definitely any sandwich from the Ace of Sandwiches. Name one secret skill you have, unrelated to work. I’m a really mean baker. Literally. Apparently I get really bossy, but my cakes also are fantastic. Where do you want to be in five years? I picked this question because, well, as a rising college senior it’s kind of on my mind a lot. The honest answer is “I don’t know,” but I can say that one way or another I know I’ll be programming. Which isn’t necessarily to say I’ll be a software engineer: The past few months, I’ve realized that I can use code within any of my interests—advocating social and economic justice, product design and user interfaces, and even my original major of biology and bioengineering. Given how much my interests and skills have changed in the past five years, it’s impossible for me to really know where I’ll be in the upcoming five. All I hope is to somehow find a way to combine some or all of my interests through coding, whether that’s through a software company, start-up, or NGO. Kindle or book? What’s your favorite book? I haven’t read anything on Kindle yet, so I’m going to have to say books. However, the moment Amazon figures out how to give Kindles that old-book smell, I might have to give it a shot. It’s really hard for me to pick a favorite book, but the one that I always find myself rereading is the graphic novel Blankets by Craig Thompson. His illustrations and paneling are gorgeously done, and he has a great ability of capturing little, human interactions in his characters. Every time I read it I find something new. Describe your perfect weekend. Wake up Saturday morning and start off with hiking or the gym. Then I like going up to a museum in San Francisco: The Academy of Sciences in Golden Gate Park never gets old. Afterward, catching up with friends over dinner, before going out for the night or hanging out at their apartments. The next morning usually entails people watching in the park, and finally settling into a book on the train ride home.
Solving Business Problems and Impacting Customer Experience with MongoDB’s Data Analytics Team
Chris Douglas is currently a Product Analytics Manager on MongoDB’s Data Analytics team in New York City. In this article, we discuss the team culture and growth, how analysts make an impact, and the close partnership they’ve built with our product organization. Read on to learn more about data analytics at MongoDB. Jackie Denner: Hi Chris! Thanks for sharing a bit about your experience on the Data Analytics team. Can you start off by telling me why you decided to join MongoDB? Chris Douglas: Coming from an SQL background, I hadn’t used MongoDB in my day-to-day but heard good things about it from developers. During the interview process, I quickly saw how passionate people were about the product and could clearly see how many interesting analytical challenges there were to solve. I joined as one of the first product analysts and have been at the company for about two and a half years. JD: It must have been exciting to be one of the first product analysts. How have you seen the Data Analytics team grow in that time? CD: The analytics team had about 14 people when I joined and has roughly tripled in size. What I’m most proud of is seeing how the team has grown with respect to maturity, complexity, and depth of work. We’ve invested a lot in telemetry to better understand where developers are in their journey and help them get the most out of MongoDB. Our growth and maturity has allowed us to help more teams across MongoDB make better data-driven decisions. JD: How do you feel you’ve personally grown since joining MongoDB? CD: Being surrounded by extremely driven and talented people has helped me learn as a person and helped me better understand how analytics can play a part in the software development cycle. The culture here really encourages collaboration, so I have the pleasure of working with a lot of different functions (from sales to marketing to product), which helps me holistically understand the MongoDB Atlas business. It’s been great to be surrounded by people with such diverse backgrounds and disciplines, and it has opened up my world view substantially. As the Data Analytics team has scaled, I’ve had the fortune of transitioning into a people manager role. This has been a great (but humbling) learning experience where I get to collaborate and work closely with two fantastic analysts. JD: Some of MongoDB’s core values are “Build Together,” “Make It Matter,” and “Own What You Do.” How does the analytics team experience these on a daily basis? CD: Our team vision is to empower a data-driven culture at MongoDB, which connects really well to our company values. We’re often the quantitative arm of any initiative or product starting from ideation all the way through retrospectives and measuring results. We collaborate with product managers to understand where there’s opportunity for growth, ideate experimentation with the design teams, and work with product marketing around target groups for outreach campaigns. Bringing a quantitative lens into the fold helps the team prioritize and learn as much as we can to create value for our customers. JD: It sounds like your team is a true partner to the product organization. How do you weave data and experimentation into the product roadmap? CD: The Data Analytics team is really here to help contextualize who is using products today and where there is opportunity to help solve pain points for developers. While nothing can replace qualitative user research, it’s nearly impossible to do this with everyone given our scale and growth. Experimentation is a great mechanism for us to learn and see what solutions work best for our customer base. A/B testing has let us learn so much, which helps us improve the customer experience and increase our pace of innovation. JD: What makes working in analytics at MongoDB exciting, and why should someone join the team? CD: MongoDB has the perfect mix of a startup culture with the advantages of working for a larger company. I could be chatting about the health metrics for MongoDB Atlas, then jump into a go-to-market strategy meeting for MongoDB Search, then talk to an economist about causal inference study strategies. There’s always something new. There’s a lot of trust and empowerment here that fosters a very collaborative and creative environment. This is largely because we’re tackling big challenges that can make a real impact for people using our product every day. The opportunity to take part in shaping the future roadmap of MongoDB products as well as knowing your work is making an impact is what excites me. Interested in making an impact as part of our Data Analytics team? View our open career opportunities — we’d love to help you transform your career at MongoDB.