『Nerd Journey: Career Advice for the Technology Professional』のカバーアート

Nerd Journey: Career Advice for the Technology Professional

Nerd Journey: Career Advice for the Technology Professional

著者： John White | Nick Korte
無料で聴く

概要

 Are you a technology professional unsatisfied with your current role? Looking for a resource to help understand changing job functions, changing organizations, or gaining recognition and progression? The Nerd Journey podcast helps explore alternative roles, increase job satisfaction, and accelerate career progression. Each week, we uncover patterns of technical career progression by dissecting careers of guests and discussing different job roles they’ve held, or discussing relevant career topics. We’ve interviewed people in IT operations, sales engineering, technical marketing, product management, people management, network engineering, cybersecurity, software development, entrepreneurs, and more. We also discuss improving job satisfaction and accelerating career growth. We are John White and Nick Korte, two technologists with experience in IT operations and sales engineering who started this podcast in 2018. We release on Tuesdays, and can be found at https://nerd-journey.com. 個人的成功 出世 就職活動 経済学 自己啓発
エピソード
  • An Intentional Ending: Completing the Journey for This Body of Work

    An Intentional Ending: Completing the Journey for This Body of Work
    2026/01/27
    When does a body of work reach completion? One answer is to end it by choice. This week in episode 356 you’ll hear the reasons behind our intentional ending of the Nerd Journey Podcast. We’ll rewind the clock and focus on the show’s trajectory and inflection points over time just like we’ve done for guests, share what we learned over the course of an 8-year journey from idea to consistently released show, and discuss our favorite moments. All of our content will remain online and accessible for listeners like you to go back and enjoy. Don’t miss our final call to action in this episode. Just because this body of work is complete, there is still work for all of us to do for our careers. Original Recording Date: 12-20-2025 Topics – A Purposeful Ending, Where We Started, Interview Format and Getting to Launch, The Why Behind the Ending, The Lessons We Learned, Our Favorite Moments, What to Expect from Us Moving Forward, There’s More to Be Done for All of Us. 1:01 – A Purposeful Ending We’ll give you the bottom line up front: this is the last episode of the Nerd Journey podcast. We still love the mission, but the time has come for us to complete this body of work.When we have interviewed guests on the show, we’ve talked through their career timeline and pulled out the lessons learned. Today, we’re going to do it for the show itself. 1:38 – Where We Started John was working as a sales engineer at VMware and was the co-host of the VMware Community Roundtable Podcast. He loved listening to podcasts, enjoyed the medium, and wanted to find a topic for a show. At the same time Nick was in the process of joining VMware, John and Nick were discussing all the things Nick needed to know to transition into sales engineering for a technology vendor. “In that conversation, I said ‘maybe we should start a podcast.’” – John WhiteAs Nick remembers it, this happened the weekend before Nick started at VMware in December 2017 (almost exactly 8 years before this episode’s recording). Nick wasn’t sure what he would talk about on a podcast.This suggestion from John started the ideation period, and our launch of the show was in July 2018. John talks about some of the initial ideas for the focus of the show. At that time, VMware podcasts and blogs were a great way to interact with the greater community. Doing something like this was also a way to become what John calls “nerd famous.” By the way, no one else can use that term now (trademarked by John).We initially considered talking about VMware news and our opinions on it since we both were going to be working at VMware.Both John and Nick came from small-to-medium business IT operations and eventually became sales engineers at a technology vendor. One of the things the show could be for is to talk about that journey and help others understand it was a possibility for them as well.John and Nick recorded about 10 episodes before launching to help hit the release cadence.Nick doesn’t remember why they chose a weekly release cadence but remembers the show launched while he was on vacation. John and Nick even recorded a podcast episode while Nick was on that vacation, which started a habit of Nick doing podcast work while on vacation. Because they had recorded so many episodes in advance, they were not going to be timely or points of authority on VMware technology. Both Nick and John’s roles were as technical generalists on the VMware side. “The only evergreen stuff that we had was the career stuff, so that became a little bit more the focus. I think that we were still thinking…we’ll just record more maybe VMware specific stuff later on…as that happens. For right now, here it is.” – John White Early episodes were very prescriptive about resumes and job interview processes at larger tech companies, for example. Nick points out that John had to carry the conversation in these early episodes because he was just learning to think about career focused topics (sort of like being new to lifting weights). But, Nick picked up a lot just from the conversations on the show. 7:50 – Interview Format and Getting to Launch Nick couldn’t remember what made them bring in guests originally, but Episode 13 with Tom Delicati was our very first guest interview on the show. John feels bringing in guests was always back of mind for him, and it was what he saw happen on the VMware Community Roundtable Podcast.“We’re just 2 people and we have our experience. But we can’t represent that as the full breadth of all of experience. That just doesn’t make any sense. So, we need to start exploring what other people’s career journeys have looked like and see if we can extract some knowledge and recommendations from that.” – John WhiteNick doesn’t remember having a prescriptive plan for interviewing guests but feels like they settled into long-form interviews as a style pretty quickly.John says this was a structure they hit upon in the ...
    続きを読む 一部表示
    40 分
  • Mind the Gaps: Organizational Changes and Your Career Lifecycle with Ryan Conley

    Mind the Gaps: Organizational Changes and Your Career Lifecycle with Ryan Conley
    2026/01/13
    Has organizational change redefined your job role? If it hasn’t yet, it will at some point. Whether acknowledged or ignored, every organizational change at a company impacts you. This is broader than just layoffs and more employees under a single manager. What are the organizational changes we might see, and what can we do to stand out and stay the course? This week in episode 355 we’re joined by guest Ryan Conley. Listen closely as we uncover different patterns of organizational change and provide practical tips to take action when those changes happen. Ryan helps us understand the corporate lifecycle and how to reframe this concept to understand where we are in the career lifecycle. You’ll hear from Ryan’s personal experience why the most resilient (and successful) technologists can identify and fill the gaps left after an organizational change whether that means working for a new boss, joining a different team, or changing job roles. Original Recording Date: 11-13-2025 Topics – Framing Our Focus on Organizational Change, Observations and Patterns, Defining the Career Lifecycle, When Colleagues Leave the Company, Layoff Resources, Working for a New Boss, Becoming Part of a Different Team, Shifting Job Roles or Job Level Changes, Parting Thoughts 2:58 – Framing Our Focus on Organizational Change Ryan Conley is a global field principal with 11p years of technical pre-sales experience. Before this, Ryan accumulated 13 years of systems administration in industries like education, finance, and consulting.In a recent episode of our show, guest Milin Desai compared organizations to living, breathing organisms that change. Nick posits that we don’t always think changes at our company will or can affect us as employees, but they do. Ryan references Aswath Damodaran’s writings about organizational change through the frame of a corporate lifecycle. We can relate by considering where our company might be in that lifecycle.As we experience the impacts of organizational change, Ryan encourages us to consider where we are in our career lifecycle. 4:19 – Observations and Patterns We see organizational change in different ways. What are some of the things Ryan has seen that he would classify as organizational changes? Let’s take a step back, past the current headlines, and look at the wider industry.Companies are growing inorganically (through mergers and acquisitions) or organically through investments in R&D (research and development), for example.Ryan has worked with companies that grew by acquiring 2 new companies each year to give an example. When you’re on the IT side of the acquiring company, there is a lot involved in the process like integrating e-mail systems, networks, and CRM systems. This process also involves getting 2 teams to work together. If one team needs to move from Office 365 to Gmail, it can be a big adjustment to employees’ daily workflow.The acquiring and acquired companies may have the same or very different cultures. In some cases, a company will want to acquire others with similar cultures, while some may not be concerned about the culture and choose to focus on the intellectual property (products or services, knowledge of how to build or manufacture something, etc.) of the company to be acquired. Nick says the experience for people on the side of the acquiring company and that of the company getting acquired can be quite different. Nick worked in IT for a manufacturing company for about 9 years, and over the course of his time there saw the company acquire several other companies. Nick usually had to go assess technology systems of companies that were going to be acquired and figure out how to integrate the systems in a way that would best service the user base.From what Nick has seen, some employees from the acquired company were integrated into the acquiring company, while others were eventually no longer with the company. Anxiety levels about an acquisition may be different depending on whether you work for the acquiring company or the acquired company. “The people are just as much of the intellectual property of the company as, in many cases, the actual assets themselves. And in some cases, that culture just isn’t a fit.” – Ryan Conley Ryan shares the example of someone he knew who left after another company acquired their employer because the culture was not a fit. Losing a key leader or a key subject matter expert after an acquisition could create a retention problem because others may want to follow them or start looking elsewhere."So how do you protect the culture internally? How do you integrate a different culture in? But also, how do you kind of protect the long-term viability of the team as individuals, first and foremost, but then also the organization long-term?Depending on the intellectual property the acquiring company is after, we don’t usually know the level of due diligence completed to understand the key resources or subject matter ...
    続きを読む 一部表示
    1 時間 13 分
  • Layoff Bounce Back: Resilience through Personal and Professional Networks with Dave Stevens

    Layoff Bounce Back: Resilience through Personal and Professional Networks with Dave Stevens
    2025/12/23
    Imagine your work day starting off like any other only to find you’ve been laid off. What would you do next? Dave Stevens lived this reality a couple of years ago and joins us this week in episode 354 to share the lessons from that experience. We’ll take you through how Dave processed the news of being laid off, the warning signs he missed, when he knew it was time to begin searching for a new role, how he thought about what to do next, and the critical importance of his personal and professional network throughout this process. Regardless of your age or the size of your professional network, Dave shares actionable suggestions for building professional connections that we all may be overlooking. Original Recording Date: 10-28-2025 Topics – Background and the Impact of a Layoff Event, Initial Forward Progress and Reliance on a Professional Network, Skills Gaps and Unexpected Positives, Elements of the Personal and Professional Network, Reaching Closure and Reflecting Back on the Lessons 2:27 – Background and the Impact of a Layoff Event Dave Stevens is a Field Solutions Architect at Pure Storage. In this role, Dave is a technical overlay for pre-sales technical personnel at Pure across North America. This is the role Dave took after he was impacted by a layoff.What was Dave’s role before he was impacted by a layoff event? For context, the layoff event we discuss in this episode took place around 2.5 years before this recording.Dave was classified as a systems engineer or pre-sales technical resource at his employer supporting multiple account reps. It was more of a solutions architect type of role, and Dave highlights his entry into this organization and role was via acquisition.Was there an element of technical marketing to the role? Nick mentions that Dave often had to attend trade shows in this role. Dave had a virtualization background and went to a lot of events to discuss how his company’s products integrated with those different technology ecosystems. The day Dave was laid off started as a normal day at his home office. His boss was based in Europe, so most 1-1 calls were usually late in the day his boss’s time (early afternoon for Dave). A meeting popped up that was earlier than usual, but Dave didn’t think anything of it.Right after Dave joined the remote session for the meeting, someone from HR joined followed by Dave’s boss.Dave wasn’t quite sure what to expect and didn’t know what was happening. He didn’t know if it was a layoff coming or some other kind of situation happening at his company.When Dave was laid off, they told him it was not for performance reasons, but there weren’t really any other details provided on why he was being laid off.“So, at that point it was just like, ‘what do I do?’” – Dave Stevens, on receiving layoff newsAfter receiving the news, Dave’s access to company systems like e-mail was quickly cut off. He went downstairs and spent the rest of his day relaxing. Dave did not want to talk about what happened any further that first day. Did Dave struggle with separating his identity from his employer or the job he held at all when this happened? Dave says he did, at least a little bit.Dave wanted to be successful in whatever role he found himself, and the reason he was in the systems engineering role at the time of the layoff event is a result of his drive to be successful in the years leading up to that role.“I also wanted to make sure that…the people that I worked with that I enjoyed working with. If I didn’t enjoy working with them, then there was no reason to continue staying there. So that’s part of my identity on how I interact with work.” – Dave StevensIn the early days of Twitter (now X), Dave defined an identity there. He also created a personal blog. Dave says his identity was often tied to where he worked.“Once this all happened, I just kind of cut that off. And I needed some time to really digest what I just went through that day.” – Dave Stevens Is there something Dave wishes people had done for him when this first happened? Dave says he wishes he would have listened to his wife. Before experiencing the layoff event, a number of colleagues who had entered the company through acquisition like Dave were either leaving or had been laid off (including his boss being laid off). At the time, Dave didn’t think much about these events.Dave’s wife had encouraged him to look for other jobs before the layoff happened, and he feels he should have listened.“It’s much easier finding a job when you have a job. There’s not as much pressure on you. You can take your time and really find the job that you want. That’s the one thing that kind of took me by surprise….” – Dave Stevens Did Dave’s wife also point him in a direction or provide feedback on the type of work he should pursue? We’ve spoken to previous guests who had spouses that provided insight into the type of work that made them happy.Dave ...
    続きを読む 一部表示
    41 分
まだレビューはありません