Soft Skills Engineering

Jamison Dance and Dave Smith
  • 5,0 (10)
  • TECNOLOGÍA
  • QUINCENAL

It takes more than great code to be a great engineer. Soft Skills Engineering is a weekly advice podcast for software developers about the non-technical stuff that goes into being a great software developer.

  1. HACE 3 D

    Episode 499: Should I quit my solo dev job with a sports team and senile seniors

    In this episode, Dave and Jamison answer these questions: I’m a new listener to the podcast and work as the sole developer for a sports team, which is the only company I’ve worked for since graduating from university 8 years ago. I listened to episode 493 while clenching my teeth as you told a listener to absolutely not take the job with the European football club as a solo developer. Yikes! While I feel I have continued to grow my skillset in my role, I’m now feeling vulnerable about having no professional experience working alongside other developers or on large-scale applications. I feel very conflicted about leaving my current company. I have a respectable developer salary for the (non-American) low cost of living area I’m in, have a great manager, and have built up a ton of good will and trust within the organization. I get all the freedom I could ask for to make design decisions, implement devops practices, try out new technologies, and make mistakes. I also find the work interesting and there’s always something else to do! I’m a little scared of the horror stories that I hear about the real dev world and don’t want to take my current situation for granted. I would really appreciate guidance on what you think I should do. I have clear skill deficits in certain areas, but would have to give up a lot of liberties with a role change. Listener Brian asks, My job is mostly okay, but could be better because of the people in it. I joined a greenfield project a few years ago as my first software engineer role after transitioning from other data work. I grew up with the project and improved my engineering skills. A year ago we hired two new people. They had relevant experience and seemed to know what they were talking about in the interview, and had five & ten years of experience (aka, more than me). Onboarding the first few months was whatever, BUT they’ve never really improved afterwards. They turn in work that has clearly not been tested or does not meet the ticket’s requirements, barely review PRs and have never (!) left any comments/feedback, and despite their level (senior+). I don’t really trust them to work on anything more than the smallest, simplest stories. I’ve provided specific feedback in PRs and in performance reviews (sometimes very low-level and specific, and sometimes very high-level about guiding questions or principles), but nothing’s changed. I’ve felt frustrated, drained, and confused - why is it such a struggle to get someone with an entire decade of development experience to turn in a straightforward PR? One other teammate has admitted (privately) that some work was sloppily done, which is consoling but otherwise I’m not sure if it’s bothering others as much as it does me. They’re offshore so maybe it’s just a communication thing? The rest of the team has been on the project since the beginning so maybe we’re poorly set up for new devs. I have high standards for myself and others and I’ve always been the most junior developer on the team and am new to the senior role. Am I just being a perfectionistic jerk? Is that a bad match for (essentially) junior teammates? Should I just reset my expectations and accept that their level and years of experience don’t translate into high performance? Thanks for any insights.

    33 min

  2. 2 FEB

    Episode 498: Testing in big corporations and how to get my first management job

    In this episode, Dave and Jamison answer these questions: ‌ Hi Dave and Jamison, Internal dev asker from the second half of Episode 441 checking back in. Your “ask what scared the previous dev” advice in particular has paid off handsomely; I now carry around a little book of eldritch warnings and, somehow, people keep bringing me their unknowable monsters to interpret. It’s almost as though the previous dev knew these sorts of things would happen! I didn’t set out to acquire Lovecraftian knowledge, but here we are, still in one piece. Today’s puzzle: getting busy humans to test our stuff early, while feedback can still make it into production. We’re trying to build a culture where people will poke at a rough prototype now, instead of filing a Very Concerned Ticket three hours before release. How do we get people to test and provide feedback earlier? Do we stay disarmingly warm, promise tiny time boxes, and make a public show of “you said / we changed” until participation feels like the default? Or do we wave our terminal windows around threateningly on a screen share and promise doom (and minor annoyances) until they comply? Thanks for lending sanity to the abyss, —An increasingly arcane internal apps dev I have been listening to your podcast regularly and am inspired by how the podcast and the community have grown. I am a developer with over 10 years of experience and have moved to Sweden from a country outside Europe, with the ambition to build my long-term life and career here. For several years, I have tried to take that step myself, but often encounter the same obstacle: I am told I need experience as an engineering manager — but without the role, I can’t get the experience, and without the experience, I can’t get the role. I have invested a lot of time and energy in developing myself: learning about leadership, coaching, communication, and team dynamics. Despite this, I find it difficult to see a clear path forward. With everything happening in tech right now, I sometimes feel stuck and uncertain how to break this cycle. My question is: how did you take your first step? How can one realistically enter an engineering manager role when the door seems closed without prior experience? Thank you for creating such an honest and inspiring podcast. It already means a lot to me — and to many others, I am sure.

    32 min

  3. 26 ENE

    Episode 497: Patronizing perf reviews and can't get anything done as a tech lead

    In this episode, Dave and Jamison answer these questions: I’m a relatively new people manager and I really struggle when it comes time for performance reviews, or even regular praise or critical feedback in one-on-ones, because I can’t help feeling like an adult “talking down” to another adult, regardless of whether the feedback is generally positive or critical and instructive. Something about it all seems so patronizing to me. How can I approach this stuff with a different mindset? Hello D & J! Quick one from your biggest fan!! This week (Tuesday 6th Jan 2k26) I was promoted to Tech Lead of our team. In my new role, I have done no work *cries*, I’ve spent all my time assisting team members, unblocking QA, dealing with ad hoc requests from product/stakeholders…. I asked the previous tech lead is this what they did? They did! And they said spent their personal time to complete stories assigned to them. Is this really what a tech lead does?!?!! Helpppp

    28 min

  4. 19 ENE

    Episode 496: Passing non-technical interviews and my internship with only other interns

    In this episode, Dave and Jamison answer these questions: Listener Tom says, I’m a software developer with six years experience, mostly at small startups with engineering teams anywhere between 2 and 10 developers. Because these startups have been small, most of the interviews were really casual. I’d speak to either the CEO, or CTO about my past experience, and we would talk about the direction the company was heading, and whether I’d be interested in joining. They felt less like interviews, and more like free-flowing conversations. I’m now back on the market, and I’m looking at larger, more established tech companies. I can get past the tech interviews just fine, but I’m struggling with the soft-skills interviews. Compared to what I’m used to they’re a lot more structured and it feels like they’re looking for answers that fit a certain criteria and format. What advice would you give to someone used to interviewing at small startups, but now interviewing at larger companies? I took an unpaid full stack internship role at a new non-profit, and it turned out to be a team completely made of other interns. There isn’t a single experienced engineer on the team. I have gone way deeper than originally intended and am now functionally a founding engineer where the founder pretends I’m a lead engineer and calls me an intern. The founder is also hellbent on having the highest development velocity, and sometimes will contribute their own AI-generated code, often bypassing the review process especially for things I’m not comfortable signing off on like an AI-generated TOS and user agreement. I recently learned that the founder is not viewed highly in their local area after a scandal where they were accused of scamming a large sum of money, which is likely why they are doing their free community projects they started now in order to save face. This has backfired, and now people are calling their projects “AI generated schemes” despite the services being completely free. I’m not sure if I should continue contributing to these projects anymore. Since the founder rushes things to get done, walks through legal areas with their AI “lawyer,” and has a bad image, I’m worried about whether my resume will be taken seriously by potential future employers. Should I continue working for this person or is the experience not worth it?

    27 min

  5. 12 ENE

    Episode 495: What to do when my boss quits and moving to Romania?

    In this episode, Dave and Jamison answer these questions: Hello gentlemen, long-time listener here, and I’d love your take on something that’s been keeping me up at night. The high powered boss that I report to is someone I genuinely like and respect.This manager is smart, kind, honest, and overall great to work with. We have a solid relationship. I also come from big tech, so I sometimes feel I have better experience around managing projects and keeping teams organized. However she recently shared in confidence that there’s a chance of resigning in the next few months. and when I asked what keeps her up at night, the headache did not seem so big of a deal to me. But ever since hearing this news, I’ve been catastrophizing the next few months. I’m not ready to job-hunt. At the same time, if this manager does leave, it could be a really good opportunity for me to step up. So here’s what I’m struggling with: 1.How do I position myself for a potential promotion without making it seem like I’m going behind my manager’s back or trying to undermine them? 2.Should I quietly start looking for an job anyways, just in case? 3.And how do I stay sane when this might all be for nothing and the manager might actually stay? Would really appreciate your wisdom on how to navigate this without losing more sleep. Thanks for everything you do! I’ve worked as an engineering manager in a few big companies in Berlin, but after too much corporate politics bs, I flipped the fingers and quit. In the 2025 economy, that wasn’t the smartest move — finding a new job has been harder than ever. I’ve been focusing on smaller companies, ideally under 100 people. Ideally less politics, more autonomy. But now I’ve got an offer from Google in Bucharest — nearly double the compensation what I could get in Germany. The catch? I’d have to leave my strong circle of friends in Berlin and start over in a new city, new country. What would you do in my place? Brainstorm with me please 🥺

    32 min

  6. 5 ENE

    Episode 494: Am I interviewing all wrong and leaving old team chats

    In this episode, Dave and Jamison answer these questions: Dear Damison and Javison, I work at a very small startup (10 engineers) and am trying to hire 2 engineers. I’m doing the intro/screener interview for these roles & am working with a recruiting firm to source candidates. My problem is that sometimes my intuition tells me that a candidate is not going to make it through our hiring process, but I can’t articulate why. Our hiring process is neither cruel nor unusual, and on paper these candidates have the skills and experience we’re looking for. But I feel a duty to let the hiring process do its work; I want to be principled about this. For reference, I’d say I screen out 2/3 of recruiter-screened candidates, and of those remaining, 2/5 of the candidates have the je ne sais quoi for which I should be saying non, merci. One made it all the way to reference checks! Do I need to do a better job rejecting these nice, smart people instead of wasting our time? Also note that I am not a manager, and although I have a lot of experience interviewing candidates, this is the first time I’ve done the *first* interview with candidates (first-ish; the recruiting firm interviews them first). Listener Jeppe says, Hi Soft Skills nation, What’s the accepted practice with staying or leaving the private chat channels of my previous team? I work at a large company and recent switched teams internally. I helped establish the team and got along really well with them. The transfer was on good terms (they invited to their Christmas dinner after the transfer!) and my managers agreed that I could always help my old team in case something came up. I’m still in the internal chat channels for my old team. I love hearing what they’re up to and catching up. They explicitly told me not to be a stranger, so I’m not! However, I don’t think there’s much business value in being in their channels. Sometimes we have more technical chats about internal tools, and it would probably be better if I had those discussion with my new team. What should I do? Should I just stay until their manager decides to kick me out? Should I be proactive and talk with the manager about it? Should I leave a teary message about how I’m going to miss them all (even if I see them regularly at lunch and outside work sometimes)?

    26 min

  7. 29/12/2025

    Episode 493: My boss one-ups my negativity and football engineering

    In this episode, Dave and Jamison answer these questions: Hey Guys, long time listener, first time asker! At my BigCorp Co., whenever I talk to my skip level about my concerns, it seems we are playing the ‘Gloom Olympics’ every time we meet. I’ll mention I worked late, and he’ll counter with, ‘That’s nothing, I haven’t slept in three days!’ This repeated lack of empathy is demotivating and I don’t think I have had a fruitful discussion with him. How can I tackle this? How can I feel heard? I’ve decided to leave my current job as a software engineer at a large retail chain. This is my first out of university, and I’ve been here three years. I’m interviewing for two other jobs: one as an engineer at another large retail chain on a team, and another at a world renowned European football club. That job would be very different. I’d be the first internal dev hire ever, and I was told I should expect no other devs to get hired for 2+ years. I’d write my own tickets and review my own prs. The project would be to build a dashboard to manage the players - drug testing, injuries, rosters - internally. What should I do? Feedback & mentorship were central to my growth at my current job. I won’t have that at the sports club. My concern is I go to the football team, drink a lot of beer & have a great time, but after 3 years of being my own boss, I’ll think I’m the greatest dev ever but really not have kept up to date with modern trends, forgotten how to take feedback, and written a lot of 💩 code.

    21 min

  8. 22/12/2025

    Episode 492: Fresh grads and startups or the goog

    In this episode, Dave and Jamison answer these questions: Listener AWS multi-region is not real multi-region, ask me how I know asks, We’ve recently acquired some bright-eyed and bushy-tailed new grads. What have you found to be the most effective way to onboard new grads into development roles? How has it changed (if at all) since the advent of LLMs? I want to make sure my new-grad crushing machine is operating as smoothly as possible considering the recent advancements in developer tooling. Those new grads won’t crush themselves! Listener Taso asks, Early in my career I was all-in on startups. Then I spent seven years in big companies in leadership roles. I learned a lot, but the politics and the pace were so slow that at some point I’m pretty sure geological processes were moving faster than our release cycles. So I finally flipped some metaphorical fingers and quit. Since then I’ve been interviewing almost exclusively with startups… except Google, where I somehow ended up with an offer on a team I’d genuinely enjoy. You’ve both bounced between big tech and startups—if you were in my shoes, how would you think about choosing between the two?

    34 min
Ver todo (500)

Valoraciones y reseñas

5
de 5
10 valoraciones

Información

It takes more than great code to be a great engineer. Soft Skills Engineering is a weekly advice podcast for software developers about the non-technical stuff that goes into being a great software developer.

Ficha técnica

  • Creado por
    Jamison Dance and Dave Smith
  • Años en activo
    2016 - 2026
  • Episodios
    500
  • Clasificación
    Apto
  • Derechos de autor
    © 2016 Jamison Dance and Dave Smith
  • Sitio web del podcast
    Soft Skills Engineering

Quizá también te guste