How I Transitioned from Visual Design to Systems Engineering

Introduction

Coming from the world of visual design where I’ve been an artist for over 19 years, exploring every medium from pencil drawings to 3D visualization, I never imagined I’d one day fall in love with the command line and the structured logic of systems engineering. Yet here I am, embarking on a new journey that’s both challenging and deeply exciting.

This post marks the beginning of my documented path into systems engineering.

Why I Transitioned

A good question you might ask is: “Why make such a huge switch?”

The honest truth is I got lost. Here’s how it happened.

My journey in design began from pure curiosity. I used to wonder how product packages were designed, which led me to discover tools like CorelDRAW, Photoshop, and Illustrator. I’d spend countless nights trying to replicate designs that caught my attention. Eventually, I mastered these tools enough to create anything I imagined.

As I shared my work, people both locally and internationally began reaching out for designs: company logos, event posters, product labels, album covers, book covers, and more. It wasn’t much money, but it gave me a sense of purpose.

After three years in that space, I began to see its limitations. Around the same time, I lost my dad a turning point that made me rethink everything. I wanted growth, not just passion. So, I transitioned into digital art and later, UI/UX design.

The Design Years

In 2021, I took my first serious steps into both fields. I spent hundreds of hours studying tutorials and practicing tirelessly. After many failed attempts, things started to click. I became confident enough to share my designs publicly and soon after, I was building user interfaces for teams and startups while also creating digital art that I was proud of.

For two years, I thrived. I built for companies, sold artworks as NFTs, and gained recognition across online communities. It was fulfilling until it wasn’t.

The UI/UX industry grew increasingly saturated. As a freelancer in West Africa, maintaining consistent income became tough. Getting design jobs now required not just a strong portfolio, but also a large social media presence, front-end skills, and sometimes motion design. The rise of AI made things even harder.

I grew frustrated, burned out, and uncertain about what was next.

Discovering 3D Design

In search of new meaning, I collaborated with a friend to build a game design studio. That’s when I picked up 3D design, working with tools like Blender, Substance Painter, ZBrush, Character Creator, and Marvelous Designer.

Though our collaboration eventually ended, that experience opened a new creative door. I learned about lighting, texturing, modeling, and the technical beauty of building digital worlds. But even then, something still felt missing.

I was broke, emotionally drained, and unsure of my direction. I needed stability, a structured path, and a career that allowed both creativity and intellectual growth.

The Turning Point

My sister suggested I go back to school. At first, I resisted, I wasn’t sure what I wanted to study. Then, while browsing through available programs, I found Systems Engineering.

It felt like a calling. I researched what the field entailed and the more I read, the more it resonated. It checked every box I was searching for in my next chapter:

• A structured learning roadmap

• High-demand, future-proof skills

• Meaningful problem-solving and real-world impact

• Continuous curiosity and challenge

• Endless opportunities for growth

Why Systems Engineering?

If you’re wondering why this specific field, here’s what drew me in:

1. Understanding How Technology Works

I’ve always loved technology. Growing up, I watched as tech reshaped everyday life from mobile phones to the internet. I was fascinated by innovators like Elon Musk, and I once told my dad I wanted to build one of Africa’s first electric cars. He laughed, but that dream stuck with me. Systems engineering gives me the tools to understand the interconnected layers of hardware, networks, software, and automation and how they all work together to power the modern world.

2. Bridging Software and Hardware

As a systems engineer, you operate at the intersection of both worlds. You’re not just coding you’re configuring hardware, optimizing networks, and managing the servers that run the internet. This hybrid nature of creativity and technicality felt perfect for me.

3. High Demand, High Relevance

Every organization relies on technology, and these systems need constant maintenance. From startups to global enterprises, systems engineers are always in demand.

4. The Joy of Problem Solving

Systems engineers are the superheroes of reliability diagnosing, troubleshooting, and optimizing under pressure. If you love solving puzzles and building efficient solutions, this is the cape to wear.

5. Infinite Learning

This is what excites me most. With my ADHD-driven curiosity, I thrive on constant change. One week you’re managing Linux servers, the next you’re automating tasks with Python or deploying cloud infrastructure. Systems engineering guarantees you’ll never stop learning.

6. Real-World Impact

Unlike some tech roles where results feel abstract, systems engineering has tangible effects keeping hospitals online, powering cloud platforms, and ensuring businesses stay connected.

My Starting Point

Like many beginners, I didn’t jump straight into Linux servers or automation scripts. My school’s Advanced Diploma in Systems Engineering provided a structured foundation.

Here’s what my first-year curriculum includes:

• CompTIA A+ → Learning the fundamentals of hardware, operating systems, and troubleshooting.

• CompTIA N+ → Understanding networking concepts like IP addressing, OSI models, routing protocols, and network architecture.

These courses helped me grasp how hardware and software interact, how networks function, and how to troubleshoot the devices people use every day. Together, they form the core pillars of systems engineering.

What I’m Learning Now

• Red Hat Enterprise Linux (RHEL): Gaining confidence with the command line, system administration, and server setup. Linux has been an eye-opener powerful, open-source, and endlessly customizable.

• Python for Automation: Writing small scripts to automate repetitive tasks. I’m currently reading “Automate the Boring Stuff with Python” a fantastic resource for beginners.

• Windows Server Administration: Learning about Active Directory, policy creation, and role management.

• AI Prompt Engineering: Practicing structured communication with AI using the CLEAR framework: Clarity, Logic, Examples, Adaptation, Results.

• Networking & Hardware Fundamentals: Reinforcing my understanding through home labs and hands-on exercises.

What’s Next

In the short term, my goals are to:

• Document my learnings from Linux commands to server setups and troubleshooting tips.

• Build small projects from basic web servers to automation scripts and network simulations.

• Share consistent updates here on Hashnode about industry trends, tools, and lessons learned.

In the long term, I aim to grow into a skilled systems engineer, capable of solving real infrastructure problems and mentoring others beginning their journey.

Right now, it’s not easy. The concepts are dense and the learning curve is steep but like anything in life, it gets easier the more you show up. And I plan to keep showing up.

Conclusion

This blog marks a personal milestone my way of holding myself accountable and giving back. Writing this down feels both grounding and healing.

If you’re also learning systems engineering or considering a transition from another field, I hope my story offers some encouragement.

In my next posts, I’ll break down what I’ve learned from CompTIA A+ and N+, what’s essential for aspiring systems engineers, and how these foundational topics shaped my entry into the field.

Thanks for reading and welcome to my new chapter.