Timeline: My Career Shift from Mechanical Engineer to Cybersecurity

What This Blog Is About

In this second blog, I want to look back on my work journey—from my early days as a mechanical engineer to where I am now in cybersecurity. I’ll walk you through the timeline of my roles, highlight the key skills and decisions that shaped my path, and share what I would do differently if I were just starting my transition today. My hope is that anyone looking to shift into tech or cybersecurity can take something useful from this.

Left: Just before kicking off a client project as an Identity & Access Management Engineer—outside their building in Sydney. Right: Unwinding after work—on a boat to Manly Beach in my One Piece costume, with the Sydney Opera House quietly in the background.

Left: Just before kicking off a client project as an Identity & Access Management Engineer—outside their building in Sydney.
Right: Unwinding after work—on a boat to Manly Beach in my One Piece costume, with the Sydney Opera House quietly in the background.

Game-Changing Moments: Timeline from Mechanical Engineer to Cybersecurity

As you look at the diagram below, you’ll see a visual representation of the key milestones in my journey from mechanical engineering to cybersecurity. The timeline highlights not only the different roles I’ve taken on but also key initiatives and skills that helped shape my career.

My path into cybersecurity wasn’t a straight highway—it was shaped by pivots, initiatives (especially initiatives!), and accumulating transferable skills across different fields.

  • 2017 – I became a licensed Mechanical Engineer. This trained me in problem-solving, systems thinking, and analytical discipline.

  • 2018–2020 – As an Equipment and Technical Sales Engineer, I learned to connect technical concepts with client needs—strengthening my communication and business acumen.

  • 2020–2021 – While in Property Management, I initiated a COVID-19 contact tracing solution using Microsoft Power Platform. This was my first real experience applying low-code automation to a real-world problem.

  • 2021 – I formally shifted into tech as a Power Platform Developer. I built automated workflows, Power BI dashboards, and even deployed solutions using Azure Data Factory—bridging into cloud technologies.

  • 2022–Present – As an Identity and Access Management Engineer, I support enterprise clients using Entra ID and PowerShell. I led a UAR remediation project in Sydney and now help train new hires—closing the loop on my transition.

The journey wasn’t linear, but each chapter gave me tools and experiences that now power my role in cybersecurity.

How It's Going

The journey hasn’t stopped at landing a cybersecurity role—I’m still in the thick of building strong foundations.

I continue to strengthen my grasp on Linux, Bash, PowerShell, and Networking—essentials in this field that, for me, have been recurring stumbling blocks. Progress isn’t always fast, but I’ve learned to lean into “learning by teaching.” Guiding new hires motivates me to stay sharp and deepen my understanding.

Even as I work through the fundamentals, I’ve seen meaningful progress. I had the opportunity to contribute to a remediation project overseas, and I’m now part of a team that supports large-scale identity systems. It reminds me that you don’t need to have everything mastered to make an impact.

One of my superiors once joked that I’m like Orochimaru from Naruto anime series—a character known for collecting countless techniques and mastering many abilities. It was meant as a compliment about my range of skills across different fields. In a way, that’s the long-term goal in cybersecurity too: to become “Orochimaru” by building a deep and wide skillset across IT and using that to approach security holistically.

I’m still overwhelmed by how much there is to learn—but I remind myself that growth in this field comes from consistent curiosity, not overnight mastery. I’m staying hungry and looking ahead. DevSecOps and AI Security are directions I’m actively considering as I shape the next chapter of this journey.

If I Could Start Over: Smarter Ways to Transition

If I could start over, I’d take a more structured and realistic approach—one that includes two types of networking from the beginning:

1. Technical Networking (the IT foundations you can’t skip)

Before diving into cybersecurity-specific courses or certifications, I’d start with the core systems and tools that security work is built on:

  • Operating Systems: Learn the basics of Linux and Windows—how they work, how to navigate them, and how they’re secured.

  • Scripting Skills: Get hands-on with Bash and PowerShell—two powerful tools for automation, analysis, and system management.

  • Computer Networking: Understand IP addressing, ports, protocols, DNS, firewalls, and how the internet works.

  • Cloud Fundamentals: Once the above are solid, move into cloud platforms like Azure and AWS—this is where a lot of modern security happens.

  • Cybersecurity Role Tracks: Only then would I start choosing a path—SOC Analyst, IAM, DevSecOps, etc.—and look for focused training.

Starting here would have saved me a lot of rework and confusion later on. These are the building blocks that often become stumbling blocks when skipped too early.

Where to start learning

If you are willing to spend some on learning, I recommend subscribing to tryhackme.com. For me, they have the best materials for beginners. If you are on a budget, you may start looking for cybersecurity roadmap in roadmap.sh. They curate roadmaps for many IT careers and within nodes are free learning sources.

2. Social Networking (the kind that builds your career)

Just as important: build your circle early. Join Discord groups, take part in local or online tech meetups, follow cybersecurity folks on LinkedIn, ask questions, and offer help when you can.
Connecting with people accelerates your learning, keeps you accountable, and exposes you to opportunities you won’t find on job boards. In my case, I might not have landed my current role if I hadn’t reached out to the hiring manager two years before I even applied. That early connection was a key factor in getting my foot in the door when the opportunity came up.

Parting Thoughts & Next Steps

Looking back on this journey, it’s clear that success isn’t about having everything figured out from the start—it’s about continuously learning, adapting, and seizing opportunities as they come. My transition from mechanical engineering to cybersecurity wasn’t a straightforward path, but each twist and turn has shaped who I am today.

For anyone considering a similar shift, my advice is simple: stay curious, be proactive, and don’t be afraid to reach out to others. The tech world moves fast, but there’s always room for problem solvers. Keep learning, whether through formal courses, hands-on experience, or teaching others. Build your network early and engage with the community—it’s more important than you might realize.

As I look ahead, I’m excited about the potential in DevSecOps and AI security, but there’s still so much more to learn.

0
Subscribe to my newsletter

Read articles from Daven Earl Bellen directly inside your inbox. Subscribe to the newsletter, and don't miss out.

Written by

Daven Earl Bellen
Daven Earl Bellen

I’m Daven Earl Bellen. I started out as a mechanical engineer and found my way into cybersecurity, where I now work in Identity and Access Management. I’m still learning as I go—and this blog is my way of sharing what I’ve picked up along the way. If you’re exploring tech or shifting careers, you’re in the right place.