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 420: New grad getting boring work and busy manager

Download

In this episode, Dave and Jamison answer these questions:

  1. Little Z says,

    Hello! I am a relatively new graduate (‘23 bachelor’s in information systems) who is currently working at a large tech company in a technical role adjacent to SWE.

    This is a great opportunity, but as time has progressed, I’ve felt growing dissatisfaction with the role. I don’t enjoy many of the projects I am put on. I feel that I am not fully making use of my technical skills/potential and that the work I do often doesn’t align my career aspirations (transitioning/diving into software engineering). This de-motivates and frustrates me, and I often feel I’m wasting my time.

    However, upon reflection, I feel that my sentiments are rooted in youthful ignorance and I am too impatient and idealistic in my expectations. What realistic expectations should I set for myself for my day-to-day work and long-term career trajectory? Should I expect to “bite the bullet” and work on things that don’t directly interest/benefit me, especially as I am still young and relatively unproven in my career? How, if at all, do economic market forces come into the picture here?

  2. Greetings!

    Long time fan, first time caller.

    This isn’t a question per se, but rather an observation that I’d love to hear your take on.

    Throughout my career, I’ve never had a boss that had less than 30 direct report. Yes, thirty. Three. Oh.

    I think this is primarly a cultural thing (I live in northern Europe), but also the fact that I’ve mostly worked in large organisations where tech was a means to an end.

    With that in mind, I find it your podcast fascinating because a lot of your answers and suggestions would be met either horror, disbelief or amusement - often a mix, I suspect.

    Weekly one-on-ones? A carreer plan? Going to skip-level managers? When your only interaction with you boss is a yearly apraisal that usually starts with the phrase “So, uuuuuh, who are you and what have you done the last year?”, your nuggets of wisdom feel less like nuggets and more like peals, as in “pearls before swine”!

    Any suggestions on how to thrive in an evironment such as this?

A smiling speech bubble

Episode 419: Yoda or Han Solo and I swear I'm senior

Download

In this episode, Dave and Jamison answer these questions:

  1. Listener Anakin asks,

    I have two former co-workers that work at great companies where I would love to work. I reached out to one looking for advice and while talking to him, he said I should join him and he offered to give me a referral. At the same time, unprompted, another old coworker reached out to me asking if I am interested in joining them. It’s like being asked to choose between training with Yoda or flying with Han Solo on the Millennium Falcon (Sorry, James)!

    But I have a big worry: what if by some miracle I get offers from both places? I don’t feel I can turn down an offer after my old coworkers vouched for me. I don’t want my friends to feel like I led them on. At the same time, I don’t think I’m close enough to either to say I want to interview, but I’m also applying somewhere else.

    So I’m thinking of applying to one, and if that doesn’t go well, applying to the other. Is there a better way to go about this? How would you approach this dilemma?

  2. Listener D says,

    I asked a question in an episode around number 110. I asked if I should switch my job, as I had just moved to another country and, after half a year, the new CTO wanted to change the tech stack. You suggested staying for a while to see what happens, so I did. It worked out well.

    On to the question! How can I be treated as a senior software engineer in my next job? When I moved the first time, I was downgraded to a mid-level developer, even though I had about seven years of experience. I did my job well, exceeded expectations, and got a promotion after four years. After working there for 4.5 years (half a year as a senior), I moved again to another EU country and was hired as a mid-level developer again! Now, after one year, I got promoted to Senior Dev, but I am afraid that the next employer could treat me as a mid-level dev. I understand that grades are different in different companies, but mid-level developers have lower salaries. How can I assure my next employer that I am a senior or even higher-level developer?

A smiling speech bubble

Episode 418: Should I "rest and vest" and how do I avoid 3-hour agile meetings?

Download

In this episode, Dave and Jamison answer these questions:

  1. I work as a Senior Software Engineer for a subsidiary owned by a mega corp. I am approaching 6 years at the company. In the last few years the company has had significant layoffs and I have been moved to a team by force with a new leadership chain and engineers I haven’t really worked with.

    Even though I was disgruntled when this happened, I gave this new team a chance. I have been successful in driving change within my engineering boundaries but I just don’t agree with many decisions made my leadership. I have concluded this team and company are no longer for me and I want to move on.

    Repeated layoffs, high bar for promotions, high stress( due to less people), no raises/bonuses have lead to fairly low morale across the org. Unfortunately, or fortunately the public stock price has gone up and many people are just resting and vesting. Even though I really want to leave it would be financially irresponsible. Are situations like this common in a software engineers careers? I am having trouble “resting”. Any advice on how to deal with the urge to perform yet you know it’s a bad decision?

  2. My lunch break is sacred, how can I set boundaries as a new lead engineer joining a new company? I’ve discovered the agile process they use is far too exhaustive when compared with the size of the company. They have 3 hour meetings covering the whole lunch window (11:30-14:30) for backlog and sprint review on two consecutive days?! To me this is totally mad, however people seem to have just accepted it. How do I tell them I am not accepting this without rejecting their culture?