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 277: Super long code reviews and replacement laptop

Download

In this episode, Dave and Jamison answer these questions:

Questions

  1. My company recently had a kerfuffle where some teams felt that reviewing a PR in less than 3 weeks was an unreasonable ask.

    As such, the company is trying to come up with guidelines for cross-team asks. The current proposal is for work of 1-2 hours they will commit to an SLA of 6 months. I feel this is a polite way of saying no to any request.

    Are there any ways we could come a more reasonable agreement on this?

  2. Hi, my laptop has died after upgrading to MacOS Monterrey and I’ve been given a 2017 Macbook with poor specs as a replacement due to no fault of my own.

    I’m at a startup of around 100 employees and I don’t think we’ve got a mature set up in terms of getting replacement machines.

    I’m a Senior Engineer and need a speedy laptop for my intense role. It’d be faster for me to use my personal MacBook than using the replacement, but I don’t think that would be allowed.

    How would you suggest I go about requesting a replacement MacBook with specs that fit my role? Do companies have budgets set aside for these expenses?

    Thanks

A smiling speech bubble

Episode 276: Startup or big company and negotiating your exit?

Download

In this episode, Dave and Jamison answer these questions:

Questions

  1. Hi guys, I’ve been listening for a few months now and am dissatisfied with my current work, where I’ve been for a year. I come from a research background, and now doing an engineering job at a B2B SaaS company is leaving me wanting a change. Moving between teams is not an option, so I plan to move companies early next year. My problem is that I don’t know whether to look for another large or mid-size company (I’m finishing final rounds at Facebook and Palantir), or go to a startup where it is likely to be more interesting (I have an offer to be the lead engineer at a very small startup, where there are already 5 developers). I have one year of industry experience. If I go to the startup, will it negatively impact my career in the future if/when I want to move elsewhere? Would it be easier to move elsewhere, and get a better offer or a higher position, if I work at Facebook or Palantir instead of this startup? Also, while I prefer research, I’m not in the position to go back to grad school and finish my PhD (I finished my MS and left to work) for monetary reasons, so I need to move to another engineering position.

  2. I’ve often heard of senior employees “negotiating their exit” instead of resigning/quitting, with rumors of large negotiated payouts. I assume that’s just a select group of people who can, but I’ve never seen much written on that. What is the situation where you can do this? How do you set yourself up for being able to get a payout like this?

A smiling speech bubble

Episode 275: Take-home tests and doing my own recruiting

Download

In this episode, Dave and Jamison answer these questions:

Questions

  1. I’m a developer responsible for hiring other developers for my company. I’m comfortable interviewing and I feel like I can get a good grasp on whether the interviewee is technically competent.

    My boss wants us to give a take-home technical test to people after the first interview if we’re happy with how they interviewed and want to proceed further.

    The current technical test is time-boxed and is designed to represent the work they would do at our company. I worry that we ask for too many requirements within the current time constraint of 2 hours, but asking for more time will put people off completely.

    What can we do to make sure the technical test is fair and a good experience for candidates?

  2. Hello Dave and Jamison,

    I am a team lead at a rapidly expanding company. We have been trying to fill open head counts (>4) for over a year now, and our team is also handed some very important and promising projects, and because of that, even more open reqs for our team. Recently in our 1:1, I was pressing my manager to fill the openings ASAP but he told me our company recruiters are so busy that our team don’t have any dedicated recruiters, and my manager have been sourcing candidates himself for almost a year now.

    I was surprised by that and offered to help. I had read some materials from the recruiting team, got the tools set up and ready to cold email people I found on LinkedIn. My question is, how do I approach them in an authentic manner? I am proud of my company and our products, but how do I reach out to them without letting them know my primary motivation is get more team members to do the work so I can get more sleep? On the other side of the table, I feel those recruiting emails are cold and a waste of my time. So looking at the funnel I built, I don’t know if I can bring myself to start spamming others’ inbox.