It takes more than great code to be a great engineer. Soft Skills Engineering is a weekly advice podcast for software developers about the non-technical stuff that goes into being a great software developer.
Workplace friction often stems from "externalities," where managers create messes or impose complex processes that shift the burden onto individual contributors. Addressing these issues requires approaching leadership with curiosity rather than confrontation, framing feedback around the impact on team velocity and shar...
Engineering professionals often struggle with maintaining attention to detail and managing complex, AI-generated codebases. To mitigate recurring errors and oversights, engineers should adopt rigorous note-taking habits and use AI-driven self-assessment tools, such as generating quizzes to verify understanding of techn...
The influx of low-quality, AI-generated code and documentation in professional environments is creating significant burnout for experienced engineers who act as the final filter. This "meat proxy" dynamic, where colleagues delegate the vetting of unreviewed AI output to others, undermines team productivity and erodes t...
Navigating career challenges in disorganized environments and transitioning into English-speaking engineering roles requires strategic self-advocacy and practical communication habits. For engineers trapped in chaotic organizations with poor prioritization and lack of QA, the most effective approach involves asserting ...
Software engineers face evolving challenges regarding professional feedback and the integration of AI-generated code. Consultants working in isolated, multi-hat roles often struggle to solicit performance feedback without appearing insecure; however, formalizing feedback loops as a standard operating procedure mitigate...
Software engineers navigate the complexities of career transitions and team leadership through practical, experience-based advice. For career switchers in analytics, technical interviews often prioritize specific coding puzzles over the high-value, product-oriented skills they possess. Success in this landscape require...
Workplace challenges in software engineering often stem from office etiquette and mentorship dynamics. Open office environments suffer from noise pollution when employees conduct meetings at their desks, necessitating clearer team norms or designated private spaces to maintain productivity. Regarding mentorship, junior...
Software engineering career advice centers on navigating workplace ambiguity and corporate transitions. When facing a lack of tasks in a new role, engineers should proactively seek opportunities by pair programming, identifying internal technical pain points, or introducing productivity-enhancing tools to demonstrate v...
The current job market for software engineers has become increasingly difficult due to a high volume of AI-generated applications, which erodes trust and complicates the resume screening process. To stand out, candidates should prioritize referrals and proactive, personalized outreach to recruiters rather than relying ...
Software engineering career growth and workplace navigation define the core of this discussion. Addressing the frustration of delayed promotions, the advice emphasizes understanding corporate leveling systems and aligning personal career goals with management’s incentives rather than pushing for immediate, policy-defyi...
Navigating career uncertainty and the rapid integration of AI into software development requires balancing adaptability with professional caution. When companies undergo sudden strategic pivots or mass layoffs, prioritizing new employment opportunities is more prudent than attempting to fulfill vague, non-technical "id...
Engineering teams often face significant friction when leadership bypasses established processes to implement AI-generated code. This "cowboy coding" creates negative externalities, shifting the burden of quality assurance, debugging, and deployment onto individual contributors who lack context for the generated output...
Navigating workplace friction requires strategic communication and a deep understanding of organizational dynamics. When dealing with unhelpful infrastructure teams, treat the interaction like an API: research successful ticket patterns, provide precise technical details, and consider escalating to management if the te...
Career stagnation and educational requirements for transitioning into software engineering serve as the primary focus. Regarding the fear of being "stuck" after four years at a single company, professional growth remains achievable through "job crafting"—proactively negotiating new responsibilities or shifting focus to...
Negotiating job offers during periods of long-term unemployment requires balancing the desire for higher compensation against the significant risk of losing a rare offer. In a challenging hiring market, especially at large companies with rigid salary bands, aggressive negotiation often yields little upside and may jeop...
Generative AI has fundamentally altered software development by eroding the incidental human connections that occur during code reviews and collaborative problem-solving. When team members rely exclusively on AI without reviewing output, they lose the craftsmanship and shared learning that define high-performing teams....
Technical leadership gaps often lead to organizational dysfunction, including consensus abuse, meeting stagnation, and unproductive bike shedding. While formal tech leads provide necessary structure and mentorship, teams lacking these roles often rely on informal leaders who step up to drive decisions and maintain mome...
Software engineers navigating career stagnation and work-life balance challenges require strategic communication and realistic risk assessment. When facing disappointing salary increases, avoid impulsive resignation; instead, identify the actual decision-makers, align compensation requests with annual planning cycles, ...
Working for companies where software serves as the primary revenue-generating product provides greater job security and career leverage than roles focused on internal tooling, which are frequently treated as cost centers vulnerable to budget cuts. When organizations demand that engineering managers oversee multiple tea...
Daily standups frequently devolve into unproductive ticket recitations, particularly when led by full-time scrum masters who prioritize rigid ceremony over team efficiency. These meetings often fail to serve their intended purpose of identifying blockers, instead creating a disconnect that hampers individual productivi...
Follow this podcast in Podwise
Sign in to get AI summaries, transcripts and mind maps for any episode, including new ones.
