Jonathan Moo

The Decisions That Brought Me Here — and Why I’m Writing About Them

Have you ever wondered how different your life might be if you had made a different decision at a career crossroads?

Ten years ago, before I left for Florida to work as a data engineer at CBS Sports, I considered three very different possibilities.

  • A local telecommunications company in Singapore had approached me through Stack Overflow, where I was among the top ten contributors on Elasticsearch at that time.
  • I had made it to the final interview stage at Facebook in Singapore.
  • I had been invited to serve full-time in a Christian ministry in Thailand.

Each possibility represented a very different direction for my career, and perhaps my life.

Instead, I took a leap of faith and moved to the United States.

At the time, data science was one of the hottest topics in technology, and I saw the move as an opportunity to grow in that field.

Looking back, I sometimes wonder how differently things might have turned out if I had chosen another path.

Of course, I’ll never know.

But that experience reminds me of something I’ve come to appreciate over the years: some of the most important career decisions are made without knowing whether they will turn out to be the right ones.

We choose technologies that may become obsolete. We design systems that other people will eventually inherit. We make decisions about teams, responsibilities, and career opportunities with incomplete information.

And often, the lessons only become clear much later.

Over the years, my work has taken me through software engineering, data analytics, and technology leadership. Along the way, I’ve come to appreciate that the most interesting challenges are rarely technical problems alone.

They involve people, trade-offs, organizational dynamics, and decisions whose consequences aren’t always immediately visible.

I’m still learning to navigate those challenges.

As I reflect on the decisions that have shaped my career, I’ve realized how valuable it is to document not just what I’ve done, but why I made those choices and what I’ve learned.

That’s why I’ve decided to start writing in public.

I want to create a space to examine the decisions I make, the systems I build and work within, and the lessons I learn—both from what goes well and from what I would approach differently.

Not as a collection of definitive answers, but as a record of thinking, learning, and evolving perspectives.

Perhaps, in sharing those experiences, some of these lessons will help others navigate similar decisions.

How did I decide to move to the United States for work?

Looking back, my decision came down to three questions:

  • Should I stay in Singapore and continue growing my career?
  • Should I travel to Thailand to pursue my passion?
  • Or should I explore the United States for a new adventure?

My employer sponsored my move to the United States on an L-1B visa. My starting salary was approximately USD 60,000, based on converting my Singapore salary to its U.S. equivalent.

I already had five years of data experience, and when I arrived, I realized my salary was lower than what some fresh graduates were earning.

Financially, it wasn’t the obvious choice.

Staying in Singapore would have been the more familiar path. However, I had begun to feel that my career was becoming stale and stagnant.

During my final interview at Facebook, the interviewer explained that the work would revolve around the Asia-Pacific region. It was an exciting opportunity, but I was also drawn to the prospect of experiencing a completely different environment in the United States.

Thailand represented another possibility altogether.

I was passionate about Christian ministry, but I didn’t feel ready to commit to serving full-time. I wasn’t sure I could be an effective testimony at that stage of my life, and I wanted more time to experience God’s realness and grow in my faith.

That left the United States.

I asked myself a simple question:

What’s the worst that could happen?

I could return home with overseas working experience.

Technology was booming, and I believed that international experience would make me desirable to employers in Singapore if things didn’t work out.

I couldn’t predict what would happen, but I believed the downside was manageable.

So, despite the salary not looking particularly attractive, I took the opportunity.

It wasn’t purely logical, nor was it entirely emotional. It was a combination of intuition, curiosity, and a willingness to accept uncertainty.

That’s how I started a new chapter in Florida.

Did I make the right decision?

Financially, things improved considerably over the next four years.

  • First year: USD 60,000
  • Second year: USD 70,000
  • Third year: USD 90,000
  • Fourth year: USD 125,000

My compensation continued to grow, but the opportunities I encountered were arguably more valuable.

As an individual contributor, I worked on two data science projects associated with major campaigns.

One involved building an application to forecast golf tournaments for a campaign valued at USD 1.5 million. Another involved developing a voice assistant for NFL fantasy projections for a campaign valued at USD 1.75 million.

Eventually, I became an engineering manager, leading a team building real-time sports predictions.

Those experiences helped shape my career, but they weren’t all smooth sailing.

During one golf tournament, an application I built became overloaded because demand spiked unexpectedly. I had to scale the infrastructure to 20 extra-large servers to restore service, working through the early hours of the morning.

For the NFL fantasy projections project, I spent long weekends working until 4 a.m. to ensure the application worked as intended.

These were difficult experiences.

They also challenged me to think beyond simply delivering working software. Building something that works is one thing. Building something that remains reliable when people depend on it is another.

Looking back, I gained more than financial rewards or professional recognition.

I gained experience solving problems under pressure, understanding the consequences of engineering decisions, and creating value through the systems I helped build.

Those experiences also shaped me as a technology leader.

But does that mean moving to the United States was unquestionably the right decision?

I’m not sure I can answer that question.

I don’t know what would have happened if I had stayed in Singapore or pursued ministry in Thailand.

Perhaps I would have been equally successful. Perhaps I would have learned entirely different lessons.

What I do know is that the decision opened doors I couldn’t have anticipated when I first made it.

And I’ve come to realize we shouldn’t always judge a decision’s quality solely by its eventual outcome.

Sometimes, making a thoughtful decision with the information available to us is the best we can do.

Why write about these experiences?

One limitation of looking back on our careers is that hindsight makes decisions seem more obvious than they were.

It’s easy to connect the dots after something works out.

It’s much harder to remember the uncertainty, doubts, and assumptions we had at the time.

That’s one reason I want to write more intentionally.

I want to document not only the outcomes of my decisions, but also the thinking behind them.

What alternatives did I consider? What trade-offs did I accept? What assumptions turned out to be wrong? And what might I do differently next time?

I also want to explore the systems that influence those decisions, whether they’re technical architectures, engineering processes, organizational structures, or the habits we develop to navigate everyday life.

Some ideas may stand the test of time. Others may change as I gain new experiences and perspectives.

And that’s part of the value of writing in public.

It gives me a chance to revisit earlier thinking, challenge assumptions, and learn from conversations with others.

What you can expect from this space

My writing will primarily explore three interconnected themes.

Decisions: How I approach career choices, technology investments, leadership challenges, and situations where the answers aren’t always clear.

Systems: The engineering practices, architectures, processes, and frameworks that help us manage complexity and build things that last.

Lessons: What I’ve learned from successes, mistakes, experiments, and experiences that have challenged the way I think.

I don’t expect every article to offer a definitive solution.

Sometimes I’ll share something that worked. Other times I’ll write about something that failed, an experiment I’m undertaking, or a question I’m still trying to answer.

More importantly, I hope to make the reasoning behind those experiences useful to others.

Ten years ago, I couldn’t have predicted where a decision to move halfway around the world would take me.

And ten years from now, I expect I’ll still be learning from the decisions I make today.

Perhaps that’s a good enough reason to start writing them down.

Leave a comment

Your email address will not be published. Required fields are marked *