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 441: Will working in healthcare hurt my reputation and precious wisdom

Download

In this episode, Dave and Jamison answer these questions:

  1. I’m currently in the interviewing pipeline for an engineering position at a fairly large healthcare company. In light of the recent events surrounding UnitedHealthcare, there’s been renewed criticism towards the insurance industry as whole. I was interested in this position and the work culture seems good, but now I’m having second thoughts. If I were to accept an offer from this company, could it somehow negatively affect my career or reputation? I feel like I’m worrying over nothing, but let me know your thoughts. Also, hypothetically speaking, what would you do if you received a job offer at a company that recently had negative press?

  2. Hi! I’m an internal applications engineer, and after a couple of years of propping up a couple of different small and midsized companys’ intranets with duct tape and cardboard, digging through old, unmaintained code that nonetheless runs the business, and trying to decipher the intentions and reasonings of the Developers Who Came Before, I have landed what is perhaps the dream position: the primary internal applications developer at my new company is retiring, and the business has hired me on such that we have a few months for said senior developer to catch me up and hand things off.

    I’ve been brought through the basics; how to troubleshoot day-to-day misshaps, which clients need to be handled with care, and I’ve been shown the excel workbook that will make the finance department explode if it’s edited incorrectly. What other non-technical questions should I ask my senior before he leaves?

    Thanks and thanks also for an awesome show!

A smiling speech bubble

Episode 440: How do I help my boss not burn out and should I tell people I'm older than I am?

Download

In this episode, Dave and Jamison answer these questions:

  1. Stefan

    Help! Most of the time people ask questions about issues that already happened. I however, would like to prevent one.

    I am a young Tech Lead and really love my responsibilities, team and especially my manager. With the help of your podcast I could even resolve my last issue regarding compensation. Of course I dutifully did my part and reallocated some of my payment increase to finance Jamisons yacht.

    My very awesome manager “Bob” is so great that he has to manage 4 teams. Naturally, because Bob and those 4 teams are doing great, Bob gets rewarded with even more work. In his “free time” Bob is a parent of two teenagers which is also not necessarily known for being a stress free environment.

    Lately I noticed that Bob is more stressed than usual. Bob told me that he wakes up in the middle of the night because he remembers missed TODOs in the job. I also see this change in his body language and general demeanour.

    Now that a very critical project is coming up, Bob, as the go to person for more work has to allocate a significant time of his day to support this project.

    I fear that Bob is on a path to burnout and this new project might be the last drop. I would really hate to get a different manager. Statistics claim it will probably be worse… Also I really wish for Bob to be well and health, too. ;)

    How can I help Bob in his situation? How do I address those concerns with him without looking condescending? We have a good and open but not close relationship, that I would not like to ruin by overstepping my bounds.

    Thank you very much. I love the podcast. You make me laugh and learn with every single episode. You rock!

  2. I am a very young senior engineer at a big tech company and I think nobody really knows how young I actually am. I just turned 24 and usually in prior jobs other developers started hating me once they found out that I am this young and already in a senior role. Here at the current place, I have the feeling that all of the engineers in levels below me are already a lot older and have more years of experience under their belt. Also, I think they do not know about my age, because I never shared that in the recruiting process, nor later on. Usually people assume I am in my early 30’s and have a baby face, but when I tell them that I am a baby face because I am actually young, they become envious and things go south from there. Should I keep this a secret or am I playing too much into this?

    PS: I am also already married and have kids, so that could make them assume that I am older.

A smiling speech bubble

Episode 439: Harried VP of Eng and first startup job

Download

In this episode, Dave and Jamison answer these questions:

  1. What advice would you give for working with an ineffective leader whose input is crucial to your work? I’m a senior developer for a mid-sized non-tech company with probably 60-80 devs, and in the past year I’ve been working more with a VP of software who seems to still be involved in code details, getting pulled in to production issues, in-person code reviews, etc.

    He’s a nice guy, but he seems like he’s being pulled in too many directions at once. When he schedules a meeting, there’s a 50% chance it happens on that day and time, and when we do have meetings, if we bring up questions and high level issues we need feedback on he’s quick to “take ownership” and say he’ll do X and Y. Inevitably, X and Y slip down the priority list because production issues and who knows what else, and we’re stuck waiting weeks on end for something that if he’d just delegated the work to someone else, we’d have long since moved on. But we still need his input to shape our work. How can we as lower-level developers (with a manager who isn’t involved in this project at all) help mitigate these delays?

  2. I’ve recently accepted a new position after spending more than three years at my first job out of college. Currently, I’m a Senior Engineer at a large, corporate-like company (300+ people), but my new role will be at a much smaller startup (20-30 people).

    I’m excited about the change but also a bit nervous, as I know startups can be fast-paced, and I’ll need to get up to speed quickly.

    What advice do you have for setting myself up for success in this new role—both before I start and after I begin? I have a couple of weeks before my start date and want to use that time to prepare effectively.