Episode 419: Yoda or Han Solo and I swear I'm senior
Jul 29, 2024
auto_awesome
Navigating career dilemmas can feel like choosing between Yoda and Han Solo. A listener grapples with conflicting job offers from old coworkers, sparking discussions on balancing friendships with career ambitions. The hosts share strategies for declining offers while maintaining relationships. They also dive into what it takes to be recognized as a senior software engineer, discussing the importance of communication and showcasing achievements in the competitive tech world. Finally, they highlight the need for aligning project goals with tangible business impacts.
When faced with job offers from former coworkers, it's crucial to explore all options while maintaining clear communication to avoid misunderstandings.
To establish oneself as a senior software engineer, candidates should highlight their influence, achievements, and leadership in past roles during interviews.
Deep dives
Navigating Job Offers from Friends
Receiving job offers from two former coworkers can present a unique dilemma, especially if there's a concern about disappointing one of them. It's important to recognize that if both parties are offering opportunities, it's entirely reasonable to explore both options without feeling obligated to commit prematurely. Communication is key; expressing gratitude for each opportunity while clearly stating the decision-making process can alleviate potential feelings of betrayal. Ultimately, pursuing the role that best fits personal and professional goals is the priority, and friends should understand this as part of the competitive job market.
Establishing Seniority in Software Engineering
Transitioning roles in software engineering often comes with the risk of being misclassified in terms of seniority, but there are strategies to mitigate this. Candidates can emphasize their extensive experience during the interview process to position themselves assertively for senior-level roles. Applicants should aim to showcase tangible achievements and responsibilities that clearly demonstrate their capabilities as a senior developer. Communicating the scope and impact of past work, particularly in terms of team leadership and business outcomes, can help reinforce their qualifications.
Influencing Perception of Career Level
To convince potential employers of higher seniority status, candidates should focus on articulating their scope of influence and the significance of their contributions. Experiences that involve mentoring others, defining complex projects, or leading initiatives that drove substantial business value will position candidates as higher-level engineers. Additionally, understanding the varying interpretations of titles across different companies can inform candidates on how to navigate these discussions. By presenting compelling narratives of past successes and the impacts made, candidates can better align themselves with the expectations associated with senior or staff engineer roles.
In this episode, Dave and Jamison answer these questions:
Listener Anakin asks,
I have two former co-workers that work at great companies where I would love to work. I reached out to one looking for advice and while talking to him, he said I should join him and he offered to give me a referral. At the same time, unprompted, another old coworker reached out to me asking if I am interested in joining them. It’s like being asked to choose between training with Yoda or flying with Han Solo on the Millennium Falcon (Sorry, James)!
But I have a big worry: what if by some miracle I get offers from both places? I don’t feel I can turn down an offer after my old coworkers vouched for me. I don’t want my friends to feel like I led them on. At the same time, I don’t think I’m close enough to either to say I want to interview, but I’m also applying somewhere else.
So I’m thinking of applying to one, and if that doesn’t go well, applying to the other. Is there a better way to go about this? How would you approach this dilemma?
Listener D says,
I asked a question in an episode around number 110. I asked if I should switch my job, as I had just moved to another country and, after half a year, the new CTO wanted to change the tech stack. You suggested staying for a while to see what happens, so I did. It worked out well.
On to the question! How can I be treated as a senior software engineer in my next job? When I moved the first time, I was downgraded to a mid-level developer, even though I had about seven years of experience. I did my job well, exceeded expectations, and got a promotion after four years. After working there for 4.5 years (half a year as a senior), I moved again to another EU country and was hired as a mid-level developer again! Now, after one year, I got promoted to Senior Dev, but I am afraid that the next employer could treat me as a mid-level dev. I understand that grades are different in different companies, but mid-level developers have lower salaries. How can I assure my next employer that I am a senior or even higher-level developer?
Get the Snipd podcast app
Unlock the knowledge in podcasts with the podcast player of the future.
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode
Save any moment
Hear something you like? Tap your headphones to save it with AI-generated key takeaways
Share & Export
Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode