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 178: Procrastinating colleague and working remotely for an on-site company

Download

In this episode, Dave and Jamison answer these questions:

  1. One of my co-workers never does their job in time and always postpones things. We are both leaders in the company. Especially when we depend on each other, it becomes really difficult.

    I tried many things like taking over their tasks, reminding them (in person, in Slack), escalating to their manager etc. None of these worked.

    As a different strategy, I organized a workshop with leaders to brainstorm how to collaborate and work together. That was really positive. We talked about each other’s responsibilities. This person was active in the workshop. Contributed and also agreed on many things. I felt really positive after this. :)

    But then shortly after, I ended up with frustration again. Nothing actually changed. Agreeing is easy but taking actions is not.

    Please give me recommendations other than quitting my job or waiting this person to quit. 😅

  2. I work remotely for an on-site company. How do you manage that relationship?

A smiling speech bubble

Episode 177: Work life vertigo and work life interviews

Download

In this episode, Dave and Jamison answer these questions:

  1. I started working at a big fintech company doing cutting edge work. I was given a ton of responsibility (owned a major component, built it from scratch, manage external relationships with vendors, had a team of 3 engineers, filed a few patents). I was extremely successful at this role but I was working 60 hours a week. Even though I was successful, I felt like I didn’t have good work life balance.

    I left and joined a well established tech company with 600 engineers. I’ve been here almost 1 year now and looking back I’ve only worked on menial feature work and software maintenance. Now I work 30 hours a week and have great work life balance. I feel like I gave up a great opportunity with my old role. How do I make the most of this role? How should I tell my manager I’m not happy? should I just look for a new job?

  2. How and when do you ask about or gauge work life balance in a job interview? I recently got to round 4 of an interview and a developer told me that a person wouldn’t do well at this company unless you put in a lot more than 8 hours per day and the CEO rewarded those who stay late at night. This indicated a bad work life balance to me so I didn’t proceed any further.

    Does it look bad to bluntly ask an interviewer “what’s the work life balance like” or ask about this in round 1? Do you think I am lazy?

A smiling speech bubble

Episode 176: Afraid to disappoint and tech co-founder advice

Download

In this episode, Dave and Jamison answer these questions:

  1. I am a junior developer with a low salary but I’m happy with my job.

    Recently, a personal/family problem occurred I needed more money to pay for it. I am three months away from my EOC (end of contract).

    I’ve found a job referral from my dear friend with higher salary and more benefits and I’m planning to apply. But after told my manager about my plans on leaving they told me they wanted to assign me to a top priority project they thought I could handle. I am so worried to disappoint them.

    They’re offering a raise but it’s not close to the other job. I’m afraid to ask for more because I don’t feel confident with my skills and I believe other people deserving it more. What are your thoughts?

  2. Hi guys, I am starting up a company in a few weeks together with a friend of mine. I’ll be the only developer in our new firm (for now!), while he’s got the domain knowledge. I’m not so worried about getting the tech stuff up and running. I get no constraints when it comes to the tech stack I choose, which is fantastic!

    What worries me is how to get into this brand new domain as quickly as possible, so I am able to deliver some value (MVP). Do you have any tips for how to go about this? I know I am not going to be an expert in the field, so at some point I just have to accept that and start coding. Anyways, I’ll learn more on the way..

    Thanks for a great show btw, Regards from Runar in Norway