Nerd Journey: Career Advice for the Technology Professional Podcast Por John White | Nick Korte arte de portada

Nerd Journey: Career Advice for the Technology Professional

Nerd Journey: Career Advice for the Technology Professional

De: John White | Nick Korte
Escúchala gratis

OFERTA POR TIEMPO LIMITADO | Obtén 3 meses por US$0.99 al mes

$14.95/mes despues- se aplican términos.
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. Desarrollo Personal Economía Exito Profesional Éxito Personal
Episodios
  • Mind the Gaps: Organizational Changes and Your Career Lifecycle with Ryan Conley

    Mind the Gaps: Organizational Changes and Your Career Lifecycle with Ryan Conley
    Jan 13 2026
    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 ...
    Más Menos
    1 h y 13 m
  • Layoff Bounce Back: Resilience through Personal and Professional Networks with Dave Stevens

    Layoff Bounce Back: Resilience through Personal and Professional Networks with Dave Stevens
    Dec 23 2025
    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 ...
    Más Menos
    41 m
  • Translating Experience: Clarity from Leadership in the People Industry with Christy Honeycutt (2/2)

    Translating Experience: Clarity from Leadership in the People Industry with Christy Honeycutt (2/2)
    Dec 2 2025
    How can we help recruiters advocate for us in a tough job market? According to people industry veteran Christy Honeycutt, our guest in episode 353, it starts with being kind and translating your experience into something a recruiter can understand. And even more importantly, it takes practice. In part 2 of our discussion with Christy, she translates deep experience in talent acquisition and recruitment that gives us insight into the current job market. You’ll hear more details about the nuances of RPOs (recruitment process outsourcers), the difference between job hugging and job abandonment, and the importance of personal branding and differentiation. Stay until the end when Christy shares her reasons for turning down C-suite positions and how clarity on her long-term goals is carrying her forward into what’s next. Now that you’ve heard someone model it for you, how will you translate your own experience? If you missed part 1 of our discussion with Christy, check out Episode 352 – People First: Systematizing Go-to-Market for Your Role with Christy Honeycutt (1/2). Original Recording Date: 09-30-2025 Topics – A Deeper Look at Recruitment Process Outsourcing (RPO), Translating Your Experience with 3 Wins, Bad Actors and Leadership in the People Industry, Today’s Job Market and Life Outside the C-Suite 2:56 – A Deeper Look at Recruitment Process Outsourcing (RPO) When it comes to RPO (recruitment process outsourcing), is this a one-size-fits-all approach, or does it show up differently depending on what a company needs? In Christy’s experience, most RPO organizations offer services like executive search, but they may offer full RPO, which usually involves hiring more than 500 people per year.Normally an RPO brings a mix of skills to the table. A client may want the RPO to take only talent acquisition or may want to control offer management, but they may want the RPO to take everything (attracting new talent, offer management, coordinating with HR for new employee onboarding). “If a company wants it a certain way, they can stop it at a certain point…. But most RPOs, full RPOs, is attraction to offer accepted and then it tees over to the HR team.” – Christy Honeycutt John has worked for companies where the recruitment or talent acquisition personnel were marked as contractors in the internal global address book but had company e-mail addresses. Would this mean the personnel are contracting directly with a company or working through an RPO? Christy says it could be either scenario. When she managed an RPO earlier in her career, they were most successful when the client encouraged the RPO to brand as the company.Someone might indicate they do recruitment for a specific company on LinkedIn but be an employee of an RPO.Christy tells us how important it is for the RPO to understand an organization’s mission, vision, benefits, and culture because the RPO is often attracting talent and selling people on why they should apply and interview.“When you think about recruitment and talent acquisition, regardless, it’s a lot of marketing because you’ve got a really cool position and you’ve got to find the perfect fit.” – Christy Honeycutt 5:55 – Translating Your Experience with 3 Wins Right now, recruiters and talent acquisition professionals have a distinct challenge. Many resumes look the same because candidates are using AI tools. “What people think is helping set them apart is actually making them look more similar. So now you’ve got recruiters and talent acquisition; they don’t know if these are fake resumes. They don’t know if they’re real. And they’re getting on the call with these people and finding out they are fake; they don’t have any of this requirement.” – Christy Honeycutt Christy shares a little secret about learning recruitment. She gives the example of a recruiter needing to recruit for an executive level role in technology. Recruiters are encouraged to seek out and find the C-players to practice asking them questions, understand nuance, and grasp the terminology. This is a training exercise.Following this process, a recruiter would then have more credibility once they speak to the A-players they actually want to hire.“What I would encourage is if you are a C-player, you’re not going to know it. Just be kind and know that the person you’re talking to has never held a technical role (probably, most likely)…and might not understand half the stuff that you guys do. The acronyms aren’t going to be the same. Just be gracious with them because the more you can help them translate your experience, the better you’re going to be positioned to get you over the line…. They don’t want to talk to 10 people to get 1 hire. They want to talk to 3 people to get a hire…. And remember that the TA, HR, recruiters, whatever you want to call them…there’s a pretty good chance that they want to help you and that they’re doing the job because ...
    Más Menos
    39 m
Todavía no hay opiniones