What do you take away from the The next role course?
Define data architecture patterns used across teams Articulate platform evolution strategies that align with enterprise goals Lead technical reviews with engineering leads and infrastructure partners Build reusable design templates that reduce rework Position yourself for principal-level roles with clear differentiation.
How does this map to your situation?
When you're asked to contribute to platform design Before a major system migration begins When new data sources enter the pipeline During cross-team integration planning.
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.
What does the The next role cover on delivery and format?
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 3-4 hours per module, recommended over 6-8 weeks to allow for integration and practice.
How does this compare to the alternatives?
Unlike generic data engineering courses, this program focuses exclusively on the transition from senior individual contributor to principal-level influence , with frameworks used by engineers who've made the leap at top financial institutions.
What does the The next role cover on frequently asked?
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.
How is the The next role delivered?
The The next role is fully self-paced with immediate online access after enrolment. Access does not expire and future updates are included at no cost. A certificate of completion is issued by The Art of Service when you finish.
How much does the The next role cost?
The The next role is $199 as a one time payment. There is no subscription and no hidden fee. Enrolment carries a 30 day satisfied or refunded guarantee, so it can be assessed in full before you commit.
More answers: what you get with every course, refund policy, all help answers.
A tailored course, built for your situation
The next role: principal data systems architect
Move from executing pipelines to defining the data architecture that shapes engineering outcomes across teams
The situation this course is for
Who this is for
Mid-career data engineer in financial services aiming to transition into architecture or platform leadership
Who this is not for
Engineers satisfied with individual contribution work, or those not looking to influence system design beyond their immediate team
What you walk away with
- Define data architecture patterns used across teams
- Articulate platform evolution strategies that align with enterprise goals
- Lead technical reviews with engineering leads and infrastructure partners
- Build reusable design templates that reduce rework
- Position yourself for principal-level roles with clear differentiation
The 12 modules (with all 144 chapters)
- Defining architectural influence
- Spotting design debt early
- Mapping data flow dependencies
- Identifying leverage points
- Aligning with platform goals
- Documenting system intent
- Positioning for expansion
- Creating design clarity
- Reducing ambiguity in specs
- Asking upstream questions
- Framing trade-offs clearly
- Leading without authority
- Choosing storage layers
- Balancing latency and cost
- Evaluating open-source tools
- Designing for extensibility
- Versioning data contracts
- Handling schema evolution
- Assessing vendor solutions
- Benchmarking performance
- Cost modeling architectures
- Documenting rationale clearly
- Creating decision logs
- Reusing evaluation patterns
- Defining contract ownership
- Specifying SLAs clearly
- Setting change management rules
- Versioning contract updates
- Onboarding new consumers
- Monitoring adherence
- Resolving conflicts fairly
- Documenting usage patterns
- Tracking adoption rates
- Negotiating terms upfront
- Reducing integration delays
- Creating template contracts
- Forecasting data growth
- Identifying tech debt hotspots
- Planning phased migrations
- Staging architecture changes
- Aligning with security roadmap
- Integrating observability
- Planning rollback paths
- Coordinating team rollouts
- Timing major changes
- Communicating upgrades
- Measuring migration success
- Building upgrade playbooks
- Framing proposals effectively
- Highlighting risk reduction
- Showing cost efficiency gains
- Tying to business outcomes
- Using data to support claims
- Anticipating objections
- Preparing backup options
- Simplifying complex ideas
- Presenting to leads
- Following up strategically
- Building credibility over time
- Earning recurring input roles
- Spotting repetitive tasks
- Generalizing solutions
- Naming conventions matter
- Building modular components
- Documenting usage rules
- Sharing across teams
- Gathering feedback loops
- Updating pattern versions
- Measuring reuse frequency
- Reducing onboarding time
- Enabling faster delivery
- Tracking pattern adoption
- Setting review expectations
- Preparing review checklists
- Asking clarifying questions
- Identifying scalability risks
- Evaluating failure modes
- Suggesting alternatives
- Providing written feedback
- Summarizing decisions
- Following up on actions
- Improving review efficiency
- Building trust with peers
- Establishing consistency
- Defining domain boundaries
- Mapping data lifecycle stages
- Assigning ownership clearly
- Tracking data lineage fully
- Monitoring data health
- Setting quality thresholds
- Alerting on anomalies
- Driving cleanup initiatives
- Improving metadata richness
- Documenting flow logic
- Reducing technical drift
- Enabling faster audits
- Linking work to speed gains
- Quantifying rework reduction
- Measuring downtime avoided
- Showing cost savings
- Highlighting risk mitigation
- Tying to compliance needs
- Demonstrating scale readiness
- Using metrics consistently
- Creating impact dashboards
- Sharing results proactively
- Positioning for recognition
- Building sponsorship cases
- Delivering on promises
- Writing clear documentation
- Responding to inquiries fast
- Owning mistakes openly
- Improving over time
- Sharing knowledge freely
- Mentoring junior engineers
- Running effective onboarding
- Creating reference examples
- Maintaining standards
- Earning peer respect
- Becoming the go-to person
- Mapping role requirements
- Identifying gaps early
- Showcasing key projects
- Gathering peer feedback
- Requesting stretch assignments
- Documenting impact quantitatively
- Preparing promotion packets
- Timing requests strategically
- Seeking sponsor input
- Refining leadership narrative
- Demonstrating scope growth
- Tracking progression milestones
- Thinking in systems
- Anticipating future needs
- Balancing trade-offs wisely
- Delegating effectively
- Setting strategic goals
- Reviewing team designs
- Guiding technical strategy
- Escalating appropriately
- Protecting team focus
- Driving innovation selectively
- Measuring architectural health
- Sustaining long-term vision
How this maps to your situation
- When you're asked to contribute to platform design
- Before a major system migration begins
- When new data sources enter the pipeline
- During cross-team integration planning
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 3-4 hours per module, recommended over 6-8 weeks to allow for integration and practice.
How this compares to the alternatives
Unlike generic data engineering courses, this program focuses exclusively on the transition from senior individual contributor to principal-level influence , with frameworks used by engineers who've made the leap at top financial institutions.
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.