Episode 122: Too Much Process and Negotiating Salaries with Multiple Companies
In this episode, Dave and Jamison answer these questions:
Is it just me or does systems like Jira and TFS get managers to go crazy on processes? We have TFS and management has created a convoluted mess of processes that takes forever to learn and gets changed on a whim to be replaced by an even more convoluted process. Every time I finish a large feature and need to merge it in, I have to run around asking ten people on what process changed since there are all sorts of permission denied and other strange error messages. In my previous job, same with Jira and Jenkins. As an engineer, do managers really need these crazy processes that get in the way or am I naive engineer who doesn’t really understand the value of these processes?
Just wanted to preface by saying that I absolutely love your podcast. It’s definitely helped me mold into a better developer and team player!
My company is having a tough time raising our next round. In light of this, I am actively looking for my next position. Financial stability and growth is my biggest concern as I am planning to get married, buy our own place, and have kids. My goal is to interview at multiple companies and get competing offers. From a hiring perspective, I can definitely see how companies and see this in a negative light. How do I navigate salary negotiations so that I can get the best deal (financially) without being stereotyped?