It takes more than great code
to be a great engineer.

Soft Skills Engineering is a weekly advice podcast for software developers.

The show's hosts are experienced developers who answer your questions about topics like:

  • pay raises
  • hiring and firing developers
  • technical leadership
  • learning new technologies
  • quitting your job
  • getting promoted
  • code review etiquette
  • and much more...

Soft Skills Engineering is made possible through generous donations from listeners. A heart with a striped shadowSupport us on Patreon

A speech bubble

Why should you listen?

Here's what listeners say:

Recent Episodes

Latest Episode

Episode 289: Sharing wisdom nicely and too many raises?

Download

In this episode, Dave and Jamison answer these questions:

  1. Hey guys, a long time listener here, I love the show.

    I’ve recently joined an early-stage startup with a tiny engineering team. It’s like most startups at this stage, there’s some chaos and a lot to figure out. It’s exactly what I like about startups.

    In the past years, I’ve been working on the very same kind of software we’re building now. I have a ready answer for many questions we might have, I’ve seen some things go badly and others work great. I’m eager to help the team deliver.

    But I also don’t want to be seen as the know-it-all jerk that tells everyone how to do their job. I have respect for my team and want to contribute. How do I use my experience without annoying my colleagues?

    Thanks for sharing your wisdom (I hope for 101% of it).

  2. Listener Andy asks,

    I moved to company A and it’s been 6 months I am constantly getting interview requests, Gave an interview and got a 30% rise moved to Company B, Now within 6 months the same thing happened, Gave an interview at Company C and got the job with 30% raise. what should I do? will it affect my long term career growth

A smiling speech bubble

Episode 288: Too excited about learning and furious boss when quitting

Download

In this episode, Dave and Jamison answer these questions:

  1. I am working at my first job as a software engineer for 2 1/2 years now. I really enjoy working as a programmer and I’m super excited about the tech industry in general.

    However, sometimes I feel like I’m too excited about everything. I spent a lot of time reading blog posts, watching tutorials or taking online courses. I think about what books to read and what languages to learn all the time. Not everything but a big part of it happens during my working hours. While I know that “loving to learn” in general is considered a positive trait, I feel like I might take it a bit too far and I should focus more on the actual tasks I have - especially, because I think my coworkers spend much less time keeping up to date with everything.

    What is a reasonable amount of time to spent on these things during working hours and beyond? How do I know I spend too much time not working on my actual tasks? How can I make sure I learn the right things that are useful to my career?

    Love the show and wish you the best. Thanks for your advice!

  2. I landed a new job that nearly tripled my salary realative to the job I’m about to leave (yes, I was horribly underpaid)! The stories and tips from this podcast really helped me out but I also landed this job through Hired.com (the podcast sponsor).

    Any good tips regarding leaving a job when you know your boss will be furious that you’re leaving? Also, should I tell my boss which company I’m going to when he asks (he definitely will)?

Show Notes

  • Tom7, the most amazing YouTuber of all time: https://www.youtube.com/c/suckerpinch
  • https://www.youtube.com/watch?v=qTBAW-Eh0tM - anagraphs
A smiling speech bubble

Episode 287: Informal favoritism and post-hoc finger pointing

Download

In this episode, Dave and Jamison answer these questions:

  1. Listener Sara asks,

    How can I deal with favoritism towards informal leaders in a group? The group is losing group intelligence because the informal leader’s reasoning and direction is favored. Example: when member A propose an argument is dismissed, but when the informal leader proposes the same argument it is cherished.

  2. How do I react to the question “why didn’t you do it this way” for features already in production? I am frustrated by being asked that. I got scolded for an idea that turned out to be bad after I implemented it (in production), although I asked the Lead for his opinion ahead of time. As soon as trouble came up a.k.a performance issue in production, he pointed the finger at me. Lost all kinds of respect for him.