Principal Data Engineer (AWS, Databricks, Ai, ML Flow, Data Architecture, Apache Airflow)
MastercardMatch Score
Against your primary resumeLogin to See Your Match Score
Create a free account or log in to unlock your CV match score across:
Protocol Intelligence
Data-driven signals on your job's competitivenessTier-1 employer and metro location, but senior specialized role limits candidate pool.
Highly specialized enterprise data engineering, cloud, and lakehouse skills required, limiting cross-industry transferability.
Explicit 12–18 years requirement plus many mandatory technologies and governance experience increases filter rigidity.
Job Description
Structured overview of role & requirementsAbout This Role
Lead design and engineering of scalable batch, streaming, and event-driven data platforms supporting analytics, ML, and AI workloads.
Develop and operate governed, cloud-native lakehouse and modern data platform architectures with robust data pipelines and governance.
Provide hands-on technical leadership including architecture reviews, mentoring, and collaborate across teams to mature R&D initiatives into production solutions.
Minimum Requirements
12-18 years relevant experience with significant ownership of complex enterprise data engineering solutions.
Expertise in Python, PySpark, advanced SQL, Apache Spark, distributed data processing, and modern lakehouse platforms.
Experience building and operating cloud-native data platforms on AWS, Azure, or similar; skilled in workflow orchestration tools like Apache Airflow or Databricks Workflows.
Bachelor's degree in Computer Science, Engineering, Information Systems, or related technical field or equivalent experience.
Ideal Candidate Profile
Strong hands-on technical leader comfortable turning ambiguous R&D objectives into secure, scalable production systems in innovation-focused environments.
Experienced with modern data architectures (data lakes, lakehouses, data meshes, event-driven) and operational excellence including CI/CD, testing, and platform automation.
Able to influence cross-functional teams without formal authority, balancing security, governance, performance, and cost in architectural decisions.