Focusing on expertise rather than titles can lead to more effective collaboration and problem-solving. By eliminating the emphasis on hierarchical titles, individuals can be recognized for their skills and knowledge within a specific domain, allowing for a more efficient allocation of responsibilities based on expertise rather than seniority. This approach encourages a culture where the right person, regardless of their title or level, is chosen for each task based on their competence in that area, ultimately enhancing team dynamics and productivity.
Today’s episode is with Jean-Denis Grèze, Head of Engineering at Plaid, which securely connects your bank to your apps. Before joining Plaid, Jean-Denis served as Director of Engineering at Dropbox, and even had a stint in law school and one year as a lawyer under his belt before diving deep into the world of CS.
While he says becoming a lawyer was a “four-year detour he probably didn’t need,” there’s a lot to be said for how it’s shaped his engineering career and management philosophy. As he puts it, he strongly favors pragmatism over perfection, and it’s something he hammers home within his engineering teams. In today’s conversation, Jean-Denis pulls on threads from across his career to weave together a modern playbook for engineering leadership — and the hard-won lessons that stick with him.
He also shares his insights on why his engineering org doesn’t have titles, the one question he asks every engineering manager candidate, and how his team prioritizes technical debt and keeping the lights on versus sexy, brand-new projects.
Today’s conversation is a must-listen for technical leaders or those who are eyeing the engineering leadership track. From motivating a team to tracking the right KPIs, Jean-Denis has got tons of great tactics and stories from his time at Plaid and Dropbox for you to learn from.
You can email us questions directly at review@firstround.com or follow us on Twitter @twitter.com/firstround and @twitter.com/brettberson