In this episode, Dave and Jamison answer these questions:

1. “I’m into my second job of leading a team of software engineers and want to level up my coaching skills. In my first role I accidentally fell into the deep end of management “fun” by taking on a team of 10 people. One of the big problems I faced was being the “go to” or “sign off” person for a lot of different things, and I perpetuated this problem by showering people with my incredible answers (based on my obviously incredible know-it-all-ness) and thus reinforcing my goto factor. I was aware of coaching as a concept then, but didn’t incorporate it into my leadership style, which I believe contributed to my eventual burn out in the role.

   Over the last year in my current team lead role I’ve been much more deliberate about various aspects of leadership, but my coaching prowess is still struggling. When I’m asked questions by my team, my default response is to jump to a specific answer based on my own opinion, and it’s only afterwards that I slap my forward and yell out “missed coaching opportunity!” (as people near me back away slowly with concerned looks on their faces).

   What are some effective techniques to try and build a habit of using coaching as a primary means to help my team work through problems?

2. I just became a technical lead for a team at my company. I’ve never held a leadership role like this before. Do you have any advice for how to do a good job?

In this episode, Dave and Jamison answer these questions:

1. Hello! Love the show ❤️

   I’m 6 months into my career as a software engineer at a very large company.

   As a new engineer, I’m often lost and confused, especially since my team is working on a green field project. My mentor is very helpful and patient with me despite all of my questions. I’ve thanked him countless times and publicly called out his support at standup and in front of management basically everyday. But I still feel like this isn’t enough. He’d never say it, but I know I’m such a burden to him and slow down the team.

   Other than quitting my job to alleviate him from my near-constant “Please help” messages, how can I:

   1) show him how much his support has meant to me and get him the recognition he deserves

   2) stop being such a drain on his productivity/life

   Thank you!!

2. I’m a Senior Software Engineer, and I played the salary game with a recently promoted Mid-Level engineer on my team, who, in a gross violation of the rules, not only volunteered his own salary, but one of another Mid-Level engineer. In retrospect he was a bad one to play the game with.

   Anyway, it turns out they’re both really close to me now, and are both making a good deal more than I was 5 years ago when I was promoted to Senior. This is mostly (maybe entirely) because I was a horrid negotiator when I first started at the company. It was my first ““real”” job, and it turns out I really lowballed the company during salary negotiations. I’m pretty ready to leave the company (for reasons both personal and professional), but I’ve submitted a talk proposal for an industry conference that takes place 6 months from now. In order to give the talk I’d need to still be employed by the company, so rather than ordering the Soft Skills Engineering Special and quitting my job, I’m going to give it a shot and ask for a 25% raise.

   My question is what advice do you have for this conversation? I’ve read all the usual ““state your value, don’t make it personal, etc”” stuff, but do you guys have anything else that’s been effective in your experience on either side of this?

In this episode, Dave and Jamison answer these questions:

1. I’m a Full Stack Developer. I feel undervalued at my current job and I am looking at other opportunities. Many recruiters approach me on LinkedIn with contract-to-hire positions. Usually this means the benefits are not as good as direct hire positions and that the company can just dispose of me when the contract is done (after 6 or 12 months, generally). Salaries seem to be higher when contracting, though. Have you ever worked as a contractor for a large company? Would you recommend it? How likely is it that companies use this type of employment as a way to temporarily hire somebody for a specific project and then get rid of them once it’s done? What signs should I look for to avoid such companies? Does contracting actually make a difference? I live in Oregon, where employment is at-will anyway, so I can get fired at any time without any warning.

2. Hello, I’m a mechanical engineer from Brazil. I really love your podcast. As a mechanical engineer I don’t develop software but I believe the soft skills are important to everyone. I work in an American multinational company and I often talk or send e-mails to the engineers there. However, our culture is different so I don’t know how to behave or how straightforward, informal or political I must be. I’m always afraid of offending someone. What kind of things I never should say or do when dealing with Americans? We Brazilians become friendly and intimate very fast. Do you guys notice these kind of different behavior from different cultures?