Reskilling non-tech employees for tech roles: Tips for getting started

This photo shows a yellow road sign against a blue sky. The sign says, "New Job Just Ahead." That's a key message when reskilling non-tech employees for tech roles. The learning curve is steep, but in just a few weeks, participants can pivot to a new role.

You’re contemplating something radical: reskilling non-tech employees to fill software and IT positions. But where do you begin? How do you prepare a cashier, customer service representative or claim processor to contribute on a software development team?

Don Jones, Head of Developer Skills at Pluralsight, and DevelopIntelligence VP Jessica Schneider unpacked this topic in a recent webinar. Reskilling non-tech employees can “seem a little daunting,” said Schneider. These individuals do not have computer science degrees or foundational knowledge in coding. They are changing careers completely, embarking on a brave new journey.

The planning effort for a reskilling endeavor like this “involves multiple stakeholders across many departments and is packed with moving pieces,” she noted. As a starting point, Scheider recommended this three-step foundation:

1. Begin with the end in mind

Think ahead to the end of the reskilling program—when graduates step into their new tech roles. What specific tasks will they need to be able to accomplish on their own? What will their team and manager expect them to know and do? What project will they be working on? Will they be fixing bugs? Building feature enhancements?

Getting precise, detailed answers to these questions is similar to the requirements phase of a software development project. Before you build software, you carefully articulate what the software needs to do.

Once you’ve defined the end goal for your reskilling endeavor, it’s easier to determine what technologies to cover in your program and at what depth. From there, you can begin making decisions about program length, structure and content.

2. Decide how you will select participants

Finding candidates who are both interested in a coding career and well-suited for it can be the most challenging part of a reskilling endeavor. You’ll need a recruitment strategy before you can establish a timeline for your training program.

Start with the graduate in mind. The teams who will receive these reskilling graduates can help you define the attributes and skills needed for success.

Before you can start recruiting, you need to know where the graduates will land. Applicants will want a clear picture of what they’ll be doing afterwards if they take part in the reskilling program. They need to be able to weigh the pros and cons. The more specifics you can provide about what happens after the program, the more comfortable employees will feel when deciding whether to apply.

Where are you going to find these employees? If they are coming from an internal department, what’s your strategy for getting buy-in from managers who may be reluctant to let a star performer transfer into your reskilling program? What’s your plan for filling positions left vacant by reskilling participants?

How are you going to evaluate reskilling applicants? Which candidates are likely to thrive—or at least persevere—as they climb the steep learning curve of a reskilling program?

3. Identify and engage champions

“The step that might be overlooked the most is to recruit champions within the business to support you in this initiative,” said Schneider. The ideal champion is passionate about the reskilling vision. Champions help with brainstorming, decision making and removing barriers as you move through the planning and implementation journey.

“Get support early and keep your champions engaged. They can help with internal communication, recruit mentors to support students through the program and collaborate on curriculum.”

Closing thought: Programs for reskilling non-tech employees are multi-layered

With these three elements in place—program requirements, recruiting strategy and champions—organizations can proceed with designing the actual reskilling program.

Schneider called these “multi-layer programs,” because they involve more than just technical training. In addition to building technical know-how specific to the jobs they’re destined for, participants must learn how to think like programmers.

“If you’re a cashier or work in a call center, your day-to-day interactions and the way you work is different from the way developers work on a development team,” explained Schneider. Effective reskilling programs model how to approach and solve problems, research issues, collaborate on a software team and more.

For organizations interested in reskilling non-tech employees, it’s important to have realistic expectations. “You’re not trying to create experts by the end of the program,” said Schneider. “You are preparing entry level developers. So, you want to give them the skills that they need to get started, and then the confidence they need to be successful and to continue to grow those skills as they move into their jobs.”

For more information on reskilling non-tech employees for tech roles, email

Image credit:

More to explore…

Tech onboarding best practices have shifted a bit since the start of the pandemic. This photo shows a young Black woman at her laptop, taking part in virtual onboarding.

Effective onboarding programs for software developers and IT professionals have eight key elements. Here’s a summary of tech onboarding best practices.

In this photo, two developers sit together with their backs to the viewer. One appears to be "driving" while the other observes. "Heroes" jump in to fix other's work. Both heroes and code hoarders damage team morale.

Pluralsight developer advocate Jeremy Morgan discussed code hoarders and heroes with DevelopIntelligence CEO Kelby Zorgdrager. Here are three takeaways.