
Date
Oct 2024
Category
Story, Leadership, Tech
Post by
Nick Rakovsky
Social Media
Nick Rakovsky transitioned from aerospace engineering to supply chain technology by applying his systems-thinking mindset to real-world operational problems. His early work with complex systems made it easier to identify inefficiencies in warehouse environments. Back in high school, I didn’t get the job. Not once, not twice, but multiple times. So I did the only thing I knew how to do, I kept showing up.
Eventually, they gave in.

Years later, I was studying business and electrical engineering while playing football. Somehow, that path led me to working on components for the James Webb Space Telescope. A million and a half miles away from Earth… and I had a hand in it. Then things shifted again, this time underwater. I worked on robotics for Navy SEAL teams, building systems that explored places most people will never see.
And that’s when it clicked:
Then came warehouses. No space. No ocean. Just chaos. Forklifts moving nonstop. Radios buzzing. Problems everywhere. And strangely, it felt more real than anything I’d done before.
Because here, you didn’t just build things, you felt them. When something broke, you saw it instantly. When it worked, you knew it mattered.
After a while, the late-night calls started stacking up:
“Where’s this truck?”
“What’s this load?”
It wasn’t inspiring. It was exhausting.
Not a “lightbulb moment.”
More like: this is broken, and it shouldn’t be.
So I built something to fix it.
DataDocks didn’t start as an idea. It started as frustration.
A simple tool to track loads became something bigger:
And eventually, a team that believed software should actually help people, not slow them down.
From satellites to submarines to warehouses, it might seem random. But it’s not.
Every step taught the same lesson:
Systems don’t fail because of technology. They fail because they forget the people inside them.
Curiosity doesn’t give you a map. But if you follow it long enough, it will take you somewhere that matters.