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 336: Roadmap roadkill and returning to office

Download

In this episode, Dave and Jamison answer these questions:

  1. Dear Dave and Jamison,

    I work for a medium sized startup, and our planning process sucks!

    We used to do quarterly planning, and it seemed like the product managers had no idea what was going on at a higher level. The big focus seems to have changed every quarter that I’ve been here, and the whole planning process is a charade: 75% of the so called ‘road map’ gets thrown away after a few weeks.

    Normally, this wouldn’t bother me, but I end up spending a lot of time in meetings helping these product managers come up with plausible timelines and making sure that what the business wants to build is actually feasible, and it’s bad for my morale to see so much of my work wasted.

    The product management team heard some of this feedback from me and others, and started changing to ‘continuous planning’, but now there is even less structure for when they build the big spreadsheet roadmap for the quarter. They bought new tools, and don’t seem to be using them.

    Should I suck it up and just check out or try and get a license to use the patented soft skills advice and quit my job?

  2. Hi Dave and Jamison in no particular order.I have been listening to the podcast for a couple of months now. I have enjoyed every episode and and the advice you give.

    I am a junior software developer who has been working at a startup 9 months ago. I was offered a remote junior position and accepted even though the company is based in a neighbouring city. This made sense at the time because I would not have to worry about commuting to the office.

    3 months ago my manager suggested that I come to the office more often as this would benefit my development and give a me a chance to socialise with my co-workers. We agreed that I go in 3 times a week.

    Now the past few weeks there has been pressure to start coming to the office full time.

    I would be fine with this but the problem is that I currently do not own a car and have to rely on public transport to get to work. With public transport it takes almost 4 hours to get to and from work each day (I actually listen to multiple episodes of the podcast on each trip) There is about 40 minutes of walk time included in that because the nearest bus stop is not close to the office.

    As you can imagine that is physically draining and also affects my work life balance as I spend almost 15 hours of the day either travelling and working. My biggest concern now is that 9 months ago If I was offered this job but as full time on site I would not have even considered it.

    Do you have any advice with how to refuse going to the office more often without making it seem like I’m opting out of an option that is more beneficial to my career. Thanks in advance.

A smiling speech bubble

Episode 335: Senior questions and overly optimistic

Download

In this episode, Dave and Jamison answer these questions:

  1. Greetings Jamison and Dave, love the show and all your shenanigans! I’m a mid-level dev who has quit my job (TM) a few times. While I feel like I’ve absorbed some good experience from each company I’ve been at, I also feel like my training is not yet complete.

    At my last company, I hit my ceiling as a dev but I also felt the bar was really low. I had to do a lot of hand holding and fielded a lot of engineer questions that could have easily been Googled and it was really frustrating. But now I’m at a place where I feel everyone else is heads and shoulders above me. The tables have turned! I’m trying to learn as much as I can on my own but I’ve found there are limits to what I can do. I feel like I’m drowning but I’m timid to ask too many questions because I remember how annoying it was to get pinged every 10 minutes at my previous job.

    What are some tips you have to navigate the murky waters of being a mid-level dev wanting to learn as much as possible to become a seasoned dev without giving off an “intern smell”?

  2. Listener Charlie,

    Nearly all your answers presuppose a software engineer has a good manager and leadership. Why is this?

A smiling speech bubble

Episode 334: Personal brand and awkward silence

Download

In this episode, Dave and Jamison answer these questions:

  1. Long time question asker, first time listener. I recently started to go back through the original episodes of this podcast where a few episodes were themed were around networking, open source work, and building your personal brand. I just wanted to share my “NETWORK=NETWORTH” story. About a month ago my CEO was terminated by our board of directors, a week after it was announced that we were having layoffs for the vast majority of the company. I had been with this company for around 4 years, a lot of my work had been doing open source projects and interacting with various other companies. Unfortunately I was one of the people who was let go as part of these layoffs. I immediately reached out to various folks in the open source world that I’ve interacted with, seeing if their companies had any openings. Within two weeks I was able to interview and get an offer without a technical interview. Building my “personal brand”, interacting with the open source community had turned a pretty stressful situation into one that was relatively a lot less stressful!

  2. Listener Stochastic Beaver asks,

    I’ve recently joined a big tech company remotely and my team is super AWKWARD. No one says anything non-work-related in team chat. My manager is the only one with a camera on in team-wide meetings. I barely saw anyone’s face. When I try to chitchat about their life during in 1:1s, somehow they don’t feel like interested in talking about themselves so I eventually stopped asking anymore. In meetings, my manager is most vocal person within the team and the other people barely speak. As a result, it’s always feels like my manager’s one man show trying to make a conversation and discussion and throwing a joke and the responses are usually some ‘lol’ in the chat.

    It’s not that the team members are not engaged to the team. Everyone is very passionate and I usually see their work related messages, code reviews, and emails coming back and forth after the evening, even in weekends. Is this normal that all the people are extremely shy in the same team? I like the work and the problem we’re solving but sometimes I find that the silence in the air is suffocating me and I also want to establish a good relationship with my coworkers. Am I asking too much for them in ‘work’? Thanks for listening.