Episode 445: Staying at my first job and my coworker is insulting other departments
Jan 27, 2025
auto_awesome
The hosts humorously dive into the quirky world of software engineering, sharing personal anecdotes along the way. They discuss the delicate balance between job satisfaction and career ambition, especially for those still in their first position after several years. The conversation touches on the 'secretary problem' and how it impacts decision-making. Listeners are provided insight into handling challenging coworker dynamics and managing workplace conflicts while maintaining professionalism. They also mix in some lighthearted math to explore job offers.
Staying at a first job for too long can hinder growth and skills development, despite initial comfort and job satisfaction.
Navigating workplace tensions and project challenges requires open communication and constructive discussions to ensure career longevity and project success.
Deep dives
Navigating Early Career Choices
Staying at the first job for an extended period may limit a software engineer's growth and opportunities. The discussion highlights that while longevity can indicate comfort, it may also result in missed opportunities for skill development and salary increases. The concept of the 'secretary problem' is introduced, suggesting that not seeking out new job opportunities may cause individuals to settle for less than ideal situations. Ultimately, while there are benefits to job hopping, engineers should carefully evaluate their current position before making decisions.
Assessing Project Viability and Team Dynamics
The challenges of attempting to pivot a failing project are explored, particularly when there is tension among departments involved. The scenario involves a tech lead trying to guide a teammate away from using aggressive tactics that could harm both their reputation and the project's future. It's suggested that the project appears doomed due to poor funding and disinterest from key departments, and that a constructive conversation about redirecting efforts may be necessary. The importance of having open discussions about project viability and team dynamics is emphasized as crucial for long-term career health.
Employee Satisfaction and Job Security
Employee satisfaction can significantly influence job security and career decisions, especially for individuals working in challenging environments. The message reinforces that despite frustrations, job satisfaction can lead to positive professional experiences. Engineers are encouraged to evaluate their current skills and potential opportunities instead of hastily seeking change due to external pressures. A balance between personal development and career satisfaction can help navigate difficult workplace dynamics.
In this episode, Dave and Jamison answer these questions:
A listener named Kevin asks,
Hey, found the show and really enjoy it! Been listening from the beginning and have noticed that one of the pieces of advice given is that you should not stay at your first job for too long, because it’s more likely that you’ve not found the best job for you. I think The Secretary Problem is the closest thing being cited.
I tend to agree with the math, but I’m still at my first software engineering job after 5 years and don’t really want to leave. There are obviously things I don’t particularly like or people I find challenging, but for the most part, I work on interesting projects with smart people, it’s fully remote, the benefits are great, and my salary is comfortable. There have been times where I started to look for another job, only to have my current circumstances improve enough that I stopped the search.
What advice do you have for someone like me?
I don’t know if it’s relevant, but I’ve managed to get married, buy a house, and just recently had our first baby. The pressure to provide and be conservative with my career is building.
Again, love the show and I hope you’ll get to answering this before I catch up. I started from the beginning in late 2024, and in mid Jan 2025, I’m just past episode 50. I’ll let you do the math.
As a tech lead, I joined a project two years in the making which had only one engineer doing everything, including management. In the two years, only a POC has been completed and a “pre MVP-MVP” build is in progress. There is a hangup though, the funding for the project is supposed to come from another departments budget that doesn’t want it, and work was committed by the department I am in, and a third department intended to be completed by the end of the quarter.
I have been trying to finesse my teammate into cancelling the project or at least allow a resetting of expectations. My manager agrees with me. There seems to be a tug of war between AVPs and Directors. This has led my teammate to make some corporate aggressive comments. These are being directed in many directions, including department heads opposing the project.
In your professional space experience, how can I help my teammate with understanding that his tactics are potentially damaging to his reputation and the project?
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