Authored by Jo Callaghan, UK Technology Director
When I tell people I've spent the last decade helping professionals transition into technology careers, they often assume I have a background in technology myself. My own journey into this sector has shown me there are opportunities for everyone. Like many candidates I now work with, I discovered and learned the skills I needed to succeed, as I progressed my career.
When I look back to eighteen years ago, when I decided to try recruitment, I found myself drawn to the tech space. Not because I was a programmer (I wasn't), but because I recognised what the industry was missing: an understanding that great tech professionals don't all come from computer science degrees. Some of the most innovative thinkers I've met started as teachers, project managers, designers, or admin. You just need determination, consistency and a clear vision of where you want to get to.
The great Tech talent myth
The biggest misconception I encounter is that you need to be "technical" to work in technology, having lots of similar experience. Supporting the growth of Gravitas' technology niches, I've placed marketing managers into cybersecurity roles, ex-teachers into developer positions, and managers from many different sectors into product management. What they had in common wasn't coding ability - it was problem-solving skills, resilience and the ability to learn quickly.
Sarah, a Project Manager for a marketing agency, decided to work towards a change of career. By upskilling in her spare time, she eventually landed a role as Technical Product Manager at a Fintech startup. Her experience consisted of coordinating complex builds, managing stakeholder expectations and working to tight deadlines, transferable from her time in agency.
Where to start: It's not where you think
The advice I give every career changer might surprise you: don't start with coding. Start with understanding the business of technology and AI. It’s no secret that AI is already transforming the workplace in many different industries.
The professionals who transition most successfully first understand how technology solves business problems. They learn the language, APIs, user stories, sprint planning, technical debt - before diving into syntax and frameworks.
Here's what I recommend:
Step 1: Industry Immersion: Read TechCrunch, follow technology leaders on LinkedIn, join relevant Slack communities. You're developing tech fluency. When someone mentions "machine learning," understand it's about pattern recognition.
Step 2: Skill Audit and Role Research: Map your existing skills against technology job descriptions. List your top 10 professional achievements, then research how those skills apply in tech. Project management becomes agile delivery. Customer service becomes user experience thinking. Financial analysis becomes data interpretation.
Step 3: Targeted Learning: Now build technical skills relevant to your target role. Product management? Learn user research methods and basic SQL. Technical writing? Understand documentation tools and version control. This part really depends on the role you are aiming for. You may need to complete a course(s) and carve out time for self-study, but as long as you are targeted you will reduce the time it takes to reach your goal.
Ensure your CV tells a story and acts as your personal promoter
I've reviewed hundreds of CVs and can easily spot the candidates who can solve real problems.
James, worked in graphic design and wanting to move into app development. He created a shift management system for small restaurants to manage staff hours, as part of a side hustle, working to support a friend’s chain. It wasn't the most sophisticated code, but it demonstrated he understood the business context, could identify user needs and could build something useful.
Your CV should tell a story about how you think. Try to document your decision-making process when you produce your new, tech-savvy, CV. Explain why you chose certain approaches and show how you handled challenges.
The networking reality check
In this sector, networking is less about formal events and more about real engagement. For example, the most successful transitions involve candidates who:
- Answer questions on Stack Overflow or Reddit
- Contribute to open-source projects (even documentation improvements)
- Share their learning journey on LinkedIn or Twitter
- Attend local meetups with genuine curiosity
Be genuinely helpful first and opportunities will follow. The tech community supports career changers who demonstrate authentic enthusiasm and commitment to learning.
The application strategy that works
Here's what career change guides won't tell you: applying through job boards is often the least effective method. The most successful transitions happen through:
- Internal mobility - Many successful placements start with someone moving to a tech role within their existing company.
- Referrals - These came through professional connections (often acquaintances from online communities or in-person networks).
- Direct approach - This is where candidates reach out directly to hiring managers or founders at smaller companies.
- Recruiter support – Connecting with a recruitment consultant that specialises in your area can open you up to opportunities you would never have been aware of.
- Traditional applications - via job search engines and job boards.
Managing the transition timeline
Every candidate asks: "How long will it take?". My answer: it depends on your target role, time commitment and how well you use your existing skills.
Typical timelines:
- Technical roles requiring significant coding: 12-18 months part-time study.
- Product or project management: 6-9 months focused learning and networking.
- Systems development such as Microsoft Dynamics 365, Salesforce or ERP: 6-12 months, depending on any prior user experience.
Set realistic expectations while maintaining momentum. Too many people give up at the six-month mark, just when they're gaining traction. Anything worth achieving takes commitment, consistency and patience.
The mindset shift that changes everything
Stop thinking like a career changer and start thinking like a technologist.
Technologists are comfortable with ambiguity. They break down complex problems into smaller pieces. They iterate, test, and improve continuously. They view failure as feedback, not defeat.
These aren't innate technical skills, they're mindsets. If you've successfully navigated any career change, you already have them.
Your next steps
If you're serious about transitioning into tech, these are some actions you could consider:
- Audit your LinkedIn profile: How many technology professionals are in your network? Start connecting with people in roles that interest you.
- Choose one technology publication to read: Make it part of your daily routine.
- Identify three companies: Not to apply to yet, but to understand their technology challenges.
- Join one online community: Such as Slack group, Discord server or a Reddit community related to your area of interest.
- Schedule time for learning: Block out specific hours each week and treat it as seriously as any other professional commitment.
- Use the free AI tools to do simple tasks: ChatGPT, Perplexity, Gemini, Copilot are all available.
The technology sector needs diverse perspectives, varied experiences and fresh approaches to solving complex problems. Your background isn't a limitation, it's what makes you valuable.
The question isn't whether you're technical enough for technology. It's whether the sector is ready for the fresh approach you bring.
Frequently asked questions
What's the biggest mistake career changers make? Trying to learn everything at once. Pick one role, master the basics, then expand.
Are there age limits in tech hiring? Officially no, but ageism exists. Focus on current skills and energy, not years of experience.
Should I get certifications? Only if the specific role requires them. Portfolio work usually trumps certificates. There are sites which offer small coding jobs for example, once you’ve completed your learning.
How do I handle technical interviews with limited coding experience? Be honest and realistic about your level but emphasise your problem-solving process. Many companies value thinking over syntax and offer training and apprenticeships.
Is it worth taking a pay cut to break into tech? Often yes, if the long-term trajectory makes sense. Tech salaries typically grow faster than other sectors.
Ready to make a change
If you have already acquired the skills you need to transition your career, view our latest jobs to start your application process, or upload your CV, and we can match appropriate jobs to save you time.