Dive into workplace woes and hilarious tech anxieties! A listener grapples with a non-collaborative architect undermining their expertise, prompting tips on maintaining professionalism. Ever feel like you have too many bosses? One principal developer shares the chaos of juggling countless urgent requests while struggling with unclear expectations. Discover how to navigate tricky team dynamics and set boundaries while fostering effective communication. Expect laughter mixed with practical advice for unique professional challenges!

In this episode, Dave and Jamison answer these questions: I struggle with behavioral interviews. I’ve gotten a little bit better as I’ve done more interviews, but it’s still a major pain point for me. I have some common behavioral question answers written out in a spreadsheet in SAR format, but I feel that not all of them are good examples for a mid-level developer. The main problem is that I can’t remember in detail all the things I’ve done at work in the past few years. For example, I can think of one time I had a small conflict with a coworker, but I can’t remember the details of what happened. I have a work diary of sorts, but unfortunately, I haven’t been regularly writing things down. Also, I usually just write down accomplishments and notable things that happened. Should I start writing down experiences that match up with these types of behavioral questions?? Do you have any advice on how I can jog my memory and reflect on all the things I’ve done during my career to craft good answers to behavioral questions? I also freeze up when I’m asked a “tell me about a time when…” question that I’ve never experienced. I’ve heard advice like “come up with a hypothetical scenario and explain what you would do” or “just lie and make up a story”. I’m the type of person who has a very hard time lying and making stuff up on the fly. I am one year into being promoted to a team lead at my company. We are made up of 4 devs, 2 QA, and a product owner. One challenge for our team has been differing time zones. Our 2 QA engineers are east coast while the rest of the team is on the west coast. Currently one of them signs off at 5pm EST and the other at 4pm EST. This means that if there’s any communication that needs to happen between dev and QA it has to happen in the morning since by 1pm PST they are headed out the door. This also constrains the times that I’m able to schedule meetings that involve QA. I’ve been thinking for awhile establishing a set of core hours from 9am-2pm PST but have been afraid of the pushback from our QA. I feel like making this adjustment is reasonable and other people I’ve asked have echoed that sentiment but my desire to people please and be looked at favorably is preventing me from making a change. In all honesty we can get by with the current set up, but I find myself getting bitter about not being able to schedule meetings in the afternoon and stories getting held up because QA is off the clock so early. What do?

A listener grapples with whether to notify a former tech lead about a recurring bug after leaving their team, raising questions about boundaries in professional relationships. The hosts discuss the importance of theory building and the art of effective communication in software development. They also explore the challenges of defining personal leadership styles during interviews, encouraging self-reflection to articulate one’s unique approach. Along the way, they highlight the role of constructive feedback in maintaining positive developer-tech lead dynamics.

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!

The hosts dive into the challenges of transitioning from startups to senior roles in major tech companies. They discuss the shift from individual contributions to leading projects and the intricacies of understanding corporate expectations. A listener's experience with commenting on draft pull requests sparks a lively debate about workplace feedback culture. The conversation highlights the balance between giving constructive feedback and maintaining team dynamics, peppered with humor about common code review pitfalls.

The hosts dive into the murky waters of AI-driven hiring, offering tips for managers to sift through the chaos of AI-generated resumes. They tackle the struggle of developers underutilizing Git, highlighting the importance of regular code commits and effective version control. The discussion includes how to persuade teams to adopt better source control practices, emphasizing the need for leadership support and peer encouragement. With humor peppered throughout, they navigate the complexities of technology adoption in software development and the generational shifts affecting coding practices.

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.

Frustrated with apathetic coworkers and legacy company cultures? Discover strategies for finding a vibrant team that aligns with your product-thinking passion. The discussion shifts to accurately reflecting technical skills on resumes, tackling the thin line between confidence and exaggeration. Learn about the impact of AI on job hunting and the need for concrete examples of proficiency. Plus, explore the common disconnect between self-assessed skills and reality in the competitive tech market.

Dive into the complexities of workplace dynamics as the hosts tackle feelings of being undervalued by a Product Manager who seems warm to others but cold to one team member. They also explore how to support junior engineers battling anxiety during mentoring sessions, emphasizing the importance of open communication and building trust. With a blend of humor and insight, they discuss personal biases, public recognition, and strategies to foster healthier collaborations in the workplace.

Discover how to enhance your communication skills while juggling computer science courses. The hosts dive into the art of clarity and effective messaging, sharing personal anecdotes along the way. Learn about the challenges of job hopping and the quest for satisfaction versus career advancement. They explore strategies to overcome the 'grass is greener' syndrome and emphasize the importance of finding fulfillment in your current role. Get ready for a blend of humor, insights, and practical advice!