Mentorship

2 posts

datadog3 min readCurated summary

Engineering spotlight: Marie-Laure Bardonnet

Marie-Laure Bardonnet’s Datadog career illustrates how engineers can grow through both technical and management paths. After working on Dashboards and Notebooks, she moved into distributed backend systems, eventually leading Datadog’s Logs engineering organization. Her approach emphasizes engineering-informed leadership, deliberate career planning, mentorship, and embracing unfamiliar challenges. ## From Web Engineering to Logs Leadership - Bardonnet joined Datadog full-time in 2017 after interning there. - She began on the Paris-based Dashboards team, where she helped: - Launch the Notebooks product. - Build the backend for a responsive Dashboard layout. - Encouraged by her manager, she transitioned into backend engineering and joined the Logs team. - Logs engineering involved real-time ingestion, processing, enrichment, storage, and querying of millions of log payloads daily. - As Datadog’s products developed shared technical requirements, Logs engineers collaborated closely with a centralized Platform team. - After one year as an individual contributor, Bardonnet became a team lead and later advanced to Engineering Manager II, overseeing both backend and frontend Logs teams. ## Balancing Product Delivery and Technical Health - Her role combines strategic planning, technical decision-making, people development, and recruiting. - At the start of each quarter, teams create OKRs that guide product and technical roadmaps. - Managers balance product priorities with: - Reliability and scalability. - Technical debt reduction. - Cross-team dependencies. - Bardonnet reviews RFCs, incident postmortems, and product documentation to help teams make sound decisions. - She supports both individual contributors and managers by identifying projects that build expertise and leadership skills. - She also participates in weekly hiring committees to recommend candidates and maintain consistent leveling. ## Structuring Teams for Future Growth - As organizations expand, Bardonnet focuses on restructuring teams to improve execution and create better growth opportunities. - Two questions guide this process: - What problems will the organization need to solve about a year from now? - How can everyone progress toward their next career step? - Logs leadership works with Product Management on a three-horizons plan to align future investments with customer needs. - Team design also considers whether each person has appropriately scoped work, meaningful challenges, and sufficient mentorship. ## Building a Self-Directed Career Path - Career planning begins by separating current responsibilities from the work someone ultimately wants to do. - Engineers should reflect on: - What work brings them satisfaction. - What they do well. - What they want to learn. - What legacy they want to leave. - Career goals should be reviewed continuously, organized across different planning horizons, and discussed with leaders. - A strong career path balances personal interests, strengths, learning opportunities, team needs, organizational priorities, and feedback. - Career direction is self-driven and may change over time, but managers and organizational leaders can help identify opportunities and create a suitable path. ## Growth Through Uncertainty - Datadog’s expanding platform and variety of engineering teams mean that career paths differ widely between employees. - Progression may be nonlinear and can require taking risks or accepting unfamiliar challenges. - Growth comes from leaving one’s comfort zone and learning through difficult problems. - Peer feedback helps employees assess whether they are progressing and feel supported. - Regardless of role or trajectory, employees contribute to Datadog’s culture by modeling high standards for quality and delivery. Bardonnet’s experience suggests that career growth is most effective when employees take ownership of their direction while seeking feedback, mentorship, and challenging opportunities from their organization.

Read original(opens in new tab)
figma2 min readCurated summary

Figma's engineering values | Figma Blog

Figma’s engineering values were created to preserve effective collaboration as the team grows without promoting a monoculture. They are intended to describe existing behaviors, guide decisions, and make explicit the tradeoffs behind how the team works. The post focuses on communication, teamwork, feedback, inclusion, and sustainable growth. ## Communicate Early and Often - Share design documents, product specifications, architecture sketches, and works in progress before implementation is complete. - Early communication helps teams: - Identify problems before significant effort is invested. - Solve problems collaboratively rather than in isolation. - Encourage people to ask for help and exchange knowledge. - Feedback must be welcomed as seriously as it is requested; sharing is useful only when people are receptive to changing direction. - Communication is not a rigid process: - Code may be the clearest way to discuss an idea. - Simple bug fixes or obvious changes may not require extensive discussion. - This value rejects the “solo genius” model in favor of using the team’s collective expertise. - The tradeoff is slower decision-making: involving more people can require additional discussion and iteration to ensure diverse voices are heard. ## Lift Your Team - Engineers should help one another grow, prioritize teammates’ success and well-being, and create an inclusive environment. - The emphasis is on lifting the team—not sacrificing individual sustainability for the company’s interests. - The value supports: - Continuous learning and mentorship. - Weekly technical talks. - Formal onboarding mentorship. - Encouragement to develop new skills. - Feedback should focus on ideas and work rather than attacking individuals. - Insults, condescension, and belittling are considered ineffective feedback. - Team members are also expected to receive feedback thoughtfully and remain open to others’ ideas. Figma’s approach is to make collaboration and mutual growth explicit expectations while acknowledging their costs. Teams adopting similar values should define concrete behaviors, ensure feedback is genuinely welcomed, and state the tradeoffs they are willing to accept.

Read original(opens in new tab)