There’s a saying in Hebrew that every ending is the first chapter of a new beginning. When it comes to my Marvell story, the new beginning had the same starting point.

I graduated university with a degree in computer engineering and joined Marvell as a Storage Security Firmware Engineer, working within a group focused on building security infrastructure from the ground up. It was a fascinating experience where I learned an immense amount about code, lab environments and firmware development. It was my ideal work environment: high energy, constantly challenging and had a meaningful impact.

I always love to find new ways to improve processes and stay busy, and I found a major roadblock early on. Compilation and loading took up to 10 minutes per task, draining hours of productivity each week. I set a goal to cut that time short. While we didn't hit my ambitious target, we optimized the process significantly, cutting down run times by 70%.

Eventually, the local team I was part of closed and I moved on to explore other paths, grateful for the deep technical foundation I had built at Marvell.

While I was at my new company, I quickly realized what I was missing. The deep sense of purpose, collaborative spirit and thrill of building things from the ground up. I missed the environment that makes Marvell unique. In fact, I believed in the company so much that I kept referring my own friends and colleagues to open roles here.

One day, while submitting a referral for a friend, my Marvell connection asked a simple question: “Why aren't you applying?”

That was all the push I needed. Three interviews later, exactly one year after I had left, I walked back through Marvell’s doors.

Returning to a brand-new office and a new role was an exciting challenge. Even though I had only been gone for twelve months, the company had scaled tremendously. New faces, massive new projects and entirely fresh technical challenges.

Stepping into a new role, an Embedded Staff Software Engineer, I immediately looked for ways to improve process efficiency. Our team's internal tools and infrastructure needed a dedicated owner. And being passionate about challenging myself and improving processes, I volunteered. That is what I love most about Marvell. If you see a way to make something better, the culture empowers you to take ownership and drive it forward.

My proudest achievement in this chapter was leading a proof-of-concept (POC) through full implementation of migrating our local testing systems to a highly scalable cloud infrastructure. As our global teams expanded, our legacy services were hitting a wall. Leading this cloud migration optimized workflows and drastically reduced build and deployment times for our engineering teams worldwide.

Today, I work on a different layer of the product, developing the software development kit (SDK) application programming interfaces (APIs) for the Teralynx switch chip line. A foundational architecture utilized by multiple teams across Marvell.

Another thing I was excited about coming back for was the ability to work on the most innovative technologies and pushing the boundaries of hardware forward. Knowing that the code I write has a direct, real-world application on global AI infrastructure gives me an incredible sense of purpose.

If I could offer one piece of advice to engineers navigating their own career paths, it would be simple. Find where you can add value. Understand your unique strengths. Don’t wait to be given the opportunity to make an impact. Ask for it.

They say you can never go back, but sometimes, returning to the right place is the absolute best step forward your career can take.