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.
Similar Podcasts
Thinking Elixir Podcast
The Thinking Elixir podcast is a weekly show where we talk about the Elixir programming language and the community around it. We cover news and interview guests to learn more about projects and developments in the community.
Python Bytes
Python Bytes is a weekly podcast hosted by Michael Kennedy and Brian Okken. The show is a short discussion on the headlines and noteworthy news in the Python, developer, and data science space.
Rustacean Station
Come journey with us into the weird, wonderful, and wily world of Rust.
Episode 527: I lost my job after 10 years and am I too old to switch to a security career?
In this episode, Dave and Jamison answer these questions: Hello Dave and Jamison! I’m a longtime listener going back to the early days of the podcast, and I’ve listened to every episode since. When I started listening, I was beginning my career as a software engineer. Your advice has truly helped shape how I think about work, engineering, leadership, and all the weird human stuff that comes with building software. Now I’m more than 10 years into my career, and I’ve run into a problem that I suspect many experienced engineers are dealing with right now. In episode 521, you talked about how brutal the current job market is, and the question asker from that episode had been unemployed for a year. I’m thankfully not there yet, but I recently lost my job in a large layoff, and the first couple of months of searching have been pretty discouraging. I’m applying to roughly 10–20 jobs a day. I tailor my resume to each role, ensuring it accurately reflects the skills and terminology in the job description. I usually include a cover letter too; AI gets the privilege of writing the mediocre first draft, and then I rewrite it into something I would actually say. Despite all of that, I’ve only made it past the resume screen three times so far, one of those was through a referral, and several other referral applications have gone nowhere. The strange part is that I’ve tried applying across the whole spectrum: Roles that would be a step up, where I think I could do the job but haven’t held that exact title before Roles at roughly my current level, where I can honestly check almost every box in the job description Roles that would technically be a step down, but that I’d happily take and feel extremely confident I could do well So my question is: How do you get companies to actually interview you when you’re an experienced engineer in a market overwhelmed with qualified candidates? At this point, I’m starting to wonder whether there’s such a thing as an awkward career middle age: too experienced for some jobs, not obviously senior enough for others, and competing with hundreds of people for everything in between. If you were in this situation, what would you change? More networking? Fewer but more focused applications? Different positioning? Showing up at the hiring manager’s house with a fruit basket and a printed copy of my GitHub profile? Would love to hear how you’d approach it from the other side of the hiring table. Dave and Jamison, Hit me with your dumbest, funniest, most brutally honest advice because I need it. So here’s the deal: I’m a software engineer with 30+ year in the industry, a dinosaur who’s already reinvented himself like a half-dozen times, network, dev, infra consultant, back to dev. Now I’m having a midlife-ish (okay, late-life) crisis and I’ve fallen in love with security and compliance. Like, actually excited about compliance, which I’m told is a red flag in itself. Problem is: I’m less than 10 years from retirement and my brain doesn’t bounce back from “starting over” the way it used to when I was a spry young whippersnapper. So, am I an idiot for even considering torching my comfy expertise to go be a security newbie this close to the finish line? Or is this exactly the kind of chaotic energy I need before retirement?
Episode 526: Why can't I get promoted so quickly after my last promotion and I got hired as a software engineer but ended up doing ops
In this episode, Dave and Jamison answer these questions: Hi Dave & Jamison! I’ve been listening for almost a year now and have worked through nearly your entire back catalog in reverse. The podcast has genuinely helped me become a better engineer, so thank you! I’m two years into my software engineer career at a large infrastructure company. I was promoted to SWE II last year, and this year my manager told me she felt my work was promotion-worthy, but because I’d just been promoted and she had others on the team to consider, she wants to target me for next year’s cycle instead. She gave me a spot bonus and said she’d try to make up for it in my raise. I understand and appreciate the honesty, but I’m also a little disappointed because I’ve worked hard to hit every milestone on the roadmap she gave me, and career progression does matter to me. My question is: How should I navigate the next year? What should I focus my 1:1s on? Should I push for a mid-year promotion if that’s an option, or instead focus on building an undeniable case for next year? How would you approach this if you were in my shoes? Hey Dave and Jamison, Long time listener. First time question asker :). I recently joined a major tech company. Before this, I worked at a mid-sized company with about 200 engineers. In my old role, I built customer-facing products. The work was challenging and exciting, and I genuinely enjoyed it. I ended up moving to a new city to be closer to family and started looking for a job. The job search was brutal. Honestly, by the end of it, I would have accepted just about anything. Luckily, a major tech company extended an offer. The money was great, and I thought it would be a huge plus to have a major tech name on my resume. It is a fully remote role, but they did mention that they could go hybrid in the future. I knew ahead of time that the team built internal tools instead of customer-facing products. But after joining, I realized most of what we do is closer to operations than actual software engineering. I know I should have screened the team better. I was just so relieved to get a good offer from a top company that I accepted without thinking twice. I am not enjoying the work at all. I am not planning to quit immediately. However, I want to be ready to leave in about a year or earlier if they decide to lay us all off. I want to make sure I utilize my time here as best as possible. Do you have any suggestions on how I can best position myself for an internal transfer or an eventual external move? Also, I have been in this role for close to 2 months now. I did a 1-1 with the manager in my first week, but after that, have not had any 1-1s. He has not scheduled anything. I was thinking of scheduling it myself but not sure if that can be seen as too forward. Btw this is outside US, if that matters :) Thanks again for your advice and laughs.
Episode 525: How do I save my company of 500 people and my new company is insane with AI
In this episode, Dave and Jamison answer these questions: Hey Dave and Jamison, First, I love your show and it has now been part of my Monday evening routine for many years to listen to your podcast while cooking dinner. I recently joined a mid-sized software company (500 people) as a senior data engineer. The salary is a significant bump from my previous job and I really like the team on a personal level. Three months after I joined, the company laid off half its employees and announced a strategic pivot away from their previous core business to become an “AI-first company” and develop new products in novel, more profitable sectors. The product that my team had been working on until that point was scrapped and there are no new projects coming from the business side. In subsequent communications, it was revealed why: Management has no concrete ideas for the future strategy, neither on what products to develop nor on which sectors to target. Instead, our team (among others) is now tasked with coming up with new product ideas to “save the company”. I’m a data engineer, not a business development manager, and while I have dealt with high ambiguity from the business side in previous roles, it was never this extreme. I was looking forward to working on interesting technical challenges within a great, experienced team, but now I feel like I’m expected to become an “idea guy”, a role that doesn’t really match my personality. My question is: Should I be patient and try to turn this situation into “an opportunity for growth”, or should I start applying elsewhere? I’m a bit worried that the short length of stay at this company will leave a stain on my CV. Many thanks to my favorite space lawyers, an anonymous listener. Hi! My current job is at a 10k+ large risk-adverse company that currently has nil, none, nada, nichts ai tools available for coding. I of course did the only reasonable thing. I’ve gotten a new job at a middle-sized fintech company that’s going ”AI first”. I’m really excited about finally using ai outside hobby projects. I worry however, that my future colleagues will go too quickly ahead while vibecoding, vibearchitecting, vibetesting… leaving a mountain of tech debt behind. A lazy colleague would actually be better than an intellectually lazy colleague in this scenario. (I sincerely hope that I won’t be that coworker) Are my worries overblown or sane? Any gotch’as to avoid? Maybe you can give a brief survival guide to the brave new AI world?
Episode 524: My CTO AI-codes big piles of slop and early mornings, late meetings
In this episode, Dave and Jamison answer these questions: I work for a small software company on a team of about 7 or 8 engineers. I like working here. I like the people, the autonomy, the pay, my boss, and the stack among other things. I try to remind myself of this regularly so I don’t take it for granted. I’ve been here for about 2.5 years and would love to continue working here. Our CTO, like many, has become a big AI cowboy coder. Every few months, he vibe codes a new project and then decides to interrupt the full workloads that we have a limited number of engineers to do to hand his project off to be cleaned up, worked into the product, and solve all of the problems that remain once actually put into practice. This usually ends up going to a different engineer per project, who is then tied up with the CTO’s whims and is no longer available to do the work planned by product. Our EM knows this and knows the frustration and lost velocity, but what can he do? (rhetorical, not the question) Most recently, I was tasked with implementing some reporting dashboards he did into the product, but he specifically asked me to make it in such a way that he can continue to work on and add to because he can’t be bothered to run the actual product. This is very concerning to several of us. He has no clue what he’s writing or how bad it is. We’ve talked about perhaps making him do PRs, but a) who can make him, he’s the CTO, and b) he’ll have no clue what to do with PR pushback given that he has no clue what he wrote. And again, who can make him actually fix it if he asks us to rubber stamp it? (rhetorical, not the question) I’ve been listening to the show for years and I’ve talked to friends at other companies, so I know this is everywhere. Is it as everywhere as it seems? Is it worth finding a new place to work where the CTO isn’t running so rampant? As I stated before, I’d rather not leave, but if I talked about that as a concern, I don’t want it to sound like an ultimatum, even if maybe it is at some level. Is this just the new reality for us, or is there something that can be done? I am a senior software engineer at a big tech company. I live in central Europe but my team is in the US and I’m 9 hours ahead. I have 7:30 pm meetings and sometimes take an hour before and/or after this meeting to prep or follow up. Previously I slept in later and started later to deal with these meetings. However, now my daughter is starting kindergarten and I wake up early (5-6AM) to be with her, drop her off, etc. Now in the evening meetings my brain is fried and I can’t even articulate myself well. The next day I think about so many things I wish I had said in those meetings. I can’t quit as I make 160K right now and I would only be making 60-80K tops in my country and have some financial commitments. Relocation to the US is also not an option because I have kids and don’t want them to move. So far I have been skipping meetings and my manager has not expressed concern but I feel so detached from my team. I don’t even know what most of my peers are working on. It feels like I am out of ideas to make this better. Please share your space wisdom with me :)
Episode 523: (Rerun of 331) Prickly ticket and title downgrade
This is a rerun of episode 331. In this episode, Dave and Jamison answer these questions: Listener ninjamonkey says, I am a new grad who is half a year into the role now at a very large company. Recently, a senior engineer on my team asked me to create a ticket for an infra team for a problem with a service. I provided logs and steps to reproduce the issue and did a health check before submitting. Right after, the manager of the team put me into a group chat with their team, asked why I created the ticket and told me to start doing my job and they can’t debug for me. From these interactions and comments on the ticket, it feels the infra team will likely not work on the tickets I report or de-prioritize them. This has left me discouraged and hesitant. I will have to do lots of this kind of infrastructure work in the future. Additionally, one of the goals my manager set for me is to work with more external teams for the upcoming year. What do I do here? Do I tell my manager about these interactions? Do I tell my team lead, staff/seniors to swap out for different kind of story? I work for a small startup. I was the first employee other than the 2 founders. Being the first developer hired, naturally means I have the most knowledge about our application. I also have good organisational skills, which has led to me becoming and being referred to as the “Lead Developer”. I have recruited 2 of the 3 new developers, and have trained both of them and got them up to speed. At first I was pleased with the progression and was keen to grow into the position, and told the founders so. Since then, I have changed my mind, I don’t want to be the lead - due to the following: The communication is absolutely pitiful. Any questions we ask of the founders we get about a 30% reply rate no matter the form of communication. We get poorly defined tasks and requirements The CTO will just blast through some of our features over the weekend and say here I fixed it for you I don’t want to quit my job (just yet… its a comin though). I have actually discussed the above points with them, but I know these 2 founders will never change their ways. How do I tell them I just want to go back to being an Individual Contributor like my Employment contract states?
Episode 522: I stayed too long at my first job and should I get a masters degree
In this episode, Dave and Jamison answer these questions: I stayed too long at my first company and now my career is ruined? Hi both, long time listener. (Since I graduated university 4 years ago actually and felt I could never find a job but listening to you guys made me feel not like such an outcast in our field.) I graduated in 2022. Didn’t really apply around much and almost immediately accepted the full time offer from the company I did my internship with during my degree. And fast forward to middle of 2026… I am still here. I’ve long stopped growing as an engineer and have actually been stuck on a simple CLI tool for almost 4 years now with little to no cloud/backend/etcetera experience to show in my 5 year career. I don’t feel I am desirable in the job market at all due to this and waited way too long to look for a job because I was comfortable and happy. I feel paralyzed (no need to put on your space therapist hats BUT some career advice would be wonderful!) (Also did I mention I am in Canada and want to move to Europe and live the rest of my life there but visa sponsorship with my level of experience is impossible? Maybe that’ll be for my next question…) Thanks for all you do, cheers! I have a non-CS engineering degree, and am looking to transition into Software Engineering. I have the option of pursuing a degree with Tuition Reimbursement from my job, but am in a bit of a strange situation deciding which degree. Basically, I’ve figured that with my current Engineering background I could pursue either a second Bachelor’s degree through Universities offering a “Post-Baccalaureate” program in Computer Science, or a Master’s degree, with maybe only a slightly longer program to get the Master’s as opposed to the Bachelor’s. Otherwise the total length/cost of the programs would be roughly the same. I have heard though that it might not be a great idea to go into a Master’s program unless you know what specifically you want to study. I am curious what you think would be more “hire-able” between the two options for someone pursuing the career change into Software Engineering?
Episode 521: negotiating . . . now? and doing good work is not enough for promotion?
In this episode, Dave and Jamison answer these questions: Dwill Ainghell asks, During the golden era of software development, it was commonly stated that you should always negotiate job offers. The argument was that the company has invested significant time and resources into you as a candidate and there is always some wiggle room for negotiations. A popular article / podcast by Patrick McKenzie likened it to doing something slightly uncomfortable like “reciting poetry while simultaneously standing on one foot” with almost no downside. (https://www.complexsystemspodcast.com/episodes/how-to-negotiate-your-salary-package/) Does this still hold true in today’s environment? I’m a SWE with 10 years of experience and I’ve been unemployed for close to a year. I’m expecting an offer from a large company and I fear that I will look like a fool trying to negotiate in my current position and the current job market dynamics. Even worse, I fear that they might retract the offer and give it to someone else. That being said, I don’t want to leave money on the table. What’s the correct course of action in today’s environment? Listener Stu says, In episode 500, you said something to the effect of “working hard and doing a great job with the work you’ve been assigned is not the promotion track”. I’d love to hear you discuss what it does take to get promoted and how to do that. In my job, we have a jira queue and engineers are tasked with taking from the top of the queue and executing work. There’s also an expectation to lead pre-defined projects (define the scope, write the tickets, and shepherd it along). All of these projects have deadlines, so how do you recommend people get the defined work done, lead projects, and still find time to do whatever it is to get promoted? Why is doing an excellent job not enough?
Episode 520: I came back to my former team and was shocked by AI and my team does not care at ALL about the code
In this episode, Dave and Jamison answer these questions: Hey Dave & Jamison, Long time listener. Love the podcast. I recently rejoined a remote team that I worked with in the past. I was super stoked to rejoin this team because they were collectively one of the most competent and technically excellent teams I’ve ever worked with. And they’re all genuinely nice people as well. I left the team before AI coding had really caught on, but coming back to the team has been a huge shock to me. Almost everyone now exclusively writes code with AI. PR descriptions are all AI generated, and code review has become copy-pasting AI-generated comments into GitHub. Being a remote team it was already hard to connect, but now it feels like almost all interactions are their AI assistant talking to my AI assistant. I’m not anti-AI, and I get that writing code with AI can be much quicker. But I’m struggling with the loss of what made the team feel good to work on, specifically the craftsmanship, level of engagement, and the learning from eachother. The product itself is still high quality (even if the codebase is less-so), but the process itself is a lot less enjoyable now. I don’t want to be the person who shows up after being away and immediately makes it everyone else’s problem that I miss the old way of doing things. But I’m having doubts if I want to be a part of this team. Is this just what software engineering looks like in remote organisations now? And should I expect most teams are now operating like this? Hi Jamison and Dave, Love your podcast. I was recently hired as a mid-level full-stack developer with the promise of leading a new squad. On day one, I discovered management scrapped the squad idea and promoted an existing developer to sole lead instead. The team consists of this new lead, two 20-year VB6 veterans, and me. The codebase is lawless: direct DB access, fat controllers, 1-2K+ LOC classes everywhere (copy/pasted boilerplate) and severe Broken Access Control (OWASP #1) where authenticated users can extract anyone’s PII (full name, home address, phone number) via a simple email query string. My coworkers rely heavily on generative AI but do not review the output. They constantly commit “AI slop” that barely functions and introduces endless bugs. I used to clean it up, but I recently realized they care so little about the codebase that no one even notices if I stop. Add in a “Senior Product Manager” whose entire UX background is a three-month internship, who invents customer requirements to defend her inconsistent designs. I am already applying elsewhere. My questions: How do you handle a bait-and-switch of this magnitude? When the team cares so little that no one notices if you stop cleaning up their AI-generated bugs, how do you stay sane and professionally sharp while riding out the clock? Show Notes https://tombedor.dev/human-attention-and-human-effort/
Episode 519: Why does my team not have a tech lead and rumors!
In this episode, Dave and Jamison answer these questions: Hi D&J! Question from Sweden! I’m a senior dev that have seen a lot of orgs without tech lead and/or staff engineer roles. I know some companies have them, but mostly newer more techy companies. Bigger older less techy companies usually have non-coding “architects”. Though that’s one title I have no good experience of, just neutral ones or worse :) In particular I’ve been in many teams without a tech lead (all developers are equal, no tiebreaker vote). It’s often successful due to a leader and/or consensus emerging organically and peacefully. I loathe the failure modes however: consensus abuse through veto (we can’t move discussion forward because someone explicitly actively disagrees, a “keeping the meeting hostage” situation), disagreement on technical priorities and choices (lowest common denominator it is…) or that the team is bickering and bikeshedding during technical discussions. Is this just a regional/cultural thing, or is it more about the type of org? Also would you say it’s to the detriment of these orgs to not have these “technical leadership hierarchies”? Thanks! Hey Dave and Jameson, love the show. I’m a Software Engineer at a major tech company. The org is non technical. I consider myself pretty well rounded. I consistently hit my sprint goals, crush my story points, and even put in weekend commits when needed as well as talk but I dont look for conversations into work im too far away involved in. My direct manager thinks my output is good. He told me to work on communication, but the work and my drive is good. I have a relaxed demeanor in a high stress environment. Recently, I learned there are concerns that my “vibe” seems lazy and unengaged, and those concerns may have been shared with my skip-level manager. When my friend literally pulled up my raw metrics and story points to defend me, the friend had no answer, but just reiterated that it’s a “vibe thing.” It feels like a political target has been placed on my back by business people who don’t understand my work but hold corporate influence. I told my manager and he says im doing fine, and people will say what they say. Everyone talks, etc, and just to focus on his feedback. My question is: How do I fight a “vibe” complaint when the data says I’m crushing it? Should I cave and alter my lifestyle to play the corporate theater game, or do I double down on my metrics, lean on my manager, or dare them to try and figure out how valuable I am? Thanks, An Engineer Who Refuses to Look Bored
Episode 518: stuck at startup and is my employer mistreating me because I'm on a visa?
In this episode, Dave and Jamison answer these questions: I have been at a small startup company for 5 years now. It’s a very small technical team, 4 devs and a tech lead that contributes code & architecture. I am getting a small raise this week for my 5 years but it’s a smaller raise than I was expecting. We’re an all remote team across the globe but I had a dev co worker in the same city as me just leave the company. This has put more pressure on me as I’m the only dev in the primary time zone we operate in, everyone else is east coast or opposite side of the world. With the added pressure and some forward comments from me in one on ones with my tech lead I expected much more that I’m being offered. I think I’m supposed to quit my job but I’m terrified of that idea. This is my first job in the field and I love the work. The full stack startup experience is fun and I’ve learned so much, and I like my team a lot. I’ve never even applied to another position in tech yet, I got this one with the first application I sent out. That’s not even considering the current state of the field rapidly changing with AI and the general lack of jobs I am constantly hearing about in tech. Is there a world where I should tell my boss I’m thinking about leaving? I’ve become an integral part of the team I think that would result in movement upwards, but that sounds so risky if I haven’t even put in an application anywhere else. Should I take the old quit your job advice even when the field is so shaky? Thanks guys! And you reading the patreon names is the best part of my week too. Hi there, I’m about 4 years into my career. I’m at my second job after leaving university. The first was at a firm under 50 employees and the current is at a firm with a global footprint and several thousand employees. Both are in Europe. I moved to Europe on a work visa as a pathway to citizenship. I’ve never felt like either my past or current employer has taken advantage of my situation, but it’s important that I keep my job. At both employers, I generally work one weekend day a week to meet expectations and keep on the promotion train. I’m not the only one; several of my colleagues do the same. For now I have the time to work late, as my significant other is back home. Soon they’ll be moving over, however, and they have made clear they will not be okay with me going into work every Saturday. Maybe I’m paranoid. Maybe the expectations at work aren’t clear. Maybe this is part of software. But basically, how do I get to a point where I can checkout on weekends and not feel guilty or like I’m falling behind? Do I need to work longer weekdays? Do I need to sacrifice promotions? Do I need to get better at saying no?
Episode 517: Is it good for my career to work at a SaaS company and why am I being asked to manage two teams?
In this episode, Dave and Jamison answer these questions: Hey guys. This question comes all the way from New Zealand. Recently discovered your podcast about a month ago, and have been catching up with older episodes on morning walks ever since - you guys are awesome. Anyway - the question: Is it more beneficial to work for a company where the software itself is the product (SaaS etc) or does it no longer matter given the rise of the robots anyway? For context - I’ve been working for a telco/internet company for just over five year. Initially when I joined there was a huge roadmap of software to develop internally - things like customer facing portals, diagnostic tools, and of course internal tooling. However over the past couple of years, it has just been cost cutting and downsizing. Given that the company is not in the business of selling software, our department has been stripped to skeletal level just to ‘keep the lights on’. So, I’ve started applying for jobs at SaaS companies on the basis that even with AI, there will at least be a continuous roadmap to work on. Or, is this a case of ‘snakes in the greener grass’… or whatever the idiom is. Keen to hear your thoughts! I’m an EM about 7 months into a role at a larger private software company. When I joined, the explicit expectation was 1 team (~8 direct reports). I’m happy to say my team has crushed it: award-winning product launch, clear monetization path, company IPO positioning. I made some bold headcount decisions, reduced spend, built the team’s trust back up, and things are now actually quite great. I’m generally a cynical person and so I don’t say that lightly :) Last week my boss told me I’m taking on a second team, bringing me to 16 direct reports. When I asked if this was a promotion track, he said no. Apparently the expectation is now ALL EMs manage 2+ teams. Problem: the internal HR leveling rubric still says 2+ teams is a Sr. EM expectation, which I didn’t apply for… precisely because I didn’t want it. When I pointed this out, he said “that’s out of date, and you’re behind your peers because you only have been running one team”. I did the job I was hired to do, did it well, and the goalposts moved without anyone telling me. The kicker: the team I’m absorbing used to be run by a Sr. EM, who now has just one team!! So a Sr. EM is shrinking scope while I’m handed their struggling team and told I’m behind. It wasn’t framed as a vote of confidence. It felt like a quiet reassignment. Three questions: Am I being oversensitive to just poor communication (it’s possible the senior EM is being managed out and I shouldn’t use that as a benchmark)? Should I push for a comp increase since I’m now doing 2x the scope I was hired for? And how hard do I push back? One constraint: I’m a couple months from planned medical leave and can’t afford to leave before then, so I have limited leverage.
Episode 516: Not a baby and my product manager doesn't know the product
In this episode, Dave and Jamison answer these questions: My company follows scrum, with daily standups. We got a new scrum master. He is very formal and procedural and I struggle with our daily meetings. He goes through a long list of assigned tickets, asking each ticket owner about status and info on progress. We are all engineers with many years of experience but it feels like we are in the kindergarten. We don’t have deep expertise about each others work. It is important to know what each of us is doing more or less, but going deep in these issues makes me disconnect, and I think these meetings are above all very good to signal blocking points and ask for help. A recitation of tickets and work being done is not their purpose. On top of that, most days it takes 25-30 mins to go through all the issues. Am I being difficult complaining about this? I tried to be polite when I raised the issue but I was told more or less that this way is better for the company. Is it common in the industry to go through dailys like this? Thanks a lot, guys, you do great work and I look forward to the SW/industry podcast that makes me laugh the most! Hi! Long-time listener here, I remember Jamison mentioning this podcast on JS Jabber and I’ve been listening ever since. Best part of my week! In my current organisation I have a tech lead role on a small, internal platform team. Our “customers” are mainly other engineers. Due to several re-orgs, I have over the years worked with a number of Product Managers and Engineering Managers who have all had one thing in common: they don’t understand the technical domain we work in very well. You could say we have “Product Managers” who do not understand the “Product”. At the same time, these people are expected to interact with stakeholders, set the platform vision, manage the roadmap and backlog, prioritise risks, write documentation, do demos, etc. In the end, a lot of this work falls through to me. I do the work, but have also received negative feedback from my skip level that I need to do a better job keeping the product manager and engineering manager in the loop. I just got a new EM and am heading into our first expectations setting meeting. How can best express that my expectation is that the roadmap for a technical platform team should be managed by someone technical? Do you think product managers have a role on internal platform teams?
Episode 515: My junior team member won't listen to me and will I be the dumbest employee at a quantum computer company?
In this episode, Dave and Jamison answer these questions: Hi from a long-time listener and first-time caller. I need some advice on a toxic workplace situation. I’m currently unhappy with my job due to a difficult dynamic with a colleague. My manager put us on the same team, meaning we share responsibility for our output. Although this colleague is technically a level below me, they act as though they have seniority. This creates significant friction: they’re resistant to advice, insist they’re always right, and refuse to accept reality even when they can’t deliver what’s required. They’re incredibly stubborn, and arguing with them about what’s feasible takes an excessive amount of effort. The situation is particularly frustrating because I’m held accountable for the shared results. If I weren’t responsible for the final outcome, I could probably just ignore their behaviour. Instead, they frequently talk a big game while contributing very little actual work. People unfamiliar with our domain are easily misled by their confidence, even though they are incompetent. Consequently, I’m forced to clean up their mess; otherwise, I’d be the one bearing the blame for the failure. I tried discussing this with my manager, but unfortunately, it made me look bad rather than resolving the issue. If I were the manager, I’d fire this person immediately, but my manager is clearly one of those people who get fooled by their smooth talk. I’m very close to handing in my notice, and let the manager know how incompetent this person is. But I’m furious that I feel I have to give up a role I enjoy just because of someone who makes my life miserable. My question is: Should I stick it out and try to navigate this politics-heavy environment, or is walking away the only option left? How do I leave without burning bridges or letting them win? Hello gentlemen, long time listener of the show and finally getting around to asking my first question (how exciting!) I’m going to be joining a new company in a few months and am wondering how to best handle the transition in order to make an excellent first impression and maybe set myself up for career growth… while not biting off more than I can chew. For context: I’m joining a company that builds QUANTUM COMPUTERS 🤯 after a background in working in completely different, non-scientific fields. To be fair I’m just joining as a Senior Software Engineer on the Cloud team, I won’t be building the actual computers. I have some experience in leadership, but not nearly as much as I wish I had, this is something I’d love to try and get into a little bit more (and couldn’t at my last company which was too small). I’m also a little intimidated at the idea of stepping into the “big leagues”, but want to use this opportunity to show that, I too, can ball. However, I am worried that everyone is going to be waaay smarter than me and that I’ve actually been playing in the ball pit for years. I’m a little scared of attempting to ball too hard and fumbling, causing dissapointment on their end, and impostor syndrome on mine. How would you go about joining a new company with the excitement of a new start and the drive to be the best I can be, while also remaining humble and grounded in reality? Should I “fake it t’ill I make it” and be super confident? Or take a more reserved approach? In France we call this a “rich person problem”, everything is great because I have a cool new job, but I don’t want to mess it up! HELP!
Episode 514: Trust issues and underperformers and my coworker resents me for being faster
In this episode, Dave and Jamison answer these questions: My parent organization has trust issues: we registered on a recent survey as one of the lowest across the bigger software org (thousands of employees). There are two groups: functional, trustworthy people who get stuff done, and people who are behind, stuck, or just not working. Those struggling say they need better emotional support, but there is consistent, documented evidence that they cannot keep up. I’m perpetually frustrated that there are only two or three people in an org of 30 who can effectively complete tasks and manage the insane workload. I am biased: those in whom I have no trust have repeatedly demonstrated that they cannot be trusted. I believe that the organization would be able to go faster without them. Whats the right answer here? Should I start my own company to abandon this mess? Do we cut scope super aggressively to allow underperformers to be reasonable contributors? One example: one of these contributors was walked through the process, given written documentation of the process, verbally confirmed an understanding of the process, and committed to starting that day. And then two days later identified they hadn’t started for those two days because they were blocked by something that was explicitly captured in the document and discussed in the recorded meeting. They do not raise this until they were asked for their progress multiple days beyond the critical start date. Hi Dave and Jamison, First, thank you for the podcast. As someone on the spectrum, it really helps me analyze social situations I struggle with. My question: I work at a software company where management is pushing the use of LLMs for coding, and my team recently started using Spec-Driven Development. SDD often requires strong upfront planning, which has quietly split my small team between developers who plan well and those who get lost in “vibe-coding” loops. One of those people is a close coworker I consider a friend (we hang out after work and have honest chats about everything). He’s not strong at planning, so I end up explaining each ticket to him in detail. But he’s really great in other ways: communicative, asks a lot of questions in refinement sessions that set a good example for others, does thorough handoffs with the QA team, always responsive in chat, always trying to help. He’s also one of the rare people who actually pay attention to alerts. Since we started using SDD, the gap in our speed and output quality has become very visible. One of our tech directors noticed and asked me to teach him planning. We spent several days drawing schemas and working through small features together, and it was clearly painful for him. The TD also had his own sessions with him, but eventually gave up because my friend seemed so discouraged, and the TD decided to “stop the torture” and leave him alone. The hard part is that after all these teaching sessions, he actually seems even slower than before and also more discouraged and down. Since then, our friendship has changed. He stopped talking to me outside work, and I think he now feels jealous or bothered by the difference in our performance. I’m okay with continuing to explain tickets and outlining detailed execution plans for him, but I worry that I’m keeping him in his comfort zone and not really helping his career. And I also miss how things used to be between us 💔 What should I do? P.S. I’m not an LLM fan or enthusiast, I take a practical approach to using them. But I hate how they’re taking jobs away from devs who really love coding but are weak at planning or not interested in it. It doesn’t feel fair.
Episode 513: Forgotten employee and what skills actually matter in the AI world
In this episode, Dave and Jamison answer these questions: How long until I am ethically obligated to let my company know I’m doing no work? There was a big re-org at the company I recently joined. It’s a huge financial company, so there’s a lot of bureaucracy. Somehow in this mess I was kicked off the first team I joined so that I was pending re-assignment. It’s been a month and I haven’t been re-assigned. Instead of being in between jobs not working, I am currently in between teams, but still getting paid! This feels unintentional on the part of the company as no one has followed up with me. I’ve been happily using the time to catch up on hobbies, but I’m starting to get concerned about what will happen when the other shoe drops. At what point do I start to venture into irreversible reputational harm? For some added context, teams at this company are about 6 people and the manager handles several teams, so I’ve never talked to my manager since I joined. I got the message about the re-org from a screenshot of an email that my scrum master shared in my last stand-up. AI changes how software is build. Actual coding is mostly done by LLMs now (I hate it, but it is what it is). What do you think should I focus on learning now to not become obsolete in 1-2 years? I am a senior dev with 13yoe, and loved coding, but now I find it hard what my role will be in the next years (still have 30+ before retirement). I do not want to go to the EM track, at least not in the near future. So is it more architecture knowledge, security, AI internals, …? What do you think?