Training course · Cursor · Data Engineering

Cursor for Data Engineers

Work productively with the AI code editor Cursor: agent mode, rules, codebase context, Tab completion, background agents and review.

Duration
2 days (14 hrs)
Format
Online or on-site
Language
German or English
Participants
open dates or exclusive for your team
Certificate
Certificate of attendance

Overview

This course connects Cursor with the everyday processes of Data Engineering. Participants work on realistic scenarios and leave with prompts, workflows and checklists they can use straight away.

Cursor is an AI code editor built on VS Code that weaves language models deeply into everyday development. Alongside context-aware Tab completion, it offers an agent mode that searches files on its own, plans changes across the whole project, runs terminal commands and fixes errors iteratively. In this two-day course you will learn to use Cursor with purpose: choosing the right interaction mode, steering context deliberately and combining AI assistance with your existing workflow of version control, automated testing and peer code review.

A key focus is making Cursor work for teams. Project rules let you capture architectural decisions, naming conventions and testing strategies so that the agent produces consistent results. You will learn to make good use of codebase indexing, targeted references to files, documentation and symbols, and MCP integrations. You will also delegate tasks to background agents, review their output as pull requests and set up a review process that takes quality, security and data protection seriously across the organisation.

Data engineers build and run the pipelines that reporting, analytics and AI applications depend on: ingestion from source systems, transformations in dbt or Spark, orchestration with Airflow or Dagster, and data quality and governance in the warehouse or lakehouse. Much of the work involves SQL, Python, YAML and a great deal of detailed knowledge about schemas and dependencies. AI coding assistants and agents accelerate this work considerably: they write dbt models with tests and documentation, optimise slow queries, create Airflow DAGs, migrate legacy ETL and explain complex lineage. Because data is often sensitive, handling schemas, sample data and credentials responsibly is at the heart of this course.

The course is delivered live – either online in a virtual classroom or on-site in our training rooms in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart and Kaiserslautern. We can also run it exclusively for your team.

Who is this course for?

  • Data engineers and analytics engineers
  • BI developers responsible for ETL and the data warehouse
  • Platform teams running lakehouse and streaming infrastructure
  • Developers modernising legacy ETL processes

Typical challenges we address

  • Ageing ETL built on stored procedures or proprietary tools with no tests
  • Slow, expensive queries and inefficient Spark jobs
  • Missing data quality checks and unclear ownership of datasets
  • Patchy documentation of data models, lineage and business logic

What you will be able to do

  • You choose the right Cursor mode for each task and use it efficiently.
  • You steer codebase context precisely and get more accurate suggestions as a result.
  • You write project rules that reliably enforce your team’s conventions.
  • You use agent mode and background agents for features and refactorings with verifiable results.
  • Use AI agents productively for dbt models, pipelines and SQL optimisation.
  • Modernise legacy ETL with AI support and safeguard results with reconciliation tests.
  • Protect sensitive data by working with schemas, synthetic samples and minimal access rights.

Course outline

Day 1

Module 1 Setting up Cursor and understanding its modes
  • Installation and migration of VS Code settings and extensions
  • Differences between Tab completion, inline edits, Ask mode and Agent mode
  • Choosing a model per task: balancing speed, depth and cost
  • Privacy mode and organisation-level settings
Module 2 Steering codebase context
  • How codebase indexing works and where its limits lie
  • Referencing files, folders, symbols, documentation and web sources precisely
  • Using ignore files to exclude sensitive or irrelevant content
  • Avoiding overlong chats and restarting tasks with fresh context
Module 3 Rules for consistent team results
  • Creating and versioning project rules and scoping them by file pattern
  • Expressing architecture, style and testing conventions as effective rules
  • Separating user rules from team rules
  • Refining rules iteratively based on the agent’s typical mistakes
Module 4 Agent mode in practice
  • Building features step by step with plan, implementation and tests
  • Running multi-file refactorings safely with checkpoints
  • Approving terminal commands deliberately and feeding error output back
  • Connecting MCP servers for issue trackers, databases or browser testing

Day 2

Module 5 Background agents, review and governance
  • Delegating tasks to background agents and running them in parallel
  • Reviewing results as branches or pull requests and steering follow-ups
  • Using AI-assisted code review alongside human review
  • Addressing security risks, secrets and licensing in enterprise use
Module 6 Practice lab: Data Engineering
  • dbt models with tests
  • Optimising SQL queries
  • Airflow and Dagster pipelines
  • Migrating legacy ETL
  • Automating data quality
  • Analysing Spark jobs
Module 7 Data protection, quality & transfer to daily work
  • Data engineering prompts should contain schemas and synthetic sample data rather than real personal records, and database credentials or connection strings must stay out of context. Apply GDPR principles such as purpose limitation and data minimisation, document data flows transparently and check new Python packages and connectors for licensing and supply-chain risk.
  • Ground rules for safe AI use in your team
  • Checking results: facts, sources, tests and the four-eyes principle
  • Personal action plan for the next 30 days
  • Open questions, outlook and resources for further learning

Practical scenarios from your field

dbt models with tests

The agent writes staging, intermediate and mart models in dbt, adds schema tests, source definitions and descriptions, and runs dbt build iteratively until models and tests pass.

Optimising SQL queries

The AI analyses execution plans, spots expensive joins and missing partitioning or clustering, and rewrites queries so they scan less data and run measurably faster.

Airflow and Dagster pipelines

Requirements become DAGs or assets with a clean dependency structure, retries, sensors, alerting and backfill support, along with tests for the transformation logic. Existing naming conventions are respected.

Migrating legacy ETL

Stored procedures or graphical ETL jobs are analysed, the business logic documented and moved step by step into dbt or PySpark code, safeguarded by reconciliation queries comparing old and new.

Automating data quality

The assistant defines checks for completeness, uniqueness, value ranges and freshness, implements them with dbt tests or Great Expectations and sets up notifications for violations.

Analysing Spark jobs

Spark UI information and logs are interpreted, skew, shuffles and memory issues identified and optimisations such as broadcast joins, repartitioning or caching proposed. Every optimisation is backed by runtime comparisons.

Possible hands-on projects

Data quality dashboard

A small web app that reads results from dbt tests or data quality checks and presents trends, outliers and affected tables at a glance.

Ingestion pipeline for a REST API

A Python pipeline that loads data incrementally from an API, detects schema changes and writes the results as partitioned tables to the lakehouse.

Lineage explorer

A tool that parses the dbt manifest and displays dependencies between sources, models and dashboards as an interactive graph. The impact of changes becomes visible at a glance.

Prerequisites

You program regularly in at least one language and are familiar with Git and an IDE such as VS Code. Confident SQL and Python skills plus practical experience with a data warehouse, dbt, Spark or an orchestration tool.

Technical requirements

Your own laptop with Cursor, Git and your usual development environment installed; a Cursor account with access to agent features is recommended.

Data protection & compliance

Data engineering prompts should contain schemas and synthetic sample data rather than real personal records, and database credentials or connection strings must stay out of context. Apply GDPR principles such as purpose limitation and data minimisation, document data flows transparently and check new Python packages and connectors for licensing and supply-chain risk.

Suggested dates

All dates are suggestions – your preferred date is always possible.

  • Mon, 23 November 2026 – Tue, 24 November 2026 Online Request
  • Mon, 30 November 2026 – Tue, 1 December 2026 Augsburg Request
  • Wed, 16 December 2026 – Thu, 17 December 2026 Online Request
  • Wed, 13 January 2027 – Thu, 14 January 2027 Online Request
  • Wed, 27 January 2027 – Thu, 28 January 2027 Kaiserslautern Request
  • Mon, 1 February 2027 – Tue, 2 February 2027 Online Request

Frequently asked questions

Do I need prior VS Code experience to use Cursor?

It helps, but it is not essential. Cursor is built on VS Code, so navigation, shortcuts and extensions feel familiar and existing settings can be imported. If you currently work with JetBrains IDEs or other editors, a short introduction during the course gets you up to speed quickly so you can concentrate on the AI features.

How do I prevent confidential code from reaching third parties?

Cursor offers a privacy mode and organisation settings that restrict how code is stored by the provider. You can also use ignore files to exclude sensitive areas from indexing and context. In the course we discuss how to align these options with internal policies, data protection requirements and sound handling of secrets.

What do rules add compared with well-written prompts?

A prompt applies to one request only, whereas rules persist and apply to the whole team. They capture architectural decisions, preferred libraries, testing strategies and style guidelines, so nobody has to repeat that information and the agent produces code that fits your codebase. Rules are versioned with the project and evolve together with it.

Does the AI need access to our production data?

No, and it usually makes little sense. For the vast majority of tasks, schemas, metadata, execution plans and synthetic sample data are sufficient. On the course you learn to give the agent exactly this context, restrict read access to development environments and still obtain reliable results.

Will this work with our data warehouse?

The working methods are platform-independent and apply equally to Snowflake, BigQuery, Databricks, Redshift, Synapse or PostgreSQL. What matters is telling the assistant about the SQL dialect and platform specifics such as partitioning or clustering. We show you how to capture this in instruction files.

How much does “Cursor for Data Engineers” cost?

The course costs a flat €949 plus VAT per participant – whether online or on-site. This includes 2 training day(s) with a live trainer, course materials, a lab environment and a certificate of attendance.

Can I suggest my own date?

Yes. Our suggested dates are just a guide. In the request form you can always describe your preferred date or period in free text – we check availability and confirm within one working day.

Is the course online or on-site?

Both are possible: live online in a virtual classroom or on-site in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart or Kaiserslautern. We can also run the course exclusively for your team.

More courses for Data Engineers

More Cursor courses

All 32 Cursor courses

Cursor · MunichCursor · SalzburgCursor · BerlinCursor · AugsburgCursor · HanoverCursor · BremenCursor · StuttgartCursor · KaiserslauternCursor · Online