Soft Skills Engineering

A senior engineer's Slack question about a new HR goals framework turns into private reprimands and tone policing, raising concerns about culture shift and being pushed out. A frontend platform team's strict pure-function rule sparks debate over dogma, trade-offs, and how to push back. Conversation includes tactics like reframing feedback, using experiments and data, and when to escalate or walk away.

A listener wrestles with choosing a fast-growing AI startup versus a recognizable mega tech offer and the ethics of reneging. The hosts compare hands-on scaling at startups to seeing institutional practices at big companies. They debate timing, reputation risk, and recommend picking roles that build momentum. A second caller describes a shift from Java to click-heavy cloud integration and gets advice to automate or return to coding.

A new CTO faces leading hardware teams without deep domain expertise and debates how to earn trust. The problems of PMs pushing AI-generated low-quality code and how that shifts bottlenecks to review and QA are explored. Practical fixes like automated guardrails, tests, and training PMs are discussed alongside strategies for talking to leadership about tradeoffs.

Panels about sudden leadership exits and what might be happening in management meetings. A senior developer's struggle with using AI in day-to-day coding and the mixed feelings it creates. Discussion of how AI shifts work toward verification, architecture, and durable patterns. Practical suggestions about investigating departures and adapting to AI-driven workflows.

A CTO worries about his CEO randomly building products and fragmenting company focus, and two engineers debate when entrepreneurial tinkering helps or harms a startup. They also cover moving from coding to leading learning: how to teach, measure training impact, and keep credibility by occasionally shipping work.

They tackle stagnant raises, inflation eating away at merit increases, and unclear promotion paths. They dig into why hiring slowed and why candidate quality can be poor. Practical ideas on how to level up without announcing a job search are discussed. Strategies for improving underperforming teams, from coaching to selective changes, are explored.

A sole-developer at a sports team wrestles with whether to stay for freedom and stability or leave to grow with peers. Debate about how working alongside other developers accelerates learning versus the comfort of a trusted role. A separate story explores underperforming hires, offshore incentives, and how sloppy work drains team energy and what to do about it.

They tackle how to get busy coworkers to test rough prototypes early and avoid last-minute panic. They diagnose why late feedback shows up and debate incentives, feature flags, and quick user sessions to encourage participation. They also explore practical steps to break into engineering management without prior title experience and how to start practicing leadership now.

They unpack why giving performance feedback can feel patronizing and how clarity and gratitude change the dynamic. They talk about the real duties of a tech lead and why unblocking others often replaces coding time. They cover delegation, creating mini tech leads, and balancing hands-on work with coaching.

The hosts tackle the challenges of transitioning from casual startup interviews to structured soft-skill assessments in larger companies. They suggest practicing answers aloud and using AI tools to prepare. Strategies like the SAR method for structuring responses are highlighted for effective communication. In a surprising twist, a listener shares their experience of an exploitative unpaid internship with a team of only interns, prompting the hosts to advise quitting for better opportunities. They emphasize the risks of reputational damage from such roles.