Personality Over Skillset: How Adam Wachtel Builds Engineering Teams

The podcast discusses the importance of building strong, collaborative engineering teams, emphasizing that personality and problem-solving skills are as critical as technical expertise. The approach centers on small, self-directed teams with minimal management overhead, where engineers are given autonomy to solve problems creatively. This culture of ownership, combined with mentorship and pair programming, supports career growth and long-term retention, even in an industry known for high turnover. Competitive compensation and a positive team environment further contribute to stability, though the reality of re-teaming during company growth is acknowledged as a potential disruption.

The conversation also covers strategies for turning around underperforming tech teams and legacy systems, focusing on prioritizing critical issues like database performance and gradually addressing technical debt. Transparency in hiring - especially about the state of the tech stack - helps set expectations and attract problem-solvers who thrive in challenging environments. While AI is changing development workflows, the core team structure remains intact, with ongoing need for engineers across experience levels. Over-reliance on AI-generated code poses risks, including reduced codebase understanding and debugging difficulties, underscoring the continued importance of human oversight and skill development.

Finally, the discussion addresses broader industry concerns about AI disrupting the SaaS model, with speculation that enterprise platforms like Salesforce or Workday could become obsolete. However, this view is seen as an overreaction. While companies are consolidating software tools and AI usage is increasing, the cost and complexity of maintaining custom AI solutions may limit their long-term viability for non-tech firms. Although AI is reshaping software development and business tooling, the complete "death of SaaS" is unlikely in the near term, with traditional platforms expected to evolve rather than disappear.

• What if you audited your core SaaS product for AI-driven cost and maintenance risks right now?

  • Move: Identify one mission-critical feature in your product currently using third-party AI services (e.g., LLM APIs) and simulate a 10x cost increase. Refactor it to a fallback logic or cached static alternative.
  • Why Now?: AI service pricing is volatile and trending upward - unexpected spikes could erode your margins or force sudden product changes. Acting now lets you control the transition.
  • Expected Upside: You'll reduce financial exposure to AI vendors, improve long-term predictability, and gain leverage to negotiate or build selective in-house alternatives.

• What if you restructured your solo development workflow to mimic a small, autonomous team's ownership model?

  • Move: Break your next feature into three roles - designer, developer, and reviewer - and rotate through them with time-boxed phases. Use pair-programming-style screen recordings for the "review" phase, even if solo.
  • Why Now?: Small, self-directed teams outperform isolated coders in quality and innovation. Mimicking this structure solo builds discipline and surfaces blind spots early.
  • Expected Upside: Higher code quality, better design decisions, and faster debugging due to enforced separation of concerns and built-in review - without needing additional hires.

• What if you treated your tech stack like a "troubled team" and prioritized one critical bottleneck this week?

  • Move: Run a 90-minute audit of your system's biggest pain point (e.g., slow load times, frequent crashes, onboarding friction) and deploy one targeted fix - even if partial - within 48 hours.
  • Why Now?: Just like a failing team, a neglected tech stack drains morale and user trust. Quick wins rebuild momentum and reveal hidden leverage points.
  • Expected Upside: Immediate user experience improvement, increased confidence in your ability to ship under pressure, and clearer insight into where to focus next - replicating the turnaround success of stabilized teams.

• Prioritize hiring engineers with strong problem-solving skills and adaptability, focusing on personality and collaboration as much as technical ability to build a resilient solo-friendly team environment.
• Adopt a hands-on, incremental approach to technical debt by identifying and resolving the most critical system bottlenecks first, then progressively tackling subsequent issues to restore stability and confidence.
• Maintain direct engagement with the codebase even when using AI tools, avoiding over-reliance on generated code to prevent knowledge gaps and ensure long-term system maintainability.
• Structure work to balance autonomy and oversight - define clear goals but allow flexibility in execution - enabling efficient progress while retaining control, especially when operating independently.
• Regularly audit third-party and AI service costs, treating them as variable operational expenses, and plan for potential price escalations by building cost-aware usage patterns early.