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 188: Drama overload and agile ouroboroses


In this episode, Dave and Jamison answer these questions:

  1. I work in a charity as an iOS developer and there is so much drama in the office about anything. I am so scared to talk with my backend engineer about work that we created a non-company slack workspace. This is how we communicate, even though we sit right next to each other. Please send help.

  2. I work in a company that’s around 10 years old with 1800 employees that started implementing agile methodologies a few years ago. It was great and improved the work, but now all the agile coaches are pushing to have physical boards and doing things apparently just to justify their own existence. I agree we all should try new methodologies but shouldn’t it always be based on a problem we are trying to solve? And shouldn’t all the team be on board with the change instead of just doing it because the agile coach wants to?

A smiling speech bubble

Episode 187: Interview insanity and making up for lost time


In this episode, Dave and Jamison answer these questions:

  1. Hello there!

    To say things pretty directly, I hate the recruiting process in software engineering, especially coding tests on whiteboard during interviews. It makes me very nervous and I already missed a job opportunity because I could not handle my stress correctly. Plus I think that the problems asked in those interviews are irrelevant to the day-to-day job, which means that I need to study again sorting algorithms and tree balancing every time I want a new job. How do you deal with those interviews? Do you do heavy preparation? Do you think that the interview process is stupid too? Should the permanent access to StackOverflow be stated as an elementary dev’s right :D ?

    Thank you very much, keep on the excellent job :)

  2. I’m in my mid 30s and have been coding for about 20 years, I have a non-technical bachelor’s degree and have had a fairly varied career. I did freelance web development work throughout college, and then after college had a couple of different jobs as the sole in-house web developer for two different small media companies. After that I spent some time running my own web dev/design business with some partners, freelanced some more, and then finally decided to get on the career track about 4 years ago. At that point, I ended up taking a remote developer job at a small company of about 8 people with no real hierarchy or management structure and worked there for 3 years.

    About 6 months ago, I moved on from there to what now feels like my first “real” job at a tech focused company (still remote), and while I’m happy with the work and compensation, I’m realizing that I’m at the bottom of the software developer hierarchy and there are many people above me who are a fair bit younger and, I assume, less experienced than I am. I don’t mind being subordinate to younger devs, but I do feel like my career is a good 5 or 10 years behind where it should be because until now I haven’t worked in an environment where it has been possible to earn a senior, lead, or management title. I’ve been coding for a long time and am very interested in moving up the ladder, leading a team and working more at the product level. Do you have any advice for how I can accomplish this quickly and make up for lost time - especially considering I’ve only been here for 6 months?

A smiling speech bubble

Episode 186: First job negotiation and am I a senior engineer?


In this episode, Dave and Jamison answer these questions:

  1. Hi! I am 29 years old and a couple of years ago I decided to turn my career around by going from teaching history to frontend development. After 2 years of education I am now doing my first internship in small but established company. I have the feeling I will soon be offered a full-time position.

    How can I ask for the best job offer (salary-wise) accordingly to my age but few experiences? I don’t want to be perceived as ungrateful, nor be exploited and get underpaid.

  2. How do you know that you are a senior engineer? Not just the title you are given, but when do you really feel like one? Some people relate this to experience, but you can be coding or doing crappy stuff for 10 years so for me this is not the answer.