Planet-Scale Global Networking
Working with Microsoft's Azure global network and large-scale cloud infrastructure.
ABOUT DO ENGINEERING
About Dr. Tuan Do
From Networks to Building Technology at Scale
My journey in technology started with something fundamental: how computers communicate.
I began my career as a network engineer at one of Vietnam's largest Internet service providers, working hands-on with Cisco routers, switches, and the infrastructure that connected people to the Internet.
That experience shaped the way I think about technology to this day. Before cloud platforms, modern frameworks, and AI abstracted away much of the complexity, I learned to understand what was happening underneath—how systems communicate, where failures occur, how performance is affected, and why architecture matters.
That curiosity eventually brought me to the United States to continue my education.
I earned a Master's degree in Computer Science from The George Washington University, followed by a PhD in Electrical and Computer Engineering from George Mason University.
But my education didn't stop when I left the university. In technology, learning never really stops.
20 YEARS OF BUILDING REAL TECHNOLOGY
Startups, growing companies, and some of the world's largest technology organizations.
Over the past 20 years, my career has included principal, architecture, engineering leadership, and senior engineering roles at organizations including Microsoft, Amazon, Amwell, POLITICO, ViTel Net, and Global Wireless Solutions.
Global Commerce & Grocery
Building technology supporting pricing and promotions for Amazon's grocery businesses, including Amazon Fresh.
Digital Healthcare
Leading software engineering and architecture for healthcare technology at Amwell.
Telecommunications
Building technology for wireless and telecommunications systems.
Digital Media
Engineering software in the fast-moving world of digital media at POLITICO.
Startups & Entrepreneurship
Taking products from an idea to MVP, production, and real customers—where resources are limited, speed matters, and every technology decision involves a tradeoff.
This experience has allowed me to see engineering from very different perspectives:
STARTUPMVPPRODUCTIONENTERPRISEGLOBAL SCALE
Technology changes.
Engineering fundamentals don't.
WHY I STARTED DO
Two passions: technology and education.
Throughout my career, I've had two passions: building technology and helping people understand technology.
I believe education is one of the best investments we can make in ourselves—and some of the deepest learning happens when we stop simply studying something and start doing it.
You can read about databases. Watch a video about networking. Take a course on cloud computing. Today, you can even ask AI to generate an entire application.
But building something real forces you to ask different questions:
01Where should the data live?
02How does a request travel from a user's phone to our application?
03How do we protect our users' information?
04Why is this API slow?
05What happens when something fails?
06What happens when 100 users become 100,000?
07Should we build this ourselves or use an existing service?
08What are we trading off when we make this decision?
That's when concepts stop being abstract and start becoming real engineering knowledge.
AI makes this philosophy even more important.
AI has made building software faster and more accessible than at any other point in my career. That's an extraordinary opportunity—but being able to generate code is not the same as understanding the system you're building.
Throughout my career, I've worked on technology ranging from startup MVPs to large-scale global systems. The scale changes. The tools change. The architecture changes.
The fundamentals remain.
Architecture. Networking. Security. Data.
Performance. Reliability. Cost. Tradeoffs.
That's where DO began.
Whether you're a founder building an MVP, a professional developing deeper technical skills, a college student preparing for an engineering career, or a high school student building your first real product, I want you to leave with more than working software.
I want you to understand what we built, why we built it that way, and the tradeoffs behind the decisions.
Because the goal isn't simply to learn another language, framework, or AI tool.
It's to learn how engineers think.
Sharing what I wish I knew earlier.
There is another reason I started DO.
Looking back over my career, there are many things I wish someone had told me when I was younger—not just about technology, but about building a career.
How do you choose what to learn? How do you find your first opportunity? What makes a good engineer beyond writing code? When should you specialize, and when should you explore? How do you communicate your ideas, work with experienced engineers, learn from failure, and make decisions when there isn't a clear right answer?
These lessons are rarely taught in a classroom, yet they can have an enormous impact on a career.
I want DO to be a place where high school students, college students, and young professionals can benefit not only from technical mentorship, but also from the perspective that comes from years of working across startups, growing companies, and large technology organizations.
I won't have all the answers, and everyone's path will be different. But if I can share some of the lessons, mistakes, and perspectives I've gained along the way, perhaps I can help someone earlier in their journey make better-informed decisions about their own.
It's the kind of guidance I wish I had when I was starting mine.
That's why I created DO—to bring together three things I care deeply about:
Building real technology.
Helping people understand technology.
Sharing what I've learned with the next generation.
BUILD. LEARN. LAUNCH.
Don't just learn.
DO.
Build something real. Understand how it works.