Episode 448: Title over salary and from figure skater to software developer
Feb 17, 2025
auto_awesome
The hosts dive into the age-old dilemma of prioritizing job title over salary, discussing how that decision impacts long-term career growth. They explore the quirks of transitioning careers, highlighting a listener's journey from aircraft mechanic to Disney performer to environmental management. Their humorous take on tech frustrations, like Linux users and Microsoft Teams, adds lightness. The importance of cultivating skills over mere hours worked is stressed, emphasizing practical experience and learning from mistakes. Unique career paths can truly set professionals apart!
When considering job offers, weigh the long-term career benefits of a prestigious title against immediate financial impacts, as titles can vary significantly in value.
Candidates with diverse backgrounds should emphasize their unique experiences and transferable skills to demonstrate adaptability and resilience during job interviews.
Deep dives
The Illusion of AI Enhancements
Adding superficial features, such as a sparkle icon to indicate AI integration in apps, does not equate to real improvements in functionality or code quality. This tactic allows developers to deflect attention from bugs and inefficiencies by falsely attributing issues to the AI component, highlighting the trend of over-relying on AI to mask shortcomings. The discussion emphasizes that this approach can create a false sense of accomplishment and may lead to a lack of accountability when problems arise, as developers may blame AI for errors that stem from their own code. Thus, understanding the actual capabilities and limitations of AI is crucial for responsible software engineering.
Navigating Career Choices: Title vs. Salary
When faced with a choice between accepting a lower-paying position with a more prestigious title versus maintaining a well-paying job with limited prospects for advancement, a careful evaluation of long-term career goals is essential. The conversation highlights the importance of considering how a staff engineer title might open doors in the future, but cautions against making this decision purely based on title accumulation. Financial implications over the years can outweigh the perceived benefits of a title if it comes with a significant pay cut. It underscores that titles can vary widely in meaning between companies, suggesting that this decision should not be taken lightly.
Leveraging Unique Backgrounds in Job Interviews
Candidates with non-traditional career paths, such as those with diverse experiences in fields like mechanics and figure skating, should highlight their unique backgrounds to stand out during job interviews. These experiences can showcase adaptability, resilience, and the ability to learn quickly, vital traits for software engineering roles. It is important to articulate a willingness to embrace new challenges and a commitment to lifelong learning, which can alleviate concerns about a non-linear career trajectory. Additionally, demonstrating transferable skills, such as technical writing abilities, can further enhance a candidate’s appeal to potential employers.
In this episode, Dave and Jamison answer these questions:
A listener named Steven says,
Long-time listener of the podcast here—it always brings me so much joy!
Should I prioritize title over salary?
I’m currently based in Europe, working as a Senior Engineer at a big company that pays really well. The problem is, there’s almost no chance for promotion due to the economy and budget constraints. Plus, because of the organizational structure, I’m stuck solving small problems that don’t have a big impact. It’s frustrating—but again, the pay is great.
Recently, I got an offer for a Staff Engineer position at another company. The catch is, the pay isn’t as good (30%+ cut), and I’m not sure about their culture or structure yet. However, the title could potentially open more doors for me in the future.
Should I take the offer, accept the pay cut, and hope it’s a step forward for my career?
Hello! Long time listener, first-time caller :-) I’m on the final stretch of classes to finish my BS in computer science at WGU, most of which I’ve done while working. I’m now 40, and I have had 3 previous occupations and employers: aircraft mechanic for 5 years at a small shop, figure skater with Disney on Ice for 6 years, and most recently a partner at an environmental remediation/heavy construction firm for 10 years where my primary responsibilities were field crew management and technical writing for ecology reports. I would love your advice on how I could use these experiences to stand out on a resume or in a job interview. How can I indicate that I’m a hard worker and that I know just enough to know that I know nothing and am ready to learn? Thank you for your time, keep up the good work!
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