Data engineer career path

Anyone who has lived through a messy migration knows which storage and governance decisions are expensive to undo. Data architects make those decisions up front, across every part of the business.

Usually when

6-8 years in, usually after leading a warehouse or lakehouse migration

Skills to add

• Open table formats (Apache Iceberg or Delta Lake)
• Data catalogs and governance (Unity Catalog or DataHub)
• Data contracts between producers and consumers
• Databricks Certified Data Engineer Professional or Google Professional Data Engineer

Have this on your resume first

A platform or modeling design you led across several business areas, with the cost, reliability or adoption outcome.

Models break most often because of the data, through stale features, bad training sets or leaked future values. You already own that part.

Usually when

3-4 years in, especially if you've built feature or training pipelines

Skills to add

• scikit-learn and PyTorch fundamentals
• Feature stores such as Feast
• Model training and evaluation
• MLflow

Have this on your resume first

Feature or training pipelines you built for a model that runs in production.

Platform work turns one-off pipeline fixes into infrastructure everybody uses, like scheduling, compute, access control and CI for data. Pick it if the systems interest you more than the business logic.

Usually when

3-5 years in, once you're building shared tooling rather than one pipeline at a time

Skills to add

• Kubernetes
• Terraform
• Data quality testing with Great Expectations or Soda
• Warehouse cost monitoring and workload management

Have this on your resume first

Shared data tooling other engineers adopted, with a reliability, cost or onboarding improvement.

Data teams serve many internal customers at once, so senior engineers already negotiate priorities and service levels. As a manager, that negotiation and growing the team is the job.

Usually when

5-7 years in, typically after leading on-call and juggling requests from several teams

Skills to add

• Intake and prioritization across stakeholder teams
• Defining data SLAs and on-call practices
• Hiring and coaching engineers
• Budgeting warehouse and tooling spend

Have this on your resume first

A cross-team data project you coordinated, with the engineers involved and what got delivered.

Data platforms need PMs who understand where data comes from, how fresh it is and what a schema change breaks downstream. You've been translating between the teams that produce data and the teams that use it for years.

Usually when

4-6 years in, if you've been the one negotiating requirements with the people who use the data

Skills to add

• Writing PRDs for internal platform products
• User research with analysts and data scientists
• Adoption and usage metrics for internal tools
• Roadmap prioritization

Have this on your resume first

A data product or platform feature you scoped with its users, and how many teams adopted it.