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 310: Flip flop and architecture astronaut


In this episode, Dave and Jamison answer these questions:

  1. Hey guys! Love the show!

    I’ve worked for 8 years as a Software Engineer for a large aircraft company, and while I had a great time there, I left because I was tired of working with old tech and wanted to learn new stuff.

    I joined a medium-size company, working with lots of fun new tech, but after 8 months I got the opportunity to get my dream job as a Software Engineer at a specific Big Tech company.

    The problem is that after I started on my dream job, I “crashed” really hard. The people and org are great, but the job revolves around working with a large legacy product, using mostly old/basic tech, and overall I’ve been feeling really unmotivated since joining.

    After 4 months there, I was called by my previous fun job, and they offered me twice as much as I’m making at this Big Tech company to come back.

    I’m very tempted, but I’m afraid of screwing my resume by leaving so early. Should I toughen up and stick with my new fancy job, or go back and make more money and maybe be happier?

  2. Hello Dave & Jamison,

    First time, long time - I am 6 months into my first engineering job and loving it! (until recently…) my large team split into smaller teams. On my old team, we had lots of work to do and it was fun. My new team, however, is suffering from “spin-up time.” My tasks have shifted from clearly defined individual contributor type tasks, to amorphous research tasks on large architectural decisions. After about 3 months of this, it feels like this spin-up time is never going to end and we just don’t actually have much work coming our way.

    On the one hand, these are more senior engineering type tasks and I could probably learn a lot if I stay to see these through.

    On the other hand, I am certainly not at a senior engineer level and I miss spending my time coding. It was fun and I was learning a lot from that too. I fear that I may be atrophying as I haven’t done much coding for multiple months.

    On the third hand (I have three hands), I could definitely be making more money elsewhere.

    Should I stay and be patient, or is it time to take the magical SSE advice? is the economy crashing? I need help!!!

    Thanks, you guys are the best, Johnny Threehands

Show Notes

Architecture Astronaut:

A smiling speech bubble

Episode 309: Missing boss support and new manager, who dis


In this episode, Dave and Jamison answer these questions:

  1. I am working on a devops team building the shared services that our engineers depend on: log aggregation, CICD, Monitoring, K8s clusters, etc. The team is myself, my boss (lead devops engineer), and a handful of pretty junior people. I feel pulled in a bunch of directions. I’ve asked for written documentation from my boss to help establish expectations and processes. Think branching strategies, who owns what, what should be prioritized. I want to make it easier to train up the junior people on the team and enable us to push back when devs ask for stuff with no context of what it will take to finish. Nothing has been written. It’s starting to get to me because without that it’s very difficult for me to push back on requests from the developers on our various teams. How do I tell my boss that I feel like he’s letting me down and that I’m drowning because it seems he just can’t be bothered to write down some base information?

  2. I have been working with my manager for almost a year to be promoted. I have been making a lot of progress on my tasks and as a developer. My manager agreed that I would be promoted in the next month or so if I kept it up. Then he quit to go to a new company. I now have a new manager and I feel like I have to start from scratch. Not much has been translated over from the old manager to the new manager about my progress. The new manager is now telling me there is no way they would hire me as a mid-level dev. I feel like I wasted a lot of time with the old manager and that the new manager is not seeing my value to the company and all the work that I’ve done to this point. I’m not going to quit or anything but I just wanted to rant. thanks for listening.

Show Notes

Writing strategy and vision documents:

A smiling speech bubble

Episode 308: FAANG to startup and Google interview prep


In this episode, Dave and Jamison answer these questions:

  1. I’m currently working at a FAANG in Europe, and seriously underpaid. I recently got an offer from a US startup (Series C funded) to work remotely. Two big pluses: I’m gonna get a 2 times pay bump, and I can finally work remotely (and travel across Europe since they support work from anywhere, now that COVID restrictions are relaxed, something I wanted to do for years). Two problems: Their tech stack is Ruby on Rails, something that no “big” companies use so I may not be considered seriously because of last X years of working on a not-so-famous tech, and current tech environment screams of a recession, so I’m safer at a big company than some startup. Do you think 2.5 years in a FAANG provides enough of credibility to take care of both of these problems if things go south? Any other factors I should consider when moving from FAANG to a remote startup job?

  2. So I’ve been working at this big-tech company for around 4 years and working as a mid-level engineer. I recently got approached by a Google recruiter for L5 or Senior engineer position. I’ve led a few projects in my current company, but I don’t consider myself a “senior” level. That and the fact that I’ve worked majorly in Frontend and the role I’m gonna be getting interviewed for is Full-stack (interview rounds seem to be focused on Distributed systems mostly).

    I’ve two questions:

    • Is this some dirty trick in recruitment I gotta be aware of? I hear about downlevel a lot, but never “uplevel”.
    • If say I do prepare like crazy and pass the interviews, do you think I may not have any luck with the team matching Google does? Like no team may wanna hire a “junior” senior?

    Love the show! Keep it up.