In this episode, Dave and Jamison answer these questions:

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?

In this episode, Dave and Jamison answer these questions:

Questions

1. Starting to work on a team that is split across time zones. With a majority of the company based in one time zone and a handful spread in others. I want to emphasis the importance of asynchronous communication. I have found Slack to begin to feel like I need to respond ASAP instead of when it is convenient.

   If we were to say slack is used for asynchronous communication, is asking the team to use signal or even text appropriate for a quicker response?

   What is a good way to reach out to team members in cases where a response is needed more immediately?

2. After about 1 year at my developer job, I was moved to work for a client company helping them launch a new product. This other client had different plans, it turns out, and now I’m just testing their API for them. That’s fine but I never get questions answered and I hate my job with my client and hate my job with this company that sells me like a cheap piece of meat. I want to quit, I will quit, but I have a lot to say about why I’m quitting. How can I NOT be nice about quitting and the reasons I’m quitting, and still feel comfortable showing my face in the industry again?

   I haven’t quit a job before, and this is my first job in the tech industry. Searching how to quit a job always comes with “remain light and positive.

This is a rerun of episode 220.

In this episode, Dave and Jamison answer these questions:

Questions

1. Hello,

   I know you said you don’t read the compliments on air most of the time but this podcast is great. I just found it a few weeks ago and I love the positive fun approach to question answering. It has really made me think about software engineering outside of the ““make code do thing”” box.

   Anyway, the question: I have been at the same company for 4 years. It is my first job out of college. I have ended up working in so many different languages and frameworks I don’t remember them all. I guess that’s just how things go. Recently I have been selected to take on a scrum master role and I feel I am quickly being groomed for management.

   That was never really my goal. I wanted to build a depth of knowledge and always have my hands on code.

   Will taking on these kind of roles hurt my chances at future technical roles? Am I dooming myself to managing spreadsheets and Jira tickets until I retire? Will I only communicate in Dilbert references?

2. My teammate frequently gives status updates or fields follow up questions about work that was mostly done by someone else. I am pretty sure they do this to be helpful not to claim credit for all the work. I just wish I could speak up about the work I contributed primarily to before they do so on my behalf. I wish it didn’t bother me since we are one team and I would rather focus on the progress of the team rather than receiving credit.

   How should I respond to these situations in a way that allows me to not get bothered emotionally and also do what’s best for the team?