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 448: Title over salary and from figure skater to software developer

Download

In this episode, Dave and Jamison answer these questions:

  1. A listener named Steven says,

    Long-time listener of the podcast here—it always brings me so much joy!

    Should I prioritize title over salary?

    I’m currently based in Europe, working as a Senior Engineer at a big company that pays really well. The problem is, there’s almost no chance for promotion due to the economy and budget constraints. Plus, because of the organizational structure, I’m stuck solving small problems that don’t have a big impact. It’s frustrating—but again, the pay is great.

    Recently, I got an offer for a Staff Engineer position at another company. The catch is, the pay isn’t as good (30%+ cut), and I’m not sure about their culture or structure yet. However, the title could potentially open more doors for me in the future.

    Should I take the offer, accept the pay cut, and hope it’s a step forward for my career?

  2. Hello! Long time listener, first-time caller :-) I’m on the final stretch of classes to finish my BS in computer science at WGU, most of which I’ve done while working. I’m now 40, and I have had 3 previous occupations and employers: aircraft mechanic for 5 years at a small shop, figure skater with Disney on Ice for 6 years, and most recently a partner at an environmental remediation/heavy construction firm for 10 years where my primary responsibilities were field crew management and technical writing for ecology reports. I would love your advice on how I could use these experiences to stand out on a resume or in a job interview. How can I indicate that I’m a hard worker and that I know just enough to know that I know nothing and am ready to learn? Thank you for your time, keep up the good work!

A smiling speech bubble

Episode 447: Overleveled at FAANG and accidental draft feedback

Download

In this episode, Dave and Jamison answer these questions:

  1. I am a mid level engineer overleveled as a senior engineer in a FAANG company. I got super lucky landing this high paying remote job, but dang… I did underestimate the expectations for my senior level. I had no FAANG experience before, just working at startups, flat hierarchies, just doing the heavy lifting coding.

    Now it is all about impact and multiplying impact across the team. I am told I should do less IC work and more leading of projects and owning initiatives.

    Can you give me some general advice on what actions I can take to get from the mid-level to senior-level? I am not really sure, what taking ownership really means in practice… These just seem like empty phrases to me without a meaning…

  2. I have had a bit of time, while running a 40 minute build, so I looked into open pull requests. One PR caught my eye and I started to read through it and left a comment with a suggestion for a small change. All in all sounds good probably, but the caveat to this is, that the PR was marked as Draft.

    I was thinking that it would be useful for the author of the PR to already get some suggestions during development, but the response got me thinking. The author passive aggressively mentioned that the PR is in Draft and that there is more work to do.

    Am I the jerk for commenting on a draft PR? Second question, what other things should I pay attention to in code reviews to not be a jerk?

A smiling speech bubble

Episode 446: Wading through AI slop and they don't get git

Download

In this episode, Dave and Jamison answer these questions:

  1. A listener named Matthias (mah-TEA-as) asks,

    In episode 444 you’re talking about the problems when hiring in the age of AI. I’m a manager who’s trying to hire right now and frankly I’m at a loss. If feels like I’m wading through a sea of AI slop. What tips do you have to cut through the slop and reach actually good candidates?

  2. Where I work the developers do not seem to “get” source code control systems like git. I’m not a developer but have worked with developers at previous jobs and usually the developers instituted good source control practices themselves.

    Our developers know they should push their code to the repo but only do it weekly/monthly, treating it as a “backup”. Some back up their laptops using tools like Time Machine so think have taken care of safeguarding their source code that way.

    How can I convince them that working in git, committing their code as they go, pushing regularly, branching/merging, tying code updates to tickets, etc will benefit them far more in the long run?