A tailored course, built for your situation
The Go-To Practitioner in DBT & Data Modeling
Become the recognized expert your team turns to for clean, reliable data models and reusable transformation patterns
The situation this course is for
Even with strong technical skills, data engineers often stay invisible when architecture decisions are made, especially when those decisions depend on deep understanding of transformation logic and model reliability.
Who this is for
Senior IC data engineer working in DBT and Snowflake, focused on delivering trusted models and scalable pipelines, seeking greater influence through technical authority.
Who this is not for
Engineers who only run queries or maintain dashboards without ownership of transformation logic or data modeling.
What you walk away with
- Proven frameworks for structuring models that others adopt as standard
- Templates for documenting lineage and logic that stakeholders trust
- Patterns for socializing changes before they break downstream
- A repeatable method to turn one-off fixes into system-wide improvements
- Clear examples and artifacts to back up your position in design reviews
The 12 modules (with all 144 chapters)
- The recognition gap in data engineering
- Signals teams trust a modeler
- From builder to reference point
- Three traits of go-to modelers
- How recognition starts with reliability
- Documenting to be found
- Naming conventions that scale trust
- Ownership beyond assignment
- Patterns over projects
- The visibility flywheel
- Recognition without self-promotion
- Case study: the quiet architect
- Designing for downstream pickup
- Modular logic blocks
- Reusable CTEs by convention
- Naming for discoverability
- Embedding assumptions safely
- Avoiding over-generalization
- The reuse threshold
- When to extend vs. rewrite
- Annotating for adoption
- Testing across contexts
- Versioning shared logic
- Case study: reused fact model
- Common logic anti-patterns
- When to use exposures
- Refactoring without breaking
- Leveraging macros wisely
- Error handling in Jinja
- The case for standard tests
- Managing dependencies clearly
- Source freshness checks
- Documentation as control
- Code reviews that teach
- Preempting logic disputes
- Case study: macro overhaul
- Docs read by non-engineers
- Describing intent clearly
- Linking to business outcomes
- Auto-documentation settings
- Embedding data quality notes
- Using descriptions as contracts
- Finding the doc minimum
- Standardizing doc patterns
- Updating without churn
- Docs in PR templates
- When to link vs. copy
- Case study: trusted source doc
- Change timing signals
- Previewing with stakeholders
- Using snapshots wisely
- Communicating model shifts
- Messaging upstream impacts
- Running design reviews
- Handling pushback calmly
- Creating feedback loops
- Maintaining changelogs
- Tagging for visibility
- Routing through data stewards
- Case study: major refactoring
- Mapping business terms to fields
- Using meta fields effectively
- Tagging for compliance
- Generating lineage reports
- Reducing investigation time
- Cross-model impact analysis
- Auditor-ready documentation
- Testing traceability paths
- Versioned lineage exports
- Linking to data dictionary
- Handling deprecations
- Case study: audit response
- Base test suite structure
- Custom test macros
- Data completeness checks
- Referential integrity rules
- Schema change detection
- Testing nullability assumptions
- Automated anomaly alerts
- Integrating with CI
- Test coverage targets
- Balancing rigor and speed
- Documentation via tests
- Case study: test suite rollout
- Spotting silent debt
- Volunteering strategically
- Building credibility quietly
- Handling overlap gracefully
- Escalating with context
- Maintaining ownership logs
- Using Slack for visibility
- Documenting decisions publicly
- Setting modeling standards
- Mentoring by example
- Avoiding overreach
- Case study: ownership claim
- Preparing for review cycles
- Bringing precedent examples
- Framing alternatives clearly
- Challenging with data
- Using diagrams effectively
- Aligning with business goals
- Anticipating objections
- Staying constructive under pressure
- Driving consensus quietly
- Summarizing decisions
- Following up without nagging
- Case study: winning a redesign
- Creating starter kits
- Standardizing project setups
- Internal template library
- Onboarding new hires
- Sharing snippets efficiently
- Running knowledge shares
- Measuring adoption
- Improving iteratively
- Linking to on-call
- Reducing ramp time
- Building internal reputation
- Case study: onboarding package
- Connecting models to business impact
- Highlighting efficiency gains
- Writing executive summaries
- Using metrics to tell stories
- Presenting in cross-functional forums
- Attributing data quality wins
- Avoiding overstatement
- Staying grounded in delivery
- Letting results speak
- Timing visibility moments
- Handling recognition gracefully
- Case study: exec mention
- Auditing your current reach
- Setting a recognition goal
- Tracking peer adoption
- Refining your signature style
- Maintaining consistency
- Adapting to new domains
- Extending influence upward
- Mentoring emerging talent
- Sustaining authority
- Measuring long-term impact
- Staying ahead of changes
- Case study: became the reference
How this maps to your situation
- When a new data product launches and modeling standards are set
- During performance reviews where influence is assessed
- After a data incident when root cause analysis begins
- Before major refactor or migration efforts
Before vs. after
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: Approximately 2 hours per week over 6 weeks, with self-paced access.
How this compares to the alternatives
Generic data courses teach broad DBT syntax. This course focuses on the unspoken skills that make practitioners indispensable: reuse, influence, and quiet authority in modeling decisions.
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.