![Revisit consent button](../images/body-df29beacd7496220cc94.svg) We value your privacy We use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking "Accept All", you consent to our use of cookies. Customise Reject All Accept All Customise Consent Preferences ![](../images/body-2159bb67f3de8ad870eb.svg) We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below. The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... Show more NecessaryAlways Active Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data. * Cookie BCTempID * Duration 10 minutes * Description No description available. * Cookie __cf_bm * Duration 1 hour * Description This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. * Cookie AWSALBCORS * Duration 7 days * Description Amazon Web Services set this cookie for load balancing. * Cookie _cfuvid * Duration session * Description Cloudflare sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services * Cookie li_gc * Duration 6 months * Description Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes. * Cookie __hssrc * Duration session * Description This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. * Cookie __hssc * Duration 1 hour * Description HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. * Cookie wpEmojiSettingsSupports * Duration session * Description WordPress sets this cookie when a user interacts with emojis on a WordPress site. It helps determine if the user's browser can display emojis properly. * Cookie BCSessionID * Duration 1 year 1 month 4 days * Description Blueconic sets this cookie as a unique identifier for the BlueConic profile. * Cookie _octo * Duration 1 year * Description No description available. * Cookie logged_in * Duration 1 year * Description No description available. * Cookie __Secure-YEC * Duration past * Description YouTube sets this cookie to stores the user's video player preferences using embedded YouTube video * Cookie __eoi * Duration 6 months * Description Description is currently not available. * Cookie AWSALBTGCORS * Duration 7 days * Description No description available. * Cookie login-status-p * Duration past * Description Description is currently not available. * Cookie AWSALBTG * Duration 7 days * Description No description available. * Cookie csrf_token * Duration session * Description No description available. * Cookie token_v2 * Duration 1 day * Description Description is currently not available. * Cookie D * Duration 1 year * Description Description is currently not available. * Cookie PHPSESSID * Duration session * Description This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed. * Cookie VISITOR_PRIVACY_METADATA * Duration 6 months * Description YouTube sets this cookie to store the user's cookie consent state for the current domain. * Cookie cookietest * Duration session * Description The cookietest cookie is typically used to determine whether the user's browser accepts cookies, essential for website functionality and user experience. * Cookie __Host-airtable-session * Duration 1 year * Description This cookie is used to enable us to integrate the services of Airtable. * Cookie __Host-airtable-session.sig * Duration 1 year * Description This cookie is used to enable us to integrate the services of Airtable. * Cookie m * Duration 1 year 1 month 4 days * Description Stripe sets this cookie for fraud prevention purposes. It identifies the device used to access the website, allowing the website to be formatted accordingly. * Cookie BIGipServer* * Duration session * Description Marketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user. * Cookie __cfruid * Duration session * Description Cloudflare sets this cookie to identify trusted web traffic. * Cookie _GRECAPTCHA * Duration 6 months * Description Google Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks. * Cookie __Secure-YNID * Duration 6 months * Description Google cookie used to protect user security and prevent fraud, especially during the login process. * Cookie cookieyes-consent * Duration 1 year * Description CookieYes sets this cookie to remember users' consent preferences so that their preferences are respected on subsequent visits to this site. It does not collect or store any personal information about the site visitors. Functional Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features. * Cookie lidc * Duration 1 day * Description LinkedIn sets the lidc cookie to facilitate data center selection. * Cookie brw * Duration 1 year * Description No description available. * Cookie brwConsent * Duration 5 minutes * Description Description is currently not available. * Cookie WMF-Uniq * Duration 1 year * Description Description is currently not available. * Cookie loom_anon_comment * Duration 1 year * Description No description available. * Cookie loom_referral_video * Duration session * Description Description is currently not available. * Cookie VISITOR_INFO1_LIVE * Duration 6 months * Description A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. * Cookie yt-remote-connected-devices * Duration Never Expires * Description YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. * Cookie ytidb::LAST_RESULT_ENTRY_KEY * Duration Never Expires * Description The cookie ytidb::LAST_RESULT_ENTRY_KEY is used by YouTube to store the last search result entry that was clicked by the user. This information is used to improve the user experience by providing more relevant search results in the future. * Cookie yt-remote-device-id * Duration Never Expires * Description YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. * Cookie yt-remote-session-name * Duration session * Description The yt-remote-session-name cookie is used by YouTube to store the user's video player preferences using embedded YouTube video. * Cookie yt-remote-fast-check-period * Duration session * Description The yt-remote-fast-check-period cookie is used by YouTube to store the user's video player preferences for embedded YouTube videos. * Cookie yt-remote-session-app * Duration session * Description The yt-remote-session-app cookie is used by YouTube to store user preferences and information about the interface of the embedded YouTube video player. * Cookie yt-remote-cast-available * Duration session * Description The yt-remote-cast-available cookie is used to store the user's preferences regarding whether casting is available on their YouTube video player. * Cookie yt-remote-cast-installed * Duration session * Description The yt-remote-cast-installed cookie is used to store the user's video player preferences using embedded YouTube video. * Cookie cp_session * Duration 3 months * Description Codepen sets this cookie for Help systems found in the website. * Cookie loid * Duration 1 year 1 month 4 days * Description This cookie is set by the Reddit. The cookie enables the sharing of content from the website onto the social media platform. Analytics Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc. * Cookie __hstc * Duration 6 months * Description Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). * Cookie hubspotutk * Duration 6 months * Description HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. * Cookie _ga * Duration 1 year 1 month 4 days * Description Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. * Cookie _ga_* * Duration 1 year 1 month 4 days * Description Google Analytics sets this cookie to store and count page views. * Cookie __Host-psifi.analyticsTrace * Duration 6 hours * Description Description is currently not available. * Cookie __Host-psifi.analyticsTraceV2 * Duration 6 hours * Description Description is currently not available. * Cookie _gh_sess * Duration session * Description GitHub sets this cookie for temporary application and framework state between pages like what step the user is on in a multiple step form. * Cookie YSC * Duration session * Description YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. * Cookie ajs_anonymous_id * Duration 1 year * Description This cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before. * Cookie vuid * Duration 1 year 1 month 4 days * Description Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. Performance Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors. * Cookie AWSALB * Duration 7 days * Description AWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target. * Cookie acq * Duration past * Description Description is currently not available. * Cookie acq.sig * Duration past * Description Description is currently not available. * Cookie ptc * Duration 2 years * Description No description available. Advertisement Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns. * Cookie muc_ads * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to collect user behaviour and interaction data to optimize the website. * Cookie guest_id_marketing * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. * Cookie guest_id_ads * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. * Cookie personalization_id * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to integrate and share features for social media and also store information about how the user uses the website, for tracking and targeting. * Cookie guest_id * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. It registers if a user is signed in to the Twitter platform and collects information about ad preferences. * Cookie bcookie * Duration 1 year * Description LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs. * Cookie __Secure-ROLLOUT_TOKEN * Duration 6 months * Description YouTube sets this cookie to manage feature rollout and experimentation. It helps Google control which new features or interface changes are shown to users as part of testing and staged rollouts, ensuring consistent experience for a given user during an experiment. * Cookie yt.innertube::nextId * Duration Never Expires * Description YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. * Cookie yt.innertube::requests * Duration Never Expires * Description YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. * Cookie session_tracker * Duration session * Description This cookie is set by the Reddit. This cookie is used to identify trusted web traffic. It also helps in adverstising on the website. * Cookie edgebucket * Duration session * Description Reddit sets this cookie to save the information about a log-on Reddit user, for the purpose of advertisement recommendations and updating the content. * Cookie did * Duration 1 year * Description Arbor sets this cookie to show targeted ads to site visitors.This cookie expires after 2 months or 1 year. Uncategorised Other uncategorised cookies are those that are being analysed and have not been classified into a category as yet. No cookies to display. Reject All Save My Preferences Accept All Toggle Search[](https://towardsdatascience.com/)Toggle Mobile Navigation [](https://towardsdatascience.com/) Publish AI, ML & data-science insights to a global community of data professionals. Sign in[Submit an Article](https://write.insightmediagroup.io) [Latest](https://towardsdatascience.com/latest/)[Editor's Picks](https://towardsdatascience.com/tag/editors-pick/)[Newsletter](https://towardsdatascience.com/tag/the-variable/)[ShipAI](https://towardsdatascience.com/shipai/) * * * [Write For TDS](https://towardsdatascience.com/submissions/) [LinkedIn](https://www.linkedin.com/company/towards-data-science/)[X](https://x.com/TDataScience)Toggle Search [Analytics](https://towardsdatascience.com/category/data-science/analytics/) # Layers of Data Quality Where and how to address problems with your data [Chad Isenberg](https://towardsdatascience.com/author/cisenbe/) July 18, 20238 min read ![](../images/000.jpg) With the recent surge of interest in generative AI and LLMs, data quality has received a resurgence of interest. Not that the space needed much help: companies like [Monte Carlo](https://www.montecarlodata.com/), [Soda](https://www.soda.io/), [Bigeye](https://www.bigeye.com/), [Sifflet](https://www.siffletdata.com/), [Great Expectations](https://greatexpectations.io/), and [dbt Labs](https://www.getdbt.com/) have been developing a range of solutions, from proprietary to open core. While some of these solutions are direct competitors, they don't all address the same problems. For example, defining an explicit [dbt test](https://docs.getdbt.com/docs/build/tests) to ensure that a column contains unique values is very different from anomaly detection on metrics (e. g., your dim_orders process generated 500,000 records one day, when it's usually more like 50,000). Data can fail in spectacular and myriad ways. You've probably heard of data quality dimensions; I particularly like [Richard Farnworth](https://towardsdatascience.com/layers-of-data-quality-320bf3770db5/None)'s [take](https://towardsdatascience.com/the-six-dimensions-of-data-quality-and-how-to-deal-with-them-bdcf9a3dba71)¹, but a quick Google search will yield dozens of different opinions. At the core, though, the idea is that data can be "right" in one aspect but wrong in others. If your data is correct but late, is it valuable? What if the numbers are objectively wrong, but they're [consistent](https://benn.substack.com/p/all-i-want-is-to-know-whats-different)²? This is an important aspect of data product management and identifying your stakeholders' priorities. There's a lot of focus on how data is malformed, missing, late, incomplete, etc., and less attention is given to the root causes of data quality issues. We spend an inordinate amount of time testing and observing the data itself rather than seeking improvement in the systems that produce, transform, and use that data. I want to explore these "layers" of data quality issues, solutions, and the teams who should be involved in resolving problems related to them. Learn this step by step with the interactive [Data Analyst](https://roadmap.sh/data-analyst) and [Data Engineer](https://roadmap.sh/data-engineer) roadmaps. ## Layer 1: Data Production All data comes from somewhere, and the source is frequently the root cause of data quality issues. Following the principle of garbage in, garbage out, you can't make useful data products from poor source system data. This layer has three fundamental sources of data quality issues: schema drift, semantic drift, and system availability and reliability. They're all extremely important, but they lead to different data quality failures. What's more is that they need different solutions, and frequently, different teams have to engaged to resolve them. Schema changes are in many ways the simplest to identify and resolve. If product engineers, either in-house or through a vendor, change the schema of a table you're using, your downstream processes may just break. This tends to be less of an issue with SaaS APIs since they follow a more mature change management protocol. This isn't a slight at developers, however; frequently, these internal teams don't even know that downstream teams are using their data assets. Schema changes that break ETL processes are frequently a symptom of poor organizational communication. Semantic drift is more pernicious and has more exposure across the enterprise. What if your development team changes the unit of measure for a field? Or what if they change the values that will be populated into a field via a dropdown menu? Your product isn't the only thing that's exposed. Operations teams for enterprise systems like SFDC, Zuora, NetSuite, and Zendesk may likewise change how they use their operational systems, and this can have an impact. Data quality issues can also be entirely accidental; I think we've all seen the poor sales rep who entered a multi-billion dollar deal through a typo. What's really fun is that you may have a combination of schema change and semantic drift; for example, _is_enterprise _customer_ has replaced a valid value of 'Enterprise' in the _customer _type_ field. As with schema changes, communication is the missing piece. Finally, there's the issue of source system availability and reliability. If the source system is down, data may not be generated for a period of time. Depending on the architecture, data may still be generated, but the endpoint for retrieval may be down. In these cases, the data quality failure is categorically different from schema changes and semantic drift. [Chad Sanderson](https://towardsdatascience.com/layers-of-data-quality-320bf3770db5/None) has been a champion for the idea of [data contracts](https://dataproducts.substack.com/p/data-contracts-for-the-warehouse)³: formal, programatically-enforced definitions of data as it's emitted from (usually) operational systems. Data contracts are a good starting point to addressing both schema changes and some types of semantic drift. Note that data contracts don't address SaaS operations teams; they need a separate system for change management. Product teams are familiar with observability and monitoring solutions like [Datadog ](https://www.datadoghq.com/)and [Splunk](https://www.splunk.com/). SaaS vendors typically have status portals, and some offer notifications when services are down. The challenge is that frequently, these systems outages never make it past their development and / or operations teams, even though they're vital to downstream data teams. Creating good processes to communicate outages and issues across the organization is just as important as the observability systems that give us that visibility in the first place. **Interventions** : data contracts, communication channels, change management, systems observability and monitoring **and** communication to downstream consumers **Go-to teams** : product engineers, SaaS systems operators (e. g., AR specialists, account executives), platform engineers, platform operators (e. g., SaaS admins, SaaS business analysts) ## Layer 2: Data Processing - Extract / Transform Let's say the source system data is pristine, or at least clean enough to be usable. There's still a lot that can go wrong. This time, we have exposure on three fronts: logical errors in development, low-resiliency design, and platform stability. When developing a data pipeline, sometimes we get it wrong. Maybe Airflow tasks don't have the proper dependencies established, or perhaps an analytics engineer made a mistake in a join. Depending on the specific error, the outcome could be the pipeline breaking entirely (usually in dramatic and fiery fashion); however, subtle logical bugs can exist in systems for years, either slightly affecting metrics all of the time, or rarely affecting metrics in a big way. During the requirements gathering process, it's essential to know what your stakeholders' priorities are. In some cases, it's critical to fail a pipeline if data is missing or has some kind of quality issue. In other cases, speed of delivery matters more than absolute accuracy. On the other end, is it OK to show partial or incomplete data, or should we only show all data once it's been processed for a given period? Misalignment between data product teams and stakeholders can mean that we're not meeting expectations. Then, there's the reality that as with products and SaaS solutions, our data pipelines actually run on platforms. What if Snowflake is down? What if there's a bug in BigQuery or EMR that affects resource allocation? These things happen, and while platform teams may be aware, there's still that communications / visibility gap to downstream teams. Solutions are plentiful but not necessarily easy to implement. Strategies like [unit testing](https://medium.com/towards-data-science/the-sql-unit-testing-landscape-2023-7a8c5f986dd3) and integrations testing are vital to catching bugs before they hit production. Tooling in the data space still lags the broader software engineering ecosystem, and data team culture is still catching up, too. On the other hand, many of the observability solutions that apply to source systems also apply to data processing systems. The sticking point, however, is making sure that this visibility is shared throughout the organization. Communications can be made through notifications channels or dashboards, but regardless of approach, we need to make sure impacted teams know what's going on. It's also worth calling out that the same issues caused by data producers applies to core asset developers, too; their consumers like analysts, data scientists, and BI developers are just as vulnerable to schema changes, semantic drift, and systems (ETL) outages. **Interventions** : unit testing, integrations testing, clear design documentation, communication channels, change management **Go-to teams** : data engineers, analytics engineers, data platform engineers ## Layer 3: Data Consumption - Analytics, AI and ML In the last mile between data and information, there's still plenty of room for mistakes. Here, the questions are less about how the data is being handled, produced, and transformed, and more about how it's being understood and used. Specifically, I want to focus on errors in applying techniques and misunderstandings of the data itself. Statistics, ML, and AI are complicated. Like really, really complicated. There are a tons of considerations when choosing models: whether your variables are continuous or discrete, the distribution of your data, heteroskedasticity, sample size, and dozens if not hundreds of others. Even if you make all of the right decisions, there may be obscure implementation bugs in your [ML library](https://github.com/scikit-learn/scikit-learn/issues/26502). A data consumer can also just not understand the context of upstream data. Maybe they didn't check the data catalog, or maybe there's not a data catalog at all. Familiarity with a data asset is vital but not always enough to avoid making these kinds of mistakes and ultimately drawing incorrect conclusions. Also, there's no guarantee that someone in the business is going to interpret a dashboard, analysis, or report correctly. This isn't necessarily through malicious intent, either. Most people who are consuming data have jobs outside of the data. Data teams are often so deep in the trenches that they fail to understand where metrics may be unclear. You'll probably spot the theme by now, but the solutions here are people-centric. Folks hired into advanced analytics and ML roles need the right training and experience to succeed. As to creating products on top of established assets, data catalogs and even just conversations with data asset owners can be a huge help. Finally, making sure that artifacts like dashboards and reports are clear is essential, and warm handoffs / stakeholder education are even better. **Interventions** : Data catalogs, dashboard labels, stakeholder education, practitioner education and training **Go-to teams** : data analysts, data scientists, BI developers, ML engineers ## Conclusion While it's important to realize all of the different ways that your data can be wrong (dimensions), it's also really important to understand how and where it can be wrong, too (layers). We talked about errors at the source (Layer 1), during data processing (Layer 2), and during consumption (Layer 3). We also talked about interventions and which teams are closest to the problem and the solution. Data quality is vital to getting value from your data, whether that be through analytics, automation, or an external data product. Data quality dimensions help us identify the axes on which our data is failing us; is it stale? Is it wrong? But it's equally important to understand why our data is failing us. The "why" is what gives us insight into solutions, either for immediate remediation or longer-term, systemic corrections. * * * ¹Richard Farnworth. (June 28, 2020). _The Six Dimensions of Data Quality - and how to deal with them_. [](https://towardsdatascience.com/the-six-dimensions-of-data-quality-and-how-to-deal-with-them-bdcf9a3dba71) ²Benn Stancil. (Jun 9, 2023). _All I want to know is what's different_. [](https://benn.substack.com/p/all-i-want-is-to-know-whats-different) ³Chad Sanderson. (January 25, 2023). _Data Contracts for the Warehouse._ [](https://dataproducts.substack.com/p/data-contracts-for-the-warehouse) ## Register Now to Continue Reading ### Unlock Towards Data Science with a Free Account All articles on Towards Data Science are available to registered users. Create a free account today to access this article and thousands more. Register for freeSign in to your account * * * ![](../images/body-9e4c3e3de7a22688d8ce.jpeg) Written By ## [Chad Isenberg](https://towardsdatascience.com/author/cisenbe/) [See all from Chad Isenberg](https://towardsdatascience.com/author/cisenbe/) [Editor's Picks](https://towardsdatascience.com/tag/editors-pick/)[Analytics](https://towardsdatascience.com/tag/analytics/)[Data](https://towardsdatascience.com/tag/data/)[Data Engineering](https://towardsdatascience.com/tag/data-engineering/)[Data Quality](https://towardsdatascience.com/tag/data-quality/) Share This Article * [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Ftowardsdatascience.com%2Flayers-of-data-quality-320bf3770db5%2F&title=Layers%20of%20Data%20Quality) * [](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Ftowardsdatascience.com%2Flayers-of-data-quality-320bf3770db5%2F&title=Layers%20of%20Data%20Quality) * [](https://x.com/share?url=https%3A%2F%2Ftowardsdatascience.com%2Flayers-of-data-quality-320bf3770db5%2F&text=Layers%20of%20Data%20Quality) Towards Data Science is a community publication. Submit your insights to reach our global audience and earn through the TDS Author Payment Program. [Write for TDS](https://towardsdatascience.com/submissions/) ## Related Articles * [![](../images/001.jpg)](https://towardsdatascience.com/building-a-data-pipeline-for-my-strava-data-98ea8b2b0767/) ## [Building a Data Pipeline for My Strava Data](https://towardsdatascience.com/building-a-data-pipeline-for-my-strava-data-98ea8b2b0767/) [Data Engineering](https://towardsdatascience.com/category/data-science/data-engineering/) EtLT of my own Strava data using the Strava API, MySQL, Python, S3, Redshift, and Airflow [Jack Leitch](https://towardsdatascience.com/author/jackmleitch/) June 21, 20226 min read * [![](../images/002.jpg)](https://towardsdatascience.com/data-pipeline-with-airflow-and-aws-tools-s3-lambda-glue-18585d269761/) ## [Data Pipeline with Airflow and AWS Tools (S3, Lambda & Glue)](https://towardsdatascience.com/data-pipeline-with-airflow-and-aws-tools-s3-lambda-glue-18585d269761/) [Data Engineering](https://towardsdatascience.com/category/data-science/data-engineering/) Learning a little about these tools and how to integrate them [João Pedro](https://towardsdatascience.com/author/joaopedro214/) April 6, 202317 min read * [![](../images/003.jpeg)](https://towardsdatascience.com/2-silent-pyspark-mistakes-you-should-be-aware-of-de52c3a188c4/) ## [2 Silent PySpark Mistakes You Should Be Aware Of](https://towardsdatascience.com/2-silent-pyspark-mistakes-you-should-be-aware-of-de52c3a188c4/) [Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/) Small mistakes can lead to severe consequences when working with large datasets. [Soner Yıldırım](https://towardsdatascience.com/author/sonery/) February 16, 20245 min read * [![](../images/004.jpg)](https://towardsdatascience.com/product-case-interviews-dos-and-donts-for-data-scientists-71f9f90b033f/) ## [Product Case Interviews Dos and Don'ts for Data Scientists](https://towardsdatascience.com/product-case-interviews-dos-and-donts-for-data-scientists-71f9f90b033f/) [Data Science](https://towardsdatascience.com/category/data-science/) How to make a great impression in product case interviews [Emma Ding](https://towardsdatascience.com/author/emmading/) December 16, 202111 min read * [![](../images/005.jpg)](https://towardsdatascience.com/building-enterprise-agent-systems-that-people-can-trust-verify-and-improve/) ## [Building Enterprise Agent Systems that People can Trust, Verify and Improve](https://towardsdatascience.com/building-enterprise-agent-systems-that-people-can-trust-verify-and-improve/) [Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/) 5 principles that determine whether an agent system succeeds in production, explained through one I built for a $100M+ company. [Sheila Teo](https://towardsdatascience.com/author/sheilateozy/) August 18, 202614 min read * [![](../images/006.jpeg)](https://towardsdatascience.com/microservices-vs-monolithic-approaches-in-data-8d9d9a064d06/) ## [Microservices vs. Monolithic Approaches in Data](https://towardsdatascience.com/microservices-vs-monolithic-approaches-in-data-8d9d9a064d06/) [Software Engineering](https://towardsdatascience.com/category/programming/software-engineering/) The Microservice vs. Monolith debate rages in software, but is reduced to a gentle simmer in the data world [Hugo Lu](https://towardsdatascience.com/author/hugolu87/) February 16, 20249 min read * [![](../images/007.jpg)](https://towardsdatascience.com/dynamic-pricing-with-contextual-bandits-learning-by-doing-b88e49f55894/) ## [Dynamic Pricing with Contextual Bandits: Learning by Doing](https://towardsdatascience.com/dynamic-pricing-with-contextual-bandits-learning-by-doing-b88e49f55894/) [](https://towardsdatascience.com/layers-of-data-quality-320bf3770db5/) Adding context to your dynamic pricing problem can increase opportunities as well as challenges [Massimiliano Costacurta](https://towardsdatascience.com/author/massi.costacurta/) October 5, 20236 min read * [![](../images/008.jpg)](https://towardsdatascience.com/big-data-file-formats-explained-275876dc1fc9/) ## [Big Data File Formats, Explained](https://towardsdatascience.com/big-data-file-formats-explained-275876dc1fc9/) [Data Engineering](https://towardsdatascience.com/category/data-science/data-engineering/) Parquet vs ORC vs AVRO vs JSON. Which one to choose and how to use them? [Mike Shakhomirov](https://towardsdatascience.com/author/mshakhomirov/) February 28, 20239 min read * [![](../images/009.png)](https://towardsdatascience.com/prototyping-machine-learning-solutions-in-globe-scale-industries-fff46ad8ade0/) ## [Prototyping Machine Learning Solutions in Globe-scale Industries](https://towardsdatascience.com/prototyping-machine-learning-solutions-in-globe-scale-industries-fff46ad8ade0/) [Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/) How to prototype machine learning solutions in globe-scale industries efficiently using a few repeatable techniques [Misbah Uddin](https://towardsdatascience.com/author/misbahuddins/) September 19, 20215 min read * [YouTube](https://www.youtube.com/c/TowardsDataScience) * [X](https://x.com/TDataScience) * [LinkedIn](https://www.linkedin.com/company/towards-data-science/) * [Threads](https://www.threads.net/@towardsdatascience) * [Bluesky](https://bsky.app/profile/towardsdatascience.com) [](https://towardsdatascience.com/) Your home for data science and AI. The world's leading publication for data science, data analytics, data engineering, machine learning, and artificial intelligence professionals. Subscribe to Our Newsletter[Write For TDS](https://towardsdatascience.com/submissions/)•[About](https://towardsdatascience.com/about-towards-data-science-d691af11cc2f/)•[Advertise](https://contact.towardsdatascience.com/advertise-with-towards-data-science)•[Privacy Policy](https://towardsdatascience.com/privacy-policy/)•[Terms of Use](https://towardsdatascience.com/website-terms-of-use/) © Insight Media Group, LLC 2026•[The New Stack](https://thenewstack.io)•[roadmap.sh](https://roadmap.sh)•[Creator Network](https://insightmediagroup.io/creator-network) #### Recommended Articles Close * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607686/image?etag=1782161464448&width=500&height=500) How Relevance Models Foreshadowed Transformers for NLP ](https://towardsdatascience.com/how-relevance-models-foreshadowed-transformers-for-nlp/ "How Relevance Models Foreshadowed Transformers for NLP") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607639/image?etag=1781250125848&width=500&height=500) Javascript Fatigue: HTMX Is All You Need to Build ChatGPT — Part 1 ](https://towardsdatascience.com/javascript-fatigue-you-dont-need-js-to-build-chatgpt/ "Javascript Fatigue: HTMX Is All You Need to Build ChatGPT — Part 1") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607930/image?etag=1782124566054&width=500&height=500) The Subset Sum Problem Solved in Linear Time for Dense Enough Inputs ](https://towardsdatascience.com/subset-sum-problem-solved-in-linear-time-for-dense-enough-inputs/ "The Subset Sum Problem Solved in Linear Time for Dense Enough Inputs") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/3660/image?etag=1780176246070&width=500&height=500) Does Your Company Have a Data Strategy? ](https://towardsdatascience.com/does-your-company-have-a-data-strategy-e8944dbec4ae/ "Does Your Company Have a Data Strategy?")