Inside the Life of a Data Engineer at Lyft – Daily Workflow

Spending a day in the life of a data engineer might surprise you. Contrary to popular belief, coding takes up only a fraction of the day. If you’re considering a career in data engineering, understanding the reality of the job and its unique challenges is vital. In this article, we’ll break down a typical day for a data engineer at Lyft into three key parts that cover meetings, collaboration, and deep work.

Overview of a Data Engineer’s Day

While many envision data engineers spending hours code-crunching, the reality is quite different. Nearly 90% of a data engineer’s day involves meetings and strategic thinking instead of coding. Let’s explore how a day unfolds.

Morning Meetings

The day usually starts with a series of meetings that can fill up the first few hours from 9:00 a.m. to 11:00 a.m. During this time, data engineers connect with stakeholders and cross-functional teams. Morning meetings serve several key purposes:

• Updating on project status: This is where you learn about ongoing projects from your data scientist colleagues, as they discuss insights gathered from data analysis.
• Identifying challenges: For example, a project might focus on detecting failed payments in a subscription model like Lyft Pink—a service that allows users to subscribe for ride discounts.
• Collaborative problem-solving: Interactions with product managers, software engineers, and data scientists foster a collaborative environment, which is crucial in a tech organization. These discussions make the morning not just a mundane task list but an engaging aspect of the role.

Midday Tasks and Maintenance

After the morning meetings, the midday session allows data engineers to tackle ongoing tasks and handle maintenance work. Here, engineers might engage in activities such as:

• Checking data pipelines: Monitoring the data workflows ensures that systems are functioning as intended. This could involve verifying that data is flowing correctly from one system to another without issues.
• Dashboard management: Engineers often work on dashboards that provide insights into operations. For instance, one dashboard might highlight the causes behind failed payments in the Lyft Pink subscription.
• Documentation and reporting: Communicating findings to other teams and documenting processes is a critical part of ensuring everyone stays aligned.

Midday is often considered an exciting time, as data engineers can see tangible outputs from their previous work. Discovering why certain subscription payments were failing allows teams to iterate on solutions effectively. An example discussed was finding that potential users of Lyft Pink were exploiting payment structures by using digital cards to bypass recurring charges, highlighting the importance of data integrity and user behavior analysis.

The Afternoon for Coding and Development

As the day transitions into the afternoon, typically around 3:00 p.m. to 5:00 p.m., data engineers finalize their day with focused coding time, often referred to as “deep work.” This dedicated time block allows for essential coding activities, which can include:

• Developing new features or models: Understanding the cause of issues identified earlier may lead to developing new solutions. In this case, a proposal for implementing wallet rotation was made to counteract payment failures.
• Productivity techniques: This period is crucial for interpretation and implementation of ideas discussed in meetings earlier in the day.
• Advancing team objectives: Individual coding projects ultimately contribute to broader company goals, enhancing both user experience and engagement.

For instance, initiating new strategies for subscription retention can lead to providing additional benefits, like a free GrubHub membership, which incentivizes users to remain engaged in the service.

The Bigger Picture in Data Engineering

The tasks covered in a data engineer’s day not only enhance their coding skills but also deepen their understanding of business needs and user engagement. In many situations, you’re laying a foundation that supports the growing needs of a data-driven company like Lyft. You get to witness firsthand how collated insights can lead to significant improvements in user experience, thus creating value for the company and its customers.

A career in data engineering offers a mix of collaboration, problem-solving, and technical work that keeps the job dynamic and engaging. While much of the day may not be spent coding, the time you do spend coding is fulfilling as you see direct impacts on the business. If you’re considering pursuing a career in this field, steps into roles such as data analyst or data engineer could be very rewarding.

Explore further resources to understand the nuances between these roles to determine what fits best for you!

Unlock Your Career Potential

Upskill and start shaping your future with DEAcademy today.