Good habits for data engineers
summary
Panel lists concrete habits: build network before you need it by doing low‑stakes non‑transactional outreach and internal events; use a recurring Friday quiz to surface business questions and onboard engineers into domain KPIs, which led to team members chasing answers and a stakeholder resurfacing a useful data point after four or five years. Expect remote onboarding to take about five times more interactions to reach the same rapport as in‑person. Carry a one‑line mini‑pitch and overcommunicate metrics, preparation and empathy to shift perception from technician to business partner.
AI-written summary · about
chapters (6)
- 0:00Introduction and panel setup
- 7:45Building relationships with stakeholders
- 16:21How others perceive technical teams
- 20:15Overcommunicating value and impact
- 25:53Long-term strategies for data engineers
- 28:21Closing remarks and Q&A
related talks
38mBuilding Effective Data Teams: Strategies for Success
50mPanel: Engineering Onboarding
51mPanel Debate: Rise Of The Data Engineer
20mScale up your job satisfaction, not your software
37mWhat I wish I knew when I was a junior developer that I would tell as a staff software engineer
49mCreating a Workplace to Retain your Tech Talent
21mHow to quickly get engineers up to speed
36mHow To Onboard New Hires Into Happy and Productive Employees