From Global Systems to Scalable Architectures: Why International Relations is My Greatest Engineering Asset
For years, my world was defined by the complex dynamics of International Relations (IR). Pursuing a Master’s in Diplomatic Studies, I spent my days analyzing macroeconomic interdependencies and global governance. I wanted to influence how the world connects.
However, I eventually hit a wall. While policy has the potential for massive impact, it often moves at a glacial pace. The results are abstract, often taking years to materialize. I realized I craved a different kind of impact: one that was tangible, immediate, and architecturally sound.
The Moment Everything Clicked
That search for clarity led me to entrepreneurship, where I founded an online retail brand. To scale, I had to look "under the hood" of our digital tools.
The first time I designed a working system—a tool that behaved exactly as I architected it—something clicked. Watching different parts of code interact like gears in a complex machine was a revelation." I discovered that software development offered what the political arena couldn't: the ability to solve real problems creatively, with results you can see in real-time."
How Diplomacy Shapes My Engineering
My background in IR didn’t disappear when I became a developer; it evolved into a systems-thinking advantage. Today, I treat software architecture with the same rigor I once applied to diplomatic policy:
-
Strategic Systems Thinking: In IR, you learn how one event ripples through a global network. In Cloud Architecture, this helps me anticipate how a single change in a backend model affects the entire application lifecycle and scalability.
-
Pragmatic Communication: Diplomacy is built on finding common ground. Whether I’m writing technical documentation or discussing API design with stakeholders, I focus on clarity and cross-functional collaboration—translating "Business-speak" into "Dev-speak."
-
Problem-Solving Under Pressure: Diplomatic studies sharpen the ability to analyze high-stakes situations. I translate this into a structured debugging mindset: stay calm, isolate the variable, and find the path to resolution.
Why This Journey Matters
A non-technical background isn’t a limitation—it’s a competitive advantage. It shapes how you think, how you lead, and how you build.
Today, as a Full-Stack Developer and aspiring AI Solution Architect, I specialize in tidy, scalable backend systems and elegant interfaces. My path wasn't linear, but it gave me a unique toolkit: a blend of global awareness and technical precision.
I’ve learned that impact doesn’t always come from institutions. Often, it comes from building the digital tools that solve real problems for real people—one line of code at a time.
