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 213: Interviewing your future boss and screwed by private equity


In this episode, Dave and Jamison answer these questions:

  1. My manager has left, so I have the task of interviewing candidates for my future boss’ position. I’m not doing it alone, one more engineering lead joins me for my tech round. After this round, the candidate gets to talk to upper management for the final decision. My question is, what are the lines you should never ever cross in an interview when interviewing your future boss.

  2. Our company was purchased by a private equity firm this year. Layoffs began immediately. While the company was gradually carved up, leadership continually violated every promise made. This week, during the most recent round of layoffs, I lost my job. I worked my butt off for years trying to contribute as much as I could to make a positive impact for both users and coworkers. Alas, despite all of my efforts, I was proven expendable. It feels like there was little point in doing as much as I did for this company, especially during the panicked response to COVID.

    How do I find and sustain a sense of security at the next company? How do I ensure that I can safely care about the company—the work done and the people helping to do it—finding that precarious balance between being invaluable and burning myself out?

A smiling speech bubble

Episode 212: Turnover and self-inflicted complexity


In this episode, Dave and Jamison answer these questions:

  1. I’ve been working at a big software company for two years. Since joining, 10 people have left my team, which is more than 50% of my team. Usually it’s the experienced developers who leave either for a different team, a different role or a different company altogether.

    The latest departure of a peer who I’ve been looking up to as a brilliant developer has been affecting my mood quite strongly. On one hand, I should be glad that I’m becoming a more pivotal member of the team, having moved up in the “seniority chain”. On the other hand, I’ve always believed the saying: “If you’re the smartest person in the room, then you’re in the wrong room”.

    Should I be concerned about this turnover rate? Is it considered normal? Why am I feeling different about this last departure than all of the previous ones?

  2. I am the tech lead on a team at a large tech company. One of the developers on our team has consistently struggled to meet deadlines and project deliverables. He frequently seems to invent his way into impossibly complex software problems. Additionally, he also seems to lack the ability to focus on a single thread, and tries to tackle diverse kinds of work in parallel. I’ve tried to help mentor and coach him, advising him to stick to one problem at a time and try to raise his hand and has for help before he backs himself into a hermeneutically sealed NP-hard problem — but I haven’t had much success. I wanted to see if you guys had any advice. Thanks a million!!!

Actual study showing actual results that we actually linked in the show notes this episode:

A smiling speech bubble

Episode 211: Biorhythm and coworker roommate


In this episode, Dave and Jamison answer these questions:

  1. Hi there Dave and Jamison! I am a tech lead in a small team of 5 people. 4 of them start working at 10-11 AM and one of them likes to start working at 1-2 PM. This person is me. Due to my biorhythm I feel I am the most productive at this time, and I also like to do some of the non-work-related stuff in the morning.

    Nobody in my team has any objections but as a team lead I feel guilty because it often happens that I block someone with my work schedule. I’m trying to do as much as I can to unblock everyone - distributing tasks in the evening, making it clear everyone knows what to do - but that’s not always helpful so it usually turns out that I am stopping my morning tasks to have a call and explain something or have a text conversation. Tbh it irritates me very much :D

    Should I feel guilty? As a tech lead, am I responsible for working at the same time everyone does?

  2. Hey Dave and Jamison! I love the show, I’ve listened to every episode and your advice has helped me a TON!

    I started a new job in a different city a month ago and because of Covid-19 everyone went remote, so I didn’t physically move to that city then. Now there are talks of going back to the office, and one of the developers on my team is also looking for a place to live so we started talking about rooming together.

    It seemed fine to me but then I realized I’d be spending almost ALL of my time with this person who I have not even met in real life yet.

    Do you think this is a good idea with a lot of convenience or a recipe for disaster? Have you ever lived with a co-worker? Any advice would be great.