When I moved to Australia on student visa, I didn’t arrive as a software engineer. Not really.
On paper, I still was one. I had years of studying patterns, writing logic, and solving problems that lived inside a screen. But reality doesn’t always align with titles. Visa constraints, local experience requirements, and the quiet competition of a new country reshaped my starting point.
So I became a kitchen porter.
At first, it felt like a step backward. There’s no elegant way to frame that initial feeling. Standing over a sink, hands soaked, repeating the same motion for hours challenged my sense of identity more than my physical endurance. But financial stability comes first. That was the agreement I made with myself.
Finding Patterns in the Chaos
Then something unexpected happened. I started recognizing patterns.
Not in code, but in plates. In workflow. In movement.
The kitchen wasn’t random chaos. It just looked that way at first. Underneath, there was structure. Plates arrived in waves, not individually. Glassware followed a different rhythm than pans. Cutlery had its own cycle. If you paid attention, you could predict the flow before it hit your station.
That’s when it clicked. This wasn’t so different from debugging a system.
Designing the System
I began organizing the dishwashing area the way I would structure a program: Inputs, processes, outputs.
Dirty dishes come in, then get categorized, sorted, and prioritized.
- High-turnover items go first.
- Large items are staged separately.
- Clean items are sent back efficiently.
I wasn’t just washing dishes anymore. I was designing a system.
Speed improved naturally, but not because I forced it. First came understanding. Then came structure. Only after that did the hands start to move faster, almost automatically. Just like coding. You don’t write fast because you try to type quickly. You write fast because you already understand the problem.
Spatial Awareness and Architecture
Even memory worked the same way. At the beginning, I had to consciously think about where everything belonged. After a while, it became spatial awareness, like navigating a familiar codebase. You don’t memorize every line. You understand the architecture.
The kitchen demanded the same thing:
- Where are the plates stored?
- Which rack is used for which item?
- What order keeps everything flowing without bottlenecks?
All of it happened in the brain first. The hands simply followed instructions that had already been optimized.
The Mindset Shift
Strangely, that realization made the work lighter. Not easier, but clearer.
I stopped seeing the role as something beneath my previous experience. Instead, I started seeing it as another system to understand, another environment to adapt to. The tools were different, but the mindset was the same. That shift didn’t just help me survive the job. It helped me take ownership of it.
There’s a quiet kind of pride in doing something well, even if the world doesn’t immediately recognize it. Especially then.
A New Perspective
I’m still a software engineer. That hasn’t changed.
But now I understand something I didn’t before. Problem-solving isn’t tied to a job title. It’s a way of thinking. Whether it’s designing a backend system or organizing a dishwashing station, the core is the same: patterns, structure, and the discipline to improve them.
This experience didn’t move me away from my path. It made me better prepared for it.