app-entwickeln-lassen.de LogoApp entwickeln lassen

Agentic Coding

Agentic Coding for Data Analysis and Data Pipelines

app-entwickeln-lassen.de editorial team 6 min read
Contents
  1. Why data work suits coding agents well
  2. Typical use cases at a glance
  3. The core risk: plausibly wrong data
  4. A proven workflow for data pipelines with agents
  5. Data protection and access rights
  6. Exploratory analysis: the agent as analysis assistant
  7. Conclusion
  8. Frequently Asked Questions

Agentic coding speeds up data analysis and building data pipelines considerably: coding agents write SQL queries, transformations, ETL jobs and analysis scripts, run them, check the results and correct themselves. At the same time, the risk here is especially treacherous – wrong data often looks just as plausible as correct data. This article shows how data teams use agents productively and safely.

Why data work suits coding agents well

Many tasks in data engineering and analytics are recurring, highly structured and easy to verify – ideal conditions for agents:

  • Clear languages and patterns: SQL, Python with widely used data libraries and declarative transformation frameworks such as dbt follow established conventions.
  • Fast feedback: a query can be run immediately; the agent sees the result and can improve it.
  • Lots of routine: connecting new data sources, renaming columns, documenting models, adding tests – work that takes time but little creativity.
  • Exploration: when analysing unfamiliar datasets, an agent can test many hypotheses quickly and summarise anomalies.

What matters is that an agent does not just write code but can also run it and check the result. This loop of writing, executing and verifying is what distinguishes agentic coding from a chat that suggests SQL you then have to test yourself.

Typical use cases at a glance

Use caseWhat the agent handlesWhat to watch
SQL queries and reportsWriting, optimising and explaining queriesCheck join logic and filters against business rules
Transformation modelsNew models, refactoring existing ones, documentationGranularity and business logic must be right
ETL and ELT jobsConnectors, load processes, error handling, retry logicIdempotency, handling partial loads
OrchestrationCreating and adjusting workflows in tools such as Airflow or DagsterUnderstand dependencies and schedules
Data quality testsTests for uniqueness, completeness, value rangesProvide business rules, not just technical ones
Exploratory analysisExamining datasets, statistics, visualisationsCritically check conclusions
MigrationsMoving pipelines between platforms or SQL dialectsSystematically compare old and new results

The core risk: plausibly wrong data

Buggy code in an app often crashes visibly. A buggy data pipeline, by contrast, delivers numbers – just the wrong ones. A join that duplicates rows, a filter that forgets cancellations, a time zone that is ignored: without targeted checks, such errors often go unnoticed for a long time and feed into decisions.

Agents are particularly prone to this because they do not know your company's business logic. What counts as an "active customer", how revenue is defined or which test bookings must be filtered out is rarely written in the code. Three ground rules follow:

  1. Document business definitions and give them to the agent as context, for example in a glossary file in the repository.
  2. Set expectations upfront: which row counts, totals and value ranges are plausible? These expectations become tests.
  3. Reconcile results against known values: new pipelines must produce the same metrics for a reference period as existing, verified reports.

A proven workflow for data pipelines with agents

  1. Specification: write down source, target, granularity, business rules and acceptance criteria.
  2. Tests first: define data quality tests and expected results for sample data. The approach matches what we describe in agentic coding and test-driven development.
  3. Implementation in a development environment: the agent works against a copy with test or sample data, never with write access to production data.
  4. Comparison: reconcile results with reference values, have deviations explained and assess them from a business perspective.
  5. Review: a person with domain knowledge checks logic, joins and filters.
  6. Deployment via the pipeline: only reviewed changes reach production through CI/CD.

Data protection and access rights

In data work, the question of what gets sent to a cloud model is particularly relevant. When an agent runs queries and reads results, personal data can end up in the context. Keep the following in mind (this is not legal advice):

  • Work with schemas and synthetic data: for many tasks the agent only needs the table structure and sample data, not real customer records.
  • Restricted read access: access to development or anonymised datasets, no write access to production.
  • Limit result sets: agent queries should default to limits and aggregations rather than full raw data output.
  • Check the contractual basis: if personal data reaches the model provider, GDPR requirements such as data processing agreements and third-country transfers must be addressed.

More in our articles on AI coding tools and data protection and local LLMs for software development, which can be an alternative for highly sensitive data.

Exploratory analysis: the agent as analysis assistant

Beyond pipelines, agents are also useful for ad-hoc analysis. An agent can load a new dataset, describe distributions and outliers, create first visualisations and suggest hypotheses. That saves time in the exploration phase. The key is to keep roles clear: the agent provides material; a human is responsible for interpretation. Always have the agent output the queries and calculation steps it used, so results stay traceable and reproducible.

For data teams that want to learn this way of working in a structured manner, we offer workshops from 799 € net in which AI developers from real-world practice train agentic coding on your own data projects. Details are in our article on agentic coding workshops for data scientists and ML engineers.

Planning an app? Request a free fixed-price quote in 2 minutes

Conclusion

Agentic coding is a major lever for data analysis and data pipelines: SQL, transformations, ETL jobs and tests come together much faster. Because wrong data often goes unnoticed, however, it needs more safeguards than other areas: documented business definitions, tests before implementation, reconciliation against reference values, restricted access rights and a review by someone with domain knowledge. With these guardrails, agents become reliable partners for the data team.

Frequently Asked Questions

Can a coding agent access our production database directly?

We advise against it. Agents should work with development or anonymised data and at most restricted read access; changes reach production through the reviewed pipeline.

How do I spot wrong results from an agent-generated pipeline?

Through data quality tests, expected values defined upfront and reconciliation with existing, verified reports for a reference period.

Is agentic coding suitable for data scientists without deep programming skills?

Yes, especially for exploration and routine tasks. A basic understanding of SQL and data models is still needed to judge the results.

What information does an agent need to build good data pipelines?

Schemas, business definitions, naming conventions, sample data and clear acceptance criteria. The better this context is documented, the more reliable the results.

This article was written by the editorial team of app-entwickeln-lassen.de – the app and AI development service of jocapps GmbH, based in Freiburg, Germany, and building apps since 2014. The content is for general information and does not replace individual (legal) advice.

You might also like

Agentic CodingAgentic Coding and Accessibility: Automating Accessibility Checks

Agentic coding and accessibility: how coding agents find and fix accessibility issues in web and mobile apps – and where manual testing remains indispensable.

6 min read
Agentic CodingThe Agentic Coding Stack 2026: Models, Tools and Integrations

The agentic coding stack for 2026 explained: which layers of models, agents, integrations and guardrails your team really needs and how to choose each one.

7 min read
Agentic CodingBuilding Custom Coding Agents: When Your Own Agents Pay Off

Custom coding agents or adapted standard tools? Criteria, architecture, effort and risks of building your own agents – so you can make the right call.

6 min read
Agentic CodingChange Management: How to Win Your Team Over to Agentic Coding

Change management for agentic coding: how to take developer concerns seriously, build pilot groups and make new ways of working stick across your whole team.

6 min read
Agentic CodingAgentic Coding for Startups: Reaching Your MVP Fast with a Small Team

Agentic coding for startups: how small teams use coding agents to reach an MVP faster, which pitfalls to avoid and when hiring an agency is the smarter route.

6 min read
Agentic CodingAgentic Coding Myths and Facts: 9 Misconceptions Checked

Agentic coding myths fact-checked: what coding agents can do today, where their limits are and which expectations are realistic for your development team.

5 min read