Episode 260: Pay cut after hired and new job ramp-up

In this episode, Dave and Jamison answer these questions:

Questions

1. Hey guys! I’m a long-time listener and like many of your other listeners have listened to each episode!

   Until now I didn’t have anything to ask, however, I have a story to tell and I was hoping for your opinions on this. Someone I know is a somewhat junior dev, they left their first job for a new job that had better pay. They were pretty good at negotiating a good salary, while still being transparent about their work history. But a few months ago management said they were underperforming compared to other coworkers and their pay would have to be cut. At first, they said at most it would be 10%. However, it ended up being 23%, which way less than even their prior job. Needless to say, they’re taking the softskills option and looking for a new job. My question is how commonly does this happen, and what are some telltale signs that this could potentially happen? Thanks for your time and a have great week!

2. I’m 8 years into a career in software engineering and I just accepted a senior engineering position at a well respected tech company in Silicon Valley. While I believe I am qualified for the position, it will be a big step up for me in terms of the caliber of engineers I’ll be working with as well as the overall scale of the system compared to my previous jobs. The standards of engineering and general productivity will likely be higher than I am used to, though I’m excited to level up. I’m not looking for advice about my specific situation, but I’m curious: what are your guys’ priorities during your first days, weeks or months at a new but senior-level job, to ensure you hit the ground running and set yourself up for a successful tenure at the company? Anything you used to do that you don’t anymore? Any common mistakes you see engineers make when they join new teams?

Episode source