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 164: Fear of firing and disengaged teammates

Download

In this episode, Dave and Jamison answer these questions:

  1. Hello,

    First of all, I love the show, thank you so much for the amazing work!

    I always think I’m going to be fired.

    I’m an extremely anxious person so I feel the need for constant feedback and for someone to tell me everything is alright. Minor problems send me into absolute despair. How can I deal with such anxiety?

    I frequently ask my manager during 1x1s if everything is alright and how I’m performing and he almost always says things are going well.

    In our 6-month performance reviews I get more detailed feedback on what I’m doing well and what I can improve. This makes me feel less anxious because I know exactly what my boss is thinking. Even if something has to be improved, at least I know it.

    Are there any indicators I can use to tell if I’m about to be fired or if my manager is happy with my work? I’ve told my manager about my anxiety and that I’d like constant feedback. That has helped, but I was hoping to get more detailed feedback. Preferably this feedback would make me able to tell, in a scale from 0 to 100, how well I’m performing.

    Thank you very much!

  2. Hey Dave and Jamison, love the show your insight.

    I have been having a problem on my team that I hope you can help with.

    We are a team of engineers that have internal customers. It’s a bit of a back end of the back end role.

    The problem is NONE of the other engineers are customer focused. They don’t engage with the real needs of our customer teams. Tickets come in, they do what’s in the ticket as it reads exactly and we end up with requirements getting lost, tickets needing to be reopened and our reputation going down the tubes.

    I have taken it on myself to engage with the customer and help them out. BUT, now I have become a glorified customer service rep and I can’t do much of my own work because I’m passing messages back and forth between engineers who don’t like to talk to their customers.

    My manager says the team needs training and he is going to work on it with them, but this has been going on for months. Should I take the Soft Skills advice of ‘Quit your Job’, or continue being a middleman?”

A smiling speech bubble

Episode 163: Sounding a warning and negative Glassdoor reviews

Download

In this episode, Dave and Jamison answer these questions:

  1. I recently joined a new team to help rewrite a batch job whose source code has long been lost. After taking some time to learn the tech stack and the business problem, I realized that the current approach will not let us meet our nightly deadline. Even a very generous back of the envelope estimate suggests that we’ll miss it by two orders of magnitude. I have some ideas on how to maybe fix this… buuuttt…

    I brought my concerns and calculations to the lead project engineer who dismissed them outright. They did not offer an explanation for why I was wrong, even when I asked for one. I started a proof of concept to illustrate my point, but there were some weird conversations that suggested that I should just drop the issue.

    I know how to make a technical argument about my concerns, but apparently that isn’t enough.

    How can I get fellow engineers to at least take my concerns seriously, not just for this project, but generally? I’m only 3.5 years into my career, so is it just a seniority thing?

  2. Hi! I’m a software engineer and I’m currently looking for my next job. It will be my second-ever job, so this means this will be my first time putting the Soft Skill Engineering advice (““quit your job””) in practice. Woo-hoo! Anyway… Browsing the job offerings I often check Glassdoor to see what people are saying about the given company, and I found a lot of negative reviews. I imagine sites like Glassdoor are negatively-biased, but these reviews left me wondering if there is any way I can investigate how good or bad working for the company would be. Maybe through some questions during the interviews? Any idea? By the way, I love the show, keep up the great work!

A smiling speech bubble

Episode 162 (rerun of episode 113): Quitting Your First Job and Too Many Responsibilities

Download

In this episode, Dave and Jamison answer these questions:

  1. How do I quit my first job if I’m working with a manager I love?

    I started my first full-time job about two years ago and I’m starting to think about looking for a new job, both because I am ready for new challenges and I’m ready to move to a new city.

    I have a great working relationship with my boss, so a part of me wants to tell her about my interest in finding a new job, both so that I could use her for a reference and also so that I can be honest with her about my intentions. She’s been a great boss and mentor to me, so there’s a part of me that doesn’t want to jeopardize our working relationship. But another part of me feels like I might be jeopardizing my presence in my current office if I make it clear that I am looking to move on, especially if my job hunt doesn’t go as smoothly as I hope.

  2. How do you deal effectively with rapidly increasing work responsibilities?

    My technical lead was recently promoted to management. Being both ambitious and the only Sr. Engineer without retirement plans in the next 4 months, I immediately stepped into the power vacuum and inverted a binary tree faster than all my coworkers to establish my position as new tech lead. After a few months the other senior engineer on my team retired, and I’ve ended up holding the bag for my new job responsibilities, my old responsibilities as a Sr. Engineer, AND the departed Sr. Engineer’s responsibilities.

    I told my manager how much was on my plate and that I was afraid my work output would suffer, and her response was to throw money hand over fist at me and promise to backfill both Senior positions within the next 12 months.

    How do I get through the next 18 months without losing all my hair? Are there any strategies to make sure the team doesn’t go up in flames when I forget about a key deadline? Or at least position myself so that nobody can tell it is my fault until I can make a subtle getaway in the brand new Ferrari I’m going to buy?