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 230: Not seeking promotion and taking code

Download

In this episode, Dave and Jamison answer these questions:

Questions

  1. Taylor asks,

    Is it frowned upon to not want to be promoted and get more responsibility? I want to keep a good work-life balance but feel that saying so will have my manager think less of me.

  2. Hi Dave and Jamison, love your show! The time has come to quit my job and I am wondering if I should keep a copy of the scripts I wrote for the project?

A smiling speech bubble

Episode 229: Other people's code and moving into product management

Download

In this episode, Dave and Jamison answer these questions:

Questions

  1. I have been working at a large tech company for two years now, after I graduated college. My job title is ““Software Engineer””, but I have barely written any code on my job in the past two years. I’m on a product team that doesn’t own any infrastructure, and when the product managers want us to build something, we find out which teams in the company own the infrastructure and stitch a product together. We often get push backs because usually the infrastructure we need to build a product belong to some entirely different team who do not have stakes in the product we’re building.

    I am worried that my coding skills are deteriorating, since most of my time at work are not spent on coding. For example, meetings where people hash out how to do something in a system none of us are familiar with, chasing down people in other teams to ask them to squeeze out time from their busy schedule to help my team, and completing process paperwork. On the rare occasions when I do make code changes, it’s been copy-and-pasting another section of the code/config and changing a few parameters.

    It seems to me that success on this job depends mostly on knowledge of the different internal systems, as well as the social capital of knowing people on different teams. Is this normal? Is this what software engineering is about?

  2. Hi there! Love the show and your fun but useful answers.

    I have a career question and would love to hear what you think.

    I’ve been an Engineer for several years now and was recently asked if I’d like to move into Product Management. At first this sounded great. I’d get to set the direction of the product, get involved with strategic planning and roadmap meetings, and generally have more input into my squads work.

    The thing is … that isn’t what it is at all. Most of the time I am fielding requests from marketing and sales people for sales collateral, sitting on customer calls, and digging through dashboards to find enough ‘evidence’ to prove why we should prioritize the backlog the way I have in mind, and I have even become the ‘bad guy’ when the squads ideas don’t line up with the Product team.

    Have I made a terrible mistake? Is Product Management really a good move for Engineers?

A smiling speech bubble

Episode 228: Unpaid team lead and banking hours

Download

In this episode, Dave and Jamison answer these questions:

Questions

  1. I’m a team lead right now, but I’m leaving the company. When I discussed with my manager, I recommended a team member to take over my position and suggested raising his salary. In the end, the manager asked that team member to take over as team lead, but refused to raise his salary or even give him the title.

    He said he needs to prove that he can take responsibility as a team lead. Then he will get the title and raise. But I feel they just want to procrastinate and save the money.

    What can I do to help my team member fight for the title and raise?

  2. Hi Dave and Jamison. You have a great show and I really enjoy listening. I am currently a software engineer at a small/medium sized tech company in the healthcare industry. I was recently asked to interview for a similar role at a pretty large hedge fund. I am wondering if there would be a big culture shift if I were to end up making that change. I am under the (possibly inaccurate) impression that for bankers something like an 80+ hour work week is common. I’m wondering if this impression is accurate, if it extends to the finance industry as a whole, and how much it extends to developers rather than bankers/traders if so. I also remember you guys mentioning in a previous episode that video game developers also typically work long hours. Are there other industries where this culture is typical?