Soft Skills Engineering is a weekly advice podcast for software developers. We answer questions about
all the stuff you didn't realize you needed to know about being an engineer:
pay raises
hiring
going into management
annoying co-workers
quitting your job
meetings
micromanagers
installing a ball pit in your office
and much much more...
For answers to these and other questions, our hosts Dave Smith and
Jamison Dance are here to help.
Why should you listen?
Soft Skills Engineering listeners are awesome. Here's what they are saying about the podcast.
Jack says:
Not only did Soft Skills Engineering help me land my first gig, I also used your advice to negotiate a $10,000 raise!
I love your podcast and will continue to heartily recommend you to everyone I know!
Hdennen says:
Facing a 9 hour drive, I grabbed a bunch of podcasts to listen to. I don't even know what the other ones are.
Seriously, this podcast is full of massively helpful and relevant content from two people who are experienced, funny, and insightful.
Saad says:
Listening to Soft Skills Engineering has completely shifted my thoughts on what it means to be an engineer.
It’s probably one of the more useful things I’ve gained during my time at Amazon.
It definitely helped me grow, and I’m totally indebted to you for that.
Follow the show
Follow the show on social media for the latest news:
In episode 27, Jamison and Dave answer these questions:
How do I write a great resume?
Do you really need a resume these days?
How important is formatting and good design?
What content should be on your resume?
Should I push back on non-engineering tasks like PowerPoint presentations?
From listener samspot: I am a Sr. Developer and I am often asked to spend time on PowerPoint
presentations for funding and other business stuff. I want to ask why the managers, analysts,
etc can’t handle these tasks. I find them to be a frequent distraction from my actual
responsibilities, especially because these are so frequently “emergency” requests. Should I
push back on this work, or is it better to be a team player?
In episode 23, Jamison and Dave answer these questions:
You are asked to be a CTO of a start-up. What questions would you ask in order to decide whether to join, and what things would you give most attention to, if you do join?
I REALLY want and deserve a raise so I hope you two discuss how a nerdy introvert gets the CFO of a small privately owned business to want to give her more money when she’s already happily donating an additional 10-20 hours a week.
In episode 20, Jamison and Dave share some stories from people who have been fired.
We also answer this question: How do I make code reviews more effective? It feels like reviewers fit into 2 categories: either they are too quick and superficial, or they get bogged down in nit picks.
In episode 19, Jamison and Dave answer these questions:
Would you ever fire someone over a coding mistake? For example, should you empathize with ignorance and explain how SQL injection works or is the mistake so basic as to be intolerable. Would you change your answer if the mistake was found during a code review or found as the source of a data breach?
How do you positively represent the desire to be demoted? I am called a ‘senior engineer’, but I got that way because of null instead of actual skill. I would like to be a senior engineer at some point, but I would be a better one if I travel more where I have seniors to look up to, established processes etc rather than stressing about defining everything myself; but that’s a weird thing to say to a current or potential boss and is hard to do without also volunteering for a pay cut.
In episode 18, Jamison and Dave answer these questions:
I’m a computer science major who still has a couple years of school left. I also have a part time job doing web development. I love what I’m learning and doing at work to the point that I question if it’s worth investing two more years into school. How would you counsel someone in my position?
From listener Antonio: How do I prepare for an interview?
