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 425: Org chart bait and switch and ole' reliable

Download

In this episode, Dave and Jamison answer these questions:

  1. I was hired at a medium sized company as a staff level IC a few months back and a big reason I accepted the job was because I would be reporting directly to the CTO. I took a significant paycut in exchange for the opportunity to learn and grow directly under this leader, as this is a career path I am interested in.

    Three months later and without any heads up, I was reassigned to a different manger one rung lower in the org chart. One month after that, my new manager abruptly left the company. Still don’t know why. I was then reassigned to a leaf-node manager and I am now several hops removed from the CTO. So far I haven’t said much because rocking the boat too early in a new gig has gone poorly for me in the past. In hindsight this was probably a mistake but I’m afraid I missed the opportunity to say “hey now, wait a second…”.

    I don’t want to hurt this current manager’s feelings by telling them I don’t want to report to them, but also I am now both severely underpaid and reporting to someone who is technically at a lower career level than I am. What do?

  2. I’m a manager in a company which I joined after college. I’ve been here for 16 years. We have grown to 180 employees but still work like a startup in many senses, like talking multiple responsibilities. So although I manage a team I’m still hands in the code at least 50% of the time. I know most of tech stack and services but am jack of all master of none type.

    Recently, management has been pushing me to take more technical responsibility. I want to do that, but it is challenging and takes more time. My CTO is super fast and churns out CODE like a machine and I feel much slower than them.

    The work is pretty decent and challenging. I get to work on new stuff but have gotten comfortable here. When I think of looking for a change and look at the expectations from other companies they are technically challenging. I worry I have missed out on learning new things by staying so long at one place. What should I do, stay or move on? I haven’t interviewed for a new job in 11 years, so that’s another fear I have.

A smiling speech bubble

Episode 424: Bragging without ego and how to predict layoffs

Download

In this episode, Dave and Jamison answer these questions:

  1. Listener Billy Bob Taco asks,

    I work at a small-medium startup, as a member of a very small team (read: just me). I work on infrastructure and APIs that support every other team, such as mobile and web clients, as well as other services. I’m relatively junior, and had to work hard to prove myself in this role. I do 100% of the system design and maintenance as well as feature development. I’ve been told on job interviews that I came across as a “little egotistical” when describing the role and the impact its had, but I don’t really know how to soften it! It’s my experience that I’m talking about when trying to share my ability and potential to fill a role. Help?

  2. Listener TimeDisplacementBox says,

    Great show, your future episodes just keep getting better and better. I have a question about avoiding lay offs. In this timeline I recently joined a large company out of college. I worked hard and surpassed goals set by my manager, getting very positive feedback at review time.

    However, a few weeks ago I started hearing that the company was over budget in engineering, huge changes started happening in upper management, and less work started flowing to our team. The concern was grounded in reality as one morning the company disbanded the team and laid off some of the newer hires including me.

    Aside from additional time travel, are there any questions I can ask during interviews to help ensure I am getting into a team that is safe from lay offs? And on the job, can you directly ask your manager if lay offs are in the future, or do you just need to watch out for the signs?

Show Notes

https://www.explainxkcd.com/wiki/index.php/2347:_Dependency

A smiling speech bubble

Episode 423: freedom from deadlines and Actual firefighting to software firefighting

Download

In this episode, Dave and Jamison answer these questions:

  1. Thank you hosting this show. This show has given me a lot of insight on nuisances of engineering that isn’t mentioned anywhere. Having some experience in industry for a while, I always find in this position where I want some autonomy but I am bounded by the deadline. What do you think should be the way to start a career that gives autonomy while having that sweet benefits from the industry?

  2. I used to be a senior manager of an operations team for a fire fighting service in Australia. I managed all of our physical operational assets - for example radio towers, mobile communications e.g. 5g, 4g technologies, mobile data terminals e.g. laptops in fire fighting appliances “fire trucks ;) “, data centers, networking so on…

    A restructuring means my team has grown to include in-house software development. While i am excited for this opportunity and on board with the changes, it is a very big shift from the physical and electrical engineering side to software development.

    The C level staff thinks the team lacks focus and there are “problems” to address.

    I have been meeting the new team and working through the changes. They are very nervous and are skeptical about how I’ll understand their world, which is fair.

    How can I best support this team? What are cultural things I should be aware of? What are key metrics I can measure that will fairly represent their hard work to the executive team? Any thoughts on what things a manager or managers can do to be supportive as the new drop in from across the room from a entirely different engineering discipline? Coding in my world is scripting and hacking about to make things work (telecommunication engineer)