Principal Engineer - Customer Domain & Customer Central
Principal Engineer - Customer Domain & Customer Central
Posted 10 days ago
SENIORITY
Manager
About the role
- Technical leadership: Own the Customer domain technology roadmap, engineering standards, solution design guidance, and alignment with enterprise architecture, security, data, MDM, and governance strategies.
- Customer Central expertise: Serve as the primary SME for application architecture, data model, business rules, integrations, providers/consumers, customer mastering, matching, survivorship, and identity resolution.
- Architecture and design: Lead architecture reviews and define patterns for customer data integration, data quality, Customer 360, golden record management, real-time services, and analytics enablement.
- Engineering excellence: Coach engineers and technical leads, review critical designs/code/deployment approaches, and promote automation, DevOps, CI/CD, observability, reliability, and secure engineering practices.
- Data strategy: Partner with business and data leaders to define customer data products, improve data quality, expand capabilities, support Customer 360, and enable self-service analytics and AI/ML use cases.
- Production reliability: Provide technical escalation for incidents, root cause analysis, performance optimization, reliability improvements, disaster recovery planning, and technical risk mitigation.
- Innovation and modernization: Evaluate emerging technologies, recommend architecture improvements, reduce technical debt, and drive modernization of customer mastering, identity resolution, and customer analytics capabilities.
- Decision Authority:
- Technical standards: Architecture decisions in partnership with Enterprise and Data Architects, design patterns, integration standards, and technical governance.
- Platform direction: Customer Central modernization roadmap, technical debt prioritization, scalability strategy, and technology adoption recommendations.
- Engineering excellence: Code quality expectations, reliability standards, security/compliance adherence, and operational readiness requirements.
- Key Deliverables:
- Customer Domain Technical Roadmap and Customer Central Architecture Strategy
- Technical standards, solution design patterns, and architecture review outcomes
- Modernization recommendations, technical risk assessments, and technical debt remediation priorities
- Engineering best-practice frameworks and production stability improvement plans
- Success Measures:
- Platform health: Improved availability, reliability, performance, scalability, and reduction in critical production incidents.
- Engineering excellence: Reduced technical debt, improved code quality, stronger deployment efficiency, and consistent engineering standards.
- Business value: Faster delivery of customer capabilities, improved customer data quality, stronger adoption of data products, and higher stakeholder satisfaction.
- Leadership impact: Growth of technical talent, architecture consistency, and successful delivery of strategic Customer domain initiatives.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
