Jaz Maslen, Software Developer

Learn all about...

What I do

I build software that helps my company run its training courses and apprenticeship programmes.

A lot of my work is about finding ways to automate jobs that would otherwise take staff lots of time.

For example, I have been building a system that automatically records lessons, uploads videos and creates transcripts, so this is all available for our customers and students.

My job is all about solving problems and making technology work better for people so they can focus on teaching, learning and creating new ideas.

Software Developer Jaz, working on their laptop, at a desk, with code on the screen.

How I became a technician

At school, I chose triple science, geography and design technology - textiles for my GCSE options. I loved science and did not want to give any of it up, so for my A-levels I did biology, chemistry and physics.

At first, I thought I wanted to become an academic researcher. After a gap year travelling, I went to the University of East Anglia to study biological sciences because I was interested in fungus and soil health.

How I became a technician

Quite quickly, I realised university and lab work were not for me. I loved learning new ideas, but I did not enjoy the very detailed research work into just one area or the pressure of being assessed all the time.

I left university after four months. I decided to learn coding so I could build websites to help small farms and environmental projects.

How I became a technician

I found an online coding course called She Codes and completely fell in love with programming. I loved that there was always something new to learn – it felt like I was using the discovery side of science in another area – coding.

I then applied for a free coding bootcamp at Founders and Coders. The application process involved building a website, creating a game and completing coding challenges.

How I became a technician

After finishing the course, I applied for a Level 4 software development apprenticeship with the company and got the job.

Since then, my role has grown into all sorts of areas including software development, automation and even fixing company Wi-Fi systems.

Want to explore the world of technicians?

Meet more technicians to find out what they do and the path they took to become a technician.

Meet the technicians

A typical day in my working life

I usually cycle into the office, and I work from 10am until 6pm.

At the start of the week, the team has a quick meeting where everyone shares their top priorities and any problems they are stuck on. At the end of the week, we have another meeting to share our updates and talk about what we have achieved.

A typical day in my working life

Every day is different. Some days I help learners during coding workshops by answering questions and helping people work through problems.

Most of the time, though, I work independently on software projects. A big part of my job is writing code to automate tasks.

A typical day in my working life

Recently, I have been building a system using a Raspberry Pi computer and a camera that automatically records workshops and uploads the videos to our servers.

I have also worked on e-mail automation systems, apprenticeship tracking platforms and even done some network engineering when the company Wi-Fi stopped working.

A typical day in my working life

I manage my own time and organise my projects each week. I track how long I spend on tasks like apprenticeship work, workshop development and software projects.

I also meet with my manager weekly to discuss my work and get support if I need it.

Could you be a technician?

There are 100s of technician roles out there. Take the quiz to find the perfect role for you.

Take the quiz

Software Developer Jaz, wearing a hoodie and standing on a ladder, working with network cables in a wall-mounted server cabinet.

What I love about my job

The thing I love most is the variety. I never know what challenge is going to appear next.

I originally expected to spend all my time writing software, but my role changes all the time. One month I might be improving e-mail systems, another month I could be learning how networking equipment works, and now I am building automated media systems.

I really enjoy being given a problem and figuring out how to solve it. Instead of being told exactly what to do, I get the freedom to research ideas, test solutions and decide what equipment or software would work best.

That independence makes the work exciting because I am always learning something new.

The skills I use most

Problem solving is probably the most important skill I use. My whole job is about finding ways to make systems work better, whether that means fixing Wi-Fi issues, automating recordings or writing code that handles information correctly.

I also use logical thinking every day. Coding is all about breaking a problem down into smaller steps and deciding the right order for everything to happen.

Prioritising is another huge part of my job because my projects can change quickly. One week my focus might be my apprenticeship portfolio and the next week I could suddenly need to fix a technical issue for the company.

Curiosity is really important too. I enjoy learning how computers work behind the scenes and understanding what technology is actually doing rather than just using it.

I really enjoy being given a problem and figuring out how to solve it. That independence makes the work exciting because I am always learning something new.

People trust me to try things out and solve problems in my own way, but I also know I can ask questions whenever I need support.

When I was doing my GCSEs and A-levels, I felt like every decision would completely shape my future. Looking back, I can see there are always opportunities to change direction, learn something new or start again.

A little more about my everyday role

The best bits about working in a team

The team I work with is incredibly supportive. Even though we all work quite independently, there is always someone available to help if I get stuck.

I like that everyone is encouraged to learn and experiment. People trust me to try things out and solve problems in my own way, but I also know I can ask questions whenever I need support.

We regularly share updates with each other, which means everyone learns from the projects other people are working on. It feels like a team where people genuinely want each other to succeed.

My favourite piece of equipment

One of my favourite things to work with is a Raspberry Pi. It is a tiny computer that can control other devices and run software.

I have been using one to automate camera recordings for workshops and lessons. The Raspberry Pi checks the lesson timetable, turns the camera on at the right time, records the session and uploads the video automatically.

It feels exciting because I get to understand how computers work underneath all the usual software and apps that people use every day.

What I like to do in my spare time

Outside work, I love rock climbing and swimming because I spend so much of my job sitting at a computer.

Rock climbing is surprisingly popular with software developers. Loads of people in my office climb - I think there is something similar about the problem solving involved in both activities.

I also enjoy learning technical things at home and experimenting with Linux systems (a type of computer operating system) and coding projects. I really like understanding how technology works at a deeper level.

My school days

At school, I was really into science, and I spent a lot of time studying. I was also a competitive swimmer and played the flute.

Outside lessons, I mostly hung around at the park with my friends after school. It was where everyone went to relax and spend time together.

I put a lot of pressure on myself during my GCSEs and A-levels because I thought my choices and results would define my future. Looking back now, I realise there are many different paths into a career and it is okay to change direction.

The most exciting thing I’ve achieved so far in my job

One of the proudest moments in my career was fixing our company Wi-Fi system. At the start, I barely understood networking equipment or even what a router did. What I thought would take a week ended up turning into nearly two months of intense learning and problem solving.

By the end of it, I had learned how to configure networking systems and get everything running again. It felt amazing because I had gone from knowing almost nothing to solving a real technical problem that affected the whole company.

A surprising fact about my job

I do far more than just coding. I have worked on networking systems, automation projects, cameras, media recording and even researching equipment for the company.

Sometimes I am writing software and other times I am physically setting up hardware or testing technical equipment.

I think a lot of people imagine software developers only sit and type code all day, but the role can actually involve loads of different skills and challenges.

The next steps in my career journey

I am finishing my Level 4 software development apprenticeship and starting to think about what comes next.

At the moment, I am really interested in automation and machine learning. I want to keep building systems that save people time and make work easier.

I also enjoy learning new technical skills, so I can see myself continuing to explore lots of different areas of technology.

The advice I’d give to someone younger

I would tell my younger self not to stress so much. When I was doing my GCSEs and A-levels, I felt like every decision would completely shape my future.

Looking back, I can see there are always opportunities to change direction, learn something new or start again. Work hard and follow what interests you, but do not feel like you have to get everything perfect straight away.