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 282: Setting boundaries late and junior joy


In this episode, Dave and Jamison answer these questions:

  1. Listener Rafael asks,

    If you’ve already been working at a company for several months, how do you set boundaries with your employer as to when, time during the day, it’s acceptable for them to contact you? What can you say to your employer or colleagues if they expect you to respond to correspondence at all times, with a 30-min turn around? Can you adjust expectations after you’ve been working the role for several months, or is it too late?

  2. Hi, Do you see any benefits to being a junior developer? Any advice you would give to a junior, like “Hey, do this while you’re still a junior, once you’re a senior+ it might be harder to do or find time for it”?

A smiling speech bubble

Episode 281: Contractor is sus and too much job hopping?


In this episode, Dave and Jamison answer these questions:


  1. Zach asks,

    A few weeks ago, I interviewed and recommended we hire a contractor candidate, who I will call “Bob”. We hired “Bob”. Today was the first time I saw “Bob” since the interview, only “Bob” was not the person I interviewed. It seems “Bob” had someone else pretend to be him to pass the interview. What should I do?

  2. Thank you for doing this show, it’s amazing and I look forward to listen to it every week. I’m a software engineer with 3.5 years of experience and in those years I’ve worked at 5 different companies consecutively, increasing my salary by around 50~70% every time I change jobs. At this point I’m afraid that it looks really bad in my resume since the longest that I’ve been at one company is 1 year and 3 months but at the same time it is really tempting to keep growing my salary and benefits that easily. Does changing jobs every ~1 year have a negative effect on my employability in the long run?

A smiling speech bubble

Episode 280: Async communication and how to quit not nicely


In this episode, Dave and Jamison answer these questions:


  1. Starting to work on a team that is split across time zones. With a majority of the company based in one time zone and a handful spread in others. I want to emphasis the importance of asynchronous communication. I have found Slack to begin to feel like I need to respond ASAP instead of when it is convenient.

    If we were to say slack is used for asynchronous communication, is asking the team to use signal or even text appropriate for a quicker response?

    What is a good way to reach out to team members in cases where a response is needed more immediately?

  2. After about 1 year at my developer job, I was moved to work for a client company helping them launch a new product. This other client had different plans, it turns out, and now I’m just testing their API for them. That’s fine but I never get questions answered and I hate my job with my client and hate my job with this company that sells me like a cheap piece of meat. I want to quit, I will quit, but I have a lot to say about why I’m quitting. How can I NOT be nice about quitting and the reasons I’m quitting, and still feel comfortable showing my face in the industry again?

    I haven’t quit a job before, and this is my first job in the tech industry. Searching how to quit a job always comes with “remain light and positive.