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 267: Cheap promotion raise and live coding blues

Download

In this episode, Dave and Jamison answer these questions:

Questions

  1. I work for an all-remote company and I’m about to get promoted. The company says they target a salary increase of 5-10%. Assuming they come to me with an offer on the low-end (5-6%), what’s the best way to go about negotiating a higher raise during promotion? I want to stay at the company and also want the shiny new SENIOR job title, so I feel like I don’t have much leverage in this situation. Any advice is appreciated!

  2. Rachel asks,

    Live coding makes me choke. As soon as someone else is watching, my brain immediately goes to mush and I’m like a chicken with my head cut off. Actually recently I learned it’s not just live coding – it extends to live spreadsheet-making and live cooking as well! I guess I’m not into performing? Anyway, this has come up because it’s impacting my career in real ways. For interviews I offer to do takehomes, which I’m great at, but sometimes I’m told live coding is the standard they apply to all applicants. What’s a non-live coder to do?

Show Notes

Consumer price index: https://www.bls.gov/news.release/cpi.nr0.htm

@Channel Twitter account: https://twitter.com/Channel

https://interviewing.io/

A smiling speech bubble

Episode 266: Switching tech stacks and awkward zoom silence

Download

In this episode, Dave and Jamison answer these questions:

Questions

  1. Should I change tech stacks every few years in order to not get pigeonholed?

    Is it a good idea to stick with a tech stack for as long as I can or should I follow the market trend and try to learn another promising tech and then try switching into that?

    Would you advise me to be more of a specialist or a generalist early in my career, and what about later when I’m more experienced? I’m a full-stack web developer who’s just starting out my first job (if that matters)

  2. I love this show so much, I’m even trying your goto advice - quitting my job! But not untill I’ve got another lined up so shhh about it already. In the mean time, I work for a huge agency as a senior(ish) developer and have recently started work with a new team. However, they have issues: no one turns on their camera for video calls, which I’m ok with, but it makes the next bit worse somehow - most say the absolute minimum in response to any questions and offer no opionions / thoughts / ideas. It makes things like sprint retro meetings very awkward. We have a scrum master running our meetings who is clearly struggling to engage the team, I try to hold off to let any of the others answer questions but I always seem to end up picking up the slack. I’ve even started timing how long I’ll let the slience endure before jumping in to answer, I’m now waiting 15 seconds. Have you come accross this before? How can I get people to engage more?

A smiling speech bubble

Episode 265 (rerun of 216): One-on-ones and inter-team power struggles

Download

In this episode, Dave and Jamison answer these questions:

Questions

  1. I have a weekly one-on-one with my manager. What should I talk about in them? Things like feedback and career goals become old and repetitive real soon, and I end up discussing current work items. I understand that a one-on-one is my time to ask questions and don’t want it to be a longer daily-standup.

  2. My front-end team mates are in a power struggle with my back-end team mates and my design team mates. They’re intentionally making technical decisions that artificially constrain the choices of other teams.

    For example, design wants a certain interaction for a new feature, and my team says “nope, it can’t work that way, cause the components we built don’t allow that”. Or, they make tickets for the back-end team as in “endpoints have to work this or that way, because our components assume that structure”. This often seems detrimental and confusing to other teams.

    When I push back against my team they are angry. When I defend my team other people are angry. When I try to strike a compromise I feel gross because I usually think my team is wrong. I’ve tried talking with other teams and managers about the problem. I feel gross about that too because I don’t want to point fingers or throw my team mates under the bus. Where should I even start?