According to a new Dice.com salary survey, MongoDB ranks as one of top-10 most highly compensated technology skills. Indeed.com rates MongoDB as the second hottest job trend. And DB-Engines.com, which ranks over 200 databases on their relative popularity, MongoDB is now the fifth-most popular database in the world, this month surpassing IBM's DB2.
All great, right?
Buried in the Dice.com data, as well as the Indeed.com data, is evidence of real confusion. For example, of the top-10 most highly compensated skills in Dice.com's survey is "NoSQL." NoSQL is not a technology. It's not really something a developer can "know" in any real sense. NoSQL is a movement that describes a different way of modeling data but, as Basho founder Justin Sheehy correctly noted, there are as many differences among so-called NoSQL databases as there are similarities.
As such, knowing Basho's Riak won't really help you understand MongoDB. Perhaps at a high, conceptual level, but expertise in one doesn't really translate into familiarity with another. They are different databases with different approaches.
Employers looking for generic NoSQL skills need to think more deeply about what their application requirements are. Looking beyond relational databases for modern application requirements is a good start, but looking to generic "NoSQL" is not sufficient. Organizations should be looking for a modern database that dramatically improves developer productivity, encourages application iteration and enables a new wave of transformational applications in areas like Big Data, Internet of Things, mobile and more.
That database is MongoDB.
Is MongoDB "NoSQL." Sure. But it's much bigger than that (based on what people search for on Google, many organizations already seem to understand this). MongoDB is the fastest-growing database in the world, not because it fits the NoSQL category, but because it significantly improves the productivity of developers and the organizations for which they work. So if you're looking to hire technology talent, you're far more likely to be successful hiring an experienced MongoDB engineer than a "NoSQL engineer." MongoDB, after all, is an actual database. NoSQL simply describes an important movement.
Meet Daniel Gottlieb: MMS Backup Engineer
Meet Dan Gottlieb, an engineer for the MMS backup team at MongoDB. What is your role at MongoDB? I’ve been working as an engineer for the MMS Backup team for just under two years. Where were you before MongoDB? Why did you choose to come to MongoDB? Immediately after college I took a position at ShopWiki, an internet shopping search engine, where I worked closely with Eliot Horowitz and Dwight Merriman, the co-founders of MongoDB. After six years, I briefly joined another startup before coming to MongoDB. The decision to join was easy. I really enjoyed my previous experience with its co-founders and I had a lot of respect for the way they start a company from the ground up; they both really care about the technology. What’s your hometown? I was born in Queens, but raised in Edison, New Jersey. My whole family is from New York and I always wanted live in the City. I want to think of myself as a New Yorker, but I'm not sure if one can ever shake the impressions of society that are formed growing up in the suburbs; reliance on cars, playing in the street and living in comparably larger houses come to mind as major differences. And knowing people in their thirties that grew up in the City and never had a driver’s license is a very foreign concept to me. Ultimately, I'm a Jersey guy. 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? At ShopWiki, I was assigned to start taking data feeds of items sold from our shopping search engine. My introduction to MongoDB happened when we began using it to process and take stock of the items stores were selling from our search engines. Up until that point, ShopWiki was using data gathered from web crawling. It was a relatively simple use case, but we were able to begin inserting and updating hundreds of gigabytes of data each day. Since joining MongoDB, I’ve seen the amount of knowledge, brainpower and organization grow exponentially. Watching the company grow from five people to ten, to twenty and then suddenly to about a hundred, by the time I “officially” joined, was very exciting. Perhaps it’s a bit superficial, but having multiple PhDs on staff makes me confident that we’re making a real difference in the database space. Bike or public transportation to work? I actually walk to work. I live six minutes away when the traffic lights align. What’s a typical day (or week) for you? I definitely have a more typical schedule now than I did when I joined. I usually have a couple of meetings a week and have a few issues to look into carefully. Then most of the week is working on development with some recruiting here and there. What do you love most about MongoDB? The people! It’s the best team I’ve ever worked with. A shout-out to Steve, Cory, Cailin, Rhea and John, they make everyday a pleasure. Everyone is incredibly smart, and particularly with the backup team we communicate really concisely and cohesively. I love that there's a lot of lateral flexibility with regard to the roles at MongoDB. Having a flourishing developer community there are plenty of opportunities to give talks at meetups/conferences, attend hackathons, or get involved with college recruiting efforts where many students actually know who you are. And the managers do a great job at matching engineers with their skill set and interests, while giving developers time to try something a little bit new when deadlines are more relaxed. What’s the most challenging aspect of your job? We take client data very seriously, especially in the MMS backup service. I’ve been working on a number of additional features to further improve the way we store and manage snapshots of client data. The big challenge is maintaining the discipline to properly plan, test, document and review code. It’s important to simultaneously develop the specs, tests and documentation with the code so that others reviewing the code can verify correctness. We do a lot of iterative testing and code review to make sure our code is as perfect as possible before shipping. What’s one of the most rewarding experiences you’ve had working here so far? I’d say the most challenging aspect of my job is also the most rewarding. It’s hard work, but after the functional spec, the refactoring, the coding, the testing, the fixing, the documentation, the code review, the QA and the stress of "waiting outside the delivery room" during its inaugural run, there's nothing better than hearing that a project worked. What’s your favorite Seamless lunch order? I usually don’t eat breakfast so it’s the restaurant that delivers at 11:45. I’m not really picky about what food it is. That being said, I usually end up with a Chop't salad, though these winter months have made anything with soup popular. Particularly, chicken and broccoli with wonton soup or a Dig Inn platter with soup on the side. Name one secret skill you have, unrelated to work. I had a job in college working at the deli counter in a supermarket so I’m actually a great deli slicer. To be fair, the real skill is caring to do the job right and being aware of each slicer’s particular quirks. One customer would come in every Monday morning to have me cut up to two pounds of pepperoni sliced paper thin because I was the only one that wouldn’t switch to a thicker slice partway through. My personal preferences are as follows: pair roast beef with cheddar or american, turkey with american and ham with provolone. I always prefer white to yellow american and kaiser rolls are a must. I strive for a quarter to a third of a pound of meat per sandwich. Consider trying hard salami instead of genoa; it tends to be smokier and less chewy. At optimal thickness, there’s eight slices of american cheese in a quarter pound. Here’s my go-to lunch sandwich: Black Bear London broil roast beef, Black Bear extra sharp cheddar, on a kaiser roll with yellow mustard. Kindle or book? What’s your favorite book? Both. I have some great programming reference books but they’re too heavy to read anywhere but on a dedicated reading surface. So I keep reference books on the Kindle. However, there's nothing quite like the experience of finishing the last few pages of a great book and then turning it over to look at the back cover and feel that it’s over. In an effort to spread the word on a newer series, check out out the (unfinished) Kingkiller Chronicles by Patrick Rothfuss. I highly recommend the first book, Name of the Wind. Fastest 736 pages I’ve ever read. Favorite book series? A more classical answer: I loved Ender’s Game/Speaker for the Dead. The last two books of that series were okay, but the first two were amazing. I also feel compelled to mention A Hitchhiker’s Guide to the Galaxy. Describe your perfect weekend. Despite (or perhaps because of) living in New York, I enjoy outdoor activities, but I hate the travel time involved. So if we lived in a world with instantaneous teleportation, my perfect weekend would be as follows. Snowboarding in the morning, then a game of softball, followed by finishing a book, learning something new and eating a Pollo Asado Calexico Burrito (with crack sauce mixed in). Are you a burrito expert? I love burritos but honestly the Calexico food carts have the best in the city. I don’t even bother with the others. If you want to learn more about MMS, visit the MMS page on the MongoDB website. If you're interested in joining the MongoDB Team there many open positions available in Engineering, Sales, Marketing, and Business Development. If you're inspired by Dan, MongoDB is looking for a Java Engineer and MMS Technical Account Manager to join the MMS team. To learn more about open roles at MongoDB, please visit the MongoDB Careers Page .
Transitioning from Teacher to MongoDB’s New Enterprise Modernization Team: Meet Gabriela Preiss
As a global company, MongoDB has amazing employees with interesting backgrounds and stories. I recently sat down with Gabriela Preiss, an Enterprise Modernization Consultant, to learn more about her journey across the globe from the U.S. to Barcelona, Spain, and her experience transitioning from teaching to becoming the first hire for MongoDB’s brand-new Enterprise Modernization Team, shifting enterprises toward innovation and generating a ton of compelling content along the way. Andrew Bell: Thank you for sharing your story, Gabriela. I’d love to know how you got to where you are today in your role. What skills are important for someone on your team to be successful? Gabriela Priess: My career journey has been from one end of the spectrum to the other. Originally, I studied English and education, and I was a high school teacher for four years. I loved teaching, and I encourage anyone who wants to pursue it to do just that, but eventually, I hit a block and craved more mobility. So I moved from the U.S. to Portugal and studied web and mobile development. Finding myself back as a junior in a new industry, I worked my way up by freelancing as a web developer, building a curriculum for a coding school, and then quickly finding my way into a lead tech support role with a popular web application organization, where I also led the QA process. So, how does all of this add up to working in and with data? I truly believe every professional experience is the chance to extract something positive — a learning takeaway. This diverse background has challenged me and shaped me, as well as helped me to be confident in my choices, to trust I’m taking steps in the right direction, because ultimately each career move has been better than the last and has led me to where I am now, with MongoDB, as an Enterprise Modernization Consultant. Ultimately a career risk led me to a job that didn’t even exist a year ago on a new team. So, we can never truly say what the future holds for us; we may be headed toward a killer career that hasn’t even been invented yet. When it comes to being successful on my team, I think this role is open to so much diversity. I’m trying to narrow down any specific skills, but I think anyone who is ambitious, independent, takes ownership with what they produce, and is curious will succeed here. Curiosity is a huge asset — someone who is open to learning and diving deep into what they don’t yet understand, eager to keep growing, and tech-curious. A big part of what we do involves us keeping our finger on the pulse of tech and data innovation, so we can confidently discuss, debate, or write about it. This means feeding ourselves with the right tech news content. AB: I’d love to know more about the modernization team. What’s your role and your day-to-day like? GP: Our reach is quite broad, but if I had to define it, I’d say the Enterprise Modernization Team (EMT) assists, educates, and helps inspire large enterprises to move toward modernization and innovation. Often, large enterprises have the most complex, costly legacies in their systems and need macro and micro aid and insights to not only modernize but also to visualize and tally the endpoint. EMT Principles and Consultants have the industry expertise and capability to translate our value proposition to senior executives and engineering management. This includes generating training content for internal teams; meeting with other teams for potential and ongoing accounts; delivering webinars, published content, and interactive exposition presentations; and meeting with clients so they have a stronger understanding of how MongoDB helps them to modernize from the most basic format, such as adopting the document model, to truly leading in innovation, such as data science, machine learning, and real-time analytics. So, EMT is a bridge between sales, technical sales, and marketing for complex industry use cases and solutions. These are the teams we collaborate most often with, working closely with sales reps and solutions architects, collaborating with solution providers, and closely aligning with the marketing team producing diverse content and product alignments. So, if you ask me what exactly is my role, I’d say it’s all of the above. Our team is small, although it’s growing quickly, and we have big plans to expand exponentially in the near future. That said, we have a democratic way of dividing the work. We’re made up of our Global Head, Boris Bialek, our Principal, Steve Dalby, and the two Consultants, including myself and Vanda Friedrichs. And we’re all expected to bring equally to the table, despite who has more seniority. This lets us all have an idea of what everyone is working on, and we frequently dip into each other’s projects either to help out or request aid. Each project is free roaming for all: as long as we’re aware of the objective and deadline, we can get creative with how we reach the endpoint. My projects are constantly evolving and regenerating, and I could joke that the only thing they have in common with each other is they all have to do with MongoDB. However, when I was hired, Boris was very clear and direct that each day would be different, and his promise has held true. I don’t have a day-to-day like most others might in regard to consistent projects, but the objective is always the same for each: how can we showcase MongoDB’s value in modernization and innovation in regards to data and tech? Because my projects are so diverse, and often more creative-oriented than anything else, I make up for what some may call a “lack of structure” by being very structured in how I plan my day. Before each day, I predetermine how my next day is going to be divided hourly by projects, tasks, and follow-ups, and I reserve some time for “self-learning,” where I take time to continue my training curriculum, since that’s an ongoing track. AB: Since this is a new role, what tools and resources (e.g., Sales Bootcamp) were you given to help you ramp up? GP: True, this was a new role when I first stepped in, so I didn’t totally know what to expect. There was a running joke I was learning by a fire hose, just having everything blasted at me, and something was bound to stick. MongoDB sets all employees up with boundless learning resources, so I created a curriculum for myself. I prioritized from the top down, based on what I needed to understand ASAP, such as MongoDB’s services and functions, and from there I had freedom to roam based on what interested me the most and what my weak spots were, and was given time to dive in deep technically. For example, I ran POVs to see the data in action from a locally set up database. I know other teams within the company have established curriculums for onboarding, but because this was a new role, I used the resources available and that worked for me. I was given a lot of liberty with my learning because it was mostly autonomous and self-driven, but that’s not to say my learning is over. The company really promotes a learning culture, and every week there are new resources with webinars, learning materials, training materials, and so on. Early into my onboarding, I participated in what’s called our Sales Bootcamp. It’s a two-week intensive training that dives deep into MongoDB’s services as a whole and lays a strong foundation to build on. It’s usually something that’s done in person at MongoDB’s headquarters in New York City, but since this is the COVID-19 era, it was done virtually, with a big cohort of new hires included from Europe and the Americas. This was a cool experience, because I got to meet a lot of new faces. Professionally, my background is originally in education, so I used to write my own curricula for my students, and I’ve been impressed with what I find the MongoDB enablement and Learning & Development teams generating. AB: What content have you and will you create? What is the purpose of this content? How is it leveraged? GP: Among many other roles, the EMT is a content-generating team, so we’re constantly working on creating something new, or collaborating with other teams to create new content. As of today, I’ve been with MongoDB for four months, and in that short time, I’ve been able to generate a lot of interesting, challenging pieces. Each project I’m given is a chance to dive deeper into that subject and expand my understanding of it — like data science or fintech, for example. One of the first projects I had was the chance to write a blog about MongoDB’s partnership with Iguazio , and how our data platform is the ideal persistence layer for Iguazio’s data science and MLOps platform, which is used to develop, deploy, and manage AI applications. Clearly, each project is a team effort, but this gave me the opportunity to dive into a topic I find personally interesting, while building connections with some of our most innovative partners. My first or second week I was introduced to an internal deck created by one of our Solutions Architects, Pascal Jensen. It was a sort of think piece on how data is being driven by the growing uncertainties of the world, in a political, social, and economic sense, and how the most innovative leading companies are responding. We decided to turn this into a more holistic, complete white paper to reach a wider audience. With that, after really digesting the deck that was available and multiple interviews with the Solutions Architects that contributed to it, I built an extensive paper around it, giving breath to the expression “digital by default.” This was something I was quite proud of, because it was so early on in my time with MongoDB, and it let me dive into truly interesting topics. I was able to build on the holistic elements of data and how it’s reshaping even the most mundane elements of the world, propelling us into the future with innovative technologies and solutions for some of the most crucial global concerns, such as hunger or healthcare. Last month, I presented my first corporate webinar with MongoDB, discussing transitioning from a relational database to MongoDB’s document model. It was a huge opportunity, because we were focusing on Spanish-speaking countries in Latin America. For me, this was almost a beta project, because I didn’t know what to expect in regard to reception. In the end, it was a massive success: overall, we had more than 6,500 registrants. That was a really exciting experience, because I knew as a team and a company we were clearly doing something right, engaging with the right audience, and connecting with the right people. There is a really positive response still outpouring from that webinar, and I was happy to be a part of it, especially as a rookie. Again, it just speaks to how much autonomy and freedom to create I’ve been given. My manager never holds me back from any opportunity and really encourages our success. In the spring, we’ll repeat the same endeavor with another webinar, covering a different topic I’m currently preparing in Spanish. AB: What was it like starting in a new role on a new team, especially during the pandemic? How do you stay connected to the team despite living in different countries? GP: Despite the pandemic, there was a lot to dive into because the company was running full speed ahead. It can be slightly intimidating being the new person on a fast-paced team, but I felt very included and seen from day one, and there was more than enough work and training to keep me busy. I haven’t really considered what it would’ve been like to work with MongoDB prepandemic, because at this point, this is all I’ve known. Staying connected with my direct team, though, has been the easiest part for me. I’ve never once felt disconnected despite never having met them in person. As of now, we’re dispersed across Dublin, London, Zurich, and Barcelona, and we’re growing. Plus, our backgrounds are even more diverse considering where we’ve lived, where we’re from, and the languages we speak. It’s refreshing to be part of a team that doesn’t feel limited to one geographic region, because it opens our minds and team discussions to diverse views and ideas. AB: How would you describe the team’s culture? And how do you maintain this culture during COVID-19? GP: The team culture is really positive, inclusive, and ambitious. Every team meeting feels like a brainstorming session, because part of our job is innovation. We’re all given a voice and are expected to use it as we shuffle through ideas and ongoing projects. But overall, our team culture is casual, in the sense that we engage with each other informally, but we all recognize what we need to be working on and by when. We’re each expected to take ownership of our work, and we’re given a lot of creative and structured autonomy. This means independently owning whatever it is we’re working on, and this goes for professional learning too. MongoDB creates a lot of resources internally that I take advantage of, from guided training and courses to reading material, interactive training, webinars, and so forth. I was paired up with one of our Solutions Architects, Benjamin Schubert, and he patiently made himself available to help guide me through some of the more technical aspects of our databases as I was learning how to maneuver through it myself, and I am eternally grateful. Of course, we have support any time we need it, and I can easily seek out resources or set up a Zoom call with an internal expert if I have any questions, but at the end of the day, the ticker moves forward only if everyone is doing their part, so each of us takes our part seriously. Interested in pursuing a career at MongoDB? We have several open roles on our teams across the globe , and would love you to build your career with us!