In this episode, Dave and Jamison answer these questions:

1. Thank you hosting this show. This show has given me a lot of insight on nuisances of engineering that isn’t mentioned anywhere. Having some experience in industry for a while, I always find in this position where I want some autonomy but I am bounded by the deadline. What do you think should be the way to start a career that gives autonomy while having that sweet benefits from the industry?

2. I used to be a senior manager of an operations team for a fire fighting service in Australia. I managed all of our physical operational assets - for example radio towers, mobile communications e.g. 5g, 4g technologies, mobile data terminals e.g. laptops in fire fighting appliances “fire trucks ;) “, data centers, networking so on…

   A restructuring means my team has grown to include in-house software development. While i am excited for this opportunity and on board with the changes, it is a very big shift from the physical and electrical engineering side to software development.

   The C level staff thinks the team lacks focus and there are “problems” to address.

   I have been meeting the new team and working through the changes. They are very nervous and are skeptical about how I’ll understand their world, which is fair.

   How can I best support this team? What are cultural things I should be aware of? What are key metrics I can measure that will fairly represent their hard work to the executive team? Any thoughts on what things a manager or managers can do to be supportive as the new drop in from across the room from a entirely different engineering discipline? Coding in my world is scripting and hacking about to make things work (telecommunication engineer)

In this episode, Dave and Jamison answer these questions:

1. A listener named Maria says,

   Hey guys! I am a software engineer working in web development at a small/mid-sized SaaS company. I come from a non-traditional background (self-taught, no CS degree) and I currently have 6 years of experience under my belt, the last 2 years of which I have been tech lead of a small team.

   I want to move into big(ger) tech, but I’ve not worked on any large scale systems so far. The biggest thing I’ve worked far had a user base of ~100k users and traffic would typically max out at ~2k concurrent users at peak times. Due to the nature of the work I’ve been doing at smaller companies (and also thanks to this podcast!) my soft skills are strong - I am good at working with lots of different people, I can deliver broad/vague projects, and I’m comfortable tackling ambiguous problems. I think my technical skills are probably decent, I’ve spent time learning system design and best practices, and I’ve put in the work to study CS fundamentals. Thing is, I would have absolutely no clue how to maintain an API that needs to handle 100k requests per second. My hands-on experience of concurrency and threading is basically just simple ol’ async/await.

   Grinding Leetcode aside, what can I do to make myself a stronger candidate for breaking into big tech? How can I be competitive against folks who already have big tech experience? Are there any projects I could do that would sway you as a hiring manager? I know it’s terrible market timing, I am just planning ahead.

   Love the show, thank you for making me a better engineer! :)

2. Hi! I have been working at my fully remote company with around 100 people in the engineering department for over a year now. While I see a lot of really smart people here, the code quality is lacking. We’re moving from a monolith powered using an opinionated framework to small services powered by a lightweight library, so there are fewer guardrails.

   I have many ideas on how to structure the code, add layering, etc., so the code is easier to understand and maintain. However, the company is very hierarchical, and despite being at a senior level, I don’t talk much to anyone higher than my lead. There are no staff or principal roles. There are also hardly any meetings, and the only ones I attend are within my small team of five people. Most of slack channels for teams are private, and I don’t ever see company-wide ideas like that thrown in the “general” channel.

   I initially wanted to present this to my team first, but I am afraid that if they don’t like it for some reason, it will be awkward to take it to higher management afterward. How can I share my ideas with a wider audience and ideally get this approved as part of my work so I don’t have to work on it in my free time?

In this episode, Dave and Jamison answer these questions:

1. This is my first time conducting technical interviews (most of which have been virtual), and I had one interview where I had a strong feeling that the candidate was cheating. They breezed through the short problems I gave them, and they were able to explain their reasoning. But during the live coding problem, they sat in silence for five minutes, and when I asked them what they were thinking, they didn’t respond. Then they started cranking out perfect code without explaining anything.

   How do you address cheating in interviews? What if it turns out to be just nerves? I don’t want to assume anything, but I also wouldn’t feel comfortable confronting them about it either.

2. I work as a team lead for a small group of 4 other devs. Our Product Owner is currently handling the requirements for new features to onboard a new large client. This involves them attending client meetings and generally isolating the development team from client shenanigans which is normally great, but it’s becoming INCREASINGLY obvious that someone on the client team has his number and he’s getting HORRIBLY out-negotiated. This has resulted in a bunch of missing requirements, changing requirements, last minute feature adds, and general confusion. I’m trying to push back, but the leadership team is coming back with “Well we promised…” and my entire team is stressing out. Note that this is AFTER we were already pressured to overcommit on capacity to get these “absolutely necessary” features developed for the client to go live.

   I like my PO, he’s a good guy and normally does good work, what can I do to help him stop from getting his butt kicked in these meetings?

   (Note: the POs are neither above nor below us in the org tree, our closest shared higher-up is the VP and I obviously don’t want to escalate it that far)

In this episode, Dave and Jamison answer these questions:

1. I’m planning to leave my job purely because of low compensation. I like my growth in my current company - but low compensation than what market is offering is quite a mental hiccup in my regular work (yep! I’m slowly becoming one of the quiet quitters). I’m thinking of going to my manager with my new offer and ask him to match it. Do retention offers actually work? As mangers yourselves, how would you want me to approach a retention discussion? I don’t want my manager to make my life hell under the pretense of “Oh he’ll leave in a year” if I do decide to stay after taking the matching offer. Love the show - pretty much my single source of wisdom for all my behavioural interviews xD

2. I was recently let go from a company. They said they would send me a shipping label so that I could return the hardware. I didn’t hear back from them for a week. A few days later a label came in for the laptop, but not for the dock or the two monitors they also sent.

   I did not enjoy my experience there and I’m feeling resentful at having to pester them so that I can get what I need to send them back their hardware.

   What is my due diligence on the score? I don’t even like the monitors.

In this episode, Dave and Jamison answer these questions:

1. Listener Olexander asks,

   I was a tech lead on some relatively known project since the beginning for more than a year. I made several trade-offs with technologies and wrong decisions. I participate in some generic Slack organisations and met several users of my product. I haven’t told them that I was connected to implementing the project but sometimes shared some insights on how the product is tested and asked opinions about some of features of the product in comparison to the competitors. Now there is a person who continuously critiques the product. Sometimes the criticism is valid but sometimes is’s just a rant. How can I influence that person without blowing my cover?

2. Listener Kieran asks,

   Hi guys! Loving the podcast from down under. I’m working part time as a dev while I complete my software engineering degree. It’s been fun, but there are almost no processes in place for development and not many other devs seem to care about improvement.

   Although I am the most inexperienced here I feel some of the devs do not care about the quality of the work as I often have to refactor some of their code due to it being buggy, slow and undocumented (still using var in javascript).

   I’ve talked to management about improving our standards. However, they brushed me off saying yeah some of the developers are stubborn. They are not brushing me off because I lack technicality as Ive been given an end user app as a solo project. How should I go about encouraging the team to improve our processes?

In this episode, Dave and Jamison answer these questions:

1. How do you politely tell a reviewer politely, “Your suggestion is stupid. I will not do it” when you get stupid review comments. If you don’t do it then the pull request can’t move forward because of unresolved issues. If you do it, then you’re compromising your design you’ve worked weeks on for some fly-by random comment.

2. A few months back, I volunteered as co-facilitator for my department’s NodeJS Guild meeting. At first, it was a struggle to get people to present. But I tried to lower the bar more and more until it was easy. I asked for 10-15m presentations, and eventually I realized people are happier “Kicking off a discussion” than they are “giving a presentation”. All the listeners are more engaged too, at least after the first 2 meetings doing this.

   Now I want people to share half-baked code, or problems they are struggling with, as part of our discussions. I want people to be able to be vulnerable. If we don’t collaborate on common problems until we feel they’re polished and won’t reflect badly on us, then we will all waste time solving the same problems.

   I also want this to scale across 15-25 small scrum teams. I think success could be my demise–if we have good discussions, then more people will come, but people won’t want to be as vulnerable with a larger group.

   In general, I think my own scrum team is very open and vulnerable to each other, but the remote work in the deparment has created distance. I want to help create more collaboration on similar problems and solutions.

   What would you do to keep this going, and improve it?

In this episode, Dave and Jamison answer these questions:

1. I seem to be very hot and cold about how I feel about my job. Some days I hate it and think about quitting, but other days, I feel it’s not that bad and can stick around a little longer. The reason for it seems to change depending on the day, but a lot of it seems to center around the people around me (i.e. developers who need me to Google for them, business people who don’t understand how to provide requirements), but sometimes I can’t tell whether it’s an attitude problem that will follow me anywhere or if it’s just time to leave. It’s a relatively small company, so I feel like I would be betraying my manager who has invested a lot in me if I decided to leave so suddenly. I’d like to give my manager a chance to address my concerns, but I’m afraid to sour our relationship if I come across as a complainer. I’m also not confident there’s any solutions to my current frustrations because it seems to be a company-wide issue. How do I make sense of all of what I’m feeling?

2. I really like my company but their project management is atrocious, ad hoc, and “old school.” They’re not giving me privileges to configure Jira in ways that allow me to get stuff done.

   Is there an effective way to convince my CTO that I’m not going to screw up our secure systems or do I just need to find a new job?

In this episode, Dave and Jamison answer these questions:

1. My company wants several complex applications rewritten. “Steve” wrote the original applications, and has been assigned to do the rewrite. There is very little documentation on the original applications, and the rewrite will take intimate understanding of the existing code and new requirements.

   Management assigned me to work with Steve. They warned me that since we have started working remotely after covid, Steve has been hard to get a hold of and not meeting deadlines. My job is to keep Steve on task.

   When I ask Steve a question he will respond “I’ll work on it tomorrow” or “I’ll have to look in to that.” Then I never hear from him again. If I tell management I haven’t been able to get a hold of him, they will contact him, then he will contact me asking “What can I help you with?” Again, all his answers will be “I’ll have to look into that.”

   Occasionally Steve will report to me that he has finished a task. But because he did it without me, I am even more confused about what needs done or how to do it.

   I feel like my job has turned in to tattling on Steve. I am afraid I’m going to be labeled a whiner and that this project will harm my career growth.

   Over the last 2 weeks my solution has been to just ignore the project. Management hasn’t checked in with me, but I’m sitting on a ticking time bomb.

   What should I do?

2. How to keep our sanity in times of uncertainty? I’ve recently changed jobs and despite the facts shows that I shouldn’t be worried, I can see my judgement is blurred by the fear of getting laid off even there’s no sign of it and I fear I would fulfill the prophecy!

In this episode, Dave and Jamison answer these questions:

1. Listener Albert Camus asks,

   Hello Team. I am a long time listener of the show, and I really enjoy it. I’m a senior engineer and want to get to the next level in my career. I talked to my manager about this. I told them I preferred the technical side and staff engineer was the next level up. He responded positively, although he didn’t give me a timeline, not even a vague estimate. In a subsequent meeting they told me it wasn’t a linear progression at the company and there’s quite an overlap in the salary range between senior and staff engineer. I was also told that the company only had a few staff level engineers and they were considered experts at a particular sub-section of a technology. This makes me feel like I am being stalled. I have seen this a few years ago, at a previous workplace, where I tried for a promotion, and the manager at that place kept giving excuses to buy time. I am afraid that could be the case here as well. I am technically strong and have good soft-skills. I have designed, developed and documented multiple features for the company. Whenever there’s a complex bug, the product manager always turns towards me for help. I also handle inter-team discussions at times, always a part of the interview panel while hiring new team members and at most times the only person representing my team from the tech perspective during alignment meetings with the sales and marketing teams. I could also say with confidence that I bring more value to the table and have data to back it up. But I am not sure how I could use all this information without seeming desperate, to really push for that promotion and a raise. I could quit and get a new job, most probably with a promotion, but I have put in a lot of effort here and I intend to stay at the current company for at least the next couple of years to reap the rewards. What can I do to get that promotion in the coming year?

2. We know that the salary is high in our area, and I don’t need all this money. So, what is your opinion on part time job and how can I get one?

   I’m a senior frontend with more than 15 years of experience and just want to live a little.

In this episode, Dave and Jamison answer these questions:

1. I work at a small company that has recently grown from a couple of engineers to 40+ due to some great new project opportunities. As part of this transition, many new policies are being implemented. The policies concerning the engineering department primarily revolve around task tracking and reporting time. Gone are the days when an engineer can charge eight hours to “fixing stuff” and earn a paycheck. Most of us are on board, but there are three engineers in particular who have been around for quite some time and vary between subtly passive aggressive to downright combative when it comes to creating JIRA tasks and logging their hours.

   The problem? They serve an absolutely critical role in our company. They are nigh irreplaceable in an extremely niche market. How should a manager strike the perfect balance between forcing an engineer to do something that they don’t want to do and not forcing them out? If this was a more common skillset, there wouldn’t be an issue with telling them “You don’t like it, go find another job”. But when there are a handful of people in the world that do this kind of thing and it closely involves hardware and these three just happen to be local… well, you get the idea. Losing these individuals would be a staggering blow the company. Making them redundant isn’t economically feasible. Time to ramp up for this position would be close to a year.

2. So I’ve recently followed the first rule of Soft Skills Engineering and quit my job. All right! I believe in the new role and I think it’ll be a good change to me.

   Despite this, I’m feeling guilty about leaving my team behind. When my managers asked me how I was feeling in the last few quarters, I’ve mostly said I’m fine! I never told them my reservations about how the codebase I’m working on has no oversight, that they need to hire another dev because I don’t trust being the sole keeper, that it seems like product has forgotten this feature. I even indulged them when they asked me to make a long-term career plan when I was certain I would leave by early next year at the latest.

   So, what’s your take on how disgruntled employees often have to hide their true feelings? Maybe I could’ve been open, but it really seemed like the odds were against us, it’s just that upper leadership was neglecting this feature and there was no urgency to improve things. But I still feel like I wasn’t being fully honest. What do you guys think?

   Thanks so much and keep up the good work! Feelin’ Guilty

   P.S. Do you feel that this industry naturally rewards lack of loyalty and connection? What do you feel about that?

In this episode, Dave and Jamison answer these questions:

1. Hi! I have been a software engineer at a very small company for 10 years. We write desktop products and single server products - I don’t have experience with scaling systems or the latest & greatest Javascript frameworks. I would like to move to a company where I can learn and grow, using a more modern stack. My coding skills are great, but it seems like I just don’t have the experience many companies are looking for. With 15 years total experience I am too junior for senior positions, and too senior for junior positions. I’m feeling stuck and am tempted to quit my job so I can focus on side projects using the latest and greatest tools. Or is there a better way to get unstuck?

2. Listener James asks,

   How do you know when it’s the right time to move on from an almost perfect job?

   I’ve been a frontend developer for 6 years and spent the last 2 years at a really great company. I have lot’s of autonomy, a competitive salary, excellent stock options, and great job security. But, so far my entire career has been working with the same technologies, and there’s no scope to learn new languages at my current job.

   I was recently contacted by a recruiter, which resulted in an interview and offer for a full-stack role with a stack that would be completely new to me but really excites me.

   I’m worried that never holding development job for more than 2 years would look bad, but at the same time I don’t want to be stagnant and not learning.

   Should I stay at my current job where I’m comfortable, or take a risk and jump into the unknown to develop my career.

In this episode, Dave and Jamison answer these questions:

1. Do you have any advice on how to give feedback to people who don’t take critical feedback well? There’s a person who joined my team with the same job title and level as me (senior product designer/L5) more than a year ago, and since then he has shown that he not only lacks a lot of skills to be considered senior but also lacks the self-awareness to see where he falls short and how he needs to improve. There have been multiple occasions in our 1:1s where he has alluded to critical feedback he’s gotten from people on our team (including our manager) and has written it off as irrelevant or untrue, will come up with excuses for his poor performance, and will make off-hand comments about the person as a way to discount their credibility. Overall I feel like this is part of a larger display of narcissist behavior; I’ve noticed that the only time he’ll listen to suggestions is if you make it not sound critical and sandwich them in between compliments.

   Up until now, I (hopefully) have avoided being on the receiving end of his negative comments, but since I’m trying to go for promotion, my manager wants me to give him more guidance and tell him directly the feedback that I’ve brought up to her. Seeing how he’s reacted in the past, I’m unsure how to just start giving him unsolicited feedback and am afraid of what he’ll think and say to others about me as someone with four less years of industry experience trying to give him advice. I’m also afraid that this will damage our working relationship as I’ve seen how despondent he becomes when things don’t go his way. I’ve told my manager these concerns and her response was that it isn’t on me if he reacts poorly to my feedback, but I feel like putting in the energy to give him feedback that he probably won’t even listen to is exhausting and isn’t worth the possibility of him becoming more adversarial towards me. What can I do? Any advice??

2. I recently joined a new company following the patented space law certified strategy of quit your job. I have a senior colleague who has been there maybe 8 months more than me. Whenever he has a problem, he likes to call me away from my desk and start explaining his entire problem to me. I have no knowledge of the real codebase yet and am not even an experienced programmer as I barely have 2 year of experience. I just stand there and nod and give various quips from time to time to pretend I’m listening. This can last up to 30 minutes and happens numerous times a day. If I say I’m busy he just waits 5 minutes before calling me over again. I cant get any work done because of this. How do I deal with this senior team mate that uses me as a rubber duck. Should I just buy him an actual rubber duck ?

In this episode, Dave and Jamison answer these questions:

1. Hi! Love the podcast and have been listening for a while.

   I have a question about dealing with “that guy” on the team. I’ve been through several teams throughout my career, and every once in a while, I get on a team where there’s always a “that guy” that everyone seems to tiptoe around. They’re the type that would yell and scream to have everything go their way, and they’re typically very blunt to anyone, saying things in a really hurtful way. These people can either be technical or on the product side, but I’ve found it really difficult to work with people like this.

   After working long enough with “that guy”, it seems the common thing people do is just to say “Oh, that’s just so-and-so.” or “That’s just the way so-and-so is.”, which I feel is the only thing you can do, but that just doesn’t sit right with me because it’s incredibly toxic.

   I don’t think the solution is to just fire people like this, but it boggles my mind how so many teams just let this kind of behavior happen because the manager can’t or won’t take any action other than give them a talking to, which seems to just allow the behavior to continue because there are no consequences.

   Have you ever dealt with situations like this? And if so, how do you normally handle it without just ignoring it?

2. I am a senior FE engineer and I have recurring 1-1s with my skip level manager (manager of my manager) who is the Head of Engineering at the unicorn I work for. I usually ask what is top of mind for them (usually hiring), give feedback about my manager, and get additional feedback on bigger picture things I’m working on (e.g. we’re currently working on metrics to measure impact and value of our design system and other internal tooling). What else would you ask them to make the best use of this time?

In this episode, Dave and Jamison answer these questions:

1. Dear Skillet HQ,

   How would you negotiate a difference in work-life balance between teams?

   I love my job and my immediate team. We’re a tech group within a larger non-tech business, and it’s a fun problem domain.

   Our immediate team has some hard-won work-life balance, in part because it would be hard to hire anyone for the role if that balance wasn’t part of the equation. However, I worry about how to communicate differences when anyone we work with - all the people we’re building software for! - have an unbalanced schedule, because, 👋that’s show-biz 👋

   I even understand why other people have their role set up that way and respect it, but I don’t want to give up my balance either.

   How can I best handle the relationship when that difference is there?

   Love the podcast and the skillet-slack! Thanks for the advice, empathy and good humor.

   Tex Archana

2. Listener Frustrated asks,

   My work keeps getting stolen in the name of code quality!

   I’m a new backend developer for a team at a large company. I’ve been with this team for almost 3 months now, and the company for over a year. We’re developing an application to replace a legacy system, and the current feature has fairly well described user requirements. The front end developers keep finding new implementation issues that require more backend development, so new tasks get added during the sprint. The longest tenure developer (LTD) on the team keeps finding better ways to implement these backend changes, but these ‘better’ ways sometimes don’t meet the newly discovered frontend needs, leading to longer development times. Additionally, the longest tenure developer often takes over the implementation work from me, which is frustrating! The longest tenure developer also sometimes becomes too busy to deliver everything in a timely manner!!

   Additionally, the state of software development maturity is very low, so I’m trying to advocate for more technical process improvements like CICD and using version control more than once per sprint! I am frustrated and finding it hard to keep up motivation when everything is such a mess, and the other devs defer to the longest tenure dev who pushes back on many of these things.

   My code quality is fine, but I haven’t yet learned enough about our application to be able to identify these larger, cleaner approaches. Every code review so far has had no issues with my code quality, but inspires the longest tenure dev to implement a simpler solution, and they often will take my tickets and repurpose them for the new work! I’m worried that if anyone looks at productivity metrics they’ll not look good for me, and it’s hard to say what I’ve accomplished so far.

   Is my frustration valid? Should I quit my job?

In this episode, Dave and Jamison answer these questions:

1. After six years at my first job out of college, I took the foolproof SSE advice and quit my job last year during the height of the pandemic. I landed at one of the Big Software Companies and learned that I negotiated very well for pay within my role (in large part, thanks to this podcast - yay!), but I am way overqualified compared to my peers and should have attempted to come in at the next software engineer level (oops).

   To get promoted I need signoff from my fairly new manager and the very tenured principal engineer (PE) who has historically run the team. My manager and the PE are frequently in disagreement, and send me one-off slacks to make requests that are directly at odds with each other. I’m squarely aligned with my manager’s prioritization which frequently puts me at odds with the senior PE. Yikes.

   The senior PE frequently overlooks technical complexity and business context, and gives far more technical opportunities to the men on the team. I don’t like his mode of leadership, and so do not want to mimic his style. Unfortunately, he’s very respected by the VP+ level so I worry that friction with him will swiftly crush my dreams of promotion.

   The parents are fighting. I’m caught in the middle and feel like I’m aligned with the side that is at a political disadvantage. Is there any hope of success for me unless they can magically start to get along?

2. I joined a small team as a developer a few years ago, and was asked by management to help introduce some formal processes to the team to help us release a project that has been in the works for a number of years.

   With the team’s buy-in, I introduced SCRUM, and started playing the role of Scrum Master and Product Owner. I may also be the development team’s functional manager in the future. It seems that having the roles of 1) developer, 2) scrum master, 3) product owner, and 4) functional manager is too much for any one person to do well. With a primary role of functional manager, which of these other roles would make sense to hold onto? Which roles would be better to either hire replacements for or coach other team members to take over?

In this episode, Dave and Jamison answer these questions:

1. I’m on a team of two. My manager/teammate is young (under 30, less than 5 years total work experience), minimally experienced with anything other than writing code, and has an inflated self-assessment of their own coding skills.

   They have a habit of either asking for (or simply changing on their own) every little thing to be their own way. This can be as unimportant as renaming all the variables to a different word with the same meaning (think $largeCar instead of $bigCar) or as bad as - after a discussion between two techniques for a feature in which their preferred method wasn’t chosen, - going in later and changing the code to how they wanted to do things.

   I’m feeling burnt out by the lack of control over my work and feeling like what I’m doing doesn’t make a difference..

   Where and how should you draw lines in order to balance writing good software with showing respect for your team members? How do you deal with people who think their actions are justifiable because they are “improving” the code but really can only defend this by claiming it is “more readable” or some other subjective measure?

2. I work at a well-funded startup and am likely going to be promoted (into another IC engineering role) in the next few months. I’m pretty clear on the leverage I have when negotiating salary before accepting a job offer, but I’m wondering how I should approach negotiation and raise expectations when it comes to receiving a promotion. Obviously, my company wants to retain me, otherwise I wouldn’t be getting promoted, but I don’t feel confident in negotiating when I’m already being given a raise and my only alternative to accepting it would be to leave and find another job.

   Additionally, I’m on great terms with my company and manager and I would not leave over a 5-10k difference in raise expectations. Just want to better prepare myself for the offer. My manager has also told me that when/if I receive a raise, I can negotiate (it’s not too late). That came up because I told him I assumed raises and promotions are long processes that need to be decided way in advance, but that is not the case at my company.

Tweet about engineers’ puzzle obsession: https://twitter.com/ryanflorence/status/1534951668214771721

In this episode, Dave and Jamison answer these questions:

1. I’m a senior software engineer at a fast growing software startup. In the past year and a half that I’ve been with the company I’ve gone through 5 reorgs and have had 5 different managers in 4 different teams. Each time I sit down to do a 1 on 1 with a new manager they ask about my career goals and aspirations.

   Initially, when I joined the company I was a weak and feeble non-senior software engineer. When I was asked this question then, my answer was “to learn and grow, and have more authority and autonomy over the systems that I build, and be considered a senior software engineer”. Over the past year and half I have proven my worth and paid my dues and got the title of senior software engineer, along with the pay raise that came with it.

   My career development horizon has not been very broad. I didn’t even know there were levels beyond senior software engineer for a long time.

   I feel like I’m missing out on growth opportunities by not having a clear answer to this question. Please help!

   Love your show, keep it up.

2. I career switched via a coding bootcamp 3 years ago and have been at my current company ever since.

   The bugs created by my garbage code from the early days made me a big believer in clean code practices — I now feel strongly about using descriptive variable names, avoiding duplicate code, etc.

   However, my boss/CTO is on the opposite end of the spectrum. As long as the code works, he doesn’t care what it look like.

   I want to stay at this company because I strongly believe in the product and I love the flexibility of a small start-up, but my boss and I keep bumping heads.

   For example, we recently switched over to PRs, and each PR my boss has made included blatant violations of the coding standards document we created together (!). When I request changes on the PR, he says he’ll do it but it isn’t a good use of our time to rewrite it when the code works.

   My question is two-fold:

   (1) As the most senior engineer on the software team, how can I go about promoting a quality-driven approach when the CTO doesn’t see the value in it?

   (2) If all else fails, I’m open to quitting, but I don’t want to end up the same boat. During interviews, what questions can I ask to find out if the company truly values code quality?

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

Architecture Astronaut: https://www.joelonsoftware.com/2001/04/21/dont-let-architecture-astronauts-scare-you/

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.

Writing strategy and vision documents: https://lethain.com/strategies-visions/

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.

In this episode, Dave and Jamison answer these questions:

1. I work for a big bank. I recently found out I am severely underpaid. I have only received “exceeds expectations” ratings since joining over 5 years ago. I rage-interviewed at a bunch of FAANG companies, made it to the final rounds of all, but always came up short on the offer.

   Expectations at my current job are low. I’ve been putting all my extra energy and time into my own startup idea with a group of small people, that shows a lot of promise.

   I so desperately want to leave my current job, but I can’t prep for interviews and work on my startup at the same time. I never interviewed since joining the bank over 5 years ago.

   I truly believe my startup can ultimately be my escape, but I’m just grappling with the fact that it may take years before I can quit vs. if I got a new job I’d have much better pay and not be depressed at my 9-5.

   P.S. are you hiring?

2. I’ve recently been placed as tech lead for a small group of 3 people, myself included. One of my teammates seems to be having a hard time communicating in a timely manner when they are stuck on something or when their task will be late. I’ve spoken to that person a few times individually on the importance of communicating early and often, but it seems like that person is happy to just muddle on until the time runs out.

   I’ve had to jump on to finish some work that was time sensitive and I’ve gone to greater lengths to slack dm on how things are going. It’s getting old. I don’t want to be micro managing. Each time I bring it up with them, it seems to get through but never manifests in action. I’m not sure if this person realizes the impact that lack of communication has especially in a remote first setting. A sense of urgency might be helpful in some respects.

   At one of our 1on1 dm chats the topic of imposter syndrome came up and we shared our mutual struggles with it. I’ve tried to encourage that person that my dm’s are open and can help but I can’t keep checking in. There should be some ownership on their end to getting help from me. How do I get this person to communicate more, share blockers or confusion so we can finish our work on time and learn on the way?

   Love your show, long time listener, first time caller.

In this episode, Dave and Jamison answer these questions:

1. Listener Þór asks,

   Dear fellow binary smiths!

   I’m a Nordic software developer with about a decade in the industry under my belt who has recently returned back to the office, following a half a year long medical absence during which I helped my partner get through her second tough cancer treatment in as many years.

   I am now contemplating taking a sabbatical for some months to reset myself, as the ordeal has had a big impact on me in many ways.

   As sabbaticals are not a common occurrence in my parts of the world, I worry about what impact taking one could have on my future prospects once I start looking around for employment again.

   How does one frame having a “mental health” gap in the career when interviewing? Are they considered a “bad” signal by hiring managers?

2. For the first time in my career, I’ve been given the opportunity to lead a project at work. This was something I really wanted and my teammates supported me. We agreed on the technical design and I recently started implementing it.

   However, I’ve been thinking about finding another job for a long time. I’m demotivated. Each week, I feel bad about how little I get done at work. It negatively impacts my self esteem, a lot. I never acted upon the desire to find another job because I have a great manager and skip level. Recently, my manager and skip level both announced they’re leaving the company.

   I’d like to pursue an opportunity at another company that seems to be a great fit for me but I don’t want to leave my teammates holding the bag for the project I’ve been working on. I’m the only backend developer working on it and my teammates trusted me to take ownership of it. It doesn’t feel fair for me to complete the more glamorous responsibility of coming up with the technical design and then leave when it’s time to do the “grunt work”. On the other hand, there’s probably at least six months left of work on this project and the company I’m interested in joining may very well not be hiring in six months. What steps should I take to not betray my teammates or myself, taking into account that my manager and skip level leave within a month and probably won’t be replaced by then?

In this episode, Dave and Jamison answer these questions:

1. I recently told my boss I thought my comp was below market value and that, while I enjoy working here, I may have to start looking elsewhere for my next opportunity unless there was a way to adjust my salary. He actually agreed with me and said he would go to HR to see what he could do.

   A few days later, he came back to me and said they could do a market-rate adjustment of 20k per year. I was super happy. He said, “great I will let HR know that you accepted by EOD tomorrow and they will get the paperwork started.”

   At 10am the following day, he, along with a couple hundred other employees, were laid off.

   So my boss, my boss’s boss, my boss’s boss’s boss and the HR rep that my boss was talking to are no longer here.

   So my questions is, what’s the appropriate amount of time to wait before bringing this up to my new boss. With so many of my colleagues now out of work , it seems a bit insensitive to be so concerned with a raise, but also, I like more money.

2. I am 8 months into my first job out of college in an entry level role and today the other new hire (4 months) got fired for poor performance. I have been assured that my performance is still satisfactory, but I have been unable to think about anything else since it happened. I know that I am probably fine, but I am still very shocked and on edge. Any advice on how to move past this without destroying my bloodpressure would be appreciated!

   Signed, your fellow high strung engineer

In this episode, Dave and Jamison answer these questions:

1. I just hired someone as my direct report who is very, very smart, and has a great background. Ivy undergrad CS, Ivy grad school, and big tech experience. This is great!

   Except… he’s definitely much smarter than me. I slacked my way through a liberal arts degree, and have worked only for small startups my whole career. I’ve gotten by, but I’m no 10xer.

   How do I be a good manager for him considering all this? I want to help him grow in his career and be a good resource for him, but I don’t know what I have to offer. Should I just give him my key to the nonexistent middle manager cafeteria, and say, “I work for you now?

2. Hi, I have a question about how to handle being confused in certain team meetings.

   It happens when the meeting is about discussing a certain problem to solve and most participants are much more up to speed with the issue being discussed. What ends up happening is that they discuss things fast, while I am hardly following and wondering if I should even be there. That is painful to me, because I’m aware that I’m not contributing much, while my time there is wasted and spent half trying to follow and half stressing out thinking what I should do.

   I guess that in order to contribute I would need to ask to be brought up to speed. Which I find a bit tricky because I’ll be asking myself: is it because I missed something? Or is it because of something I actually couldn’t possibly know? And secondly, should I have it clarified, which would disrupt the discussion and draw it out for others (especially if I need to go back to something that the group already went over)?

   Or should I address this completely differently, for example by requesting meeting agendas and preparing questions before the meetings? I’d love to hear your thoughts on how to tackle this, because it’s a pain every time it happens.

In this episode, Dave and Jamison answer these questions:

1. Hi :-)

   I work as a Senior Data Scientist, and about half a year ago I joined a start up that was founded by a large corporation. And while this job comes with the perks of a bigger company - like good salary, paid overtime, … , - it also comes with its organizational overhead and politics:

   We are only about 30 people but already a quarter of us acts as managers. I write “act” because the official org chart is flat (with the CEO at the top and the rest of us directly underneath). The unofficial org chart is hidden and depending on who you speak with, you get their view point on how roles and responsibilities should look like. As a result, I’m left with putting together the pieces to build a picture that somewhat resembles the truth. So far, I’ve concluded that we have multiple (!) management layers, that there’s a power war taking place in the middle management layer, and that you can make up your own titles that mean NOTHING, because no one has any official, disciplinary authority over any one, but that are still to be respected! What a great opportunity for job crafting :-D

   To make things worse, I prefer and come from organizations that have a truly flat hierarchy. For example, I’m used to step outside of my role should the situation require it (like doing some managerial tasks, supporting sales, …) and that I can speak my mind, irrespective of what the title of the person is who I’m talking to. While this was beneficial in my previous positions, this does not work well here! And while I understand that adapting my behavior would be more in line with the company culture, I find this extremely difficult. On the one hand, because of the hidden org chart, on the other because we are all fully remote and I rarely see people from other teams.

   To avoid accidentally stepping on anyone’s toes, my current solution is to stick my head in the sand and focus on my coding. However, this leaves me disgruntled because I feel like I’m not being myself, and that I’m withholding a viable part of my skill set: to see the bigger picture and serve the company as a whole instead of just implementing tickets.

   Please help, I do not understand how this company works :’-D How would you navigate the situation? I don’t want to quit because, individually, my coworkers are super nice, and the work is really interesting.

   All the best <3

2. Hi,

   I’ve been working at a well-known multinational company for a few years now. The entire time I’ve been here, the company has been well behind what I believe to be industry standards, but they have some great perks, which means it’s been really easy for me to create “wow” ideas (just do the same thing that everybody else has been doing for a few years).

   At the risk of sounding full of myself, I’ve noticed that I’ve created a critical person risk. There’s not only no push for me to train others in my work; things I thought were standard knowledge is entirely new to this team! I don’t want to become the trainer for a team that has no desire to learn new skills, and I don’t want to dumb down my work either. Is there a happy medium where I can build exciting new things and not create an absolute craphow when I leave? Should I even care about it since no one else does?

• The Tyranny Of Structurelessness - https://www.jofreeman.com/joreen/tyranny.htm

In this episode, Dave and Jamison answer these questions:

1. I’ve been a Staff Software Engineer at my company for 1 1/2 years. We have about 120 engineers company-wide. I’ve had 4 different bosses during the last year and our team has moved around a few times on the org chart.

   I lead a team of 2 engineers. My boss told me I shouldn’t be doing any of the coding but should spending my time working with the product manager, doing research for upcoming features, doing code reviews, managing the Jira board, mastering jellyfish metrics, reviewing architecture documents, setting up measurement in our logging tool and coordinating deployments of our features.

   Because my team is small and our product roadmap is pretty well defined, these tasks do not take 40 hours per week. I feel like I have nothing to do. I’ve tried to improve the velocity of the team by doing some coding and triaging on bugs. I miss doing the technical work and feel like I could do more but I also want the other 2 engineers on the team to own most of the big, bulky tasks.

   What do you suggest I do? Should I enjoy my light load or should I be looking for other ways to add value?

2. I am the lead developer on a few projects with developers that have 20+ years of experience compared to my eight years. I have been made lead of the projects, but I’ve never actually had management tell the team that I am the lead or that I have any control whatsoever on the members of the team (typical ‘all of the responsibility, none of the power’ scenario). One of my teammates is tough. He writes unreadable but working spaghetti code. He also works in the field and will often times push to master and then leave to perform fieldwork, leaving the team in the lurch for several days before he can come back and fix his broken code. He habitually fails to push code, often holding the source on his own computer for months before pushing. I have mandated using pre-commit hooks to guard against breaking the build, but as IT has control over the repositories, these become “optional” and appear to be disregarded. I have brought this up with management, to no avail; the behavior continues. I have also expressed my concerns with management, and provided data on the impact this has to the project via tickets and time spent between the remaining team members.

   How do I rein in this unwieldy developer? What else can I do?

• https://www.gamasutra.com/view/feature/4111/dirty_coding_tricks.php?page=4

In this episode, Dave and Jamison answer these questions:

1. My boss keeps recommending bad movies. I watch most of them but I feel bad because they’re not good and I don’t want to disappoint my boss. They are ‘okay’ but are really mediocre. Do I just ignore my boss’s suggestions or should I keep watching these terrible action-heist movies even though I don’t like them?

2. Does it matter if my emails are well written?

   I’m a software engineer. I asked my partner how I should word a part of my email. After reading my email they were appalled. They said that it was “abysmally written and lacked refinement”. I’ll admit that it wasn’t my best written email, but who cares? It was just an email letting a team member know that I had followed up on a ticket a while ago, so it wasn’t like this was going to a client or something. Plus I felt like the email conveyed the message that it needed to.

   In my mind as long as the email isn’t offensive or covered in grammatical errors and conveys the message, isn’t that good enough? My partner argued that I should write my emails more eloquently since my “terrible” emails will reflect poorly on me. I told other engineers care more about the content and less about how well-written any given email is, but they wouldn’t budge. In addition to that, some of the emails I’ve gotten from our senior and staff engineers seem like they were written with someone who has the English skills of a middle schooler and they seem to do fine for themselves.

   Thoughts?

This episode is sponsored by Compiler, and original podcast from Red Hat. Check it out

Reference to the Dragon book on Wikipedia

Robustness principle: Be liberal in what you accept and conservative in what you send

In this episode, Dave and Jamison answer these questions:

1. Listener Casey asks,

   My team has built an internal framework for continuous delivery that enabled a key product release last year. The tooling has gained widespread adoption and popularity throughout the org, to the point that some leaders are requiring teams to use the framework for any new services. Things are generally going great, except that “my team” consists of only 2 people including myself, and we have so much work that the soonest we can look at new features is ~18 months from now. Some individuals, who are being required to use our framework, are frustrated and protesting loudly about how the framework doesn’t work exactly the way they think it should. How can I shelter my team from the outbursts of unhappy users? Or bolster their resolve so they don’t take on the anxiety of growing pains?

   P.S. We’re all remote so this happens 99% in chat channels and DMs.

2. If something goes right, product takes credit. If something goes wrong, engineering takes the blame. How do you change that organizational dynamic? (Other than your usual answer.)

We are celebrating our 300th episode by publishing unique songs about the podcast. To get access to the songs, join Patreon: https://www.patreon.com/SoftSkillsEng

In this episode, Dave and Jamison answer these questions:

1. Greetings! I have been with my current company for a number of years, and was recently promoted to Engineering Manager. I enjoy working here, and have a great manager and team. A job posting at another company recently piqued my interest (great salary, appealing company values, fully remote) and got me thinking, would it look terrible if I applied for, or switched jobs, so soon after a promotion to management?

2. How can I figure out if communication problems with a team member are cultural or personal? My teammate immigrated to the states. We occasionally stumble over conversation and misunderstand each other. I think this is exacerbated by being remote. For example, they will ask a pointed and direct question that sounds like a challenge to my approach to a problem. When I attempt to answer, it’s clear we are nowhere near the same page and I need to back up and provide more detail.

   I am working and have worked with others who immigrated from the same country. I’ve had similar difficulties connecting before that I have not had with other teammates from other regions. However, this is not universally true of every teammate I’ve had from this area.

   If it is a cultural style, I would rather learn to adapt. I’m not interested in suggesting everyone need to conform to my cultural sensibilities. But if I can determine it’s a personal difficulty, we can work on it together.

In this episode, Dave and Jamison answer these questions:

1. I’m a new team leader running a new project and when asked for a delivery date I gave my best guess (noob!). That date is at hand, our project is not. I gave a new delivery date and you guessed it, it’s later than the date I said way back when.

   I presented this new date to my boss, but he wants us to deploy what we have now… even though if we deployed what we have now the business’s cash flow would ignite tearing our collective hopes and dreams asunder. I told him this, in those words, and he said (with a knowing look) “ahhh, you’ve got to play the game, you have a reputation to protect”. I said I’d prefer a reputation of honesty, accuracy and improvement. He said he was talking about his reputation. His other teams consistently miss delivery dates, so I’d guess he has a reputation of missing delivery dates.

   I’d love to share my more accurate date, but that now feels like going behind his back, but if I don’t go behind his back - I’m going to get stabbed in my front. For now I’ve settled on putting my new date in confluence so I can use it as a shield when the inquisition comes. Dave, Jamison, what would you do and why?

2. A parallel team has sold our VP on their internal framework, and has the VP convinced all other groups in his org should become dependent on it as a multi-app, multi-platform solution.

   Their framework is very buggy and they are very slow to acknowledge and fix bugs. They claim that due to the overwhelming amount of users/adopters of their framework, they can’t look at bugs, or that other projects take priority. This blocks our development. No one except them wanted to use their product, and somehow they used forced widespread adoption to avoid responsibility for missing their deadlines. This group has magnificent soft skills that have allowed them to evade being accountable for their issues.

   This team is a darling to the VP, so they are immune to accepting our feedback for the points I listed in the above question.

   How can we, who are multiple levels removed from this VP, improve our situation? Our group enjoys working together and on our product, so we don’t want to leave. We just want to find a way to become more tolerant of this other underperforming team.

• https://www.hillelwayne.com/post/we-are-not-special/

In this episode, Dave and Jamison answer these questions:

1. Earlier I decided I would quit my corporate engineering job in 2022. I’d stagnated, I wasn’t writing as much code as I wanted, and my company made me write our services in an internal domain specific language (DSL), which I don’t like. I’ve put off quitting due to anxiety reasons and not knowing exactly what I want to do next. I’ve even thought about taking a short gap to figure things out, but maybe that’s just me being a dramatic young person (I graduated university in May of 2020).

   However, now my company has done something terrible and promoted me to a second level engineer! And my manager has actually listened to my feedback! How could they?

   I still want to leave because the DSL ruins my coding skills and won’t transfer elsewhere. I work with great people. Also, I play an important role in the group because we’ve had so much turnover this past year. I don’t want to fall into the trap of thinking “the grass is always greener on the other side”, but I think leaving would be best for my career. How can I approach this without giving the impression that I’m flaky or ungrateful? And should I stop deliberating and quit my job sooner rather than later?

2. I started a new position three months ago for a large pay increase, I am a fully remote software dev on a team of mostly local developers. My manager-to-be left the company a week before I started, and has not been replaced. The onboarding has been extremely lacking, I don’t have a mentor or buddy, I have very little l communication with my direct manager, and I have very little guidance on what to actually do, so I have been doing… nothing. Some days I do not even open my laptop. How do I start the conversation with my manager that I need something to do, without revealing openly that I have been doing nothing for the past three months?

In this episode, Dave and Jamison answer these questions:

1. Liam asks,

   I was the second hire in my team and worked with one lead engineer who created the entire codebase from scratch. This engineer’s code was functional but not well architected and has many inconsistencies. They have since left the company and replaced with two new senior developers who are a lot stronger technically.

   We recognize issues with the current codebase but we’re finding it hard to make decisions on the best way of solving things. We’re all at the same seniority level and the managers above us do not have hands-on experience with our codebase or tech stack.

   Because we’re at the same seniority level I don’t want to start acting beyond my job title and make all the architectural decisions, but at the same time I don’t want to be a pushover.

   How should decisions be made in a team with a flat structure and no defined leader?

2. My previous manager quit the company last year and we’ve been assigned a new one. While the previous manager knew technical side of the project really well, the new one seems to be clueless. He is not even showing any interest in learning about what we do. He is a good people manager, but lack of context makes him really bad project manager. What should I do? Should I talk to him to convince him to learn more or maybe it is normal and we were just really lucky with the previous manager?

In this episode, Dave and Jamison answer these questions:

1. Hi! long time listener first time caller. i am the CTO of an early startup with 15 employees (12 engineers). 3 months ago, we hired a new engineer whose output is quite low compared to other engineers on the team. i have brought this up with him many times and tried to coach him on his debugging skills, time management skills, etc. After months of this, I am not seeing any change in output and am growing frustrated. At this point, I suspect that the engineer is just spending very little time on their tasks compared to others on the team (who admittedly often work late into the night). I don’t want to fire the engineer or micromanage his schedule, but am concerned that their slowness will impact our culture and product. Do you have any ideas on how I could help this engineer improve?

2. Howdy fellas,

   I started my first SWE job out of college at a startup in the bay area and work in a team of three. Myself, my technical manager, and one other developer who comes from an adjacent field. I came three years of interning as a developer at a very relaxed company with 3000+ employees. I’m finding I have a lot more ownership over my work now than ever before and I really enjoy that!

   What I don’t enjoy is watching my manager run around like a headless chicken. Between managing all our jira boards, creating POC’s for a complete redesign of our core services, interviewing candidates, planning features for our existing services, and doing regular sprint work they have too much to do and not nearly enough time for all of it. This results in many things that are critical getting scrambled, forgotten, miscommunicated, or just dropped for lack of time on their part.

   I’ve tried to take some of the small tasks from them that aren’t necessarily a manager’s job such as managing the jira board and help desk tickets. Unfortunately they insist that they don’t want me to take over small tasks like that because they can handle it, but the same issues from them being overloaded persist.

   I think the team over all would be a lot more effective if they were able to focus in on particular tasks, but since they won’t let me help what else can I do?

In this episode, Dave and Jamison answer these questions:

1. Love the podcast, love the banter and jokes, keep up the great work! Now, for my predicament:

   Good news: I just got my first job at a FAANG! Bad news: I’m coming in at the lowest level of software engineering despite being in my mid-30’s and nearly 10 years of non-FAANG experience.

   Given that it is my first Big Tech™ company, I understand being down-leveled, but I did not expect to be downleveled THIS much. I’m glad to have finally “hit the big leagues”, but I’m not thrilled that I’m on equal footing with a fresh college graduate. Hurt feelings aside, what is the best Soft Skills advice on how to catch up to the mid-30’s engineers who joined a FAANG fresh out of college? My plan is to tell my aspirations to my manager once I start and see how they can help me perform as well as possible in order to promote quickly, but I can see how that might come off as greedy or entitled. What do you think?

2. Should I do anything about a lazy tech lead?

   Since covid and working from home, my tech lead went from a frantic micromanager to a lazy coaster.

   They seem to do 1-2 hours of work per day. They set their slack status to ‘away’ so you can’t tell if they are at their desk or not. They’ve stopped coding completely, but we have an excellent PM so there isn’t much else for them to do. Sometimes during stand-up you can clearly hear them driving their car. Even asking them for help/advice on slack can mean several hours waiting for a response.

   Management hasn’t noticed because we are a large team who all work really hard, so the feature output is still high.

   My dilemma: do I count myself lucky that they are no longer micromanaging and keep my mouth shut? Better the devil you know etc. Or, do I gather some evidence and tell their boss? I could be learning so much more from an engaged tech lead, and the team might feel less toxic.

   Final doozy: due to some incredible stock market gains I have some heavy golden handcuffs so #1 priority is keeping my own job and not creating an enemy that gets me fired.

In this episode, Dave and Jamison answer these questions:

1. I work in a squad that has been slow in delivering. Squad leadership (including myself) concluded we need a staff engineer (one level above senior engineer) to help guide tech directions and to support other engineers.

   Unfortunately we have received only a single applicant- senior engineer “Brett” who’s already on the team. Brett is a good engineer and has a lot of great qualities - but falls short of the “staff” level. Our tech lead “Chris” doesn’t think Brett is suitable due to bad technical decisions Brett has made in the past. Chris also thinks Brett should have been discouraged from applying in the first place. (Brett’s manager is outside the team so has less visibility on what’s happening inside the squad)

   We’re suddenly in a bind. If we give Brett the role we are in the same situation as before but having to pay him more.

   If we don’t give him the role we run the risk of losing him in this environment - which would be very bad as he is a good engineer!

   Should our decision be down to how Brett interviews? What could have been done differently?

2. I recently did some extensive planning for a feature with a back-end engineer where we negotiated what the GraphQL api would look like. As I was finishing up my feature work, I realized that they departed from that plan and didn’t tell me. Now the feature is late. They’re having to make adjustments because the departure from the spec made it impossible for the front-end to handle the data. I’m having to do more work because they used a completely different architecture than what we discussed. What’s even more frustrating is that the end result on the backend is going to be exactly the design that I initially proposed (this is documented), which the backend engineer shot down when I proposed it.

   I feel angry that they dismissed my technical expertise. This has also eroded my faith in collaborating with this person. Retro’s coming up. How would you approach retro? What outcome do I even want here? I don’t think more process is going to be helpful (I spent 6-8 hours on the planning portion of this feature). I am starting to wonder if my perception as a primarily front-end engineer prevents the back-end engineers from lending me credibility.

In this episode, Dave and Jamison answer these questions:

1. Hi Soft Skills!

   I’m writing to you as I look forlornly at my paycheck, unchanged for the last year and a half, and wonder if I’ll ever see market rate again. While I prepare my leetcoding skills for the trek that is your classic Soft Skills Adventure (quitting), I think about future interviews and wonder: how common is it to have something like a COLA clause in your employment agreement? Something like “Oliver will receive a raise of no less than the current CPI% per year”. Are there other ways to mitigate this, other than joining a company with more people and less greed? I don’t think I should have to beg for COLA-s with good reviews in hand. In fact I think those reviews call for raises!

   Thanks for bringing more joy to my life :),

   Mr Twist

   P.S. I am grateful I’m not paid in porridge and any reference to Oliver Twist isn’t to suggest Tech Salaries aren’t livable wages.

2. Mr. Peanut Butter asks,

   I’m a senior IC at a small startup and I’m struggling to get along with an engineering manager. M has a say in my promotion and has already said no once, which was pretty painful considering the time and energy I’d spent helping their team succeed. I think there are two headwinds to M changing their mind 1) I’m FE-focused, and M’s conception of FE work is dated and simplistic. 2) M can be a bit of a blowhard. Said generously: M is a top-down thinker, quick to make conclusions, process-focused, and loves discussing architecture and design patterns. In contrast, I’m a bottoms-up thinker, pragmatic, plain-spoken, slow to make conclusions. M and I meet regularly to discuss cross-team matters, and it is my least favorite meeting of the week, even weeks that include dentist appointments. M sometimes devolves into lecturing me about software fundamentals (which I know at least a well as they do). I know from experience that there’s an M at nearly every company, so I’m reluctant to order up an SSE Special. How do I leverage this dreaded weekly meeting to turn M from a detractor to a promoter?

In this episode, Dave and Jamison answer these questions:

1. Is it possible to move too fast and do you believe in too much enthusiasm? I am one of the youngest member of the team and am always willing to start new projects and balance a few different things. Is there a point where this can start hurting my career? I’ve gotten bumped in compensation fairly, almost 25% raise since I first started. My career goal is to stay on the programming side but want to become a possible trainer for newer engineers/devs.

2. Listener Michael asks,

   I’m a backend engineer in an engineering/coding role with a small bit of SRE type work. I love the work as I get to dig deep into tech we use and have become subject a matter expert on databases within the company. I really like my team and my manager in particular, and get to learn a lot every week. My manager is leaving my team to lead a new team within the company that is focused on the company’s SaaS offering and I’ve been given the option of joining this new team if I wish. I like their managerial style and how they have helped me with my career progression so far. However, I’d be doing Site Reliability Engineering (SRE) work. I’m not sure if I’m ready yet to commit to being an SRE and code less/focus more on ensuring the reliability of mission critical production systems. I don’t know how easy it would be to switch back to more of a coding role in a years time or if it would pigeonhole me into that type of role. Have you got any advice?

In this episode, Dave and Jamison answer these questions:

1. I recently joined a new company that pays me much better and has much better engineering practices than my previous job.

   I referred a great engineer who was hired on a different team. Then, another engineer from my old job applied for MY team and is currently being interviewed for the role.

   This engineer is one of the reasons I left my former company! They have an impressive resume and interview well, but are unable to complete even the most basic tasks and have no interest in improving their skills. They asked me to put in a good word with my tech lead, but if anything, I want to encourage my tech lead NOT to hire them. I’m not a part of the interviewing process but I feel an obligation to let my tech lead know just how bad this developer is. Help?

2. Thanks for thinking I’m neat! I think you are pretty neat too!

   In my most recent 121, my manager asked me to give some feedback on another colleague on whether I thought they would make a good Engineering Manager. My genuine thoughts about my colleague are that they’re pretty good technically, they have good communication skills, are friendly, and just generally a good team player. Outside of work, we’re pretty good friends and so I really want to see them succeed. However, I can’t shake the feeling that they wouldn’t necessarily be a good Engineering Manager and I can’t figure out why. What are some other (not so obvious) qualities that you think are important for EMs, since on paper, I would think they tick a lot of the boxes.

In this episode, Dave and Jamison answer these questions:

1. Hi! Thanks so much for all the work you do to put this show out, it’s kept me sane the past year. To sum up my problem…I’m aware this is going to sound like a slightly bananas thing to complain about, but my team’s tech lead is superhumanly productive.

   About 8 months ago, we hired Sarah. I can’t overstate how awesome Sarah is, but, well, in some ways that’s the problem. My team already suffers from under-resourcing. Rather than pushing back on unrealistic requests, Sarah will churn out 90% of the work required by working crazy hours so that we make the deadline. She always shares the credit and plays up even the smallest contribution any of the rest of us made, so again, that’s not at all the issue.

   For context, my team doesn’t have a manager, and our leaders are super high up the org chart.

   The problem is that now leadership expects this velocity from the team all the time, not realizing that this it relies on Sarah’s definitely-unsustainable level of productivity. Many other teams in our org are struggling to deliver due to the same resource constraints we face, so now their work is being lumped on our team as well, because the perception is that we’re The Team That Can Handle It. We’ve already lost one team member this year due to burnout, and the pace just keeps increasing. Additionally, I feel like this undermines leadership’s trust in my opinions. Leadership sometimes asks me how long a given thing will take. I’ll give an honest answer, but then when Sarah delivers the thing much faster by working 14-hour days, it makes it look like I’ve been sandbagging my estimates.

   How do I approach this? I’ve thought about explaining my concerns to Sarah in a 1:1, but I feel like I’d just come across as lazy and whiny…for all I know, she thinks we all should work like she does, although she’d definitely be too polite to say so outright. Are there any other options, or is this a :partyquityourjob: situation?

2. Hello Hosts!

   I love the podcast and its light and humorous tone on a not so light subject.

   Ours is a small team with just 2 engineers in a mid-sized company. I joined recently as a senior engineer. The other person was hired for the same role a few months after me. The problem is that this other engineer doesn’t seem to posses senior level skill-set. I often find them making obvious mistakes and struggling to understand user stories. On most occasions they aren’t even able to finish their work, let alone making technical design decisions.

   I tried to bring this up in a casual way with them, and they seemed to get a bit touchy and defensive about it and they also seem to have a difficult time in making honest conversations about issues. So I never brought this up again. This situation of them not being able to carry out their expected responsibilities is taxing me a lot as I have to pick up the things they mess up in addition to my job.

   If this was from a person at a much junior level, that would be understandable. But this doesn’t make any sense to me.

   I am not very comfortable with the idea of ratting them out to the manager and seeming like a non-team player, but I am also afraid that I cannot put up with them for long while also still maintaining my sanity.

   If you were in my situation, may I know what would you do differently and how would you deal with this person? Thanking you!

In this episode, Dave and Jamison answer these questions:

1. I wanted to know if listing past offers (as a brand name signal) on your resume will help or hurt you during the resume screening and interview stages?

2. I am an SQA engineer at one of the FAANGS, and I feel inadequate in my position; I get the gist QAs are not valued much. Essentially I got into this domain early in my career, and I find moving out of this role difficult. My long-term goal is to get into a PM role. Is that even possible, or should I first switch to the Dev role to build a better foundation? Help me. I am lost.

In this episode, Dave and Jamison answer these questions:

1. Hey guys, a long time listener here, I love the show.

   I’ve recently joined an early-stage startup with a tiny engineering team. It’s like most startups at this stage, there’s some chaos and a lot to figure out. It’s exactly what I like about startups.

   In the past years, I’ve been working on the very same kind of software we’re building now. I have a ready answer for many questions we might have, I’ve seen some things go badly and others work great. I’m eager to help the team deliver.

   But I also don’t want to be seen as the know-it-all jerk that tells everyone how to do their job. I have respect for my team and want to contribute. How do I use my experience without annoying my colleagues?

   Thanks for sharing your wisdom (I hope for 101% of it).

2. Listener Andy asks,

   I moved to company A and it’s been 6 months I am constantly getting interview requests, Gave an interview and got a 30% rise moved to Company B, Now within 6 months the same thing happened, Gave an interview at Company C and got the job with 30% raise. what should I do? will it affect my long term career growth

In this episode, Dave and Jamison answer these questions:

1. I am working at my first job as a software engineer for 2 1/2 years now. I really enjoy working as a programmer and I’m super excited about the tech industry in general.

   However, sometimes I feel like I’m too excited about everything. I spent a lot of time reading blog posts, watching tutorials or taking online courses. I think about what books to read and what languages to learn all the time. Not everything but a big part of it happens during my working hours. While I know that “loving to learn” in general is considered a positive trait, I feel like I might take it a bit too far and I should focus more on the actual tasks I have - especially, because I think my coworkers spend much less time keeping up to date with everything.

   What is a reasonable amount of time to spent on these things during working hours and beyond? How do I know I spend too much time not working on my actual tasks? How can I make sure I learn the right things that are useful to my career?

   Love the show and wish you the best. Thanks for your advice!

2. I landed a new job that nearly tripled my salary realative to the job I’m about to leave (yes, I was horribly underpaid)! The stories and tips from this podcast really helped me out but I also landed this job through Hired.com (the podcast sponsor).

   Any good tips regarding leaving a job when you know your boss will be furious that you’re leaving? Also, should I tell my boss which company I’m going to when he asks (he definitely will)?

• Tom7, the most amazing YouTuber of all time: https://www.youtube.com/c/suckerpinch
• https://www.youtube.com/watch?v=qTBAW-Eh0tM - anagraphs

In this episode, Dave and Jamison answer these questions:

1. Listener Sara asks,

   How can I deal with favoritism towards informal leaders in a group? The group is losing group intelligence because the informal leader’s reasoning and direction is favored. Example: when member A propose an argument is dismissed, but when the informal leader proposes the same argument it is cherished.

2. How do I react to the question “why didn’t you do it this way” for features already in production? I am frustrated by being asked that. I got scolded for an idea that turned out to be bad after I implemented it (in production), although I asked the Lead for his opinion ahead of time. As soon as trouble came up a.k.a performance issue in production, he pointed the finger at me. Lost all kinds of respect for him.

In this episode, Dave and Jamison answer these questions:

1. I keep hearing about Web3, DAOs and Smart Contracts. Part of me wants to get excited about these and other shiny things but I just don’t seem to care all that much any more.

   How long into your careers did y’all stop getting excited about shiny stuff and how do you keep learning when it is not all that exciting to you any more?

   Maybe it is time to be a manager? 😛

2. Every work day seems to start the same way. I check slack, then procrastinate for about 2 hours before feeling so guilty about getting nothing done that i actually start doing some work. Once i get started i don’t have any issues concentrating.

   I want to work, i like my job but i also can’t crack this habit. I am assuming this is not normal…any ideas that could help me out?

   PS: I think (might not be true) i use to be better at getting started before the WFH was the norm

Article by Dave on how to make your standups awesome: https://blog.standuply.com/are-your-standups-awesome-91fb124033be

In this episode, Dave and Jamison answer these questions:

1. In the past couple of years I transitioned from a freelancer, to a full-time software engineer, to a product owner, to a manager of a small product development team. Due to the relatively rapid changes, I feel I have not had enough time to go particularly deep in my knowledge and experience with any of these roles.

   I’m currently focusing on developing the soft skills needed to be a better manager. I have this nagging feeling though that I should still be developing my technical skills. But in the grand scheme of things, is it still useful for a manager to continue to develop technically in order to provide useful input/guidance on technical decisions? Or would it be better to leave the technical decision-making to the team and instead focus purely on building up the team, supporting members in reaching their career goals, and improving processes? Thanks in advance for your thoughts!

2. Hi! Love the show and recommend it to everyone, even if they’re just asked for directions…

   I’m the Front End Lead at a fast growing startup. I really want to start delegating more, so I decided I’m going to appoint a front end tech lead on each of our teams. I already have my tech leads picked out, but…..

   My problem is with one of the teams. The person most fitting for the job is a very talented, yet very junior developer. This team also includes a very senior developer, which I believe is not fit for the job at all. But the senior developer is looking for a promotion.

   I’ve consulted with my managers and they think passing over the senior dev is basically forcing them out of the company (or at the least, making them a very disgruntled employee).

   Right now i’m holding back my decision just because of this. Please help me!

   Thanks :-)

• https://www.lesswrong.com/tag/paperclip-maximizer
• https://www.decisionproblem.com/paperclips/
• https://charity.wtf/2019/01/04/engineering-management-the-pendulum-or-the-ladder/
• https://charity.wtf/2017/05/11/the-engineer-manager-pendulum/

In this episode, Dave and Jamison answer these questions:

1. I started working at a new company last month. I’m just under senior level (I-II-III-Sr) and I am working on a project with someone slightly more junior, who started there a few months earlier, to help them complete a project on time.

   Despite my best efforts, I can’t get on the same page with them. They ignore half of my suggestions, don’t give me straight answers to my questions, take forever to review pull requests, and are making very little progress each day without reaching out for help. I am not certain what to do, but I’m worried I’ll leave a bad impression with my new manager (who is actually pretty reasonable, I’m just paranoid) by missing the deadline, which is in checks watch 1 week.

   Any suggestions? Should I quit my job? (leave that option off the table for now)

2. I hate my current job and cannot see myself working here for more than a few months. Is it better to find a new job before quitting? If I quit tomorrow with no offers from other companies, how does this affect salary negotiation for a new job while I’m currently unemployed? Finance-wise, I’m stable enough to not be working for months to a year but I am worried about not having current employment putting me at a disadvantage in my job search. Not working would definitely free up my time and energy (which is being steadily drained each day) to prepare for interviews.

   I recently got a raise and promotion to a senior role too. Does quitting shortly after look bad on a resume? I could coast for the next few months in my current job while I search for a new one but I feel like this would be in bad faith. It takes a long time to actually fire someone at my company for performance, even if I barely do any work.

   Thanks for reading my question. Love the show.

In this episode, Dave and Jamison answer these questions:

1. Listener Shayne asks,

   ‌

   I’m about to start a new gig after 8+ years at a company. I was an early employee at the current company and have accumulated a lot of responsibility, influence, and a fancy title.

   I’ll be an IC at my new company (also very early stage) but the most senior engineer second only to the CTO.

   What are some tips for this transition? How can I onboard well? How do I live up to my “seniorness” in the midst of learning a new code base, tech stack, and product sector?

   I managed to stay close to the code despite adding managerial responsibilities in my current role, so I’m not worried about the IC work. I really want to make sure that I gel with my new teammates, that I’m able to add valuable contributions ASAP, and that folks learn that they can rely on my judgement when making tradeoffs in the code or the product. Halp!

2. I got into software development to become a game developer. Once I became a software developer, I found out I really enjoyed the work. My wife and I joined a game jam (lasting 10 days) over the weekend. I very quickly have realized how passionate and excited I get about game development again! But this has led to a problem - I would much rather be doing that. I find myself moving buttons around or making another CRUD end point a means to an end now, thinking about how I much rather be creating exciting experiences. How can I handle this? Quitting my job to pursue a pipe dream just isn’t feasible.

In this episode, Dave and Jamison answer these questions:

1. Jealousy - as bad as it is, it still happens. I was the first employed programmer at a startup. Within the first year of my work there an colleague from my previous company I worked for asked me if it’s okay with me if he comes work for the same start-up as me. Since I strive to be a good person and friend I answered “yes”, but deep down I knew it is a bad idea and what I was thinking will happen, happened. So few years passed in the same company and my friend got promoted higher than me and into a position I wanted to move to eventually. The company is kind of small and there is no room for more positions like his (Tech Lead). So now I live with Jealousy. Each time I see his title I’m reminded of it and I don’t know what to do. I’m even thinking about just leaving the company and never work with friends again.

2. I have been doing software development for around 7 years now and in recent times I have lost the enthusiasm to write code at work. I mostly feel bored and tired. I have no other marketable skill and talking to people usually exhaust me, so moving into a management path is not an option. Honestly, I feel like, these days I am at work just for the money; I love the money, no complaints about it, and I want to make more of it. How can I still be relevant and valuable even if I am completely bored and waking up to work feels like a work in itself, these days? P.S: I have already tried quitting my job and that didn’t help. Now I am at my new job. Six months in and I feel bored already.

In this episode, Dave and Jamison answer these questions:

1. Listener Rafael asks,

   If you’ve already been working at a company for several months, how do you set boundaries with your employer as to when, time during the day, it’s acceptable for them to contact you? What can you say to your employer or colleagues if they expect you to respond to correspondence at all times, with a 30-min turn around? Can you adjust expectations after you’ve been working the role for several months, or is it too late?

2. Hi, Do you see any benefits to being a junior developer? Any advice you would give to a junior, like “Hey, do this while you’re still a junior, once you’re a senior+ it might be harder to do or find time for it”?

In this episode, Dave and Jamison answer these questions:

1. Zach asks,

   A few weeks ago, I interviewed and recommended we hire a contractor candidate, who I will call “Bob”. We hired “Bob”. Today was the first time I saw “Bob” since the interview, only “Bob” was not the person I interviewed. It seems “Bob” had someone else pretend to be him to pass the interview. What should I do?

2. Thank you for doing this show, it’s amazing and I look forward to listen to it every week. I’m a software engineer with 3.5 years of experience and in those years I’ve worked at 5 different companies consecutively, increasing my salary by around 50~70% every time I change jobs. At this point I’m afraid that it looks really bad in my resume since the longest that I’ve been at one company is 1 year and 3 months but at the same time it is really tempting to keep growing my salary and benefits that easily. Does changing jobs every ~1 year have a negative effect on my employability in the long run?