It takes more than great code to be a great engineer.

Subscribe Now Support us on Patreon

Soft Skills Engineering is a weekly advice podcast for software developers. We answer questions about all the stuff you didn't realize you needed to know about being an engineer:

  • pay raises
  • hiring
  • going into management
  • annoying co-workers
  • quitting your job
  • meetings
  • micromanagers
  • installing a ball pit in your office
  • and much much more...

For answers to these and other questions, our hosts Dave Smith and Jamison Dance are here to help.

Why should you listen?

Soft Skills Engineering listeners are awesome. Here's what they are saying about the podcast.

Jack says:

Not only did Soft Skills Engineering help me land my first gig, I also used your advice to negotiate a $10,000 raise! I love your podcast and will continue to heartily recommend you to everyone I know!

Hdennen says:

Facing a 9 hour drive, I grabbed a bunch of podcasts to listen to. I don't even know what the other ones are. Seriously, this podcast is full of massively helpful and relevant content from two people who are experienced, funny, and insightful.

Saad says:

Listening to Soft Skills Engineering has completely shifted my thoughts on what it means to be an engineer. It’s probably one of the more useful things I’ve gained during my time at Amazon. It definitely helped me grow, and I’m totally indebted to you for that.

Recent Episodes:

Episode 89: Departed Engineers and Employment Contracts

Download

This week Jamison and Dave answer these questions:

  1. How do I deal with co-workers who constantly cite the decisions of engineers who don’t work here anymore?
  2. My employment makes it sound like the company owns my past work and side-projects. Is this true? Is this normal?

Episode 88: How To Dress For Interviews and Learning To Interview

Download

This week Jamison and Dave answer these questions:

  1. How do you dress for interviews? Full on informal beach bum? Smart casual? Formal suit tie?
  2. I’m a new developer and have been asked to interview incoming developers. How do I learn how to interview?

This is the NoRedInk interview process. This is the blog post Jamison likes on getting data out of the technical portion of the interview. This is a slightly pessimistic look at pitfalls in the standard interview process. Google wrote a great article about structured interviewing that might also be helpful.

Episode 87: Pushover Coworkers and Productivity Metrics

Download

This week Jamison and Dave answer these questions:

  1. My peers give up and say “have it your way” whenever we have technical discussions. How do I get them to be more vocal about their opinions?
  2. I like the idea of measuring things, but metrics seem easy to game. How do I effectively measure team and personal productivity?

Jamison cites this tweet and this blog post about examining your own productivity.

Episode 86: Sharing Salaries and Offensive Words

Download

This week Jamison and Dave answer these questions:

  1. Could you (Jamison and Dave) share some salary information publicly? It would help to know how much others make.
  2. My boss uses an offensive word in technical discussions. How do I ask him to stop?

Episode 85: Annoying Know-it-alls and Company Headshots

Download

This week Jamison and Dave answer these questions:

  1. One of my co-workers is a know-it-all, which is pretty annoying. How do I work with them?
  2. A former employer still has my photo on their team website eight years after I left. How do I get them to take it down?

Episode 84: Shy Developers and Outsourced Architecture

Download

This week Jamison and Dave answer these questions:

  1. I work with a very shy and anxious remote developer. How do I work effectively with them?
  2. Our manager is outsourcing the core architecture of our next products to an offshore team. How do I tell him I think this is a bad idea?

Episode 83: Gaps In The Resume and Moving To Business

Download

This week Jamison and Dave answer these questions:

  1. I think I’ve saved enough money to get out of the rat race. If something goes wrong and I need to get a job again, how do I explain a long gap in my resume?
  2. I like writing code but I’m interested in moving to a more business-focused role. How can I test this without burning bridges? Do I need to take a pay cut?

Episode 82: Blow Ups and Job Security

Download

This week Jamison and Dave answer these questions:

  1. How do I smooth things over after a blow-up between team members?
  2. A team mate admits he writes bad code on purpose for job security. What do I do?

Episode 81: Unwilling To Grow and Forced Out During Two Weeks Notice

Download

This week Jamison and Dave answer these questions:

  1. A developer on a team I lead doesn’t seem interested in growing. How do I help them engage more?
  2. I gave two weeks notice, but was told part of the way through to not come in any more. I still had work left and this made me feel bad. Is this common? Did I do anything wrong?

Jamison talks about the Khan Academy engineering culture. He kinda misquoted it though. They don’t explicitly say they lay people off who don’t progress.

Episode 80: New Team Leads and Constant Follow Up

Download

This week Jamison and Dave answer these questions:

  1. How do I keep up with new tech as a team lead?
  2. I manage a team. A manager from a different team wants me to run everything I do in my team by him. What do I do?

Jamison mentions this by Charity Majors on the pendulum between technical and people leadership.

Jamison also mentions this HBR article on employee happiness.