In this episode, Dave and Jamison answer these questions:

Questions

1. I have a question about ‘title inflation’, where you get promoted faster than your experience would normally suggest for that specific title. If I’ve been a ‘Senior Software Engineer’ for all of a year, and am now getting recruiting offers for Director and VP of Engineering jobs, is it worth interviewing and seeing where it goes? I don’t really see myself at that level, but I… might be able to level up to it quickly!

2. Should I take a remote work offer or find a new job in a new place? I am moving to another country with my husband in 2 months. I am the only frontend developer in the team and my company has been having difficulty hiring people, so my boss asked me if I could work for the company as a remote employee. I am reluctant to the offer because my plan has always been to find a new job so that I can blend in with the local community. Not to mention the 12-hour time difference and lack of new challenges. Sadly, I find it difficult to reject him and leave my colleagues behind. What is a better action to take?

In this episode, Dave and Jamison answer these questions:

Questions

1. I work for an all-remote company and I’m about to get promoted. The company says they target a salary increase of 5-10%. Assuming they come to me with an offer on the low-end (5-6%), what’s the best way to go about negotiating a higher raise during promotion? I want to stay at the company and also want the shiny new SENIOR job title, so I feel like I don’t have much leverage in this situation. Any advice is appreciated!

2. Rachel asks,

   Live coding makes me choke. As soon as someone else is watching, my brain immediately goes to mush and I’m like a chicken with my head cut off. Actually recently I learned it’s not just live coding – it extends to live spreadsheet-making and live cooking as well! I guess I’m not into performing? Anyway, this has come up because it’s impacting my career in real ways. For interviews I offer to do takehomes, which I’m great at, but sometimes I’m told live coding is the standard they apply to all applicants. What’s a non-live coder to do?

Show Notes

Consumer price index: https://www.bls.gov/news.release/cpi.nr0.htm

@Channel Twitter account: https://twitter.com/Channel

https://interviewing.io/

In this episode, Dave and Jamison answer these questions:

Questions

1. Should I change tech stacks every few years in order to not get pigeonholed?

   Is it a good idea to stick with a tech stack for as long as I can or should I follow the market trend and try to learn another promising tech and then try switching into that?

   Would you advise me to be more of a specialist or a generalist early in my career, and what about later when I’m more experienced? I’m a full-stack web developer who’s just starting out my first job (if that matters)

2. I love this show so much, I’m even trying your goto advice - quitting my job! But not untill I’ve got another lined up so shhh about it already. In the mean time, I work for a huge agency as a senior(ish) developer and have recently started work with a new team. However, they have issues: no one turns on their camera for video calls, which I’m ok with, but it makes the next bit worse somehow - most say the absolute minimum in response to any questions and offer no opionions / thoughts / ideas. It makes things like sprint retro meetings very awkward. We have a scrum master running our meetings who is clearly struggling to engage the team, I try to hold off to let any of the others answer questions but I always seem to end up picking up the slack. I’ve even started timing how long I’ll let the slience endure before jumping in to answer, I’m now waiting 15 seconds. Have you come accross this before? How can I get people to engage more?