Engineering Habits for Analytics Engineers
Engineering habits are the software practices analytics engineers borrow to keep data work reliable: version control with Git, pull requests and code review, separate development and production environments, and basic continuous integration that runs checks before changes merge.
Stage: Role and Foundations · Part of the Analytics Engineer roadmap · Last reviewed 19 November 2026
What to learn in Engineering Habits
- Create a branch, commit changes and open a pull request
- Review a teammate's SQL change using a checklist
- Keep development and production schemas separate
- Configure CI to run a build on every pull request
- Resolve a merge conflict in a model file
Engineering Habits interview questions
Why do data teams use pull requests?
A pull request lets another person review SQL and logic before it reaches production, catching errors and sharing knowledge. It also runs automated checks and leaves a history of why each change was made.
What does CI add to a data project?
Continuous integration automatically builds and tests changed models on each pull request, often in a temporary schema. It catches broken SQL and failing tests before merge, so production tables are not the first place errors appear.
Where Engineering Habits fits in the Analytics Engineer roadmap
Engineering Habits belongs to the Role and Foundations stage (beginner level), which takes about 6 hours. Where analytics engineering sits.
Other units in this stage
Back to the full Analytics Engineer roadmap