Best Practices

The importance of community in a great data career | Census

Allie Beazell
Allie Beazell April 08, 2022

Allie Beazell is director of developer marketing @ Census. She loves getting to connect with data practitioners about their day-to-day work, helping technical folks communicate their expertise through writing, and bringing people together to learn from each other. Los Angeles Metropolitan Area, California, United States

Data can be a lonely field. In startups, especially, you’ll often find a data team of one.

While virtually everyone in the company needs data and interacts with the data team, professionals on the business-side of things often have little to no understanding of what the data folks are actually doing, never mind what challenges they face.

“If you are truly a data team of one, you may or may not be appreciated and measured correctly, because your stakeholders and management chain have no ability to calibrate,” Census founder and CEO Boris Jabes said. “It can be frustrating.”

The benefits of the data community

Boris attributes the momentum driving the data industry today to the people working together to build better data systems, rather than the wealth of new technology available.

Every industry advancement began with a catalyst: a person or small group of people who imagined something new was possible. Those visions then became reality when more people came on board to advance and adopt them.

Community has played a giant role in connecting such people.

For junior data professionals with just a few years of experience especially, there’s a deep need to connect with people more senior in the field. You can solve algorithms, create data sets, process pipelines, and expand general analytical skills independently. However, the ability to dissect ideas, the exposure to fresh viewpoints, and the chance to learn from the mistakes of others are crucial to developing essential hard and soft skills — and these can only be gained by interacting with other big data folks.

“A startup will give you a lot of work to do with a lot of scope,” Boris said. “But what matters more is who your coworkers are and if you will learn from them. Will they make you better at your job?”

So what happens if your data team is small, or everyone has little work experience? Then it’s up to you to find community outside the company. That’s how Jessica Cherny, a full-time senior data analyst at Ironclad, came to start Data Angels in 2020. Cherny and her sister Diana, also a data analyst, wanted to give women in data an informal forum where they could meet and engage others with similar job titles.

“We wanted to build a place for all analytics folks; where senior data folks can mentor, and junior folks can learn about data while dipping their toes into it in a safe environment,” Jessica explained. “A big thing that drew me to data science in college was that it is so collaborative. It felt very welcoming, so I wanted to build a place that captured this feeling.”

A community gives data professionals a place to commiserate with others who truly understand the challenges of their career path. It can be both a collaborative space to work through sticky issues, and an educational hub to advance technical skills.

It’s why we launched the Operational Analytics Club earlier this year. The OA Club gives members a space to learn from each other; it’s a space for data folks to go beyond the responsibilities of their job description, to connect with people who share their passion, and to network with people who can advance their careers.

Building your data career through relationships

In every industry, relationships are crucial to career advancement – and data is no different. Jessica was connected to the team at Ironclad through her relationship with her college mentor, whose venture capital firm had recently invested in the startup. Ironclad had no data team when Jessica came on board, so she spent two years as a data analysis team of one.

“My mentor saw that I wanted to do data analytics at a tech company, and he knew that the team at Ironclad was collectively really smart and had a low ego,” Jessica said. “I interviewed, and it was easily the best interview experience I’d ever had.”

Jessica’s boss, the vice president of product, had a data background and understood how important it was for her new junior analyst to learn the industry’s best practices from people who had experience in the field. Since there were no senior data people on the team to take her under their wing, Jessica was matched with other people from her supervisor’s network for one-on-one meetings and coffees.

The experience proved so valuable, Jessica took it upon herself to expand her network before opening it up to more women in data.

“I thought, hey, I could do this myself,” Jessica recalled. “I could reach out on LinkedIn or Slack and talk to people who are senior data analysts or directors of data – the kind of people I want to be when I grow up.”

Jessica’s initial list of 25 contacts eventually formed the foundation for Data Angels. She and her sister invited people they already knew to join the community and began posting about it to their social media channels. When Jessica began hosting quarterly panels with women in data management roles, interest in the group exploded. Today, Data Angels has around 500 members.

Boris attributes the group’s rapid growth to a hunger among data professionals for beneficial relationships that will help them develop.

“You need the guild and solidarity. You need a community to bring you growth,” he said.

Finding a sense of belonging

Whether you’re a data scientist, software engineer, machine learning engineer, data architect, or data engineer, solidifying relationships with others is key to your success. If you’re a junior data professional with no senior data people in your organization to learn from, you’ll have to seek out those people elsewhere – through formal communities like Data Angels, the Operational Analytics Club, or just by reaching out through Slack channels and online forums.

The data industry is evolving rapidly. While it takes an active approach to stay on top of new tools and trends, data practitioners need to look beyond skill sets to something far greater. They need business strategy, so they can advance their careers, make appropriate business decisions, and be recognized as the organizational leaders they are.

“When you’re a team of one, it can be particularly difficult to map the progression your career should take,” Jessica said. A community of like-minded folks gives data practitioners a frame of reference regarding what their career path progression can look like and help each other achieve what they need to grow in their profession.

“Everyone understands managerial growth, and after decades we understand what it takes to progress in an engineering career,” Boris said. “We’re still figuring out what that looks like for data.”

Listen to the wide-ranging conversation Boris and Jessica had about growing a meaningful data career and managing as a data team of one below or on your favorite streaming platforms. 🎧

💡

Then, head on over to The Operational Analytics Club to discuss your takeaways with your community.

Related articles

Customer Stories
Built With Census Embedded: Labelbox Becomes Data Warehouse-Native
Built With Census Embedded: Labelbox Becomes Data Warehouse-Native

Every business’s best source of truth is in their cloud data warehouse. If you’re a SaaS provider, your customer’s best data is in their cloud data warehouse, too.

Best Practices
Keeping Data Private with the Composable CDP
Keeping Data Private with the Composable CDP

One of the benefits of composing your Customer Data Platform on your data warehouse is enforcing and maintaining strong controls over how, where, and to whom your data is exposed.

Product News
Sync data 100x faster on Snowflake with Census Live Syncs
Sync data 100x faster on Snowflake with Census Live Syncs

For years, working with high-quality data in real time was an elusive goal for data teams. Two hurdles blocked real-time data activation on Snowflake from becoming a reality: Lack of low-latency data flows and transformation pipelines The compute cost of running queries at high frequency in order to provide real-time insights Today, we’re solving both of those challenges by partnering with Snowflake to support our real-time Live Syncs, which can be 100 times faster and 100 times cheaper to operate than traditional Reverse ETL. You can create a Live Sync using any Snowflake table (including Dynamic Tables) as a source, and sync data to over 200 business tools within seconds. We’re proud to offer the fastest Reverse ETL platform on the planet, and the only one capable of real-time activation with Snowflake. 👉 Luke Ambrosetti discusses Live Sync architecture in-depth on Snowflake’s Medium blog here. Real-Time Composable CDP with Snowflake Developed alongside Snowflake’s product team, we’re excited to enable the fastest-ever data activation on Snowflake. Today marks a massive paradigm shift in how quickly companies can leverage their first-party data to stay ahead of their competition. In the past, businesses had to implement their real-time use cases outside their Data Cloud by building a separate fast path, through hosted custom infrastructure and event buses, or piles of if-this-then-that no-code hacks — all with painful limitations such as lack of scalability, data silos, and low adaptability. Census Live Syncs were born to tear down the latency barrier that previously prevented companies from centralizing these integrations with all of their others. Census Live Syncs and Snowflake now combine to offer real-time CDP capabilities without having to abandon the Data Cloud. This Composable CDP approach transforms the Data Cloud infrastructure that companies already have into an engine that drives business growth and revenue, delivering huge cost savings and data-driven decisions without complex engineering. Together we’re enabling marketing and business teams to interact with customers at the moment of intent, deliver the most personalized recommendations, and update AI models with the freshest insights. Doing the Math: 100x Faster and 100x Cheaper There are two primary ways to use Census Live Syncs — through Snowflake Dynamic Tables, or directly through Snowflake Streams. Near real time: Dynamic Tables have a target lag of minimum 1 minute (as of March 2024). Real time: Live Syncs can operate off a Snowflake Stream directly to achieve true real-time activation in single-digit seconds. Using a real-world example, one of our customers was looking for real-time activation to personalize in-app content immediately. They replaced their previous hourly process with Census Live Syncs, achieving an end-to-end latency of <1 minute. They observed that Live Syncs are 144 times cheaper and 150 times faster than their previous Reverse ETL process. It’s rare to offer customers multiple orders of magnitude of improvement as part of a product release, but we did the math. Continuous Syncs (traditional Reverse ETL) Census Live Syncs Improvement Cost 24 hours = 24 Snowflake credits. 24 * $2 * 30 = $1440/month ⅙ of a credit per day. ⅙ * $2 * 30 = $10/month 144x Speed Transformation hourly job + 15 minutes for ETL = 75 minutes on average 30 seconds on average 150x Cost The previous method of lowest latency Reverse ETL, called Continuous Syncs, required a Snowflake compute platform to be live 24/7 in order to continuously detect changes. This was expensive and also wasteful for datasets that don’t change often. Assuming that one Snowflake credit is on average $2, traditional Reverse ETL costs 24 credits * $2 * 30 days = $1440 per month. Using Snowflake’s Streams to detect changes offers a huge saving in credits to detect changes, just 1/6th of a single credit in equivalent cost, lowering the cost to $10 per month. Speed Real-time activation also requires ETL and transformation workflows to be low latency. In this example, our customer needed real-time activation of an event that occurs 10 times per day. First, we reduced their ETL processing time to 1 second with our HTTP Request source. On the activation side, Live Syncs activate data with subsecond latency. 1 second HTTP Live Sync + 1 minute Dynamic Table refresh + 1 second Census Snowflake Live Sync = 1 minute end-to-end latency. This process can be even faster when using Live Syncs with a Snowflake Stream. For this customer, using Census Live Syncs on Snowflake was 144x cheaper and 150x faster than their previous Reverse ETL process How Live Syncs work It’s easy to set up a real-time workflow with Snowflake as a source in three steps: