What it’s really like working in tech without a STEM degree  

If you’ve ever felt unsure about entering the tech world without a Computer Science or Engineering degree, you’re not alone. The perception that tech is only for coders or maths wizards is slowly fading, and for good reason.  

Our Head of Graduate Talent, UK & EMEA, Fleur Laffont, explains, “We need to demystify tech. There’s more to tech than coding! It is a constantly evolving sector with immense opportunity. There’s a role for everyone. People often think it’s not the right industry, or they need a Computer Science degree. It’s not the case. You can have a successful career in technology regardless of your academic background. Technology and business change all the time. You will always be learning.” 

What’s in this article? 

Why you don’t need a tech degree to work in tech 

Imposter syndrome is real, but it doesn’t last forever 

Top tips for new grads starting in tech roles 

Navigating your first year: What to expect 

Why you don’t need a tech degree to work in tech 

Many roles in tech, like business analysis, project support, risk, compliance, or cybersecurity, rely on critical thinking, communication, teamwork, and the ability to learn quickly. 

In fact, at FDM, we actively seek out people with a wide range of academic backgrounds. Why? Because problem-solving in tech benefits from different perspectives. A History grad might spot patterns others miss. A Psychology student might understand users better. A Linguistics major might translate technical ideas into everyday language. 

Sonia Purewal, now a Service Analyst at FDM, wasn’t sure where her degree would lead, although she always had an interest in technology. She explains: 

“Coming from a Criminology background, I didn’t have the traditional route into IT. But that didn’t stop me. I knew I wanted more, so I joined FDM. I began my training last year, and by January 2025, I had started with a client as a Service Analyst. Since then, I’ve worked for the public health care system and helped manage communications with external parties. Now, I’m focused on incident and problem management, and I’m aiming to develop my skills further to eventually join a team in cyber security.” 

Imposter syndrome is real, but it doesn’t last forever 

Starting something new always comes with uncertainty. But entering the tech world without a technical background, it can feel like everyone else knows more than you. That feeling has a name: imposter syndrome. And here’s the good news: it’s normal, and it passes. 

In your first few weeks, you might be faced with unfamiliar tools, technical jargon, or fast-paced meetings. Take it one step at a time. Ask questions. Write things down. Remind yourself that no one expects you to be an expert on day one. What matters most is your attitude and willingness to learn. 

Your past has taught you more than you think 

Even if you didn’t study coding, your past gave you valuable skills that tech employers want. Writing essays? That’s analytical thinking. Group presentations? Communication and teamwork. Research projects? Attention to detail and independent learning. 

Once you start working in a tech role, you’ll realise that these skills come in handy more often than expected. Whether it’s breaking down a complex issue, leading a client conversation, or writing up reports, your background can help you stand out in the best way. 

Top tips for new grads starting in tech roles 

Breaking into tech is exciting, but those first few months can feel like you’ve been dropped into a sea of unfamiliar tools, jargon, and workflows. The good news? You don’t need to know it all right away. What matters is building smart habits that help you grow into the role. 

Isel Abdellatif, FDM’s Regional Recruitment & University Partnerships Manager, shares: 

“Go in with confidence and use your transferrable skills. We would recommend keeping a keen eye for opportunities to develop and grow. This could involve learning a new programming language or familiarising yourself with tech tools that you’ve not used before! A keenness to learn new skills is a must, and it’s also good to be open-minded and flexible about the opportunities to enhance these skills as you progress in your role.” 

Here’s how to get started:

Keep a “technical learning journal”

Tech roles come with a flood of new systems, acronyms (like API, CI/CD, SQL), and coding conventions. Every time you come across something you don’t know — whether it’s a command-line function, a Jira status, or a piece of documentation, write it down. Then, research it or ask a colleague to explain. Over time, looking back on your notes will be a powerful reminder of how far you’ve come.

Speak up early and often

It can be intimidating to contribute when you’re new, but your perspective matters. Don’t underestimate the value of fresh eyes; you might notice inefficiencies or question assumptions that others have grown used to. Whether you’re asking questions, giving feedback, or offering a new idea, speaking up helps you build confidence and visibility.

Don’t compare your journey

In fast-moving teams, it can seem like others are excelling while you’re still finding your footing. But everyone has different strengths, learning styles, and backgrounds. Some people might have prior experience with certain tools, while you might excel in critical thinking or communication. Focus on your own development and acknowledge your progress, one milestone at a time.

Celebrate the small wins

From successfully running your first stand-up to debugging your first piece of code, every achievement counts. Take time to reflect on what you’re proud of each week; it builds momentum and reminds you that you’re progressing, even if it doesn’t always feel like it. 

Navigating your first year: What to expect 

Month 1–3: Onboarding and information overload 

This is your foundation-building phase. You’ll be absorbing everything: tools, terminology, team dynamics, and workflows. Expect training sessions, shadowing opportunities, and lots of documentation. 

You might feel like you’re drinking from a firehose. That’s completely normal. Your job right now is to observe, ask, and absorb. 

What to focus on: 

• Learn your team’s tech stack (e.g. what languages, platforms, frameworks they use) 

• Get comfortable with tools like Git, Jira, Confluence, Slack, or Azure DevOps 

• Start your “technical learning journal”, you’ll thank yourself later 

Month 4–6: Confidence building 

At this stage, things start to click. You’ll have a better grasp of the systems and start applying your knowledge to real tasks. Maybe you’re writing your first scripts, taking ownership of small tickets, or contributing to data analysis or testing. 

You’ll still have questions (and should!). But now, you’re asking sharper, more contextual questions, and that’s a sign of growth. 

What to focus on: 

• Volunteer for sprint tasks, even small ones, completing a ticket builds confidence 

• Start thinking about writing clean, maintainable code or clear documentation 

• Practise explaining technical concepts to non-technical stakeholders 

• Ask for feedback regularly: what are you doing well, and where can you improve? 

Month 7–12: Growing your impact 

You’re now an integrated part of the team. You know the lingo, understand the workflows, and are likely taking on more complex tasks or even mentoring newer starters. You’ll also start thinking about your long-term direction — whether that’s specialising (e.g. DevOps, data, security) or broadening into business-facing roles like product or project management. 

What to focus on: 

• Identify areas of the tech stack you enjoy, then go deeper 

• Look for small inefficiencies you can solve (scripts, automations, documentation updates) 

• Offer to lead a task in sprint planning or demo your work in a team meeting 

• Start networking internally, build relationships with teams you might want to collaborate with 

Your background isn’t a limitation, it’s a launchpad 

If everyone on a tech team thought the same way or had the same training, the outcomes wouldn’t be nearly as strong. You bring a unique lens to the work, shaped by your studies, your personal experiences, and your interests. 

Forbes reveals that diverse teams deliver 60% better results and make better decisions in 87% of cases. The business case for diversity is now stronger than ever, and diversity, equity and inclusion are key pillars that should be a priority for every business.   

Our Diversity and Inclusion Coordinator at FDM, Sheldan Bristol-Walton, shares: 

“Diversity is not just our people but our ideas, our peers, our information. The importance of these diverse elements of FDM allows us to quickly adapt to changing environments and empower each other.”  

Conclusion  

If you’re about to start a tech role without a traditional tech degree, take heart. You are more prepared than you think. Your first year might feel like a steep climb, but every question asked, every tool mastered, and every small win builds your confidence.  

At FDM, our Skills Lab supports graduates on their journey into tech . The Skills Lab uses experiential learning models,  immersing consultants into realistic, hands-on scenarios that replicate real-world challenges. During coaching, consultants work in cross-functional teams to develop  their professional and technical skills ensuring they are immediately impactful in their roles, adding value to client assignments from day one. 

There is a big emphasis on nurturing our community with a range of employee networks and initiatives that ensure everyone feels valued and connected. 

Ready to start your journey?
Explore our Graduate Careers Programme and take the first step today.