newsfilter.io
Interview, Fireside Chat

The Best Hiring Tip -- Plaid CTO Jean-Denis Greze

  • Candidate Evaluation Criteria

    • Duration over "Bounces": Expresses strong preference for long tenures (e.g., 10 years) over frequent short-term roles (e.g., 12–18 months), viewing constant job hopping as a red flag that prevents teams from building velocity.
    • Resume Limitations: Considers resumes and LinkedIn profiles "surface-level" and insufficient for capturing true talent; views the interview room interaction as the primary method for assessment.
    • Portfolio Signals: Values evidence of curiosity and output, specifically citing GitHub projects, shipped work, and personal blogs as indicators of capability.
    • Role Specificity: Warns against seeking "the best engineer" generally; advises matching skills precisely to business needs (e.g., a CRUD app does not require distributed systems expertise).
    • Trajectory Red Flags: Identifies staying too long at the same level or frequent, unproductive company switches as key warning signs.
  • Hiring Strategy for Founders

    • Hiring the "Here and Now": Recommends hiring for immediate problem-solving needs for the first 15 employees to support product-market fit and momentum.
    • Management Transition Point: Notes that management breakdowns typically occur between 15 and 30 employees, requiring a shift from tactical to strategic hiring.
    • Management Candidate Timelines:
      • The "Four-Year" Candidate: A leader who previously managed 75–100 person teams; high risk as they may have lost muscle in managing smaller (e.g., 20-person) teams and lack excitement for early-stage work.
      • The "Two-Year" Candidate: A leader who previously managed 35–40 person teams; easier to hire but requires reevaluation every few years as the company scales.
    • Scaling Warning: Avoids long-term hires who may not understand current ground-level technology shifts or lack the drive to "roll up their sleeves."
  • Common Hiring Mistakes

    • Vague Role Definitions: Mistakes occur when requirements are not crisp (e.g., confusing general "data science" with specific "risk and fraud" experience in a creative environment).
    • Misaligned Interview Panels: Senior interviews often fail when panels ask generic questions (e.g., "tell me about a failure") instead of role-specific scenarios.
      • Example: An HR lead should assess teamwork through difficult execution challenges, while a GTM lead should assess collaboration with product managers on data requirements.
    • Lack of Comparison Baselines: Hiring the first "perfect" candidate without comparing them to others makes it difficult to validate their true quality.
      • Solution: Interview 3–4 additional candidates even after finding a top contender to ensure the panel has a calibrated sense of "great."
  • Post-Hire Success Metrics

    • Objective Data Points: Mandates setting objective evaluation markers at 2–3 months to determine if a hire is successful.
    • Milestone Review Cycle: Advises scheduled reviews at 3, 4, and 5 months to answer specific questions: Did the trajectory change? Are the assigned tasks completed?
    • Early Intervention: Stresses that if objective data does not confirm success, leaders must be willing to have the difficult conversation about departure rather than letting it continue by chance.