Engineering Manager – Data Platform, Lakehouse Foundation
Lyft · Toronto, Canada
Experience: 3+ years of experience
At Lyft, our purpose is to serve and connect. We aim to achieve this by cultivating a work environment where all team members belong and have the opportunity to thrive.
As the Engineering Manager for the Lakehouse Foundation team, you will lead a group of engineers responsible for the foundational data layer that all of Lyft's data systems and emerging AI workloads are built on. The team owns catalog and metadata management, table formats and storage, and the access patterns and gateways through which other engineering teams interact with Lyft's data. As Lyft converges on a unified lakehouse architecture, this team builds and operates the single source of truth that powers analytics, machine learning, experimentation, and every business decision made from data. You will play a key role in shaping the team's technical direction, partnering with peer Data Platform teams on a multi-year platform evolution, and developing engineers who operate with autonomy on systems of significant scale and complexity.
Lyft's Infrastructure teams build the foundational systems that the rest of engineering depends on to move fast, ship reliably, and scale efficiently. These are high-leverage roles where the work you and your team do has a multiplicative effect across the company. We're looking for experienced leaders who can balance the discipline of operating critical infrastructure with the curiosity to keep evolving how Lyft builds.
Engineering at Lyft is a place where managers and engineers operate with high ownership and strong technical judgment. Our engineers expect their managers to be honest, available, and focused on the work that matters: developing their teams, removing obstacles, and giving people the support they need to do their best work. We build teams that are inclusive, technically rigorous, and have a strong sense of ownership for what they build.
## Responsibilities:
• Lead a team responsible for Lyft's foundational data layer, including catalog and metadata management, table formats (Iceberg/Delta), and the gateway and access patterns that all other data systems build on
• Drive the team's contribution to Lyft's multi-year lakehouse modernization, including the migration to Unity Catalog and the convergence of metadata across the data stack
• Partner with peer Data Platform teams (Compute, Data Trust & Governance, Data Orchestration, Streaming) and engineering organizations across Lyft to ensure the foundation evolves coherently with the systems built on top of it
• Define and own the team's technical direction, balancing platform-level investment with the day-to-day reliability needs of a foundational layer that thousands of pipelines and queries depend on
• Mentor and guide the professional and technical development of engineers across levels, including senior individual contributors operating at staff level and engineers early on in their careers
• Ensures the team operates with strong ownership, makes effective decisions in ambiguous and high-stakes situations, and demonstrates technical rigor in a domain where mistakes propagate across the company's data systems
• Foster a culture of cross-team engagement, where engineers proactively partner with customers and adjacent teams rather than working in isolation
• Provide ongoing feedback and coaching, recognize individual contributions, and ensure each engineer has clear expectations and support to grow in their role
• Own your team's deliverables and ensure that the foundational systems they own remain reliable, scalable, and well-understood by the broader engineering organization
## Experience:
• 3+ years of experience as an Engineering Manager, leading teams of 5+ engineers including senior individual contributors
• Experience managing data infrastructure or platform teams. Direct experience with lakehouse architectures (Databricks, Snowflake) and modern table formats (Delta, Iceberg, Hudi) strongly preferred
• Track record of leading teams through multi-quarter platform migrations or major architectural transitions, with demonstrated ability to make strategic decisions under ambiguity and navigate cross-team dependencies
• Experience operating as the primary cross-org partner on initiatives that span multiple engineering teams, including aligning technical direction with peer teams, vendors, and senior stakeholders
• Track record of developing engineers, including senior individual contributors on a staff trajectory, by matching them to ambitious technical scope and supporting their growth
• Experience leading geographically distributed teams across time zones, including building communication practices that keep distributed teams operating as one integrated organization
• Technical background sufficient to contribute meaningfully to architecture and design discussions, evaluate technical tradeoffs, and provide credible direction to senior engineers
• Experience building inclusive teams with strong ownership culture
• Excellent written and verbal communication, including the ability to operate at the strategic level with senior leadership and at the technical level with engineers
## Benefits:
• Extended health and dental coverage options, along with life insurance and disability benefits
• Mental health benefits
• Family building benefits
• Child care and pet benefits
• Access to a Lyft funded Health Care Savings Account
• RRSP plan with company match to help save for your future
• In addition to provincial observed holidays, salaried team members are covered under Lyft's flexible paid time off policy. The policy allows team members to take off as much time as they need (with manager approval). Hourly team members get 15 days paid time off, with an additional day for each year of service
• Lyft is proud to support new parents with 18 weeks of paid time off, designed as a top-up plan to complement provincial programs. Biological, adoptive, and foster parents are all eligible.
• Subsidized commuter benefits and Lyft ride credits
Lyft is committed to creating an inclusive workforce that fosters belonging. Lyft believes that every person has a right to equal employment opportunities without discrimination because of race, ancestry, place of origin, colour, ethnic origin, citizenship, creed, sex, sexual orientation, gender identity, gender expression, age, marital status, family status, disability, pardoned record of offences, or any other basis protected by applicable law or by Company policy. Lyft also strives for a healthy and safe workplace and strictly prohibits harassment of any kind. Accommodation for persons with disabilities will be provided upon request in accordance with applicable law during the application and hiring process. Please contact your recruiter if you wish to make such a request.
Lyft highly values having employees working in-office to foster a collaborative work environment and company culture. This role will be in-office on a hybrid schedule — Team Members will be expected to work in the office at least 3 days per week, including on Mondays, Wednesdays, and Thursdays. Lyft considers working in the office at least 3 days per week to be an essential function of this hybrid role. Your recruiter can share more information about the various in-office perks Lyft offers. Additionally, hybrid roles have the flexibility to work from anywhere for up to 4 weeks per year. #Hybrid
The expected base pay range for this position in the Toronto area is CAD
As the Engineering Manager for the Lakehouse Foundation team, you will lead a group of engineers responsible for the foundational data layer that all of Lyft's data systems and emerging AI workloads are built on. The team owns catalog and metadata management, table formats and storage, and the access patterns and gateways through which other engineering teams interact with Lyft's data. As Lyft converges on a unified lakehouse architecture, this team builds and operates the single source of truth that powers analytics, machine learning, experimentation, and every business decision made from data. You will play a key role in shaping the team's technical direction, partnering with peer Data Platform teams on a multi-year platform evolution, and developing engineers who operate with autonomy on systems of significant scale and complexity.
Lyft's Infrastructure teams build the foundational systems that the rest of engineering depends on to move fast, ship reliably, and scale efficiently. These are high-leverage roles where the work you and your team do has a multiplicative effect across the company. We're looking for experienced leaders who can balance the discipline of operating critical infrastructure with the curiosity to keep evolving how Lyft builds.
Engineering at Lyft is a place where managers and engineers operate with high ownership and strong technical judgment. Our engineers expect their managers to be honest, available, and focused on the work that matters: developing their teams, removing obstacles, and giving people the support they need to do their best work. We build teams that are inclusive, technically rigorous, and have a strong sense of ownership for what they build.
## Responsibilities:
• Lead a team responsible for Lyft's foundational data layer, including catalog and metadata management, table formats (Iceberg/Delta), and the gateway and access patterns that all other data systems build on
• Drive the team's contribution to Lyft's multi-year lakehouse modernization, including the migration to Unity Catalog and the convergence of metadata across the data stack
• Partner with peer Data Platform teams (Compute, Data Trust & Governance, Data Orchestration, Streaming) and engineering organizations across Lyft to ensure the foundation evolves coherently with the systems built on top of it
• Define and own the team's technical direction, balancing platform-level investment with the day-to-day reliability needs of a foundational layer that thousands of pipelines and queries depend on
• Mentor and guide the professional and technical development of engineers across levels, including senior individual contributors operating at staff level and engineers early on in their careers
• Ensures the team operates with strong ownership, makes effective decisions in ambiguous and high-stakes situations, and demonstrates technical rigor in a domain where mistakes propagate across the company's data systems
• Foster a culture of cross-team engagement, where engineers proactively partner with customers and adjacent teams rather than working in isolation
• Provide ongoing feedback and coaching, recognize individual contributions, and ensure each engineer has clear expectations and support to grow in their role
• Own your team's deliverables and ensure that the foundational systems they own remain reliable, scalable, and well-understood by the broader engineering organization
## Experience:
• 3+ years of experience as an Engineering Manager, leading teams of 5+ engineers including senior individual contributors
• Experience managing data infrastructure or platform teams. Direct experience with lakehouse architectures (Databricks, Snowflake) and modern table formats (Delta, Iceberg, Hudi) strongly preferred
• Track record of leading teams through multi-quarter platform migrations or major architectural transitions, with demonstrated ability to make strategic decisions under ambiguity and navigate cross-team dependencies
• Experience operating as the primary cross-org partner on initiatives that span multiple engineering teams, including aligning technical direction with peer teams, vendors, and senior stakeholders
• Track record of developing engineers, including senior individual contributors on a staff trajectory, by matching them to ambitious technical scope and supporting their growth
• Experience leading geographically distributed teams across time zones, including building communication practices that keep distributed teams operating as one integrated organization
• Technical background sufficient to contribute meaningfully to architecture and design discussions, evaluate technical tradeoffs, and provide credible direction to senior engineers
• Experience building inclusive teams with strong ownership culture
• Excellent written and verbal communication, including the ability to operate at the strategic level with senior leadership and at the technical level with engineers
## Benefits:
• Extended health and dental coverage options, along with life insurance and disability benefits
• Mental health benefits
• Family building benefits
• Child care and pet benefits
• Access to a Lyft funded Health Care Savings Account
• RRSP plan with company match to help save for your future
• In addition to provincial observed holidays, salaried team members are covered under Lyft's flexible paid time off policy. The policy allows team members to take off as much time as they need (with manager approval). Hourly team members get 15 days paid time off, with an additional day for each year of service
• Lyft is proud to support new parents with 18 weeks of paid time off, designed as a top-up plan to complement provincial programs. Biological, adoptive, and foster parents are all eligible.
• Subsidized commuter benefits and Lyft ride credits
Lyft is committed to creating an inclusive workforce that fosters belonging. Lyft believes that every person has a right to equal employment opportunities without discrimination because of race, ancestry, place of origin, colour, ethnic origin, citizenship, creed, sex, sexual orientation, gender identity, gender expression, age, marital status, family status, disability, pardoned record of offences, or any other basis protected by applicable law or by Company policy. Lyft also strives for a healthy and safe workplace and strictly prohibits harassment of any kind. Accommodation for persons with disabilities will be provided upon request in accordance with applicable law during the application and hiring process. Please contact your recruiter if you wish to make such a request.
Lyft highly values having employees working in-office to foster a collaborative work environment and company culture. This role will be in-office on a hybrid schedule — Team Members will be expected to work in the office at least 3 days per week, including on Mondays, Wednesdays, and Thursdays. Lyft considers working in the office at least 3 days per week to be an essential function of this hybrid role. Your recruiter can share more information about the various in-office perks Lyft offers. Additionally, hybrid roles have the flexibility to work from anywhere for up to 4 weeks per year. #Hybrid
The expected base pay range for this position in the Toronto area is CAD
72,000 - CAD
15,000, not inclusive of potential equity offering, bonus or benefits. Salary ranges are dependent on a variety of factors, including qualifications, experience and geographic location. Your recruiter can share more information about the salary range specific to your working location and other factors during the hiring process.
Lyft may use artificial intelligence to screen applicants, however, Lyft employees make the ultimate selection and hiring decisions.
This job fills an existing vacancy.
Careeroza — One-stop Zone for Aspirants
Study material, Careeroza mentorship, tech jobs, and career guidance on careeroza.com.
Public study materials
- Python (Python)
- Python Fundamentals · basic
- Control Flow · basic
- Strings · basic
- Collections / Data Structures · basic
- Functions · basic
- Modules and Packages · basic
- File Handling · basic
- Exception Handling · basic
- Object-Oriented Programming (OOP · medium
- Advanced Python Concepts · advance
- Functional Programming · advance
- Multithreading & Multiprocessing · advance
- Async Programming · advance
- System Architecture (System Architecture)
- Fundamentals of System Architecture · basic
- Distributed System Basics · basic
- System Reliability Concepts · basic
- Scaling Concepts · basic
- Networking Basics · basic
- Web Communication · basic
- API Communication · basic
- Proxy & Delivery Systems · basic
- Web Architecture Basics · basic
- Rendering Architectures · basic
- Frontend Advanced Concepts · basic
- Message Queue Basics · medium
- What is Load Balancer · medium
- Load Balancing Algorithms · medium
- API Design Basics · medium
- API Protection · medium
- Authentication Basics · medium
- Security Tokens · medium
- Security Threats · medium
- Encryption & Security · medium
- SQL Database Basics · medium
- SQL Scaling Concepts · medium
- NoSQL Databases · medium
- Database Optimization · medium
- Replication Strategies · medium
- Caching Basics · medium
- Cache Storage Systems · medium
- Cache Strategies · medium
- Event-Driven Systems · advance
- Queue Reliability · advance
- Microservices Basics · advance
- Microservice Communication · advance
- Distributed Transactions · advance
- DevOps Basics · advance
- Automation Tools · advance
- Deployment Strategies · advance
- Monitoring Basics · advance
- Monitoring Tools · advance
- Distributed System Concepts · advance
- Distributed Algorithms · advance
- Express.js — Web APIs & middleware (expressjs)
- Application setup · basic
- Routing deep dive · basic
- 1. MVC / Layered Architecture · medium
- Validation · medium
- File uploads · medium
- Sessions & auth (stateful) · medium
- Passport & strategies · medium
- Templating & SSR · medium
- WebSockets & SSE · medium
- Security middleware · advance
- Reverse proxies & trust · advance
- Performance · advance
- API design & versioning · advance
- Testing with Supertest · advance
- GraphQL & tRPC (overview) · advance
- Deployment checklist · advance
- Middlewares · basic
- Request & Response · basic
- System Designing (System Designing)
- Day-1 : What is system Designing ? · basic
- Day-2 : Vertical vs. Horizontal Scaling · basic
- Day-3:How to do vertical scaling ? · basic
- Day4:How to do horizaontal scaling ? · basic
- Day:5TCP vs UDP · basic
- Day6:IP & DNS · basic
- Day7:Client-Server Model · basic
- Day8:HTTP & HTTPS · basic
- Databases (SQL vs NoSQL) · medium
- Caching · medium
- Day9:Latency & Throughput · basic
- Load Balancing · medium
- Indexes & Query Optimization · medium
- CDN · medium
- Proxies · medium
- Message Queues · medium
- Horizontal vs Vertical Scaling · medium
- Database Replication · advance
- Database Sharding · advance
- Consistent Hashing · advance
- CAP Theorem · advance
- Rate Limiting · advance
- Service Discovery · advance
- Event-Driven Architecture · advance
- API Gateway · advance
- Distributed Consensus · expert
- Microservices · expert
- Observability · expert
- Idempotency · expert
- PACELC Theorem · expert
- Two-Phase Commit · expert
- Back-of-Envelope Estimation · expert
- Designing for Failure · expert
- SQL (SQL)
- SQL Fundamentals · basic
- Database Operations · basic
- Table Operations · basic
- CRUD Operations · basic
- Filtering & Operators · basic
- SQL Functions · basic
- GROUPING Data · basic
- Joins · medium
- Constraints · basic
- Subqueries · medium
- Set Operators · medium
- Views · medium
- Indexes · medium
- Normalization · advance
- Transactions · advance
- Stored Procedures & Functions · advance
- Triggers · advance
- Advanced SQL · advance
- Query Optimization · advance
- Database Design · advance
- SQL Security · advance
- Backup & Recovery · advance
- Questions · interview questions
- Django (Django)
- What is Django · basic
- Installing Django · basic
- Features of Django · basic
- MVT Architecture · basic
- Django vs Flask · basic
- Creating Project & Creating App · basic
- Django Project Structure · basic
- URL Routing · basic
- Views · basic
- Templates · basic
- Static & Media Files · medium
- Models · medium
- ORM (Object Relational Mapping) · medium
- Model Relationships · medium
- Migrations · medium
- Django Admin · medium
- Forms · medium
- Authentication · medium
- Authorization · medium
- Middleware · medium
- Signals · medium
- Class Based Views Deep Dive · advance
- Generic Views · advance
- File Handling · advance
- Django REST Framework (DRF) · advance
- Advanced ORM · advance
- Caching · advance
- Asynchronous Django · advance
- Background Tasks · advance
- Interview Questions · interview-questions
- JavaScript (JavaScript)
- JS Introduction · basic
- Variables & Data Types · basic
- Operators · basic
- Control Flow · basic
- Functions · basic
- Scope & Execution · basic
- Closures · basic
- Objects · basic
- Arrays · basic
- Strings · basic
- DOM Manipulation · basic
- Browser APIs · medium
- Asynchronous JavaScript · medium
- Fetch & APIs · medium
- ES6+ Features · medium
- OOP in JavaScript · medium
- Prototype & Inheritance · advance
- Advanced Functions · advance
- Memory Management · advance
- Error Handling · advance
- Modules · advance
- Advanced Async Concepts · advance
- Functional Programming · advance
- JavaScript Internals · advance
- Performance Optimization · advance
- Angular (Angular)
- Angular Fundamentals · basic
- Project Structure · basic
- Components & Templates · basic
- Data Binding · basic
- Directives · basic
- Pipes · basic
- Component Communication · basic
- Lifecycle Hooks · basic
- Routing Basics · basic
- Routing · basic
- API Calls · basic
- Forms · medium
- Routing · medium
- Services & Dependency Injection · medium
- RxJS & Observables · medium
- Authentication & Security · medium
- Component Interaction · medium
- State Management Basics · medium
- Error Handiling · medium
- Perfomance Basic · medium
- Real World Features · medium
- Advanced Angular Architecture · advance
- Change Detection · advance
- Advanced RxJS · advance
- State Management · advance
- Dynamic Rendering · advance
- Perfomance Optimization · advance
- Modern Angular · advance
- STAR (Situation, Task, Action, and Result) (Situation Based Questions)
- Node.js — Server-side JavaScript (nodejs)
- Getting started · basic
- JavaScript on the server · basic
- CommonJS modules · basic
- ES modules (ESM) · basic
- npm & package management · basic
- Asynchronous JavaScript in Node · basic
- The event loop · basic
- Essential core utilities · basic
- process & configuration · basic
- File system basics · basic
- HTTP & HTTPS servers · medium
- Streams · medium
- Events & EventEmitter · medium
- Advanced filesystem · medium
- crypto · medium
- Compression & encoding · medium
- Child processes · medium
- net, dgram & DNS · medium
- readline, timers & scheduling · medium
- Testing & diagnostics (intro) · medium
- Worker threads · advance
- cluster & multi-process scaling · advance
- Performance & tuning · advance
- Debugging & observability · advance
- Security hardening · advance
- Native addons & N-API · advance
- Architecture patterns · advance
- Graceful shutdown · advance
- 100 Questions · interview questions
- MongoDB — Documents & data modeling (MongoDB)
- Introduction · basic
- Shell, Compass & tools · basic
- Databases & collections · basic
- CRUD operations · basic
- Indexes deep dive · medium
- Explain plans & performance · medium
- Aggregation framework · medium
- Schema design patterns · medium
- Mongoose basics · medium
- Mongoose advanced · medium
- Drivers & connection · medium
- Operators for updates & arrays · medium
- Replication & read preferences · advance
- Write concern & read concern · advance
- Multi-document transactions · advance
- Change streams · advance
- Sharding (overview) · advance
- Atlas Search & full-text · advance
- GridFS & large files · advance
- Backup, restore & ops · advance
- AWS Crash Course (AWS)
- What is Cloud ? · basic
- What is AWS ? · basic
- If not cloud ? · basic
- Cloud Computing · basic
- AWS Pricing · basic
- AWS Shared Responsibility Model · basic
- AWS Management Console · basic
- AWS SDKs · basic
- AWS IAM · medium
- Users, Groups, Roles · medium
- Policies · medium
- AWS Organizations · medium
- AWS Cognito · medium
- AWS Directory Service · medium
- AWS KMS (Key Management Service) · medium
- AWS Secrets Manager · medium
- AWS Shield · medium
- AWS WAF · medium
- AWS Inspector · medium
- AWS GuardDuty · medium
- EC2 · advance
- Launching EC2 Instances · advance
- EBS Volumes · advance
- Security Groups · advance
- Key Pairs · advance
- Elastic IP · advance
- User Data Scripts · advance
- Auto Scaling · advance
- Load Balancers · advance
- ALB · advance
- NLB · advance
- Serverless Compute ,AWS Lambda, Lambda Layers · advance
- Event-Driven Architecture · advance
- ECS · advance
- EKS · advance
Lyft may use artificial intelligence to screen applicants, however, Lyft employees make the ultimate selection and hiring decisions.
This job fills an existing vacancy.